Jim, do you use the basic or advanced settings?

 

Hi Ted,

 

I used the Advanced settings with AA unchecked in the Fsx.cfg and filtering to Bilinear.  I just recently installed the DX10 Fixer and that utility reenabled AA.  I fly 99.9% of the time with MSE V2 photoscenery.  My photoscenery is crystal clear but I am seeing some minor stuttering.  I did not employ any of the tweaks or settings recommend by Nick in the Fsx.cfg except the AA and filtering settings.  I tried with the BufferPool setting once and it made things worse as far as fps.  The only tweaks I have employed in the Fsx.cfg is to raise the LOD_Radius to 6.5 and the Texture_Max_Load to 2048.  Of course I also have DX10 enabled.

 

Best regards,

Jim

 

 

 

Only a few hours ago I used Paul J's guide to set it up with the MS FSX Profile.Guess what? All of sudden Nvidia or something has now wiped all those settings and taken it back to Global_Driver_Profile.

 

Hi Rick,

I remembered you were downloading the .nik file from Paul's website and you were going to import that into your NI.  Well, if you imported it properly, you also need to hit the Apply button and that will save the settings in NI.

 

 

 

And all I did since a few hours ago is carry out Windows Updates, suffer a CTD with that ntddll.dll error.

 

Do you have the Uiautomationcore.dll in your main fsx directory?  If so, remove it.  Put it in a temporary directory and then run FSX again.  I just had an ntdll.dll error too and removed the Uiautomationcore.dll from my fsx folder (I did NOT put it there.  Some recent software program installed it and I suspect PMDG).  I tried the exact same flightplan/situation and no ntdll.dll crash.  I would just be interested to see if this fixed your ntdll.dll crash too.  I plan on trying to replicate the crash by putting the Uiautomationcore.dll in the main fsx folder again and see if I can get the crash.  The Uiautomationcore.dll is part of the Microsoft.net framework package that developers use to make sure their application runs properly as intended including managing memory for the application.  This dll might be conflicting with the latest Microsoft.net (4.5) Uiautomationcore.dll that the developer used to manage his application.  Microsoft.net framework packages are not backward compatible.

 

Hang in there!

 

Best regards,

Jim

That FSX doesn't work in alt-tab has been in the nvidia notes FOREVER.  It's a random thing but sometimes if you alt-tab you can't get back.  The easier solution?  Just alt-enter to temporarily go to windowed mode

No problems at all with the driver here.

This is beginning to get crazier by the minute. I decided to check Nvidia Inspector. Only a few hours ago I used Paul J's guide to set it up with the MS FSX Profile.Guess what? All of sudden Nvidia or something has now wiped all those settings and taken it back to Global_Driver_Profile. ....

 

That's normal behavior of the nVidia Inspector. If you start it and switch to the profile window you will ALWAYS shown the global profile. But there where you see the profile name it's a drop down menu and you may see many, many profiles in alphabetical order. Scroll down and you may find "MS Fligh Simulator X". Click on that and you got it and now you see what you have for FSX.

Spirit

That's normal behavior of the nVidia Inspector. If you start it and switch to the profile window you will ALWAYS shown the global profile.

 

So, what in effect you are saying is that even after I have done the Apply Changes, it immediately reverts to Global profile, and the MS FSX Profile ONLY gets applied when the sim is running?

Do you have the Uiautomationcore.dll in your main fsx directory?

 

No, Jim, it's in my Windows/system32 folder where Paul's/ and Nick's guide recommended it should go. And how astute of you to suspect it being in the FSX Main Folder, because I've just done a search, and sure enough it is there. Will remove it as advised. Included in the latest batch of Windows Update was a .NET update. Thanks for your words of encouragement, Jim.

 

How can I abandon this hobby after the amount of cash I've spent on it? It's an obsession now. And the best part about it is that there is this Forum where there are so many people like yourself and Paul, and others too, who go that extra mile to help flounderers in this sea called FSX.

 

 

I remembered you were downloading the .nik file from Paul's website and you were going to import that into your NI. Well, if you imported it properly, you also need to hit the Apply button and that will save the settings in NI.

 

Yes, I did download Paul's .nic file but as I had already run his NI Guide, I did not import it as you had pointed out in a previous post where it ought to go. Will do so now.

 

I've not touched the FSX.cfg after the last Paul's Guide tweaks, i.e. Buffer Pool, etc, and have as per Nick, unchecked the AA setting in Display,and am using Trilinear.

 

Will report back much later this evening.

 

Thanks to everybody else not acknowledged in this thread.

So, what in effect you are saying is that even after I have done the Apply Changes, it immediately reverts to Global profile, and the MS FSX Profile ONLY gets applied when the sim is running?....

That's the way it is. One can have different profiles for many different games and it's connected through the name of the main program (fsx.exe).

Spirit

That's the way it is. One can have different profiles for many different games and it's connected through the name of the main program (fsx.exe).

Spirit

Thanks for that clarification. Sigh of relief, now!

Thanks for that clarification. Sigh of relief, now!

You're very welcome. :rolleyes:

Spirit

 

 

No, Jim, it's in my Windows/system32 folder where Paul's/ and Nick's guide recommended it should go.

 

You might want to take another look at those guides VC10Man.  I read them both as saying to put the UIautomationcore.dll in the FSX directory.

 

Jim, thanks for the feedback. Now I ought to stop derailing this thread and let it get back to the new drivers.

 

Ted

Thanks for this, Ted - correct.

 

UIAutomationCore.dll version 6.0.5840.16386 goes into the root folder of FSX - where fsx.exe lives. It should NOT be placed anywhere else in the computer, nor should it be registered (regsvr).

 

This version - 6.1.7600.16385 - is the original Windows 7 default file, and should not be touched.

If you have already put the "FSX version" one (the top one) in the Windows system folders - you can use this 6.1.7600.16385) one.

 

Version 6.0.6001.18000 does work, but it is the wrong one, and will cause occasional freezes, hanging FSX.

Version 6.0.6001.18000 does work, but it is the wrong one, and will cause occasional freezes, hanging FSX.

 

Thank you for this!

 

Not DX10 related in my case, but i spent some time today trying to find if there is a some problem with 6.0.6001.18000 version. There are many recommendations on the internet that we should use "6.0.5840.16386 or higher". Well, no! No higher. Only 6.0.5840.16386 realy works without any problems. In my case, FSX menu(and whole FSX actualy) is more responsive with 6.0.5840.16386 - which results in better smoothness too

Okay, gents, thanks for that. I'm getting confusing messages here. Somewhere along the line, a long while ago, I remember somebody advising that that UIAutomationCore.dll should be placed in the Windows/System32, which is why I placed it there. If my memory serves me right, I also recall there were one or two workarounds to TakeControl, etc, regsvr, etc,etc.

 

Okay, I will follow the advice here. Doing it right now.

 

Compared to yesterday's tear-my-hair-out frustration at losing a flight, today, touch wood, same flight, Emirates 777-200LR Dubai-Manchester, well into 5 hours of this flight,and so far at 40k, no gremlins.

Hi Rick:

 

Good stuff. "same flight, Emirates 777-200LR Dubai-Manchester, well into 5 hours of this flight,and so far at 40k, no gremlins."

 

Yeah - that "fix" of putting it in the two major Windows 7 System folders was profligated by a Microsoft support person who didn't know what the ramifications would be. As you see - because FSX was tested with Vista (by Microsoft) - the Vista UIAuto...blah works with FSX... but fsx was never tested with Windows 7, and there was a change in that file. If you put the old Vista version into Windows 7 - any Windows 7 - certified programme that uses UIAuto...blah - will hang, crash, fail or otherwise stop working - just as FSX stops working with the Windows 7 version. We can't just replace system files with any old file, so - our version goes where FSX looks first - in it's own backyard - the FSX root folder.

 

All the Best, :wink:

 

peej

　

　

I'm giving this one a miss as in the 327.23 notes it says:-

 

Flight Simulator X–pressing Alt+Tab to switch to the desktop does not work. [293729]

 

Can anyone confirm this or does it work for them using this driver?

 

This has been on NVIDIA driver release notes for a long time, and they also have 4 Flight Simulator X references.

Paul J, thanks for the interesting info about the UAu..blah

 

What I can't stop thinking about is why, in some installations, including my own, run for a year plus with absolutely no issues without adding the UA... I can seriously mess with my FSX Acc, click around like a maniac, literally for hours, and I simply can't get it to hang.

 

One should think that when so many people get their salvation from this, it should be consequent. One of those things I guess