September 14, 200916 yr Well, after a week of trying to fix my full screen menu lockup problem, i admit defeat. New .cfg file, new logbook.bin file, repair and reload SP1 and Sp2, new drivers, countless changes to nHancer and fsx settings - nothing worked. I suppose I could re-format the drives and start over completely, but I'm tired of trying to fix it. FS9 is working perfectly, and while not as good as fsx, at least I can fly it.Thanks to all those who offered suggestions.Dale Dale
September 14, 200916 yr No need to surrender. I had massive problems with my Geforce 8800 GTS with nHancer with the various recommended 3D settingss and AA/AF. I finally resolved all the problems by going back to a 'non-tweaked' setup with AA/AF through the FSX and I was positively surprised with the framerates (20+ with Wilco Airbus, 40% MyTraffic) AND with a much improved image quality and stability. nHancer would sometimes work with certain drivers, sometimes it would not and produced quite some graphic corruptions and abnormalities (menu issues, black screens, problems switching from full-screen to windowed and vice versa). For me, nHancer has been more of a hassle than a benefit and I have tried every possible setting.-Pat
September 14, 200916 yr Author You have tried the arrow keys rather than the mouse haven't you?Yes, I read that worked for some, but not on my system. Thanks for the suggestion.Dale Dale
September 14, 200916 yr Author No need to surrender. I had massive problems with my Geforce 8800 GTS with nHancer with the various recommended 3D settingss and AA/AF. I finally resolved all the problems by going back to a 'non-tweaked' setup with AA/AF through the FSX and I was positively surprised with the framerates (20+ with Wilco Airbus, 40% MyTraffic) AND with a much improved image quality and stability. nHancer would sometimes work with certain drivers, sometimes it would not and produced quite some graphic corruptions and abnormalities (menu issues, black screens, problems switching from full-screen to windowed and vice versa). For me, nHancer has been more of a hassle than a benefit and I have tried every possible setting.-PatAt one point, I turned off nHancer, but still had the problem. Now, "turning off" is not the same as uninstalling it, so I guess I should go back and try that. Thing is, FSX was working beautifully with nHancer. The problem started after I installed the FSD 115. I can't say it was the FSD program because I uninstalled it and still had the problem.BTW, I have the latest version of nHancer, 2.51, and checked to make sure I also have the latest .net Framework 3.5 w/sp1.Dale Dale
September 14, 200916 yr At one point, I turned off nHancer, but still had the problem. Now, "turning off" is not the same as uninstalling it, so I guess I should go back and try that. Thing is, FSX was working beautifully with nHancer. The problem started after I installed the FSD 115. I can't say it was the FSD program because I uninstalled it and still had the problem.BTW, I have the latest version of nHancer, 2.51, and checked to make sure I also have the latest .net Framework 3.5 w/sp1.DaleCould the uninstall of FSD's plane have left something behind? May want to look inside the files and see. Also, have you checked what version of FSUIPC you are running? I find that sometimes, the plane installer comes with it and it overwrites the original one. OK if you actually update FSUIPC, but if it actually rolls back a couple versions maybe it could screw it up. Maybe the FSD installer overwrote something that one of the other add-ons also use? Last resort would be to uninstall FSX completely, clean the registry and re-install FSX.Also, not being familiar with your previous attempts, what Nvidia driver version are you using? I read 2.51 version of nhancer has issues with the 190 series nvidia drivers. There is a beta update the fixes this issue available on their site.Larry Larry Falcone No matter where you go............... ...................there you are............ Buckaroo Banzai
September 14, 200916 yr The problem started after I installed the FSD 115. I can't say it was the FSD program because I uninstalled it and still had the problem.I have the FSD C115 installed and have never had any problems with menu lock ups in FSX.
September 14, 200916 yr I have the FSD C115 installed and have never had any problems with menu lock ups in FSX.I had to use the enchancer beta also for the 190 drivers and it works perfectly in my system. Good luck I am no done flying til you pry the joystick out of my cold dead hands
September 14, 200916 yr Author Could the uninstall of FSD's plane have left something behind? May want to look inside the files and see. Also, have you checked what version of FSUIPC you are running? I find that sometimes, the plane installer comes with it and it overwrites the original one. OK if you actually update FSUIPC, but if it actually rolls back a couple versions maybe it could screw it up. Maybe the FSD installer overwrote something that one of the other add-ons also use? Last resort would be to uninstall FSX completely, clean the registry and re-install FSX.Also, not being familiar with your previous attempts, what Nvidia driver version are you using? I read 2.51 version of nhancer has issues with the 190 series nvidia drivers. There is a beta update the fixes this issue available on their site.LarryI'm using the 182.5 Nvidia driver, and Fsuipc 4.5.3 (registered). I tried going back to FSUIPC 4.3, but no change. Tomorrow, I'll delete it and reinstall 4.5.3, just to be sure.The FSD installer puts in a lot of files, probably part of their ant-piracy effort. After I did the uninstall, I found a FSDX.dll file still there, but removing it didn't change anything. I ran CCleaner and cleaned up a few registry errors, but still no help. I sent FSD Support an E-Mail to see if they had any suggestions, but have not received a reply.Before I do a complete uninstall of FSX, I need to get a large external drive and some software like Ghost. My fear is that I'll remove FSX and also mess up the registry for FS9, at which point, I may throw the entire PC in the trash!Thanks for the input, all good suggestions. Dale Dale
September 15, 200916 yr I'm using the 182.5 Nvidia driver, and Fsuipc 4.5.3 (registered). I tried going back to FSUIPC 4.3, but no change. Tomorrow, I'll delete it and reinstall 4.5.3, just to be sure.The FSD installer puts in a lot of files, probably part of their ant-piracy effort. After I did the uninstall, I found a FSDX.dll file still there, but removing it didn't change anything. I ran CCleaner and cleaned up a few registry errors, but still no help. I sent FSD Support an E-Mail to see if they had any suggestions, but have not received a reply.Before I do a complete uninstall of FSX, I need to get a large external drive and some software like Ghost. My fear is that I'll remove FSX and also mess up the registry for FS9, at which point, I may throw the entire PC in the trash!Thanks for the input, all good suggestions. DaleTry 186.18 driver release ... set all do defaults ... don't use and utility programs.
September 15, 200916 yr Author Yes! I uninstalled nHancer, set up with Nvidia control panel and now my menu screens work in full screen. Thanks a bunch to all those who gave me suggestions and encouragement.The wierd thing is, I checked my change log and everything was working with nHancer for nearly 2 weeks! Somehow, the FSD installation might have triggered something which affected the interface between nHancer and the display. I may retry nHancer because I would much prefer to control antialiasing from the GPU rather than within FSX.In all the changes I made, I somehow lost all my water textures (probably the repair process), but I think I will only need to reload Ultimate Terrain.Thanks again to all those who helped,Dale Dale
Create an account or sign in to comment