Blurries are driving me insane! Help please!!

[Artie]

The memory was set manually because my gigabyte mobo wouldn't set it correctly, so I know the timings are good.

I will set the vsync on in FS to lock it and see what that does.

The drive has plenty of space and was defragged 3 or 4 times, although not with O&O.  (I won't use it after I had a bad experience with it on my older machine)

What I do not get is how RTM gave me NO blurries on a far less substantial system, with moderate settings out of the box.  This does not compute!

Thanks

Art

[NickN]

I understand

but trust me...

FSX runs fine... the
problem is you or
your system



Been here, done this I dont know how many times and its always the same result.. somewhere, somehow the user locates the problem be it a bad FSX install, bad settings or bad decisions about not using the right defrag after using my list which shuts down the LAST ACCESS system and forces other defrag software to TRASH a hard drive because they use the LAST ACCESS algorithm to defrag the drive

As long as you are on a REAL WindowsXP SP2 install disk and not on a Dell (or other) SP1a install disk (or very old Sp2 disk) that requires SP2 be installed after Windows goes in... your fine to use O&O 8.5

v10 requires different instructions

And make sure you are not overclocked when any installing is going on. People clocking improperly is another reason.. damaged system files, application files, etc. Clocking is OK but not untill everything is installed and stable.

[Artie]

Nick, here are my most recent settings:
(Pics were updated)
[SOUND]
AmbientUIMusicVolume=-6.000000
SOUND=1
SOUND_QUALITY=2
SOUND_LOD=0
UISound=1
AmbientUI=1
PrimaryDevice={00000000-0000-0000-0000-000000000000}
VoiceDevice={00000000-0000-0000-0000-000000000000}
[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=0
TEXTURE_BANDWIDTH_MULT=60
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=True
[BUFFERPOOLS]
Poolsize=8000000
[Main]
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=7554
PerfBucket=6
Maximized=0
Location=6,0,1679,1019,\\.\DISPLAY1
HideMenuNormal=0
HideMenuFullscreen=1
[PANELS]
IMAGE_QUALITY=1
DEFAULT_VIEW=1
QUICKTIPS=0
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=3
DETAILED_CLOUDS=0
CLOUD_COVERAGE_DENSITY=5
THERMAL_VISUALS=0
[DISPLAY.Device.NVIDIA GeForce 8800 GTS 512.0]
Mode=1680x1050x32
TriLinear=1
[CONTROLS]
Controls_Default=Standard
Controls_Current=Standard
JOYSTICKS=1
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
[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
[GRAPHICS]
SHADER_CACHE_PRIMED=1693458432
TEXTURE_MAX_LOAD=1024
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=0
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=0
LANDING_LIGHTS=0
AC_SELF_SHADOW=0
EFFECTS_QUALITY=0
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
D3D10=0
[USERINTERFACE]
PageID=1
OpenATCOnCreate=0
SHOW_MISSION_CAPTIONS=0
PAUSE_ON_LOST_FOCUS=1
PROMPT_ON_EXIT=1
SITUATION=FLIGHTS\OTHER\FLTSIM
Map_Orientation=2
[Trusted]
L:\FSX\GAUGES\Cessna.DLL.zcwwbeuttrirrukrkurnzwrunwtllbkrbleewihq=2
L:\FSX\GAUGES\Cessna172.DLL.htirnzlqiilnltqotiiqianclirtoeczbzrenleb=2
L:\FSX\GAUGES\Cessna182s.DLL.ccwzwblrrwholnauhlltiuboncelooncqluouziq=2
L:\FSX\GAUGES\CessnaWAlpha.DLL.wutnhieatrakalzotizwzhhainbkktrwleuriczh=2
L:\FSX\GAUGES\Bendix_King_Radio.DLL.ltwkhreoezheweuwbrwbkhbkzcwkrlkoawqbbecq=2
L:\FSX\GAUGES\Bell_206B.DLL.rbqwtluatehccbiiokhketknthzolttzuutheoua=2
L:\FSX\GAUGES\Cessna.DLL.weizotqitcneoahzttoeklnlkhqiliuuwccuukwo=2
L:\FSX\GAUGES\Cessna172.DLL.uzhzlrrltzluzawiunnebzizzeukkkacceqkqizk=2
L:\FSX\GAUGES\Cessna182s.DLL.kwwhwwnuthwetrqunhclhzwaelrhhahrlqneokcw=2
L:\FSX\GAUGES\CessnaWAlpha.DLL.btklulerhietrwqezucrqbqqleuqbzonqcbrkhhe=2
L:\FSX\GAUGES\Bendix_King_Radio.DLL.qchcnluulbcctulknnoqaowtuthqheoazuarbnlt=2
L:\FSX\GAUGES\Bell_206B.DLL.hrkwllabhbkiqbkuutnnlwbwrotlaeueihueezww=2
[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=0
IFROnly=0
AIRPORT_SCENERY_DENSITY=0
[TERRAIN]
LOD_RADIUS=8.000000
MESH_COMPLEXITY=100
MESH_RESOLUTION=21
TEXTURE_RESOLUTION=27
AUTOGEN_DENSITY=0
DETAIL_TEXTURE=1
WATER_EFFECTS=0
[AContain]
ShowLabels=0
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=0.000000
Torque=0.000000
GyroEffect=0.000000
CrashTolerance=0.000000
General=0.000000
UnlimitedFuel=True
TrueAirspeed=False
AutoCoord=True
RealMixture=False
StressDamage=False
GEffect=False
ManualLights=False
GyroDrift=False
CrashWithDyn=False
CrashDetection=False
AutoTrim=False
[SIM]
SYSCLOCK=1
[STARTUP]
DEMO=0
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=
LoadWindow=1
[FACILITIES]
COUNTRY=
STATE=
CITY=
GTL_BUTTON=4096
[Misc]
Com_Rate=7


Here is nHancer profile:

AA: 2x1(Enhance),TranspMS
AACompat: 0
AF: 16x
VSync: On TripleBuffer+
SLI: AFR3 [0x0240020E]
DX10-SLI: AFR [0x000000F1]
Perf: HiQual
Trilin-
AnisoSam-
NegLOD: Clamp
LOD: 0.000
DXT3+
MipMap:None
ConfTxtClamp+
OGLCompat: 0
OGLVersion:
ExtLimit: 0
DynTiling: 1
CPU:SingleCore
Prerender: 3
HDR:On

And my latest pic (this is about the same quality as I had with pic 3), and this is  as good as it gets, but is still far from being likeable.

https://www.discount-pool-supplies.com/ ... latest.JPG

Keep in mind I use no AV, and have processes down to near minimum.  Notice the 200+ FPS!!!  Weird...

Thanks for taking a look.

Art

[Wii]

Lock fps at 20 or 30. The only way to get rid of blurries (and max settings with extreme FPS with no jumps) is using a quad core.
AMD x2 2.5ghz
320gb HD
3gb RAM
8800GT 512mb
Just wait for the blurries to load. I max FSX and the only time the blurries are noticeable is around 4000ft and on a large flat area with unl. vis.
Suck it up. Unless they are extreme (and by that photo they are not) you are OK cuz it happens to most if not all.

PS try turning AA off. Takes a load off your card and helps it load textures faster. That's what zaps the blurries for me.

[NickN]

Lock fps at 20 or 30. The only way to get rid of blurries is using a quad core.
AMD x2 2.5ghz
320gb HD
3gb RAM
8800GT 512mb
Just wait for the blurries to load. I max FSX and the only time the blurries are noticeable is around 4000ft and on a large flat area with unl. vis.
Suck it up. Unless they are extreme (and by that photo they are not) you are OK cuz it happens to most if not all.

PS try turning AA off. Takes a load off your card and helps it load textures faster. That's what zaps the blurries for me.

bad advice all the way around

AA in drivers is required to keep the sim looking sharp

I run unlimited in the large urban areas and lock at 30 outside in the bush



http://www.simviation.com/cgi-bin/yabb2 ... 1203009077


http://www.simviation.com/cgi-bin/yabb2 ... 1203009488


http://www.simviation.com/cgi-bin/yabb2 ... 1201590450


http://www.simviation.com/cgi-bin/yabb2 ... 1201693522



although I do agree his CPU is the weakest link...

[Artie]

I suppose I could try the older version of O&O defrag since FSX is on its own drive.  I don't think it could do much harm there.

Did you have a look at my latest info?

Thanks

Art

[Corrupt Silence]

All I have to say is that I agree with NickN. You see my specs below, and I have had very little issue with blurries. The graphics quality of FSX as a matter of fact floors me vs. FS9. I am also using FSX w/ SP2 and Acceleration. No disrespect meant Artie, but you are doing something wrong. I also do not use O&O, but only because I don't have the funds to purchase it for a few more weeks.

[PhilTaylor]

http://blogs.msdn.com/ptaylor/archive/2 ... -or-2.aspx

would indicate Texture_Bandwidth_Mult needs to be set based on your FSP. 120 is probably not a good value; especially if you go to locked FPS without changing this.

http://blogs.msdn.com/ptaylor/archive/2 ... -week.aspx

would indicate that values as high as 80 are probably not wise and in general this is not a good value to tweak when on multicore box. lets do some math just to level set what you are doing. to get 20FPS, you can spend no more than 50millisecond per frame for all actions. If the frame is taking 50ms, a setting of .8 means take .8*50= 40ms for scenery loading and 10ms for everything else. the default time of .33*50 means 16.5ms for scenery loading and 33.5ms for everthing else. it would seem this setting is starving the sim of frame time.

tweaks can be dangerous if used incorrectly.

[Artie]

Phil, I appreciate your monitoring this forum.  I assume you have been following this thread from the beginning.

In your opinion, is my approach logical or not?  My first concern is eliminating blurries, and if I set the sim up to free every available cpu cycle available my chances of doing this are greatly increased, right?

As I mentioned, RTM caused no blurries on a much lesser capable machine, so I do not understand why I cannot find my way out of the blurries on SP2.  None of this  makes any sense to me.

I will note that since turning the autogen slider back on, there was a massive frame hit, but, the blurries were not as noticeable only because the textures are obscured in great measure by the autogen, so it is a little more acceptable, but still not quite what I am after.

I'd appreciate your response Phil.

Thanks

Art

[NickN]

I agree with Phil that with SP2 TBM is most likely going to want to remain default. However, I have also set up many systems where it required adjusting it.

The TBM should not be touched until everything else has been adjusted, set and verified, and only should be looked at as the last setting to work with after all else. If good smooth frames are being rendered, no other problems are showing but the ground textures are simply having a bit of a time keeping up, then that is an option. AND that also assumes there are no hardware, background activity or other problems in the mix. TBM should --not-- be adjusted to fix massive blurs.

That is why when I posted the MAX range on the TBM, the setting -typically- is left at default (what FSX sets it to when the config file is first built)

I run 80 and see textures having problems keeping up otherwise. But I also run a DDR3 system @ DDR3 2000 and a clocked Quad core at 3.6gig and 500MHz FSB, and a 768MB clocked video adapter. My personal system will render blurs, although not all over, with a lower value. Textures can be seen sharpening in-flight and not stay razor sharp everywhere if that value is not 80 on my system. I do not recommend everyone run or use it. its a last resort test/tweak, and, its adjusted in values of 10 (at a time, per test flight.. not jacked up 20-40) from default to see if it makes a difference. if it doesnt.. it should be set back to default.

We found in the past that TBM is a sensitive setting and prior to SP2 there were a lot of successes even on slower hardware in clearing up blurs and scenery rings tweaking TBM and the Swap Wait Timeout as a set, however with SP2 its very hit and miss, Swap Wait is no longer used or has the same effect, and, the TBM is usually best left at default unless you know exactly what you are doing and work the value slowly while testing.

It

[macca22au]

NickN:

[kagazi]

"Also, I assume you marked the OS if its 32bit for it to use 4GB, correct?"

Hello Nick,

Are you referring to the Userva= and 3gb switches?

Thanks.
Kagazi

[NickN]

"Also, I assume you marked the OS if its 32bit for it to use 4GB, correct?"

Hello Nick,

Are you referring to the Userva= and 3gb switches?

Thanks.
Kagazi

Yes

[NickN]

[quote]NickN:

[Microsoft Corporation]

Artie:  I don't think it's your drivers.  I built my new rig last month with ForceWare Release 169 WHQL, and have not noticed blurries.  In fact in my last flight over Alaska I was almost hypnotized by the "plaid" pattern of the terrain tiles clearly repeating out to the horizon -- blurries might have even been preferable to that monotony!  :-?

My guess it the problem lies in your settings (aniso?), or maybe the vid drivers if you had 'upgraded' them from an older set.  Wikipedia has article about this! http://en.wikipedia.org/wiki/Anisotropic_filtering

I have a E8400@~4Ghz, 2x1GB corsair PC3-1800, 8800 GTS 640MB, WinXP SP3. (yes SP3).  FSX Delux w/acceleration.  I use 2 monitors: #1 28" @ 1920X1200, #2 20" (can't remember resolution but it's only for guages).   I use the NVidia control panel 3D settings to manage my FSX settings.

Good luck!

EDIT:  here's your problem!  I just found it on your setting you posted:
TriLinear=1