July 3, 201312 yr Just chiming in here Gary since you mention the problem also exists for you under FSGRW. I have not noticed the effect you describe at all, unlike AS 6.5, in FSGRW. Now I have three monitors (TripleHead2Go) and any effect would be magnified (or disguised?) by that real estate. All things considered I think it is your computer spec/FS9 settings at fault ... likely culprit being the beta PFPX you use. :rolleyes: Lucky man.
July 9, 201312 yr Author My entry looks: [DISPLAY.Device.AMD Radeon HD 6570.0] Mode=1280x1024x32 MipBias=5 PanelAsTexture=0 Note: I use FS2004 in windowed mode exclusively. Mine looks: [DISPLAY.Device.NVIDIA GeForce GTX 285.0] Mode=1600x1200x32 PanelAsTexture=0 I always use FS9 full screen. That is how mine looked too. Windowed mode for Vatsim. :wacko: Here is my current fs9.cfg. Where would you suggest trying it again? [DISPLAY.Device.NVIDIA GeForce 9800 GTX/9800 GTX+.0] Mode=1680x1050x32 TriLinear=1 TextureAGP=0 MipBias=6 [DISPLAY] UPPER_FRAMERATE_LIMIT=0 TEXTURE_BANDWIDTH_MULT=120 RUNWAY_LIGHTS_SURFACE_SCALAR=1.2 RUNWAY_LIGHTS_VASI_SCALAR=1.0 RUNWAY_LIGHTS_APPROACH_SCALAR=1.0 RUNWAY_LIGHTS_STROBE_SCALAR=1.5 [TERRAIN] TERRAIN_ERROR_FACTOR=25.000000 TERRAIN_MIN_DEM_AREA=10.000000 TERRAIN_MAX_DEM_AREA=100.000000 TERRAIN_MAX_VERTEX_LEVEL=19 TERRAIN_TEXTURE_SIZE_EXP=8 TERRAIN_AUTOGEN_DENSITY=4 TERRAIN_USE_GRADIENT_MAP=1 TERRAIN_EXTENDED_TEXTURES=1 TERRAIN_DEFAULT_RADIUS=9.500000 TERRAIN_EXTENDED_RADIUS=9.000000 TERRAIN_EXTENDED_LEVELS=1 All things considered I think it is your computer spec/FS9 settings at fault Not sure I follow, care to ellaborate? I had this issue on my old rig as well as my new one. My new rig is a fresh install of everything (I did copy my old LDS 767 folder over after installing the LDS 767 fresh). Had I not had this issue on my old fs computer (that is now my work computer), I would agree but something is wonky here. I never noticed it before Feb 2012 but then had to do a fresh install of flight sim on my old computer (it was time) and in the process I upgraded to ASE. Since then this problem persists. I installed ASE first on my new computer and have since tried ASv6.5 (currently use), REX, and now FSRGW. BTW, my FS computer is only for FS. PFPX is on my work computer right next to it :Whistle: Right now I use an external FPS limiter to try to smooth out the Vsync issue in windows mode BTW. I'd ultimately love to go back to ASE since it was had very current WX, DWC made the FS wind bug gone, and it eliminated the FS haze issue (we all know the one). But the flicker every minute was just to much for me.
July 9, 201312 yr I can't see anything critical in your FS9.cfg with one exception: What is the entry "TextureAGP=0" for? Unfortunately, I don't know much about Anti-Aliasing, bi-linear or tri-linear filtering or graphics settings at all. I have AA deactivated from within FS2004 and set it via Catalyst Center. Harald Harald Geyer Gründer der Messerschmitt Freunde Dresden v. V.
Create an account or sign in to comment