Robert S 75 Posted June 12, 2008 Share Posted June 12, 2008 Rafal,Congrats and thanks for posting the updates! Building your own PC always comes with a few initial glitches...as for the CPU overtemp error, possible causes might include bad temp sensor or need for a BIOS update. I'm assuming you monitor temps as you run the PC and all is within normal operating specs? If those do not solve, maybe try re-seating the CPU into the socket and ensure that the thermal paste you used between the CPU and heatsynch/cooler was done sufficiently.As for Nvidia drivers, latest doesn't always mean greatest and the screenshots you provided attest to the OEM drivers working fine!Blurry textures? I had those but and solved them, but let me look up what I did. As for my ticket, certainly it is in first class, right? :-) Link to comment Share on other sites More sharing options...
Robert S 75 Posted June 12, 2008 Share Posted June 12, 2008 Found this on FS9 blurries:The explanation for this is complex, but it depends on hardware settings for the video card and also on settings in FS2004, primarily the level of bitmapping used. One possible cause is the simulator settings: the "Aircraft Texture Size" slider in the Display settings seems to apply to the scenery textures as well - try dragging this slider to "Massive" if you are affected by blurring. For some strange and unaccountable reason, the "Aircraft Texture Size" slider can affect scenery textures at settings lower than "high" (set at "High" FS2004 uses 512 x 512 texture sheet, the preferred size of autogen). "Medium" (256 x 256) will affect autogen textures, but no other scenery textures. "Small" (128 x 128) will affect most scenery textures to some extent.Checking 'use extended terrain textures' under the display settings will help, as will running in full screen mode, but ultimately the problem is caused by the way FS2004 handles terrain texture loading.If you are confident about editing FS9.cfg, try setting TEXTURE_BANDWIDTH_MULT to a higher figure. The default is 40, on a fast machine you may be able to increase it to 300 or more. Link to comment Share on other sites More sharing options...
Rafal Haczek 1612 Posted June 13, 2008 Author Share Posted June 13, 2008 Yes, I already have all those sliders fully to the right.As for the tweaks, I've used a mix of popular tweaks by alstriff, Holger S. and Koorby (VOZ):UPPER_FRAMERATE_LIMIT=25TEXTURE_BANDWIDTH_MULT=400TERRAIN section :TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=21TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.000000TERRAIN_EXTENDED_RADIUS=9.0000000TERRAIN_EXTENDED_LEVELS=1And I'm open to experimenting with them more.As far as I know blurries come due to faulty MFS engine. As such they cannot be cured in 100% but can be reduced.That's great that you were successful with it and I too will do my best to achieve it.As for the CPU question, I must admit I'm definietely not a hardware guru (ashamed).I'll get to the shop with my box and ask the guy who set it together to have a second look inside.Best regards,Rafal Link to comment Share on other sites More sharing options...
Burkhard 23 Posted June 18, 2008 Share Posted June 18, 2008 Raid 0 only is faster when you access large files. With files lower than typical cluster sizes times the number of disks, so below 6 KB, it even gets slower due to the overhead. But FS is mainly texture loading, and these are already large compared to this size. Link to comment Share on other sites More sharing options...
Recommended Posts