- #Fsx sp1 and sp2 download install
- #Fsx sp1 and sp2 download drivers
- #Fsx sp1 and sp2 download update
- #Fsx sp1 and sp2 download driver
As soon as you boot FSX or FS9, or any other game in the list, the Nvidia drivers override the settings you made and change them without you knowing.
#Fsx sp1 and sp2 download driver
Why? because if you don't, Nvidia driver profiles REMOVE your ability to change driver settings and FSX settings so no matter what you set in the drivers, Nvidia OVERRRIDES them and FORCES your card to run the way they want it to run, which is BULL on their part. Proper driver upgrades and proper setup of the drivers with Nhancer is a must! The raised the default to 4000000 in SP1. It will have an affect on the turns and panning smoothness but it does lock the video memory from using 5, 8, 10MB for anything other than the buffer cache so if you are short on video memory this may be an issue. This is another area you may wish to leave out or test. A 256mb card may only be able to handle 5000000. I do not use these lines at all anymore and just leave them out. it can be raised to max of 6000/6000 or reduced as desired. TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=xxxxĭefault is 4500 trees and 3000 buildings. You may wish to leave it out of the config and keep the Texture bandwidth multiplier at the FSX default when it created the file. With SP2 I am no longer using the SWAP_WAIT_TIMEOUT= line above however I have not tested all circumstances yet.
SWAP_WAIT_TIMEOUT =37 <- NOTE: With changes to SP2 this setting enabled in the config may cause problems there is a scale used for SP1 as follows: I would say most should be somewhere around 40-90 MAX. Although the max Texture Bandwidth Multiplier can go to 400 like FS9, to do so is suicide in FSX. TEXTURE_BANDWIDTH_MULT =70 <- I would be cautious with this after SP2. HideInfoText=1 <- gets rid of the mag, brakes and other info on the screen (optional)ĭisablePreload=1 <- a Must in order to offload the memory from the default flight and not allow FSX to double load on boot. leave this entire section out except for quad core and in some cases dual core. WideViewAspect=True (FALSE if you do not have a wide screen monitor)ĪffinityMask=xx <- affinity mask not needed for single core. UPPER_FRAMERATE_LIMIT=? You will need to experiment with your FPS setting. Here is a list of the ONLY areas one may wish to work with The best tweaks are now all in Windows setup and the correct use of O&O Defrag! Use it to copy/paste edits but do not overwrite the new file.
#Fsx sp1 and sp2 download install
Install your addons one at a time, reboot in between and make sure you have the updates for them.ĭO NOT MIGRATE the FSX.cfg file you have!
Start the sim, set up the sliders/checkboxes as you had them.
#Fsx sp1 and sp2 download update
(Many add-ons install this update now automatically. Make sure you have the C++ library update installed. Make sure you have the latest DirectX installed. If you want the Acceleration SDK install it from the disk. Boot the sim and allow it to complete the install and boot the default flight.
Install Acceleration which will install SP1 and SP2 automatically. If you have the Deluxe version and want the SDK installed, install it off the DVD now.Ĥ. Install RTM, fire up the sim and let it complete the install and boot the default flight. The only tweaks that should be looked at are ones that are designed for dual/quad core, the light scale for the airports, the tweak which removes the sims ability to preload the default flight and only if the system is very slow, perhaps work with the added autogen lines, but otherwise Aces did a bang-up job of getting FSX to run without having to tweak the config as of SP2Īnd yes, a clean install getting rid of the old install and allowing FSX to update asĪces intended with SP2/Accell is the best way to go.ġ. Many of the tweaks used in the past, like what happened with SP1, are no longer helping the sim and in many respects cause problems. Yes, with the changes SP2 incorporates, you all need to be careful of editing the FSX.cfg file.
0 kommentar(er)
