• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Fix/Tweaks for FSX

bojote

bojote

Messages
13
Country
us-florida
HIGHMEMFIX=1 in [GRAPHICS] section
Allows FSX to manage more than 512MB of video memory on WDDM1.0 and WDDM1.1 without making textures dissapear or consider them stale.

UsePools=0 in [BufferPools] section
Bypasses the explicit vertex buffer and goes directly to the command buffer offloading from the CPU this buffer management and offering 20%-40% performance increase.

I wonder if this forum its a better place to discuss this stuff... was anyone here familiar with those tweaks/fixes? Im particularly interested in the 'reasons' why ACES never mentioned this.
 
I havent known about these.

Aces probably didnt want everyone messing with their raw FSX config file.

Figure 3 versions of FSX; Base, SP1, SP2 / Accelleration (would that be 4?)
Figure several versions Windows; XP, XP64, vista, vista 86, vista 64, and now Win7 32 and Win7 64....

Then you have multiple versions of GC's out that were stammering on getting DX10 to work correctly and efficiently..

So coming up with FSX configs that worked with all of those was probably the ultimate nightmare... making sure it worked with 'most' everyones systems. It was probably more of a threat and possibly 'nightmare' to offer those suggestions...



Bill
 
Well, I've seen nearly a 30% increase in average framerates at 33MO with one of my "most framerate unfriendly models" loaded as a user a/c, and four Global Express XRS's, four Citation X (full models), five Citation II's, four CJ1's, two Victory's and six Navion's loaded as AI...

...and that's on top of the "normal AI" that FSX already has!

With only these two entries added for the fsx.cfg file:

HIGHMEMFIX=1

UsePools=0

It's bloody brilliant!
 
lionheart said:
I havent known about these.
Aces probably didnt want everyone messing with their raw FSX config file.
Click to expand...

I tried Phil Taylor (I know he's not MS anymore) and Rafael Cintron.. zero, nada.. they ignore me :)

I don't want 're-assurance' from them on the 'why' those tweak/fixes work, I know the 'why', I just want some 'answers' to 'better understand' the root causes for a particular 'disturbing' string of code I found... that goes like this: Workaround.Performance.HIGHMEMFIX in g2d.dll I want to understand WHAT WHERE THEY THINKING... (I'm pretty sure its related to render states and WDDM handing of texture addressing modes) what I don't understand is the silence. or why ignore me? are they under some kind of NDA? I just want to make our hobby better.

BTW, For the UsePools tweak, this is a good read:

http://msdn.microsoft.com/en-us/library/ff539490.aspx

UsePools=1 (default) 'Explicit vertex buffers'
UsePools=0 bypasses Explicit vertex buffers draw calls go directly to the API 'Command buffer' (CPU is free to do more work) but Video Card will have more work, so you are 'shifting' the balance in FSX making it more GPU bound ;)

Evidently, those people using nhancer with High AA, Aniso, Vsync on, UNLIMITED frames in FSX and AutoGen set to dense will IMMEDIATLY crash FSX ;) like in 2 seconds!!

If AutoGen is batched PER FRAME, and you are not using local vertex buffers, all those calls go directly to the D3D API and the command buffer 'could' be filled stalling the GPU if it doesn't 'process' all the instructions fast enough.
specially if using overclocked i7's running 4.2 so careful with UsePools=0 it needs a carefully balanced machine with an ULTRA high speed video card. the 'success rate' of UsePools=0 varies depending on your config.
 
Last edited:
You must log in or register to reply here.
Back
Top