ENBSERIES plug-in and Alt+Enter crash?

[Cirrus22 9]

When you access a menu it is the same thing. You are causing the DX window to refresh or redraw. There isn't any difference.

That makes sense. Also, I just got the crash again - I'd set UseEffect=0, and ENBseries effects were on. I was getting out of the flight analysis back to flying, and it crashed. It seems to crash more often coming in and out of that 'esc' screen (with End Flight/Flight Analysis/Continue Flying) than any other menu for me!

[Turbine777 13]

I wonder if it's because direct X itself is being disabled for a longer period and not just recovering from a change? I have been able to reproduce it with just the slightest window resize, however like you mentioned it's more common when something like you described happens and the percentage does seem to go up. For me there is a 90% chance I'll crash on a similar screen. It's when the FSP message box comes up and looks just like the "End Flight/Flight Analysis/Continue Flying" screen where it is a smaller box and the rest of the screen is black. FSX rarely is recovering from that point, if at all.As I mentioned above I am hoping it is only during this phase of it going from enabled to disabled. Perhaps try to disable it (Shift+F12) before accessing the menu or window your talking about. That way it is going from a disabled state back to a disabled state. I really hope that's it anyway since the other night when I tested it I had success for a long time with no crashing to what I could reproduce prior in just a couple minutes. That's what I wanted to test tonight but not sure I'll be able to since I'm on my way out right now for dinner with me sista. If I don't get time tonight, tomorrows my day off so will for sure then.

[NGXfanatic 85]

I am following this thread with great interest, and I'm very relieved to know I am not the only one with this issue. I have had this full to windowed mode crash with ENBseries ever since I moved from XP64 to W764, and for the past 2 months I just removed ENB because of all the trouble it was giving me. Flying exclusively in Full or Windowed mode for the whole duration of a flight is a no go for me, I have to be able to web browse or see the weather reports in Active Sky Evolution. Dan, thanks for bringing this glitch to NickN's attention at the GEX forum, because of you and NickN I learned of the "useeffect=0" tweak. One thing I should mention, NickN says do not use alt-enter, Nvidia acknowledges there is an issue with using that shortcut with FSX. You should use the FSX menu to switch modes, this may help to prevent the crashes. I'm testing this scenario out now, and so far no crash if I use the menu instead. And DO NOT disable ENB with shift-f12, only use it to turn the effect on. The point of the tweak is to make sure the effect is always disabled especially in mode changes., The onus is on the user to enable it with shift f12, and with the tweak the user should not worry about disabling it before the screen mode switch.Thanks again, I'm hoping this bug is squashed once and for all!

[Guest nzch2010]

Hope you don't mind me butting in here, recently NickN mention in one of his threads that there is an issue with ALt +Enter in FSX /W7. He said to not ever use it as it causes a CTD. He reccomended hitting the "window" key. I read this a few days ago, and sorry I cannot remember the subject thread. But he was adamant that Alt + Enter is a no no.CheersJulian

[Turbine777 13]

Glad to do my part AJ. It would be nice to see some other peops with the know how to join in when they have the time.Unfortunately I haven't had much time to try everything I wanted to tonight but I did a couple tests. From what has already been said, it seems to only be with advanced aircraft and complex systems that this happens. Why? I have no idea, perhaps it's a .net or C++ event triggering the problem? Again, I'm out of my realm and at this point reaching but I did just do a flight in the RealAir Duke B60 with numerous Alt+Enters without issue. It is an advanced aircraft in the smaller sense of the phrase but wanted to test it since I don't have many middle of the road aircraft in terms of complexity.I ran in windowed mode and kept an eye out for CPU spikes and processes hogging memory, but didn't see anything. I also ran the MD-11 in windowed mode and did tons of resizing and caused the crash again but still without seeing anything important or worthy to note.There have been some that use a modified or added file for the gradient or "enbpalette". I want to test out some to see if useing this file or not matters at all but don't see why it would. I have Tim's (Rex) and some others, even a couple I made with very subtle changes but haven't been able to stay put long enough tonight to try them out.I did try to run in XP SP3 compatibility mode but FSX crashes and won't start. It looks like it's having issues with FSDT's addon manager but don't want to have to uninstall stuff at the moment just to test it, and besides would be a different issue anyway for another day.

[NGXfanatic 85]

Yes, I remember when I read Nick's writeup on the interaction of W7 with FSX that alt-enter is to be avoided. The strange thing for me is that alt-enter never caused a crash for me on W7, but when I brought ENBseries into the mix, the crashes started occuring. Its a hard habit to break, but if I can confirm its causing my ENB screen mode crashes, I will just have to get used to the FSX menu bar, or the windows key of course. I stay on full screen when I'm busy with the flight (i.e. takeoff/climb to cruise and landing), but during preflight preparations and the long cruises I prefer not to window key to desktop, but to go to windowed mode where I can resize the window and multitask with other apps for either preparing for flight (TOPCAT/ASA or fuel planners) or web browse/keep current with enroute/destination weather with ASA. Its much easier for me for FSX to be windowed during these times vs. having to hit the taskbar and enter, if that makes any sense.

[Turbine777 13]

Hope you don't mind me butting in here, recently NickN mention in one of his threads that there is an issue with ALt +Enter in FSX /W7. He said to not ever use it as it causes a CTD. He reccomended hitting the "window" key. I read this a few days ago, and sorry I cannot remember the subject thread. But he was adamant that Alt + Enter is a no no.CheersJulian

Thanks Julian, I read that as well, but that method is fine if you don't plan on taking focus entirely off FSX. He explained to just hit the windows key, then hit enter to return but this wouldn't work if say you needed to minimize to change web sites, plan routes etc...On a different note, it is still changing the DX window so not sure how that seems to work any different?Maybe theres something here I'm missing. Oh well, tomorrows another day.

[NGXfanatic 85]

Yeah, I don't see why a simple keyboard stroke can cause FSX to crash. I'm not in any position to comment on the validity of this, I'm just curious. I wish I could figure out a way to make a macro with FSUIPC to do the mode switch, it can be a nuisance to hit the alt key to bring up the FSX menu and then using the mouse to select the menu entry. I'm so spoiled by the alt-enter, I even had the keystroke saved on one of my logitech g9 mouse buttons. I'll see if FSUIPC has a way to assign a button to this command, I would be surprised if it didn't considering all the things it can assign keys or joystick buttons to.

[NGXfanatic 85]

Bad news.... during a 2 hour test flight on final approach in the PMDG MD11, I went to the controls options (while in fullscreen mode) from the fsx menu to change a keyboard setting, and when I returned the screen went black. Fiddling around hoping to get the session back, FSX crashes with a API.dll fault. The reason I went to the controls settings menu was that I had rebuilt my FSX.cfg from scratch just to test the new ENB tweak, and some keyboard commands that reverted to default which interfered with some of my addons. I seldom access the FSX menu to fiddle around once I'm in flight, but I needed to do for this reason,Up until that point, I had been able to switch modes (with the FSX menu, not alt-enter) quite a few times with success. Whenever I did a full to window to full screen switch, pulled up a menu from the FSX menu bar, or resized the window when in windowed mode, ENB disabled itself as to be expected with the tweak. I will try another flight tommorrow replicating my normal "routine" and see if I can induce more crashes. I cannot say for sure if the crash is attributed to the ENB mod, but it's possible. In conclusion, I think maybe progress has been made and I may be able to use the ENB bloom, but some testing on my end awaits.

[b0gey_dead_six 11]

Bad news.... during a 2 hour test flight on final approach in the PMDG MD11, I went to the controls options (while in fullscreen mode) from the fsx menu to change a keyboard setting, and when I returned the screen went black. Fiddling around hoping to get the session back, FSX crashes with a API.dll fault. The reason I went to the controls settings menu was that I had rebuilt my FSX.cfg from scratch just to test the new ENB tweak, and some keyboard commands that reverted to default which interfered with some of my addons. I seldom access the FSX menu to fiddle around once I'm in flight, but I needed to do for this reason,Up until that point, I had been able to switch modes (with the FSX menu, not alt-enter) quite a few times with success. Whenever I did a full to window to full screen switch, pulled up a menu from the FSX menu bar, or resized the window when in windowed mode, ENB disabled itself as to be expected with the tweak. I will try another flight tommorrow replicating my normal "routine" and see if I can induce more crashes. I cannot say for sure if the crash is attributed to the ENB mod, but it's possible. In conclusion, I think maybe progress has been made and I may be able to use the ENB bloom, but some testing on my end awaits.

No issues here for me, using *******' shader mod, highmemfix, yadda yadda.. i too alt-enter a lot during a flight with various add-ons like CS, PMDG, and LDS.

[Turbine777 13]

Thanks for the input guys. Keep it coming. The more people testing (and more importantly, sharing their findings), the more info we can gather for a more solid answer to what's going on here. As for *******'s shaders, that's interesting and was on my list to try. I recently removed his fix since I installed FSWC and the two don't play nice as mentioned in my original post above. I think some more testing is in order on your side DJ, and maybe tomorrow I'll reinstall them if all is good and confirm your findings. Keep testing and let us know please.Maybe then we can toss a rope around ******* and drag him in here for a general synopsis :(

[NGXfanatic 85]

I'm all for that, remember ******* SAVES!

[themose 11]

I was having problems with the Black screens while switching with Alt+Enter.I removed *******'s Shader mod 3, ENB and tried a few flights without both..All good.I then tried the ENB without the Shader mod and it has been working great..

[Guitarman 0]

I was having problems with the Black screens while switching with Alt+Enter.I removed *******'s Shader mod 3, ENB and tried a few flights without both..All good.I then tried the ENB without the Shader mod and it has been working great..

I also removed SM3 but it was because of FSWC.@ DanDo you have this issue with Tim's (from REX) ENB mod too ?

[Turbine777 13]

I also removed SM3 but it was because of FSWC.@ DanDo you have this issue with Tim's (from REX) ENB mod too ?

Hi Dan, Yes, I have used Nick Needhams, Tim's and the two files (Warm and Neurtal) from the Rex page that you told me about. I don't think the ini has anything to do with it other than the UseEffect=0 keeping it defaulting to off which I think has made it much more stable. I think it's rather just the .dll. I'm getting a late start today and want to go through each again with a few tests per but so far, no good. Maybe since others like Phil have had success without the shaders tweak, we might have better results without FSWC? I have a lot of tests to try but maybe later will try it without FSWC too and see what happens.