Archived

This topic is now archived and is closed to further replies.

Aerah

Some dll´s you might need.

Recommended Posts

Regarding Win7 64 systems: This is probable old news for most of you, but if there are anyone out there who missed this it might be of some help. I have played with the NGX some time now, and I have yet to experience any CTD (knock wood). My suspicion is that putting these dll files into the FSX root folder will actually increase overall stability. This is not scientifically proven though...but it wont hurt either. The reason for my claim is that before getting hold of these dlls, I would experience CTD with 90% predictability when fiddling with FMC on the MD-11. And after I put these into the FSX folder I could no longer produce CTD no matter what I did with the FMC (even adding lots of various FIX points witch was a guaranteed killer). So here are the files: msvcp71.dll (version. 7.10.3077.0)msvcr71.dll (version 7.10.3052.4)UIAutomationCore.dll (version 6.0.5840.16386) Hope this help.Robert

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

If you really want to copy these dll's to another location ( and there should really be no need to do so), it makes more sense to copy them to your FSX directory, if you want FSX ( and it's addon dll's) to be persuaded to us them. That being said, it is totally unnecessary to do this. Geoff

Share this post


Link to post
Share on other sites

Either they are somewhere on your computer (just search), or you must download them (just google). Robert

Share this post


Link to post
Share on other sites
Either they are somewhere on your computer (just search), or you must download them (just google). Robert
If you start downloading odd version of dlls from the internet, and just COPYING them into Windows, GOD HELP YOU,You can look forward to re-installing windows. Geoff

Share this post


Link to post
Share on other sites

As long as you utilise common sense when downloading/placing DLLs, you should be fine. This sounds like the exact problem I'm having, I already have the automationcore but I'll try the others, thanks.

Share this post


Link to post
Share on other sites
Regarding Win7 64 systems: This is probable old news for most of you, but if there are anyone out there who missed this it might be of some help. I have played with the NGX some time now, and I have yet to experience any CTD (knock wood). My suspicion is that putting these dll files into the FSX root folder will actually increase overall stability. This is not scientifically proven though...but it wont hurt either. The reason for my claim is that before getting hold of these dlls, I would experience CTD with 90% predictability when fiddling with FMC on the MD-11. And after I put these into the FSX folder I could no longer produce CTD no matter what I did with the FMC (even adding lots of various FIX points witch was a guaranteed killer). So here are the files: msvcp71.dll (version. 7.10.3077.0)msvcr71.dll (version 7.10.3052.4)UIAutomationCore.dll (version 6.0.5840.16386) Hope this help.Robert
The advise now from both REX and Orbx is to delete the uiautomationcore.dll file from both your System 32, SysWow and FSX folders (just renaming them .txt instead of .dll, so you have it for backup).They are suspecting that this file has been causing FSX crashes.I'm having trouble with the REX weather engine now and getting crashes during flights, usually right when I make a mouse-click. First thing REX asked is if have have deleted the uiautomationcore.dll file from my root FSX folder yet.I don't have it there, so that's not my problem, but I did delete if from the SysWow folder after taking ownership of it and I believe that has stopped my crashes from Orbx scenery.

Share this post


Link to post
Share on other sites

I use REX to give me looks and Active Sky Evolution to give me weather. No problems for me there. (I also use ORBX scenery btw). NB! I added the version data for each file to make sure you get the right one. Robert

Share this post


Link to post
Share on other sites
If you start downloading odd version of dlls from the internet, and just COPYING them into Windows, GOD HELP YOU,You can look forward to re-installing windows. Geoff
You are not supposed to copy them into the Windows folder. They are meant to be copied into your FSX folder. Robert

Share this post


Link to post
Share on other sites

Gonna give that a try, renaming it in the sys32 folder.

Share this post


Link to post
Share on other sites
The advise now from both REX and Orbx is to delete the uiautomationcore.dll file from both your System 32, SysWow and FSX folders (just renaming them .txt instead of .dll, so you have it for backup).They are suspecting that this file has been causing FSX crashes.I'm having trouble with the REX weather engine now and getting crashes during flights, usually right when I make a mouse-click. First thing REX asked is if have have deleted the uiautomationcore.dll file from my root FSX folder yet.I don't have it there, so that's not my problem, but I did delete if from the SysWow folder after taking ownership of it and I believe that has stopped my crashes from Orbx scenery.
Quite strange that.I have sometimes got CTD while moving within FSX menu and read about the uiautomationcore.dll fix. Since I put into the root folder that .dll I have never had CTD when moving in the FSX menu (Praying.gif ).Bye.

Share this post


Link to post
Share on other sites

Regarding msvcp71.dll & msvcr71.dll , I was reading elsewhere that taking ownership of these files in their original location fixes the crashes also. It's working for me so far, I'm just not very knowledgeable about problems that might arise from taking ownership of system files.

Share this post


Link to post
Share on other sites

This seems to have actually fixed my CTDS, none yet... managed to do a few full flights. Thanks!

Share this post


Link to post
Share on other sites

I hope more people would try this out since it seems like a very promising solution to various CTDs, especially regarding manipulating the FMS in PMDG aircrafts. Robert

Share this post


Link to post
Share on other sites
You are not supposed to copy them into the Windows folder. They are meant to be copied into your FSX folder. Robert
OK, that makes a lot more sense. MY BAD - I missed that "FSX Folder" part in your original post. Having the CORRECT (or suitable versions) in the FSX directory will force their use, if a suitable version is not being specified in the dll's manifest. Loser.gif

Share this post


Link to post
Share on other sites
Were is the "great" PMDG support on this theory?
Another school of thought one can find on the internet is exactly the opposite to yours regarding the uiautomationcore.dll's It says to delete all of them and not to believe any other suggestion. To be honest, I'm about to beleive neither of them at this point. I have been living in Placebo land for a while i think

Share this post


Link to post
Share on other sites
Were is the "great" PMDG support on this theory?
Placebo=snake oil, voodism. None of which are a substitute for proper coding!
Randy, I haven't quite been able to figure out your motives here on the forums lately. Calling me an Intel ###### over in the hardware forum because I said they were faster than AMD's offerings, bringing stuff like this into here. So I'll bite the troll and ask. What are you getting at? I could be misunderstanding some things, but I doubt it...

Share this post


Link to post
Share on other sites
Placebo=snake oil, voodism. None of which are a substitute for proper coding!
You're directly calling me a liar then and going against a ton of evidence to the contrary (including Microsoft support on the MSDN forums). If I use the default Win7 uiautomationcore.dll and sit and bring up the right click menu about 20-30 times in a row, the sim crashes. It does not do that with the Vista 32 version, which is what I recommend people put in their FSX root folder. This is not a PMDG issue we can fix with "proper coding" - it's a Microsoft problem and happens with any airplane. The situation builds up over the course of a flight as you use the menus and switch views and will eventually result in a crash that can look like it was triggered by something else. Regarding the other two files I have no specific information - those are Visual Studio runtimes presumably used by FSX itself.

Share this post


Link to post
Share on other sites
You're directly calling me a liar then and going against a ton of evidence to the contrary (including Microsoft support on the MSDN forums). If I use the default Win7 uiautomationcore.dll and sit and bring up the right click menu about 20-30 times in a row, the sim crashes. It does not do that with the Vista 32 version, which is what I recommend people put in their FSX root folder. This is not a PMDG issue we can fix with "proper coding" - it's a Microsoft problem and happens with any airplane. The situation builds up over the course of a flight as you use the menus and switch views and will eventually result in a crash that can look like it was triggered by something else. Regarding the other two files I have no specific information - those are Visual Studio runtimes presumably used by FSX itself.
im Not Worthy.gif anddddd Tabs saves the day once again. Oh Great Tabs! We worship thou!

Share this post


Link to post
Share on other sites
You're directly calling me a liar then and going against a ton of evidence to the contrary (including Microsoft support on the MSDN forums). If I use the default Win7 uiautomationcore.dll and sit and bring up the right click menu about 20-30 times in a row, the sim crashes. It does not do that with the Vista 32 version, which is what I recommend people put in their FSX root folder. This is not a PMDG issue we can fix with "proper coding" - it's a Microsoft problem and happens with any airplane. The situation builds up over the course of a flight as you use the menus and switch views and will eventually result in a crash that can look like it was triggered by something else.Regarding the other two files I have no specific information - those are Visual Studio runtimes presumably used by FSX itself.
Hello Ryan, hello guys,I have recently had to format FSX drive and unfortunately did not save that file. I have yesterday copied the W7 default file. Where to download the Vista version? Thanks, bye.

Share this post


Link to post
Share on other sites

I've had two CTD's recently while taxiing with the NGX, both attributed to "ntdll.dll" - both at FSDT's KLAS airport.Think throwing that dll into my FSX folder will help stop the crashing?

Share this post


Link to post
Share on other sites
I've had two CTD's recently while taxiing with the NGX, both attributed to "ntdll.dll" - both at FSDT's KLAS airport.Think throwing that dll into my FSX folder will help stop the crashing?
Put in the uiautomationcore.dll one in the main root FSX folder. Make sure it is the same one as above version ...Just finished a flight from Aerosoft's Corfu good 3 and half hours not one single issue.. :)

Share this post


Link to post
Share on other sites
Put in the uiautomationcore.dll one in the main root FSX folder. Make sure it is the same one as above version ...Just finished a flight from Aerosoft's Corfu good 3 and half hours not one single issue.. :)
Please say, what are your settings in fsx.cfg:TEXTURE_MAX_LOADLOD_RADIUSThanks

Share this post


Link to post
Share on other sites
Put in the uiautomationcore.dll one in the main root FSX folder. Make sure it is the same one as above version ...Just finished a flight from Aerosoft's Corfu good 3 and half hours not one single issue.. :)
At the time of my CTD, I had the uiautomationcore.dll (Version 6.0.58) in my root FSX folder. The CTD itself pointed to NTDLL.DLL as the cause of the CTD - so I'm wondering if I should put a 32Bit NTDLL.DLL file in my Root FSX folder to gain protection against it crashing as I did with the uiautomationcore.dll .

Share this post


Link to post
Share on other sites