Is there still a way of obtaining those graphics drivers, that still work with nHancer prior to the 257.... drivers released for nvidia cards?Ryans post convinced me that this would be the easiest solution, rather than getting the latest drivers and configuring a whole new setup.

Tabs: The big reason people like me update drivers is because I'm a gamer outside of FS too - for example there's bound to be a new driver release in the coming days or weeks that optimizes performance in Starcraft II, I was standing in line for that game at midnight this past week haha, so you can bet I want it to perform as well as it can.If all you use your system for is FS, then by all means stay on the 197.45 driver that still works with nHancer.

Thanks for the help guys,Angelo Cosma

Is there still a way of obtaining those graphics drivers, that still work with nHancer prior to the 257.... drivers released for nvidia cards?

Of course, they are on NVIDIA website, look for "beta and archived" drivers.

Is it possible to "remove" the flickering in the water where the sun reflect in FSX? Also is it possible to remove the flickering which happens in the edge of trees when flying in FSX?

Well HOT DAMN! That worked! I have very good AA with SB4 running now. As a matter of fact AA_MODE_SELECTOR_OVERRIDE and AA unchecked in FSX seems to work better! I've gained back the few frames I've lost using AA_MODE_SELECTOR_ENHANCE and AA checked.This is awesome... Thinking that maybe this override setting should be included in the original post as an addendum for SB4 users. Maybe placebo but it seems that even the AA TRANSPARENCY setting is working better this way as well.Thanks Jason...-Robert

Yeah, it seems to work great except that using trackir and now I KNOW i've lost complete vsync. The reason you might be seeing an increase by a few frames is that if vsync turns off, the graphics card is not throttled back on when it can display a frame on the LCD. I read quite a bit about vsync and how it works and I just can't seem to live with vsync off using trackir. I'm going to try an older nvidia driver to see if this may be a problem with the graphics driver. I'm soooo close to having the graphics on this thing nailed. I'm also just using a 9800GTX+ card and it looks awesome....until I fire up SB4.-Jason

In an attempt to resolve my vsync issues with squawkbox 4, I found a thread on avsim that talked about setting vsync using FSX instead of using the graphics driver. I tried it and it didn't seem to do much. My computer has needed a clean install for a while so I decided to wipe the system and start over with all the software I was installing. Before I go further, here is my configuration:AMD Phenom II X4 (was running at 3.5GHz before I wiped the system - BIOS upgrade reset my overclocking so I'll have to redo it)EVGA 9800 GTX+ video card (no overclock here)4GB RamWindows 7 64bit2 x 500GB in RAID0TrackIR w/version 5 softwareCH products yoke and rudder.Squawkbox version 4After I did the clean install of Windows 7 (not an upgrade and not a re-install over my old version) I thought I would experiment with different nvidia drivers. I started out with the 197.57 version of the driver. I decided also to not tweak any graphics card settings. This is purely out of the box configuration.With FSX, all I changed was my screen resolution and set my framerate to unlimited. I fired up FSX, put myself in parking spot #1 on the ramp at CYVR and fired up TrackIR. I run FSX mostly in Full Screen mode so that's all I tested so far.Using trackir, if I move my head quickly, there is noticeable tearing on the screen. I exit FSX and implement the fix I found on Avsim. I add the following to my [GRAPHICS] section in FSX.cfg file:ForceFullScreenVSync=1Fire up FSX. No tearing to be seen. Fire up SquawkBox 4 and couldn't see any tearing. That's great. Usually I would see it right away. I happen to run some newer games on this machine and wanted to run the latest drivers to take advantage of some bug fixes or improvements for some of the other games I play so I upgraded the driver to the 258.96. I removed the VSync line above from the file to ensure I could see a difference between having that line in or out of the file. Fire up FSX and can confirm the tearing, I put the line above back into the file and the tearing goes away. Fire up squawkbox and there is some tearing of the screen. Not as much as having vsync off but enough that it's noticeable. Read some people were having problems with the latest driver so I downgraded to 257.21. Still had the same outcome I experienced with the other driver. I really didn't want to downgrade to the 197 driver so I tried changing my framerate slider in FSX from ulimited to 90. BAM! No more screen tearing again with SquawkBox running. I moved it back to ulimited and saw the problem again.I know from my last tests that forcing the vsync in the card driver gave me the same results. Before I reinstalled my system I tried using FPS_Limiter to limit my framerate down to 30 but it did not have any effect. I also had the BP=0 fix applied and it was no help.It could be that my 9800 GTX+ is getting overwhelmed with the speed that my trackir is moving but it seems if I just drop down from unlimited even to 90FPS using the slider that my vsync problems go away. I think I'll stick to the 257.21 driver for now even though I may be able to use the 258 driver.I hope this helps others that may be experiencing this problem with vsync.Now that I have things sorted out I'll be doing some further experimentation and configuration tweaks to get my system back up and running to full power again.-Jason

Hi,After install of nvidia 258.96 driver and the tweaks with Nvidia Inspector I got a problem. When I'm going to the outside of the plane and go back to the VC , the PD of the MD11 won't refresh.Switching to 2D cockpit and back to VC solves the problem but this is not how it should be.Edward Smeets

Hi,After install of nvidia 258.96 driver and the tweaks with Nvidia Inspector I got a problem. When I'm going to the outside of the plane and go back to the VC , the PD of the MD11 won't refresh.Switching to 2D cockpit and back to VC solves the problem but this is not how it should be.Edward Smeets

This has been a problem with nvidia drivers for as long as I can remember

Hey guys, just did a clean install of windows 7 x64. Going to install the new 258.xx drivers and test this out. I wonder if the guys at nhancer will come out with 2.6.x anytime soon. I am sure it's a long difficult process, I am just glad I can wait from a distance.-Justin

Well, didnt they lose all the source code and every single line have to be written again from scratch? I wouldnt hold my breath waiting for that, you'd have to be exceptionally motivated to be able to rewrite something like nHancer from scratch.

Well, didnt they lose all the source code and every single line have to be written again from scratch? I wouldnt hold my breath waiting for that, you'd have to be exceptionally motivated to be able to rewrite something like nHancer from scratch.

Yea I think I heard something about that on their forum. I guess that really sucks for whoever has to rewrite all that code. I guess I'll put it on my xmas list this year.-Justin

Well, didnt they lose all the source code and every single line have to be written again from scratch? I wouldnt hold my breath waiting for that, you'd have to be exceptionally motivated to be able to rewrite something like nHancer from scratch.

I don't think the source code was lost, Martin had a water cooling accident that destroyed his three GTX 480s he had in SLI. His explation for nHancer 3.0 taking so long is that he does this in his spare time for free, so there has to be something of interest to him in doing it - for him, that means rewritting the program using the new Windows Presentation Framework that Microsoft recently released for making GUIs vs. the old version that used .NET.

Hi,After install of nvidia 258.96 driver and the tweaks with Nvidia Inspector I got a problem. When I'm going to the outside of the plane and go back to the VC , the PD of the MD11 won't refresh.Switching to 2D cockpit and back to VC solves the problem but this is not how it should be.Edward Smeets

I definitely have never seen this myself Edward, don't know what to tell you.

I don't think the source code was lost, Martin had a water cooling accident that destroyed his three GTX 480s he had in SLI. His explation for nHancer 3.0 taking so long is that he does this in his spare time for free, so there has to be something of interest to him in doing it - for him, that means rewritting the program using the new Windows Presentation Framework that Microsoft recently released for making GUIs vs. the old version that used .NET....

Oh ok, I thought the water accident destroyed his hdd as well. Either way, he's rewriting from scratch.

Guys, please see my edit to the original post - Nvidia Inspector 1.93 is a huge update and basically does everything nHancer used to do and more with a full GUI, no more cryptic names etc.

Nice! Thanks for keeping tabs,,, Tabs :(

Guys, please see my edit to the original post - Nvidia Inspector 1.93 is a huge update and basically does everything nHancer used to do and more with a full GUI, no more cryptic names etc.

Hi Ryan,What is the best way to update to Nvidia Inspector 1.93 from the earlier version. Also have you some screenshots of the new program with settings?ThanksAndrew Dixon