FSX - DX10 Scenery Fixer V2 2FSX - DX10 Scenery Fixer V2 2
Jemima Torguson
-FOREWORD-
Now and then comes the time when your SIM gets realy laggy and you can't seem to figure it out what's exactly causing the issue. Is it your drivers, your SIM settings, a particular addon or is just because you overloaded your SIM?
-HOUSEKEEPING STEPS-
This just happened to me and I decided to start again from 0. For housekeeping stuff I went ahead and uninstalled all my Addons in an order that I thought would make the best sense:
Finaly I uninstalled FSX:SE, restarted my PC, cleaned up the registry and tried to delete everything FSX related from all known locations (Program Files, AppData...). I basically opened all locations where I knew FSX or addons are installing stuff and deleted those. Final step was to defragment the drive where all of the main files were installed.
Not to forget: I reverted all nVidia inspector settings to default!
-FRESH INSTALL-
I then installed FSX:SE fresh and the first thing I did was to start FSX and move all scenery setting sliders to the max (even the water reflections). Further I turned Anisotropic ON, AA ON, Lens flare and advanced animations ON, frames to unlimited, all traffic OFF, all shadows OFF...and then closed FSX:SE. This step was necessary to get the first fsx.cfg created.
1. 252 (CORE 1 and it's HT OFF, all other CORES with theyre HT ON)
FSX loads a lot quicker
FPS seems improved a bit but negligible
CPU load clearly shows that the new setting has an effect. You can see this with the switch from VC to outside and back as usual (I WILL CALL THIS PROCEDURE AS "THE VIEW SWITCH").
FINDING 3 (probably the most important finding ever): If you set a tweak (here was AFF MSK) and comment it out afterwards in your fsx.cfg, IT WILL STAY THE WAY YOU TWEAKED IT BEFORE! To be clearer: lets say you set "AFFINITYMASK=252" and afterwards comment it out "//AFFINITYMASK=252". Your FSX will NOT return to the default settings but remain in AFF MSK 252 setting. I'm not a programmer but this is how my system performed.
There are so many known "tweaks" and I tried all of them and always thought that if a "so called tweak" does not work, I'll comment it out and have my genuine FSX setting back so I could try another tweak. This beeing the case you have a plethora of tweak combinations and might be the reason some of you can't get the system "finetuned" or some tweaks work more or less better on a end-user machine.
-BUFFERPOOLS-
1. Having settled for AFFINITYMASK=20 (remember it's a vanilla FSX:SE install so far and I didn't move the ACFT from EDDM Gate 104), I went for the USEPOOLS=0 tweak. This supposedly moves some of the CPU load to the GPU.
For consistency check I tried to comment the Usepools=1 out to have CORE 1 without any load. I failed at the beginning and then tried to play again with AFFINITYMASK to try to get FSX to "reset" itself.
I think I got it solved switching AFF MSK to 252 - start FSX - reboot PC - set AFF MSK back to 20 (I realy can't recall how it got fixed but it did) and got my wellknown 77FPS back. So again: I think the tweak sequence does make a difference...
*PART II the switch to DX10*
I recently purchased the FIXER and the cloud shadows. This is also the reason why I started all this since I thought I have lost FPS after applying DX10 + Fixer + clouds.
4. Installed DX10 fixer using Steve's profile with HD shadows. I changed nothing (AA listed as 4x).
Interesting thing here: if you go to the FSX.CFG from the fixer GUI, it reads out some of the settings from the file (you can apply tweaks from the GUI itself). If you remember further up, I commented the Usepools tweak out and got CORE 1 unloaded. The fixer yet still displayed Usepools=1 entry (blank poolsize and treshhold). Checking fsx.cfg I found no active Usepools entry (mine was commented out and no new one has been created). Maybe a slight bug with the Fixer GUI.
5. Installed Steves Cloud Shadows. I encountered a problem while updating the libraries, something related to DLL.XML. Since I didn't install any Addons that needed to be triggered with FSX, the file was simply missing. I didn't want to create one by myself and decided to (see point 6).
7fc3f7cf58