Download thousands of free add-on aircraft for Microsoft Flight Simulator X on FSX Downloads! General Aviation Planes, Jets, Turboprops, Warbirds, Military. 70+ channels, unlimited DVR storage space, & 6 accounts for your home all in one great price.
This is one of the worst pieces garbage that I have ever seen as an add on. Just plain horrid And fact you to pay for this only get 5 minutes from time launch it test out You gotta be kidding me. How about 30 minutes. Or 60 My God isn t enough do any more than 2 decent crashes, if can even 2. Viewed these explosions many angles. All them sucked bad rest.
If could given a 10 would have. Seriously people.do NOT waste your bw or nets on download. There were some GREAT explosion packs 2000 and 2002, but 2004.I simply don know what else say.
It s HORRID They are fake looking they take place 20 50 feet away plane, which course, in 1 piece with distant fireball. Was sooooooooo excited nice back 2004. Thanks nothing.
I also have had two major problems running Flight Simulator X since upgrading to Windows 10 however after much research and testing believe that all problems now appear to be resolved. I wish to therefore share my findings that may help others experiencingthe same difficulties.The first problem noted was that when a pre-saved flight was loaded in full screen mode, the loading screen was black. The flight did load but it was found that none of the menu or exit screens would display - but they would if displayed in window mode- ALT/Enter to change display modes.
This problem was resolved by updating my video card drivers to the absolute most recent from the manufacturers driver update site. Using windows update driver gave me a driver dated Nov 15 which did not resolve the issue yetthe driver from the manufacturer site was dated Dec 15 and all worked properly. My video card is a NVIDIA GeForce GTX 570 so it appeared NVIDIA had identified and corrected the problem.My second problem was that if I loaded a pre-saved flight and then attempted to change the time, date or year, (which I do almost every time), the program would crash within less than a minute after reloading scenery textures etc.
And the 'program has stoppedworking' message would appear every time. Some online research and running the 'dxdiag' command revealed that the crash was due to a windows system file called UIAutomationCore.dll which could be found in both the Windows System32 and SysWOW64 folders. Removingboth these files fixed the problem but introduced many others with other programs. Found that removing the file from just the SysWOW64 folder also resolved the FSX crash problem but found that certain aspects, (like video display), did not work properly inthe new Microsoft Edge Browser along with a few other issues didn't seem quite right.I then tried changing the 'UIAutomationCore.dll' file in the SysWOW64 folder only with the same file from my Windows.old Folder - (which I assume is my old windows 7 files still on my system in case I choose to roll back to Win 7 at the end of my 30 daygrace period) - and all issues appeared to be resolved. Thanks for your findings.Re: Black screen in full screen mode. Many have experienced this problem, and of course the workaround was to enter windowed mode to use the menu bar, exit sim, etc.
And you have rightly observed that Nvidia's latest driver did incorporate a fix forthis, one which I had used and worked well in this regard. However, I found that suddenly, mid way in a flight, I would get a freeze and have to reboot. This happened a few times, so figured that the only change I had made in the intervening time was toupdate the Nvidia driver to 361.43. So to test, I rolled back the driver to 359.06, and the sim freeze stopped, however, I was back to switching between full screen and windowed modes. Will wait for Nvidia's next version and test that one out. I assumeyou are not getting the freeze problem with 361.43.Re: UIAutomationCore.dll. I had posted a while ago about this error.
This one comes up, when the menu bar in FSX is used many times, and as in your case, you changed the date/time. However, itis strongly recommended that the UIAutomationCore.dll found in System32 and SysWOW64 not be moved or replaced as that is needed by Windows. Instead, an earlier version of the said.dll should be used, but this time placing it in the FSX directory. FSXwill first search its own backyard for that.dll before it searches elsewhere in Windows. And this fix works for this type of error.
The version I use (and there is choice of two) is 6.0.5840.16386. The other version has digits ending with 18000 andthey can be found at:putting a Win7 version of the.dll into your Win10 SysWOW64 folder hopefully won't pose any problems in the future. Did you save a copy of the Win10.dll in case you need it?Appreciate your post on these issues. Thanks 'Chriso' for your suggestions!!Yes I have kept all my original Win 10 UIAutomationCore.dll files so I could put them back if an alternative fix could be found. So I am very pleased to announce that I have been able to put the original back into the SysWow64 folder as using the file yousuggested in the FSX directory has also stopped the crashing as you said it would!! So thank you so much as I am very pleased I now do not need to alter my Win 10 system files!!I had actually tried my Win 7 UIAutomationCore.dll file in the FSX directory after reading a post suggesting something like this with the original Win 10 'Automation' files back where they belong however the crashing still occurred.
However, using the olderfile you suggested does appear to have done the trick as I have just enjoyed a faultless 3hr flight! Before commencing I was able to change from day to night and time date etc. Without any crashes as what religiously happened before.No I have not experienced any freezes using the latest NVIDIA video card driver 361.43 (dated Dec 15) and everything displays as it should in full screen mode.
All menus, selection and exit screens appear as do 'tool tips' for aircraft control buttons, soall is looking great for me with everything now appearing fully functional again without any glitches. I do hope it can stay that way!!I used to experience some freezing which was always limited to around the Melbourne area however I was able to overcome this by disabling a freeware airport I had installed.So thanks again for your valuable advice as it does appear to have restored my FSX to operate successfully on Windows 10.!!Regards. I have got a little bit different problem.
My laptop keyboard stop working (even the shut down button) and I am waiting if it comes again but this time the fsx 'not responding' error occurs. I tried to make a couple of adjustments:1.install pmdg all from the beginning.2.update win10 and Nvidia gforce.3.update keyboard and change the filter settings4.check the compability of fsx to win85.run fsx as admin every timethen I download the win7 dll file as you recommended from the link you had written. I tried to change the dll but I could not manage to move my win10 dll because I should need the admin capabilities, so I decided to put the win7 dll in the folder while theother one is still in there and I did, however fsx stop working after a while when I was cold and dark at the apron, so I take back the win 7 dll to the desktop. I run fsx about 30-40 minutes and it is looking good. Can you please help how can I change thedll files just in case I need to try in the future.thanks in advance. You have brought up a number of issues that you are having, so I hope that you can sort out your keyboard and other problems. I now refer to your.dll file issue:I assume you are referring to the UIAutomationCore.dll file. The problem mentioned is when after using your FSX Menu bar many times, you suddenly get a freeze and subsequent game crash. Is this happeningin your case?
If so, then first go to your Event Viewer Admin Events and see what the Error is when FSX crashes and what is the faulting module. If it is UIAutomationCore.dll, then the fixshould work for you. If it is another error code, then that will need further investigation.In your explanation of what you've done, I think you may have got something wrong. Firstly,don't delete, move or alter any UIAutomationCore.dll in Windows (e.g. In System32 or SysWOW64): these are Windows files that should remain where theyare.
What you need to do if you get this error in Event Viewer, is to download the version 6.0.5840.16386 from (which I think you havedone):downloading it, place the.dll into FSX Directory - don't put in anywhere else. What this does, is that FSX will search its own Folder first and apply the fix before trying any other UIAutomationCore.dllfound elsewhere. Hope this is clear to you - write back if you have problems. Many thanks for replyıng so soon about my dll problems and so sorry to reply after a whıle.ı am tryıng to check my fsx and ıt runs quıte well, no problems about fatal errors and not respondıng ıssues. however my keyboard ıs totally dısaster. ı thınk ıts about my ıvap but ı can not be sure. maybe about PMDG (ı unıstall and ınstall agaın) keyboardstops workıng anytıme durıng onlıne (sometımes at the gate sometımes ın the mıddle of the flıght sometımes just before landıng). Whıle all the other programmes are workıng fıne.
The worse thıng ıs: after sometıme later thıs problem occurs my wın10 restartıtself automatıcly but after the restart the keyboard problem stıll exısts and ıt can not be fıxed wıthout forced ıt to shot down manually. I trıed avsım and many other forums and ı found to unınstall and ınstall IvAp (ı dıd) run IvAp V2 external but ıt makesall thıngs worse, the keyboard stops workıng whıtın 10 mınutes.
So ı turn back to run IvAp from fsx. Please help to fıx thıs. Now ı am at the dead end:(thanks ın advance. I'm not familiar with ivAp as it has to do with an Online flying network. You mentioned that your laptop keyboard works without problem with other computer programs, except when using ivAp, PMDG, etc.Speaking generally, you need to ascertain what program is causing this keyboard malfunction. Is it possible for you to run FSX in its vanilla (default) state, without any PMDG products, ivAp, or anyother add ons? You will need to uninstall all these products to test this and reboot your computer.
Then take a flight (or more flights) and see whether your keyboard and the allocated keys for FSX function properly. If they do, then you can installyour add ons, only one at a time and test each one by flying, to see where the problem begins. I know this will be a long experiment, but you need to find out what program(s) may be conflicting with your keyboard. I can't imagine it to be a PMDG productas they are fully tested and I have not heard of any such problem with them, but you will need to find out by checking each one out.Of course you would have updated your laptop drivers, scanned your system for errors and defragmented the drive (except for an SSD). Another possibility (if you think that ivAp is the cause of thisproblem is to visit their community forums (you would be registered with them) or send them an email. The one I found is here:.