What can cost this problem, I have also model 35 and evrything is ok but A36 have the gauges but no aircracft as per pictureplease adviceThank youHappy LandingJacek

Could be a protection thingy. Did you enter the code right and ran the installer 'as admin' with a right click? Also turn off your antivirus software for the time installing and disable the Windows UAC. Sorry, general tips of some sort, but they help on most installing issues, which I think this one is.You've started two threads on this, right?

Do you have Ezdok Camera installed ? If yes, remember to always run the EZCA config after you install a new aircraft...the pics above are typical of not having done it.If you haven't got EZCA I don't have a clue....Regards

I've had this happen as well with other planes, but it is not related to the initial install. For instance after several flights in the C208 Caravan by Carenado the interior textures disappeared and gauges were no longer operating.

If you have Windows Vista or 7 - 64 bit Download UIAutomationCore.dll from here:http://www.mediafire.com/?mik2mlqdz1wDrop the UIAutomationCore.dll file into the FSX root folder. While your in the root FSX folder, hold down the shift key and right click, select "open command window here" from the list of options. Copy and paste this:regsvr32 UIAutomationCore.dllinto the Command Window. Press EnterAdd this line to your [graphics] section of your FSX.cfg file:HIGHMEMFIX=1These two steps should fix your problem.Kind regards,

If you have Windows Vista or 7 - 64 bit Download UIAutomationCore.dll from here:http://www.mediafire.com/?mik2mlqdz1wDrop the UIAutomationCore.dll file into the FSX root folder. While your in the root FSX folder, hold down the shift key and right click, select "open command window here" from the list of options. Copy and paste this:regsvr32 UIAutomationCore.dll

I don't know who told you to do it like that but you don't register the dll when you only want the local application (FSX) to use the dll. You only register it when you want other applications outside of the containing folder to have access to the file. The dll isn't needed in Vista either, that's where the file comes from in the first place, its the Windows7 version of the dll that won't work with FSX properly.As has been stated already the cause of the above error is due to Carenados anti piracy measures. It's not caused by EZdok either as you would be able to see the wings if you were seeing the VC model from the exterior.

Thank you all for the inputs. I understand the anti-piracy thing a little. In this instance and with a couple of other payware aircraft. I paid for, entered the proper registration key or serial number and the aircraft still vanish. I also have the HIGHMEMFIX=1 line in the configuration for FSX.cfg.

If you have Windows Vista or 7 - 64 bit Download UIAutomationCore.dll from here:http://www.mediafire.com/?mik2mlqdz1wDrop the UIAutomationCore.dll file into the FSX root folder. While your in the root FSX folder, hold down the shift key and right click, select "open command window here" from the list of options. Copy and paste this:regsvr32 UIAutomationCore.dllinto the Command Window. Press EnterAdd this line to your [graphics] section of your FSX.cfg file:HIGHMEMFIX=1These two steps should fix your problem.Kind regards,

Hi Stephen - I'm so sorry, my friend, as you are such a wealth of help and knowledge here, but neither of these will fix it:The UIAutomationCore.dll (version 6.0.5840.16386) cures the 'menu-ing' and freezing problems suffered by win7 - fsx users: it's due to FSX not being tested for compatibility with the version (6.1.7600.16385) now included in the Windows system folders. It is not compatible. Secondly, as Andy noted - DO NOT REGISTER the Vista version, as it will force all other apps (which depend upon the new version) to fail.HIGHMEMFIX=1 is needed, but certainly has nothing to do with the OP's problem.The only other thing I can think of, that might be a cause - is your installation of Bojote's Shaders v3.0 and his WaterConstants.dll.All the Best,

Hello V PilotsI have checked Ezdok; use all of your advisees and nothing positive, I just want to thank you for spending your time to help meI checked on Vista, my laptop and no problem there, but on Windows 7 my FSX dedicated computer, no textureI purchased both 35 is working on Win 7 but 36 still nothingI have Rex and Traffic and others add-ons and I’m really afraid to format and get FSX from scratchThanks againJacek

This is landing in Kandahar ,Hercules ,not but image for VFR landing ,

Jacek,I'll move this on over to the unofficial Carenado support forum.

you don't register the dll when you only want the local application (FSX) to use the dll. You only register it when you want other applications outside of the containing folder to have access to the file.

Hi Stephen - I'm so sorry, my friend, as you are such a wealth of help and knowledge here, but neither of these will fix it:The UIAutomationCore.dll (version 6.0.5840.16386) cures the 'menu-ing' and freezing problems suffered by win7 - fsx users: it's due to FSX not being tested for compatibility with the version (6.1.7600.16385) now included in the Windows system folders. It is not compatible. Secondly, as Andy noted - DO NOT REGISTER the Vista version, as it will force all other apps (which depend upon the new version) to fail. All the Best,

Thanks Andy and Paul,Gee, you learn something new everyday. LOL Been telling people that for so long, I can't remember where I first saw it. I guess I had better unregister it. I wonder how that can be done, simply by deleting it, running FSX and then pasting another copy in? I guess I will go looking to answer that one.Kind regards,

Hi Stephen - the original is version 6.1.7600.16385.dll, and can be found at: http://dllcentral.co...5%29/download/#- use the purple "Download UIAutomationCore.dll" link with the green arrow on its' left side.It needs to go in:-C:\Windows\System32C:\Windows\winsxs\amd64_microsoft-windows-uiautomationcore_31bf3856ad364e35_6.1.7600.16385_none_0c0d85465bcceb37C:\Windows\SysWOW64C:\Windows\winsxs\wow64_microsoft-windows-uiautomationcore_31bf3856ad364e35_6.1.7600.16385_none_16622f98902dad32I couldn't find any other locations for it, so just paste into these folders and register each as you suggested in the earlier post.

I just had the same thing the other night for the first time (I've had FS since SubLOGIC). I had just finished a flight in the XP Lear 24 and switched to the default 172 when it happened. I don't think this is related to Carenado.