Can someone tell me if the LM fix listed below in P3Dv3.3  is meant to solve the "shimmering/flickering" issue many of us see in Orbx scenery particularly in add on airports on buildings, towers and other objects? I have been able to significantly reduce this effect by setting 4X SGSS in Inspector as many have done  but it really over taxes my current GPU.

Also I have read the issue isn't really apparent if you have a 4k monitor (not sure if this is true) but I do not run a 4k monitor.

I seem to recall Rob A. saying something about LM working on this and again was wondering if this is the fix for this annoying objects shimmering issue. Thanks in advance!

• Fixed custom z bias scenery flickering issues including runways and runway markings
  

OK.. please don't beat me up. I am getting conflicting message on EZDOK

 

I want to uninstall client and reinstall the client only for V3.3). Would updating the client only break EZDOK?

 

YEs or No?

Got a source for this?

 

Cheers, Rob.

Hi Rob, It's being called the Anniversary Update, due for launch 29 July, with release to Insider Ring on 15 July for final beta. My source is the Windows 10 Forums, excellent and very well managed and moderated source for all things related to Windows 10. This is where all the beta testers seems to be camping out also.

 

 

Can someone tell me if the LM fix listed below in P3Dv3.3 is meant to solve the "shimmering/flickering" issue many of us see in Orbx scenery particularly in add on airports on buildings, towers and other objects?

I would think not, The LM fix would solve the default z fighting on the default runways and airport buildings, the Orbx issues come from re using old FSX textures for DX9 and porting them over without resolving the flickering or z fighting, problem is we just accept them without making a noise about them, other developers resolve them easily enough, All the z fighting with Orbx textures are repetitive at all the Airports they do and all on the same items, baggage trolleys, aircraft stairs, inside hangars, static cars and aircraft etc, see the pattern, it`s the library objects that are shared that suffer and need a revamp in my opinion, some say reduce AA helps, increase it, turn receive shadows on for objects, fly at dawn/dusk.

OK.. please don't beat me up. I am getting conflicting message on EZDOK

 

I want to uninstall client and reinstall the client only for V3.3). Would updating the client only break EZDOK?

 

YEs or No?

 

I've updated to v3.3 and am not experiencing any issues whatsoever with EZDOK. 

 

Obviously reinstall the client at your own risk, however I'm fairly confident that EZDOK will continue to fully function.  :smile:

So to get the latest 3.3 from 3.2 for those that want the bug fixes like the 3rd party menu fix, cloud rendering fix, etc.. one just needs to get the "client" and this will not mess up any scenery installed in the main folder like Orbx Global products like Global Textures, Vector, etc... or 3rd party stuff such as FSDT scenery, PMDG aircraft, etc... Sorry for what some may classify as a dumb question but this is my first time updating P3D and don't want to screw it up.

I know myself and one other chap that would sure appreciate any help with this question. Thank you

I know myself and one other chap that would sure appreciate any help with this question. Thank you

 

I believe the answer is 'yes', to your question. You understand it correctly. 

 

I was previously running v3.0 and updated to v3.3 earlier today (err, yesterday, now). At any rate, I uninstalled "Prepar3D v3.x (Professional/Academic) Client". I also uninstalled "Prepar3D v3.x Content" (however this latter step is optional).

 

 

I then downloaded the Install_Client.msi from Lockheed's website, along with cont1.cab and Install_Content.msi. Again, the latter two would not be required in your situation, as far as I know.

 

You'd then run the installer for the client and you should be all squared away! 

So to get the latest 3.3 from 3.2 for those that want the bug fixes like the 3rd party menu fix, cloud rendering fix, etc.. one just needs to get the "client" and this will not mess up any scenery installed in the main folder like Orbx Global products like Global Textures, Vector, etc... or 3rd party stuff such as FSDT scenery, PMDG aircraft, etc... Sorry for what some may classify as a dumb question but this is my first time updating P3D and don't want to screw it up.

 

Yes,  You only need the Client Update to bring you officially to Version 3.3.3.  The Client update will have all the menu fixes and so on.  The Client update will Not effect anything in Scenery or or Airplanes.  

 

So what will it effect with a Client update Only ?  Just from the Add On's i have 

 

Active Sky Next is waiting for an update.  They are very quick to update

 

Gtn 750 is waiting for an update.  Also pretty quick to Update 

 

Rex_Texture Direct and  "Cloud Sizing algorithm"  when you select this option it will Modify the Cloud.fx Entry in your ShadersHLSL folder to achieve this. After the Client Update Just select this option again (Just to be on the Safe side)  

 

EZdok is working perfect (For me anyway) 

 

This is from the last Update but still relevant now (Questions and Answers)  http://www.avsim.com/topic/484945-how-do-i-update-prepar3d-v3-using-the-new-installers/?p=3412567

[improved cloud performance]

 

Has anyone confirmed yet ?

Does this fix the OVC cloud performance issue when define volumize is enabled in cloud.fx ?

Does this fix the cloud performance issue when there is more than one visibility layer enabled ?

 

meanwhile, patiently awaiting an update of both RSP and PTA

Don't see any compelling reason to update at the moment, i think perhaps i'll wait a few weeks.

 

+1

Hello,

about the VAS, is there any changes with this latest version ?

Thank you.

There are rumors on other forums that VAS usage increased nastily (the guy tested over FVFR scenery).

Anyone confirms ?

light scattering .. nowhere :(

Installed the latest update this morning, joystick still will not work no matter what I do, can't believe there's no fix for this.

I've updated to v3.3 and am not experiencing any issues whatsoever with EZDOK. 

 

Thank you. Once F1 has got their GTN 750 update.. I'll upgrade