Hi all,

 

First: For users that like to let the simulator minimized and browsing the web, this is not a solution.

 

I have been amazed by the visual quality of the ENB tweak. Particularly I am using the ENBPlus Natural tweak from Tim at REX Forums.

The only problem is that many abandon the ENB due to the crashes when switching from window mode to full screen mode. 

Because I was so amazed by this tweak and couldn't think of not using it, I tried to find a method in order to avoid crashes.

 

I will not present a method in order to switch between window and fullscreen all the time. The system is prone to crashes if the user is switching all the time.

However, If you are able to set the flight parameters and enter full screen mode once, I don't find the need to return to window mode.

I use my ipad or another laptop in order to search the web while flying. The simulator runs in full screen mode.

 

I will write the drawbacks first, so anyone who doesn't like the solution can dismiss the rest.

So, the drawbacks are:

 

-You have to be careful when you setup the flight for every click you do. It is not difficult to remember after a while.

-I can't use the replay function in some aircrafts after the flight is complete. The sim crashes.

-If you fly online and you get a disconnection, you risk a CTD if you have Ivap set to window mode. I have it this way.

However I also have FSUIPC set to autosave every 15 minutes, so I don't lose any flight even if I get a CTD. Using the AAX though, you'll have to save the FMC parameters via the right CDU, but this opens a window...so there is some search for how this can be done.

 

I found these links in avsim forums :http://forum.avsim.n...l-it-ever-stop/ and http://forum.avsim.n...d-possible-fix/

where users UVW and mr340 proposed to copy the d3dx9_26.dll from Windows\system32 to the P3D/FSX folder. I did it, and also copied all the other d3dx9.XX.dll files into the P3D folder. So, these credits go to them!

 

So these are some 'rules':

 

First, after you install the ENB tweak in you Prepar3D folder:

 

1) Use [GLOBAL]\UseEffect=0 in the enbseries.ini file.

2) Copy all d3dx9_XX.dll files from C:\Windows\SysWOW64 to the main Prepar3D folder, where XX are numbers from 24 to 43. (I don't know whitch are actually necessairy but it doesn't cost anything, just ~58mb). These files can be obtained also from C:\Windows\System32, but a user named Jettix in the second link above, suggested that the System32 contains 64bit versions of the .dlls while the SysWOW64 contains 32bit versions and P3D-FSX are 32bit programs. I am not a programmer, so I have no idea what is correct here, but I copied the SysWOW64 dlls.

3) When P3D starts, I can use any menu in Window mode, except from 'Select Aircraft' and 'Load Flight'. These menu options can be used only in Full Screen mode.

4) Some add-on aircrafts once opened in Full Screen mode will cause the sim to crash again, if I try to switch to Window mode. I have find a solution that seems to work witch is:
When you first start P3D, it opens in Window mode. If the window's left and right borders are not visible, (ie. the window is maximised), then double-click the window's header (upper boarder). This will de-maximize the window. Leave it as it is when you use Window mode and do not maximize it again while in window mode. I observed that in this configuration, I could switch from Window to Full Screen mode without getting a crash. In an amount of ~10 such experiments I got one crash while using this rule, but I didn't get a crash 9 out of 10.

 

5) When in full screen and you want to go to window mode, enter the top-down view before switching if you are on the ground, and the external spot view if you are in the air. These observations are not some kind of solid proof but they worked for me.

 

6) The replay can be started at the end of the flight only from Window mode. Then you can enter Full screen (while replaying).

 

Notice: The Aerosoft's Airbus X Extended seems to be the most prone to crash of all my add-on aircrafts. This may well don't 'follow' these rules all the time. It may give you a crash some times.

 

Lastly, this is the 'method' I use:

 

1) Start Prepar3D

2) Enter window mode if you are not already in window mode.

Window mode:

3) Select Airport/parking position. Select time/date

4) Open all peripheral add-ones, like TrackIR, OpusFSX, Ivap (connect, send flightplan etc). Normaly I also set TrackIR to use High Priority in the processes tab.

5) Select View/Full Screen

Full Screen mode:

6) Load Flight and/or select your aircraft

7) If you need to exit again in window mode to use a aircraft loader for example, switch to top down view first, then use View/Window mode. Do the same to reenter FullSceen mode.

8) Fly all the flight in Full Screen and use Shift+F12 to use your ENB of course!

 

In most aircraft I am able to switch to window/full screen without crashing. So I prefere this method instead of exiting full screen. However as I said, the AAX is the most prone to crashes so I do not exit full screen mode at all when using it.

 

Two more hints:

-Try to use also Alt+Tab. I found that it helps avoid crashing but again not with the AAX.

-I use my Samsung SyncMaster2233BW in High Contrast mode using the control dials of the monitor and the results in day flights are +30% more effect. Amazing!

 

 

I post some screenshots from my latest test flights:

 

PS. Thinking of the DX10 debate lately,  I think that these visuals are the best expirience I ever had with flight simulator! Running 'butter smooth' also! there is no debate for me when this realism of image quality can be achieved! Enjoy!

Thanks for putting a lot of work into this post but unfortunately my sim still crashed within minutes.  many of the things you mentioned I have done before and was currently doing.  I had enb disabled on startup using the '0' setting, I also made sure I was in windowed mode and could see the left and right borders..i.e. not maximised, changed to top down view on runway, went to full screen, then back to windowed and boom...d3d9.dll crash.  Sorry had really hoped this would work.  I also copied as you said all the d3dx9_XX.dll from WOW64 folder. It simply doesnt work.  I dont have a View-Windowed Mode on my P3D when in Fullscreen it just shows a box beside Fullscreen and clicking it alternates back to windowed.  BTW FTX have an amazing version of it, looks fantastic.  REX one is way too dark especially at night.

 

Chris Ibbotson

I had tried that using PMDGs 737NGX so thought I would try a smaller less demanding aircraft like a Carenado one.  Exact same results, I cannot even get Enbseries to switch on unless I go into fullscreen mode first but this time sim crashed before I could even switch enbseries on, second I went to top menu and selected full screen it crashed and that was from a demaximised window view and tried external spot view this time as top down view didnt work last time either :(

I guess the easy way to avoid crashes is to NEVER use any menu whilst flying but as I use AI Traffic the only way to get permission to land and avoid a conflict of ground traffic moving onto the active whilst you are on approach is to use P3D's ATC but this 99.9% of the time causes a crash as it alters the screen as the ATC window becomes active

Hi Chris,

 

Doing more flights with more add-on aircrafts I have seen that some are more prone to crashing than others. For example, the standand mooney bravo never gives a crashes. Also I have seen certain add-on aircrafts to crash in every posible scenario when exiting full screen mode in an airport but do not crash in another airport. So, there must be internal reasons that make the sim crash in some occasions witch are not fully understood, like graphics memory load. However the most safe solution is indeed to never exit full screen while doing a flight. I am currently following this rule. One drawback is that some aircraft/scenery combinations do not allow me to use the GSX services, because GSX services usually do not give a crash only in Window mode and this require exiting the full screen mode.

Chris, I have seen that some windows cause crashes while other don't. For example, if I use any 2D panel view from the view menu it never gives me a crash in fullscreen. Even FS2crew window does not give a crash. Yesterday I discovered that the Ivap window when selected from the config to run in fullscreen, does not give a crash. However the GSX window always give a crash, Maybe its something similar with the ATC window you mentioned.

 

Another guideline I could give you is to try to switch to 2D panel view (not VC) before you start any panel or have to switch to window mode.But again, this does not always work in every add-on with the same success.

 

Clear skies!

 

 

Sent from my iPad using Tapatalk - now Free

I get crashes even if using the sim in windowed mode if enbseries is installed and activating most menus and definitely using ATC.  Ive tried pausing the sim and changing to external views in the hope it would reduce load on the graphics system but no didnt work, Im also aware the the longer I have left the sim running prior to accessing anything then the likelihood of a crash increase, I get d3d9.dll crashes on the ground or in the air doesnt matter what the situation is

I do not use the menus in window mode, especially when I have loaded an add-on heavy aircraft. As I said, 'Select aircraft' , 'Load Flight' and possibly some other will crash if you use then in window mode. However even with an add-on loaded I can access window mode menu options like Display, AccuFeel, Time/Date, Go to airport are some.

 

Also, after installing all d3d9.XX.dll files I have never got a d3d9.dll error. The only crash reports are module: 'unkown'.

 

If you follow my 'method' above, and your last move is to select full screen and after that select your aircraft, do you still get a crash?

Im afraid I followed your original post completely and it still crashed, accessing menus in windowed OR full screen crashed the sim, I might get away with either mode briefly but definitely the longer the sim is running (memory use must increase and possibly trigger it) I am 100% certain to get a crash if I access any form of menu or pop up menu like ATC.  

Im given up on enbseries as its NOT compatible and never truly has been, its never been written for flight sims.  FSX and P3D does some sort of change when you access a menu, it must be this enabling or disabling of the d3d9.dll module which causes the crash.  Without using Simlauncher utility it would be virtually impossible to start P3D using enb as you would have to launch the sim to its default flight, change aircraft - reload - change airport - reload - change time/date - reload...each of these potentially risks a crash.

 

Im going back to using FXAA Injector, would love to try SweetFX but it doesnt work in P3D..sim crashes before it can even be launched (no one can make it work)

 

Chris Ibbotson