wulfbindewald

sgssaa off (Nvidiainpector set to Nvidia default) and AA 4X would solve this appearance issue. Thanks for Your help!
 
But due to unacceptable shimmering on I will continue to use as a compromise 8XCSAA again plus proven Nvidiainspector settings, but to reduce the ground vehicle settings from 10 to 5%. One thing I´ll check is to reduce from 4 to 2 SGSS.....as a further compromise.
 
Topic closed so far.

UPDATE:
The prob has been solved.
I disabled and enabled again the Convert Effects in the DX10 Controller Lights/Effects box. No further adjustments e.g. LightField option necessary. The reason for partly not displayed lights came from still unconverted files (reproducible). I wonder why the fixer tool has not alerted this although I have often used the DX10 controller.
 
Nevertheless I´m happy and learned a bit more about the DX10 fixer complexity and the mighty FSX SDK tool.
 
Wulf

I have the fx_hugh texture in my directory. I could sort out the transperancy problem by temp. deactivating the texture file.
In the corresponding Orbx forum this issue has been clarified as the dev has provided a link to a couple of missing files in the Effects folder.
 
Wulf

Hi Steve,
 
although I have not changed anything in the debug menu now the VC shadows are present and well displayed. So I am confused why the VC shadows now work properly and I am not able to reproduce.
So I completly de- and reinstalled V2.4 again and the problem (no VC shadow displayed, see pic 2) was there again although HD shadows ticked. Are the shaders well activated from the first start?
After playing within shadows menu all is fine again.
No visible difference between HD applies to  "Airliner(30)" or "All(0)".
 
Debug menu: There was no recognizable difference between shadows 2 to 5 with exception of shadow edge quality (saw cut edges). HD exterior ticked or unticked does not matter.
 
For me this issue is resolved.
 
For info: The used aircraft is the freeware project Airbus A320 
 
Wulf