tunnelcat

Got it. I obtained the .dll from the link provided by the original poster, but I was confused by his renaming instructions. The one I have is the proper version number for Vista. Thanks.

OK, I'm a little confused. Why do we need to rename the downloaded .dll? There is no copy of this .dll in my FSX folder and I don't intend to put it in any Windows System folder. I have a downloaded copy with it's proper name sitting in another Document folder ready to put into my FSX main folder, so I need some clarification.

That sure looks like a driver issue. If you let Microsoft update your video drivers, it may have corrupted something. I NEVER let Microsoft update an Nvidia video driver, after I "accidentally" didn't see one listed in the important updates sections and let it install one. What a mistake. No more. I always do manual updates and I always "hide" the video driver updates so they don't pester me anymore. What driver version did you finally end up with? Also, you may want to read through this very detailed post about updating Nvidia's drivers. You may be able to recover things with his instructions. It's either that, or go back to the driver you were using before things epically failed. http://www.evga.com/forums/tm.aspx?m=1776353&mpage=1

Hmmmmm. I'm also using 310.90 at the moment. I was going to migrate up to the next WHQL because 310.90 had issues with SLI configurations, which I don't have anyway. I haven't been flying since I installed it on my GTX 680 a few weeks ago. I'll give it a whirl with FSX before I change drivers.

I'm about 2 driver revs back from the most recent and Microsoft tried to bozo anther one on me this time, AGAIN. I'm "guessing" they want to make things work better for Win8, which I don't have nor do I ever want. I finally got tired of it and "HID" the update. fppilot, what Nvidia driver version did you find worked best for FSX? By the way, to all Nvidia GPU users, Nvidia changed the way they update drivers. Driver updates from the Device Manager no longer work and driver rollbacks no longer work. I really messed up my system doing just that. Here is the "approved" way to either update or go back to an earlier driver. Read this guy's instructions to the letter. Also, MAKE SURE you do a "custom install" so that you can choose the specific items you want. Nvidia loves to install a bunch of crapware most users don't need. And most people only want the graphics driver, and if you have other games, PhsyX. If you ARE NOT using the graphics card's built in sound chip via HDMI, in other words, you have a separate sound card or motherboard-based sound chip, DO NOT INSTALL THE NVIDIA SOUND DRIVER. It will save you an airplane load of headaches and black screens. http://www.evga.com/forums/tm.aspx?high=&m=1776353&mpage=1#1776353

If she hates Win7, she would just looooooove Win8.....NOT! All you XP users are going to be out of luck come 4/8/2014. Microsoft is ending their support for it next year. And if you want something remotely close in appearance and function, Win7 is still being sold, for now. My husband is still using an XP machine, but he's now thinking of getting a Win7 rig before Microsoft nixxes that deal and forces everyone to Win8. http://windows.microsoft.com/en-us/windows/end-support-help I also do not allow automatic updates. I still got burned one time because I didn't scan the list of updates very thoroughly before hitting "install" and I didn't notice that Microsoft had put a graphics driver for my Nvidia card in the mix. When that installed, what a mess, since I had PrecisionX running to control my card's fan. Really borked up my system. Had to go do an uninstall Microsoft's video driver, PhysX and PrecisionX, clear out the registry of left over junk, then reinstall the new drivers and software. I was not a happy camper. What's scary is that Microsoft is still sticking video drivers in "Important updates", so watch out. An I uninstalled that update on all of my Win7 rigs. I'll wait for Microsoft to fix the mess.

Oops, you're right. AMD does not support hyperthreading. I've been using Intel too long. :huh: I've noticed that Process Monitor has been recomended. It's a wonderful tool, but the learning curve is very steep. It logs everything unless you know how to set the filters and I've had some difficulty because of the overwhelming information. It can be done with a little persistance. I was using it to find out which service or program was not unhooking from my registry and causing a temporary account problem when I logged off and back on. There is another tool called Process Explorer, from Windows Sysinternals as well, that may help you too. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx This tool shows you everything that's loaded in the background and when it starts and if it's running. You can then go to this guy's link and see which Microsoft services are safe to disable for your OS. http://www.blackviper.com/

"deleted"

Isn't this the FSX hyperthreading issue? If you have a computer with mulitple hyperthreaded cores, doesn't this stuttering problem occur specifically with FSX? I sure notice it on my system when I have it enabled. I've taken to turning it off whenever I run FSX to smooth things out. I've looked into getting Process Lasso to make this easier to do, but I'm unsure of how to use it, so right now, I turn hyperthreading off in my BIOS whenever I want to do a long stint of FSX.

I'm running Ultimate Defrag and it's working fine. It is a very complicated program to use though and it took me awhile to get a system going I like. What options do you have set? In the "Settings" section, I'm using the High Performance Option with Custom [select Files], sorted in the order I want them on the drive and then I make sure select Strict Placement, Sorted by [DEFAULT]. This will make sure the folders are sorted in the way you actually listed them. In the "Options" section next to the Defragment Mode, I checked "Respect High Performance" and "Respect Archive" (which places all my preselected rarely used files to the center of the drive to get them out of the way) and "Put Directories Close to the MFT" (for faster file table lookups). My only caveat with this program is that it really stresses the drive because of all the file moving around. I've heard of people complaining that this program trashed their drive. So what I did was have one drive specifically dedicated for FSX because it's so huge of a program. I sorted the folders to put the textures and other scenery and weather at the top of the list and the first part of the drive. Then I put FSX after that. Once I get everything defragged, I rarely run the full job again. What I usually do is then run "Fragmented Files Only" and that's very quick and doesn't do a lot of moving of files around.

Thanks, I'll take a look at 'process lasso'. Pardon my ignorance, but does RW3 mean?Also, should I be using the affinity mask setting in my FSX .cfg file as well? It seems from reading around that this and turning off HT, are 2 of the most important tweaks for getting FSX to run at it's best.

Just another question here. I have quite a few other games on the same rig that has FSX on it. Would turning off HT impact the performance of those as well? I too have noticed those irritating stutters while flying in FSX and I would like to try turning off HT to see if that solves the problem, but I don't want to negatively impact my other games in the process.

Remember a few years back when Avsim was unfortunately compromised and everyone started getting loads of email spam? Well, the Feds and Microsoft solved the problem for us. They brought down the Rustock Botnet and all, and I mean ALL the spam I was getting in that one particular email account (the one I'd been using for Avsim) disappeared and vanished completely THE NEXT DAY! I know the spam originated from the Avsim attack because I'd never gotten spam in that account before that incident. I am soooooo grateful. Anybody else notice a drop in their spam load?http://krebsonsecurity.com/2011/03/rustock-botnet-flatlined-spam-volumes-plummet/

Ok everyone, I've got things working with the new settings. Looks pretty good too! Thanks!Kim

Slick9,Just got through installing Nvidia Inspector and setting up FSX after a few days of messing around with it. Here's a couple of tips for decent frame rates and a good looking image.Be sure to set Water to '2.0 low' in the graphics section. Turn off almost all moving land vehicles, but you can leave some boats, about 10 -15%. You'll have to experiment with other settings to see what gives you decent frame rates with your card. Turn OFF AA and turn ON 'Trilinear Filtering' WITHIN FSX. Also limit your frame rate to 30fps. There is an outside FSX frame limiter program that helps with more stable frame rates, but I haven't messed with that yet.Now OUTSIDE FSX, run Nvidia Inspector (I got my copy from Guru 3D). Now go to the PMDG Support Forum at Avsim and then to the PMDG General Forum. Click on the sticky link on "How to set AA in FSX/FS9". The first section has an image of the settings you'll need to make. Make sure you have MS Flight Simulator X selected from the pull down menu in Nvidia Inspector before you change and apply things. Seems to working for me now after going through a bunch of searches to get all the right info. Here's a link to NickN's post about using Nvidia Inspector as well and you can compare his settings with PMDG's. The only thing I did different from his settings was to set 'Antialiasing - Transparency to 4xSupersample' which was mentioned in the above PMDG settings. I'm not sure if AA transparency will work with the Nvidia 460, so be careful. You also may have to lower AA to 4x if your card can't handle it.http://www.simforums.com/forums/fsx-and-nhancer-settings-for-new-drivers-updated_topic36586.htmlOne other thing I did differently was to force V-sync ON. I absolutely HATE the horizontal image tearing that shows up with it turned off. I have a horse of a machine, so I hope it works out in the memory department. I'll see if these settings give me any problems, but after a little tweaking, so far so good. I even have max 4096 REX2 cloud textures running, at Kai Tak with the PMDG 747 at about 25fps too!

Well, those settings locked up FSX when I exited the flight. Never had that happen before. Had to end the process from the task manager just to get out of the sim. Looked good while I was flying though. :Cry:Does anybody have a good list of graphics settings and tweaks for FSX that would work on a newer i7 960 Win 7 64 Bit machine with a Nvidia Geforce 480 1.5GB card? I've tried all sorts of settings and .cfg tweaks and I still get some blocky ground textures and the nasty V-sync tearing across the screen when I turn my aircraft.

Great! I'll give Inspector a whirl!Kim

Something similar along those lines. I've been perusing the 'Disappearing Textures Fix' thread and all the work Ryan and Bojote have done to solve the problem. How does using Nvidia Inspector conflict with the recommendations from Bojote with those in this thread, when Bojote says to ONLY use the Nvidia Control panel, not Nhancer or Inspector, and to set things WITHIN FSX? And since FSX doesn't say what AA level it uses, how do you know what AA level it's displaying? It's all getting so overwhelming! I'd just like to fly my Queen, not replace the engines!Kim

Oh gaads! I forgot all about that! I'd set it to 'auto rudder' when I was trying out a stick with no rudder pedals the other day and I must have forgot to set it back. I've got to remember to turn off auto mixture too! Doh! :(

This may be a little nit-picky, but with my old FS9 747-400 Queen of the Skies, the nose gear would turn with the rudder pedal inputs when taxiing. Not so with my FSX 747-400X Queen. It stays straight no matter which way I turn. I know that nose gear tiller steering is not modeled in this aircraft, but shouldn't the front gear at least turn when steering the aircraft on the runway with my pedals like it used to in the older aircraft? I'm I missing something?Kim

The toe brakes are probably still an AXIS function because that allows for differential brake application pressures, depending on which brake you press and how far you depress those brakes. I'm betting that the left toe brake is the A axis and the right toe brake is the Y axis for all types of rudder pedals. First, make sure your controller is calibrated, either through Windows or some Saitek program, then go into the controller screen in FSX, then select the 'controller axis' tab. Make sure your controller is selected in the pull down menu before you set things. Then click on the left toe brake line and then the 'change assignment' button. When the little window comes up, just press the left toe brake to set. Repeat for the right toe brake. Also make sure you check the 'reverse' box and make sure it sticks. I've had those check marks disappear sometimes. Make sure you don't move the Z or swivel axis just yet when setting the brakes. After you set the toe brakes, then go down to the rudder axis line, select it and click on 'change assignment' again. Then move the Z axis or swivel part of your controller and that should be selected as well.If that works for you, then you need to set 'sensitivities' in the calibration tab. Also make sure the rudder pedals are selected in the pull down menu. I ended up setting all three axis sensitivities all the way to the right. With the 'null zone', I had to set it about 1/3 of the way to the right for my brakes because of some sloppy analog pots that kept sending out spurious noise which kept the brake warning flag on. You can set the rudder 'null zone' a lot less for better control. Hope this helps. If I'm wrong, may a Saitek owner please come forward. ^_^

Yeah, the CM program does a very good job of calibrating those sometimes sloppy analog pots that CH Products puts in their controllers. If you can learn the scripting in the CM, you can program quite a bit of functionality. I've been lazy so far and just downloaded some pre-made scripts that others took the time to create. But I think I'm going to take the time and learn how to do it. There are some good tutorials over at the CH forums if you want a guide.

What brand of rudder pedals are you using. I think my CH rudder pedals show up like this in the 'Control Axis' section:A axis is the left brake with 'reverse' checkedB axis is the right brake with 'reverse' checkedZ axis is the rudder inputBut let me double check.As far as I know, there are no 'button' or 'keys' settings and I'll have to go back into FSX and see what my sensitivities are set to. I'll go fire up the sim and take a look for you and post back. <_<

What driver version do you have? If it's over 2xx.xx, you can't use Nhancer, yet. All us new Nvidia driver users will have to wait until version 2.60 comes out. You can use NVIDIA Inspector, but I've heard that it's a little harder to use. If you want to wait for the newest version of Nhancer, here's what I did in the meantime:Here's the settings within my Nvidia Control Panel. I made these settings apply only to FSX, not globally. You may want to lower the AA setting if your frame rates tank. My 480 even has trouble with REX2:Antialiasing - Mode to 'Enhance the application setting' and then ticked the antialiasing box within FSX (be sure you do this or AA won't work)Antialiasing - Setting to '8xQ'Antialiasing - Transparency to 'Multisample'Anisotropic Filtering - '4x'Texture Filtering - Anisotropic sample optimization 'ON'Texture Filtering - Negative LOD Bias 'CLAMP'Testure Filtering - Trilinear optimization 'ON' (Set 'trilinear filtering' within FSX too)See if these work for you. Here's the NVIDIA Inspector link from Guru 3D if you want to try it out.http://downloads.guru3d.com/NVIDIA-Inspector-1.94-download-2612.html

To even get a snowball's chance in heck for the throttle quad work right, you have to use either the CH Control Manager 4.51 or FSUIPC. Now the Control Manager program should have come on a disk with your controller. If you want to go that route, first, plug in all CH products controllers you own to make sure all the Windows drivers are installed (I'm assuming you have Windows 7 or Vista. XP is a nightmare of driver windows that get thrown into your face). If that has already happened previously, then install the Control Manager WHILE the controllers are still plugged in. After the install, remove the disk and reboot, leaving the controllers plugged in. When you're alive again, launch the Control Manager and add all your controllers with the 'ADD' button at the top. You will have to add each controller you own from the drop down list one at a time. Then click on 'SAVE' and name this map some name. Next time you launch the CM, click on the LOAD button and load your map. Then you have to click on the 'download' button to get things to talk between the CM program and the Windows controller applets. This is where you can now calibrate your controllers. The calibration is MUCH more accurate through the CM than the Windows applet and since I have 4 CH controllers, it's a Godsend for other sims I own. In fact, if you install CM, don't ever use the Windows applet ever again with CH products. The only problem is that in order to have the reverse thrust work with the levers, you will have to learn how to do the scripting that is part of the CM program. Now if you're not into scripting or learning how to do it, you can get premade script maps from members of the CH forums, and some of them are pretty good.Now a much easier method would be to use FSUIPC. But in order to set up your controllers within FSX or FS9, you will need to purchase the full version from Pete. The freebie that comes with some add-on aircraft is locked out for controller setting. If you own the full version, you can set all the functionality of your controllers inside the sim much more accurately, including reverse thrust. The only reason to use the CM program is if you own other types of sims that don't use FSUIPC as an intermediary between the controller and the sim. Here's some links for you:http://www.ch-hangar.com/forum/index.php?showforum=32http://www.schiratti.com/dowson.htmlKim