What is z-fighting Rob?

 

It's where two or more items (object or simple texture plane) share the same space in the virtual world and they will contend to be seen which causes a flickering.  It's a precision issue, but to deal with it the z-bias can be set to identify correct order of display.  Another trick is to slightly offset the two objects.

 

 In P3D (different from FSX ... at least according to the P3D SDK) there are z-bias settings that need to be made in 3DSMax in order for them to work well in P3D.  But z-fighting can also be related to a driver problem.  Here is excerpt from SDK docs:

 

 

Cheers, Rob.

I have noticed some texture flickering in a few of my sceneries - just enough to be annoying.  Yesterday when doing a flight over the Alps, I noticed flickering over the mountains.  

 

While I don't really understand what you have posted above Rob, is there a remedy for these flickering issues which one could apply more generally?

 

 

is there a remedy for these flickering issues which one could apply more generally?

 

Unfortunately there are many things that can cause flickers

1.  3D model/texturing issue (needs to be resolved by developer)

2.  Drivers (needs to be resolved by nVidia/AMD)

3.  Shadow map quality (if you have shadows enabled in their various flavors)

4.  3rd party products changing clip mode on the camera (I know EzDok does this and needs to be set back to normal)

5.  could also be a compatibility conflict (LM have fixed a z-bias issue in the past) in P3D  (i.e. using FSX models in P3D)

 

Sorry, I don't have a remedy ... but you might want to take a look at #4 if you're an EzDok user.

 

Cheers, Rob.

So is Aerosoft Split working for most of you in P3D?

 

Was going to purchase as am flying out there with friends in September and want to familiarize myself with the layout/approach etc.

Very hi VAS is reported could Jim or any else have a look to see what VAS level is like when starting at Split and hanging around a bit. Would like to see if you guys get the same?

 

Think I might have wasted £20 :(

VAS with my settings after 2 full 360 VC and exterior pans is about 1.1 GB free.

 

Testing out lights and they seem fine to me ... a little too bright at gate/terminal.

 

Another quick video at night:

 

 

Cheers, Rob.

 

4.  3rd party products changing clip mode on the camera (I know EzDok does this and needs to be set back to normal)

 

 

There might be another conflict here but maybe a minor. If one flies helicopters with wideview aspect enabled and the clipmode set from minimum to normal there will be a scenery/texture bleed through below the helicopter. So now the choice is ours z-fighting or bleed through :S

 

BTW after installing Split X v1.1 the APController quit unexpected. Loaded the PMDG NGX and all sounds were working. Nevertheless having 15 frames and every 1-2 having 10 second freezes in the NGX makes it a show stopper. But that is different prob. 

 

Afterall Split X is great i like it a lot. Got my rating for Split in january as it is a CAT C airport and the visual database of our full flight sim does not look even close to Aerosofts scenery :S

Thanks Rob

 

Just did this on works PC with FSX

 

Used Process explorer on the PMDG NG rwy 5 with no airport installed, in the VC VAS was 1265 and after going though all views VAS was 1401

 

Re-installed Split X

Rwy 5 PMDG NG in VC VAS was 2226 and after all view 2467, so the airport seems to use 1gb of VAS, seems a lot for a small airport imo.

Thanks Rob.  

 

I do use EZDOK so will check this option out.

A 700 MB VAS footprint is unusual already ('Mega Airports' like AS Dublin X and 'airport surroundings extensively modelled' like AS Thessaloniki X fit that - already expensive - bill). 

 

1.000 MB VAS would be - even worse - a totally different ballpark ...  

I think it's time for developers to even more seriously start thinking about how to minimize the VAS footprint and realize users will normally not only use their product but rather use it in combination with other products that also use VAS.

 

If they don't we will end up with lots of amazing looking airports we won't be able to use but only look at.

If they don't we will end up with lots of amazing looking airports we won't be able to use but only look at.

 

+1

Couldn't agree more, Richard. For quite some time I've been thinking the same thing. It is getting to be a real problem.

If they don't we will end up with lots of amazing looking airports we won't be able to use but only look at.

 

That list already has many airports on it, and sadly, it seems to grow with almost every new release now.

 

Cheers,

 

Jerome

A guy has posted up a lot of bugs and gif's showing the bugs in P3D

 

VAS 1gb for a small airport. Come on!!!

 

What a great shame was really looking forward to this and being aerosoft no refunds for a product that is atm poor,

 

Did not use the new tech as they said it would, use's far to much VAS and has a lot of bugs with shadows and lighting.

 

Very disappointing.