Anybody using this entry in the FSX.cfg?

 

[Main]

DisablePreload=1

 

(prevents the default flight from being loaded as FSX boots, which should speed up FSX boot and avoid loading things into memory that you do not need)

 

I was wondering if it reduces startup VAS or just screws up the 777 initializing process?

I use this and it loads quicker with the main menu opening with the trike and harbour etc

 

Not noticed any diff in vas or problems with pmdg

All it does is prevent FSX from loading a flight while the spinning aircraft is displayed.

I cannot speak for PMDG products but it certainly does interfere with the correct loading of some complex addon aircraft, notably the Sibwings AN-2.

 

I have tried it in the distant past and I can say that any time it might save is lost again when loading the flight.

Simple logic, the flight must take time to load, whether it is while the spinning aircraft spins or thereafter.

 

There are those who swear by this tweak, my view is that is yet another that is no longer required as computer hardware has overtaken and removed the issue.

I've used it for years never had a problem

Never had a problem with this either.

Some guys have had issues, precisely CTDs, when using AES related to disablepreload=1. It seems the issue stops when this line is removed. I don't have AES to test it myself though.

i use AES with this line in the cfg and dont have any issues either with the sim / pmdg / AES

I think this line also has a benefit with Vsync in DX10

 

http://forum.avsim.net/topic/416988-vsync-in-dx10/

 

Michael

We don't recommend using this - it can result in certain internal FSX variables not initializing properly without the default ultralight having been loaded in the background first. Can cause weird issues or CTDs on load.

I read that it helps to have vsync running in DX10

 

Enviado desde mi Nexus 5 mediante Tapatalk