December 31, 201213 yr I posted an earlier question about shimmering and Land Detail Textures and one response indicated that the problem I was showing was not DX10 shimmering. Here is a higher resolution screen grab of a flight over Harbor Island between Elliott Bay and KBFI. FSX is running with ORBX Pacific Northwest scenery, GEX, UTX, REX. FSX generates 23 - 28 FPS as shown here. - Does this picture show "shimmering" or is this some other DX10 problem? The effect is only noticed in the tiles immediately under the aircraft. All other textures are sharp and clear. I see no problems with fences, runways, or clouds. FSX is running DX10 with Land Detail Textures checked on - removing the check mark makes the illustrated problem go away Here are the other graphics settings: [GRAPHICS] HIGHMEMFIX=1 // KOSTAS 8/13/12 D3D10=1 TEXTURE_MAX_LOAD=1024 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=0 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=0 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 TEXTURE_BANDWIDTH_MULT=40 UPPER_FRAMERATE_LIMIT=30 WideViewAspect=True RUNWAY_LIGHTS_SURFACE_SCALAR=.3 //adjust values to suit your scale RUNWAY_LIGHTS_VASI_SCALAR=.3 RUNWAY_LIGHTS_APPROACH_SCALAR=.3 RUNWAY_LIGHTS_STROBE_SCALAR=.3 [Main] FIBER_FRAME_TIME_FRACTION=0.66 // ADDED 8/13/12 Default is 0.33 [TERRAIN] LOD_RADIUS=4.500000 MESH_COMPLEXITY=97 MESH_RESOLUTION=24 TEXTURE_RESOLUTION=27 AUTOGEN_DENSITY=2 DETAIL_TEXTURE=1 WATER_EFFECTS=5 AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 31, 201213 yr This is the "black dots" issue and not the shimmering one. I have ATI HD6850 and I had the same problem until in the Catalyst Control Center (CCC) I turn mipmaps to OFF and the black dots disappear! I hope this fix work for you too :smile: Stratos Moschos
December 31, 201213 yr Could you post your complete cfg file? The first thing I see is that you are not using a bufferpool setting of any kind and second you FFTF is way too high. Jamie Moses Jamie Moses
December 31, 201213 yr Yup Mipmaps, and like Jamie says - BP is waaaaaay too high.. i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
December 31, 201213 yr Author "The first thing I see is that you are not using a bufferpool setting of any kind and second you FFTF is way too high." I changed FFTF to 0.33 then 0.22 and it makes NO difference in the image I have done a lot of experiments with BP on/off and various values in between. Using NO Buffer Pools seems to give the best frame rate with no loss of image quality on MY particular system. I did turn BP back on and it makes no difference in the image. "I turn mipmaps to OFF and the black dots disappear!" "Yup Mipmaps, and like Jamie says - BP is waaaaaay too high." HOW do change/manipulate Mipmaps? I find nothing in nVidia Inspector regarding Mipmaps Is there some obscure fsx.cfg control line for Mipmaps? e.g. TEXTURE_SIZE_EXP ? AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 31, 201213 yr Try this [bufferPools] UsePools=0 in graphics section and try.10 for FFTF. This works very well with my setup. Also, What are your scenery settings,and are you running high traffic settings? We could help out more if we could see your complete cfg file. Hope this helps. Jamie Moses Jamie Moses
December 31, 201213 yr From what I understand, you are never supposed to use DX10 in FSX. It is a preview version only. Please see this post here: http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/ Kevin Witt
December 31, 201213 yr Author Here is a screen grab with DX10/Detailed Land Textures checked on and the associated settings; Following is the fsx.cfg that was used to start FSX: [bUFFERPOOLS] UsePools=0 [GRAPHICS] HIGHMEMFIX=1 // KOSTAS 8/13/12 D3D10=1 TEXTURE_MAX_LOAD=2048 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=0 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=0 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 [sOUND] AmbientUIMusicVolume=-6.000000 SOUND_FADER1=0.750000 SOUND_FADER2=0.730000 SOUND_FADER3=0.500000 SOUND_FADER4=0.960000 AmbientUIMusic=FSX01 PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03} VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03} SOUND=1 SOUND_QUALITY=2 SOUND_LOD=0 UISound=0 AmbientUI=0 [Display] ChangeTime=4.000000 TransitionTime=4.000000 ActiveWindowTitleTextColor=255,255,255 ActiveWindowTitleBackGroundColor=0,28,140,64 NonActiveWindowTitleTextColor=255,255,255 NonActiveWindowTitleBackGroundColor=24,33,87,64 InfoUpperRightTextColor=255,0,0 InfoUpperRightBackGroundColor=0,0,0,0 InfoLowerLeftTextColor=255,255,255 InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoBrakesEnable=True InfoParkingBrakesEnable=True InfoPauseEnable=True InfoSlewEnable=True InfoStallEnable=True InfoOverspeedEnable=True BLOOM_EFFECTS=0 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=40 UPPER_FRAMERATE_LIMIT=30 WideViewAspect=True RUNWAY_LIGHTS_SURFACE_SCALAR=.3 //adjust values to suit your scale RUNWAY_LIGHTS_VASI_SCALAR=.3 RUNWAY_LIGHTS_APPROACH_SCALAR=.3 RUNWAY_LIGHTS_STROBE_SCALAR=.3 [Main] //FIBER_FRAME_TIME_FRACTION=0.66 // ADDED 8/13/12 Default is 0.33 FIBER_FRAME_TIME_FRACTION=0.1 // reset 12/31/11 per AVSIM advice User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc ProcSpeed=11493 PerfBucket=7 Location=-4,-4,1684,1054,\\.\DISPLAY1 Maximized=2 HideMenuNormal=0 HideMenuFullscreen=1 [PANELS] IMAGE_QUALITY=1 DEFAULT_VIEW=0 QUICKTIPS=1 PANEL_OPACITY=100 PANEL_MASKING=1 PANEL_STRETCHING=1 UNITS_OF_MEASURE=0 [Weather] WindshieldPrecipitationEffects=1 MinGustTime=10 MaxGustTime=500 MinGustRampSpeed=1 MaxGustRampSpeed=200 MinVarTime=5 MaxVarTime=50 MinVarRampSpeed=10 MaxVarRampSpeed=75 TurbulenceScale=1.000000 WeatherServerAddress=fs2k.zone.com WeatherServerPort=80 WeatherGraphDataInDialog=0 AdjustForMagVarInDialog=1 DynamicWeather=0 DownloadWindsAloft=0 DisableTurbulence=0 CLOUD_DRAW_DISTANCE=6 DETAILED_CLOUDS=1 CLOUD_COVERAGE_DENSITY=7 THERMAL_VISUALS=0 [DISPLAY.Device.NVIDIA GeForce 8800 GTS.0] Mode=1680x1050x32 TriLinear=1 [AccelerationPack] ControlsFirstRun=0 HomePageFirstRun=0 [CONTROLS] Controls_Default=Standard Controls_Current=Standard KBDAIL=64 KBDELEV=64 KBDRUD=64 [TextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 [TextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 GForce=1,3 FuelPercentage=1,4 [TextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 FrameRate=2,1 LockedFrameRate=2,2 GForce=2,3 FuelPercentage=2,4 [slewTextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 [slewTextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 [slewTextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 FrameRate=2,1 LockedFrameRate=2,2 Missing Trusted Section [DynamicHeadMovement] LonAccelOnHeadLon=-0.020000 LonAccelOnHeadPitch=-0.010000 RollAccelOnHeadLat=0.010000 YawAccelOnHeadLat=-0.100000 RollAccelOnHeadRoll=0.100000 MaxHeadAngle=5.000000 MaxHeadOffset=0.300000 HeadMoveTimeConstant=1.000000 [VirtualCopilot] VirtualCopilotActive=1 [DISPLAY.Device.NVIDIA GeForce 8800 GTS.1] Mode=1280x1024x32 [uSERINTERFACE] OpenATCOnCreate=0 PageID=1 ShowAllACPaintSchemes=1 SelectAircraftManufacturer=All SelectAircraftPublisher=All SelectAircraftType=All SHOW_MISSION_CAPTIONS=0 PAUSE_ON_LOST_FOCUS=0 PROMPT_ON_EXIT=1 Map_Orientation=2 DisplayFuelAsWeight=0 SITUATION=c:\users\administrator\documents\flight simulator x files\Benchmark 2 Baron 58 West Point KBFI KSEA S50.FLT [MAPVIEW_MAP] SHOW_AIRPORTS=1 SHOW_VORS=1 SHOW_NDBS=1 SHOW_APPROACHES=1 SHOW_INTERSECTIONS=1 SHOW_VICTOR=0 SHOW_JET=0 SHOW_AIRSPACE=0 SHOW_FLIGHTPLAN=0 SHOW_WEATHERSTATIONS=0 SHOW_WEATHERSYSTEMS=0 SHOW_DATATAGS=0 SHOW_TERRAIN=1 show_flight_history=0 [ATC] ShowATCText=1 COMM_MSG_NONE_COLOR=FFFFFFFF COMM_MSG_ATC_USER_COLOR=FFB6FFB6 COMM_MSG_USER_ATC_COLOR=FFFFD21B COMM_MSG_ATC_AI_COLOR=FF00FF00 COMM_MSG_AI_ATC_COLOR=FFFF7840 AutoOpenAirTrafficWindow=1 UsePilotVoice=1 PilotVoice=0 [PointOfInterestSystem] CycleSetting=0 [sCENERY] LENSFLARE=0 DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=5 [TrafficManager] AirlineDensity=0 GADensity=0 FreewayDensity=0 ShipsAndFerriesDensity=0 LeisureBoatsDensity=2 IFROnly=0 AIRPORT_SCENERY_DENSITY=0 [TERRAIN] LOD_RADIUS=4.500000 MESH_COMPLEXITY=97 MESH_RESOLUTION=24 TEXTURE_RESOLUTION=27 AUTOGEN_DENSITY=3 DETAIL_TEXTURE=1 WATER_EFFECTS=5 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=2500 // Dec 31 2012 fpr TreeX 2.0 addon [AContain] ShowLabels=1 ShowUserLabel=0 ShowLabelManufacturer=1 ShowLabelModel=1 ShowLabelTailNumber=0 ShowLabelDistance=1 ShowLabelAltitude=1 ShowLabelAirline=0 ShowLabelAirlineAndFlightNumber=0 ShowLabelFlightPlan=0 ShowLabelContainerId=0 ShowLabelAirspeed=0 ShowLabelHeading=0 LabelDelay=1000 LabelColor=FFFF0000 [iNTERNATIONAL] ASLAT=2 ASLON=1 MEASURE=0 [REALISM] PFactor=1.000000 Torque=1.000000 GyroEffect=1.000000 CrashTolerance=0.980000 General=1.000000 UnlimitedFuel=False AllowEngineDamage=True TrueAirspeed=False AutoCoord=False RealMixture=False StressDamage=True GEffect=True ManualLights=True GyroDrift=False CrashWithDyn=True CrashDetection=True AutoTrim=False [sIM] SYSCLOCK=1 [sTARTUP] DEMO=0 SHOW_OPENING_SCREEN=0 STARTUP_DEMO= LoadWindow=1 [FACILITIES] COUNTRY= STATE= CITY= GTL_BUTTON=1513 [Misc] Com_Rate=7 [DISPLAY.Device.] Mode=1024x720x32 Disable=1 Filter=0 Dither=0 MipMap=0 Fog=0 FullScreenFiltering=0 VolShadow=0 SoftShadow=0 AnimWater=0 Water20=0 VolTexture=0 TnL=0 DXTn=0 TextureForce=0 PanelAsTexture=0 TEXBEM=0 UseShaders=0 TableFog=0 Shader20Plus=0 [FlightPlanMap] LineWidth=2 SHOW_AIRPORTS=1 SHOW_VORS=0 SHOW_NDBS=0 SHOW_APPROACHES=1 SHOW_INTERSECTIONS=1 SHOW_VICTOR=0 SHOW_JET=0 SHOW_AIRSPACE=0 SHOW_FLIGHTPLAN=1 SHOW_WEATHERSTATIONS=0 SHOW_WEATHERSYSTEMS=0 SHOW_DATATAGS=0 SHOW_TERRAIN=1 show_waypoints=1 show_airways=1 show_markers=1 show_volume_boundaries=0 show_ac_twr=1 [DISPLAY.Device.NVIDIA GeForce 8800 GTS.0.0] Mode=1680x1050x32 Anisotropic=1 AntiAlias=1 [DISPLAY.Device.NVIDIA GeForce 8800 GTS.0.1] Mode=1024x768x32 [RWW_WEATHER_MAP] SHOW_AIRPORTS=0 SHOW_VORS=0 SHOW_NDBS=0 SHOW_APPROACHES=0 SHOW_INTERSECTIONS=0 SHOW_VICTOR=0 SHOW_JET=0 SHOW_AIRSPACE=0 SHOW_FLIGHTPLAN=1 SHOW_WEATHERSTATIONS=1 SHOW_WEATHERSYSTEMS=1 SHOW_DATATAGS=1 SHOW_TERRAIN=1 [WeatherMap] SHOW_AIRPORTS=0 SHOW_VORS=0 SHOW_NDBS=0 SHOW_APPROACHES=0 SHOW_INTERSECTIONS=0 SHOW_VICTOR=0 SHOW_JET=0 SHOW_AIRSPACE=0 SHOW_FLIGHTPLAN=1 SHOW_WEATHERSTATIONS=1 SHOW_WEATHERSYSTEMS=1 SHOW_DATATAGS=1 SHOW_TERRAIN=1 [MULTIPLAYER] condAccoutPassword=0 VoiceVolume=1.920000 Edited January 1, 201313 yr by firehawk44 Image far exceeds 400KB limit. AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 31, 201213 yr Ok, wow, First I would rename your config and save it, then delete fsx.cfg ,launch FSX and it will rebuild it. Try adding one tweak at the time. Also your display settings are way too high for your setup. Lets us know how this works out for you. Jamie Moses Jamie Moses
December 31, 201213 yr From what I understand, you are never supposed to use DX10 in FSX. It is a preview version only. Please see this post here: http://forum.avsim.n...f-all-settings/ Kev - that was almost two years ago!! I think you may not understand what Steve is actually doing: Steve has been actively researching - and repairing the FSX shader system, with the intention of alleviating the left-over DX10 issues. These are the FSX High-Level Shader Language files which ACES were unable - through time constraints or other reasons - to complete in time for the release of SP2. The initiative, enthusiasm and work output which Stevejp - on his own - has displayed in taking on the job of actually finishing that development, is an incredible achievement. There is no such thing as "never intended as a finished product" - they were simply left in that state, likely pegged as a low-priority item by Project, Business and Marketing management. It is one thing to 'better' a product with an improvement, or to fix a known issue - but it is quite another to knowingly allow a product to market, and label something like DX10 as a "Preview" with that "Preview " programming barely functional, and not at all representing a true preview of "what's coming with DX10". Steve's work-in-progess, currently at version 3.2.2, has been successful to the degree that I feel that a wholesale move for many "simmers" - to DX10 is now a practicality. There are dozens - if not several hundred FSX users - and growing daily, who have very successfully completed this transition, and I believe it has somewhat created a new and exciting experience for that avid flight-simmer: an alternate to P3D, and at the same time has created an opportunity for forward-thinking commercial FSX developers to take a unique marketing advantage, with a leading role in furthering this change by virtue of their in-depth knowledge of the FSX shader technology. you are never supposed to use DX10 in FSX. True - we used to get from A to B on horseback, too. All the Best, and have a Happy New Year! Paul J. i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
December 31, 201213 yr Kev - that was almost two years ago!! I think you may not understand what Steve is actually doing: Steve has been actively researching - and repairing the FSX shader system, with the intention of alleviating the left-over DX10 issues. These are the FSX High-Level Shader Language files which ACES were unable - through time constraints or other reasons - to complete in time for the release of SP2. The initiative, enthusiasm and work output which Stevejp - on his own - has displayed in taking on the job of actually finishing that development, is an incredible achievement. There is no such thing as "never intended as a finished product" - they were simply left in that state, likely pegged as a low-priority item by Project, Business and Marketing management. It is one thing to 'better' a product with an improvement, or to fix a known issue - but it is quite another to knowingly allow a product to market, and label something like DX10 as a "Preview" with that "Preview " programming barely functional, and not at all representing a true preview of "what's coming with DX10". Steve's work-in-progess, currently at version 3.2.2, has been successful to the degree that I feel that a wholesale move for many "simmers" - to DX10 is now a practicality. There are dozens - if not several hundred FSX users - and growing daily, who have very successfully completed this transition, and I believe it has somewhat created a new and exciting experience for that avid flight-simmer: an alternate to P3D, and at the same time has created an opportunity for forward-thinking commercial FSX developers to take a unique marketing advantage, with a leading role in furthering this change by virtue of their in-depth knowledge of the FSX shader technology. True - we used to get from A to B on horseback, too. All the Best, and have a Happy New Year! Paul J. :LMAO: :LMAO: Jamie Moses
December 31, 201213 yr To TacomaSailor: You're running an i5-750 at 3.4 gig, 4-gig ram and an 8800 w/ 640 MB of video ram: your settings would be appropriate for a 4.4-gig proc, 6 gig ram an 460Ti. Your Inspector SGSS should take care of the "sugary look" As Jamie suggests - roll back almost all of your settings - all are very high: start with something like these:- [GRAPHICS] TEXTURE_MAX_LOAD=1024 [Weather] DETAILED_CLOUDS=0 CLOUD_DRAW_DISTANCE=3 or minimum CLOUD_COVERAGE_DENSITY=4 or minimum [TERRAIN] LOD_RADIUS=3.500000 Set all Terrain to minimum MESH_COMPLEXITY= MESH_RESOLUTION= TEXTURE_RESOLUTION= AUTOGEN_DENSITY=3 DETAIL_TEXTURE=1 WATER_EFFECTS=3 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376 [sCENERY] IMAGE_COMPLEXITY=3 I think you're ignoring the How-to, and just guessing at your settings. If you want to get the best from DX10 - making it better than DX9 - we have a fair amount of work to do - the least of them is cleaning up the pc's un-needed processes. Word Not Allowed's guide certainly works for DX9, but there ar lots of folks with DX9 problems, too. What we have done here is tested a lot of settings, and the successful guys here know what needs to be done. We can also get into alpha and mipmap checking too, to make the sim even smoother. Read the doc again, do like Jamie and I have suggested, post your Inspector settings here, and then we'll talk some more. Oh - yeah - and have a Happy and Prosperous New Year!!!! All the Best, pj i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
December 31, 201213 yr Author Here is a screen grab with every FSX scenery option set to OFF/0/lowest possible setting except for Texture Resolution=5m I renamed the fsx.cfg so that FSX would load a new default .cfg As you can see - the problem is exactly the same as with my customized settings Leaving Land Detail Textures checked on and setting Texture Resolution to off (slider furthest to the left) makes the shimmering image go away - I guess 'cause no textures are loaded I have tried every possible nVidia inspector setting for Antialiasing and Aniostropic processing and none of them diminish the shimmering Again - my basic question is - What problem does the "shimmering" image represent? There are no other image quality problems - no blurries, no stuttering, no tearing, and no other visual artifacts when I use my customized "High" settings. While running FSX with my customized settings on the displayed flight path I note the following: Frame rate is 23 - 30 - limited to 30 and never drops below 23 All four cores run at over 90% busy the GPU runs at about 65% busy and 75% memory NO OOM problems FSX VAS stabilizes at about 1.8GB The free memory list for Windows is fairly high Physical paging rates are low I have eliminated EVERY process on the system that is not necessary to run FSX Edited January 1, 201313 yr by firehawk44 Image removed. Exceeds 1600W and 400KB limits AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
December 31, 201213 yr Here is the answer.. i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
January 1, 201313 yr Author Paul J - thanks for the suggestions - I have tried to exactly follow your recommended fsx.cfg (earlier post by you) and the nVidia Inspector settings shown under your "current config" I have attached some images that show the results - still shimmering (? is that the correct term) in the tiles closest to the aircraft Again - my basic question is - What problem does the "shimmering" image represent? What causes shimmering in DX10? I am pretty good with hardware and system software so I would appreciate as detailed an answer as anyone can provide. Many google searches find lots of ideas on how to fix DX10 shimmering but no details about the cause. The DX10 shimmer disappeared for several minutes this afternoon running the same saved flight I use to generate the image shown here. When I changed nVidia Inspector AntiAliasing - Transparency SS to 8XSGSS I still saw the problem. But when I changed water effects in FSX to 2.Max ALL shimmering vanished. I was able to continue the flight with an fps of about 22 and no other visual anomalies. Then I changed Global Texture Resolution to Very Dense and the shimmering reappeared. Now, after many attempts to duplicate the shimmering disappearance - it is still always there. Does the disappearance / reappearance of shimmering with 8xSGSS and changes to water effects mean anything useful. Here is the nVidia Inspector settings for the images above - I hit Reply when I meant to hit Preview Edited January 1, 201313 yr by firehawk44 Image removed. Exceeds 1600W and 400KB limits. AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
Create an account or sign in to comment