Josh Glottmann Posted March 5, 2015 at 11:44 PM Posted March 5, 2015 at 11:44 PM I recently partitioned my Mac in an attempt to be able to use FSX again rather than X-Plane. I installed FSX, SimConnect (I think), vPilot, the IVAO MTL, SP1, and SP2. Everything seems to be running fine aside from the fact that FSX crashes within the first 30 minutes of it being opened. I'm running both FSX and vPilot as an administrator (right clicking). The crash also seems to be occurring when I'm "interacting" with FSX. (Changing views, changing where the camera is pointing, etc.) Crash Report Hopefully I can get FSX running! Thanks, Josh Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted March 6, 2015 at 12:02 AM Posted March 6, 2015 at 12:02 AM The crash report from vPilot is essentially useless - it's basically just confirming that yes, FSX did indeed crash for some reason. The FSX crash report would be much more relevant. Have you applied the UIAutomationCore.dll fix? Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 6, 2015 at 12:08 AM Author Posted March 6, 2015 at 12:08 AM That shows how long it's been since I've used FSX... I thought that it was FSX's crash report, sorry. Let me try doing that. Thanks EDIT: Out of curiosity, where are FSX Crash reports located? Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 6, 2015 at 12:21 AM Author Posted March 6, 2015 at 12:21 AM Just installed the .dll. Worked fine for a few minutes, then decided to go ahead on crash when trying to choose another view Found the log (I think). Here is all the information I got. Link to comment Share on other sites More sharing options...
Ernesto Alvarez 818262 Posted March 6, 2015 at 01:21 AM Posted March 6, 2015 at 01:21 AM error code shows a memory access violation. one clue would be you installed the sim in the default location, definitely not recommended. Windows protects that X86 folder which is usually the cause of a lot of errors with some of these. my recommendation would be uninstall and reinstall outside that folder, IE C:\FSX itll help get around a lot of these. Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 6, 2015 at 01:24 AM Author Posted March 6, 2015 at 01:24 AM You don't know hard it was to install FSX without an optical disk drive :roll: Looks like I put the dll in the wrong folder, trying again. Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted March 6, 2015 at 01:44 AM Board of Governors Posted March 6, 2015 at 01:44 AM I haven't used a Mac since 1991, so forgive me if my next question is dumb.... When running on a Mac, are you also running Windows of some sort? If so, which version? If Windows 8, DO NOT use the UIAutomationCore.dll fix. I can see your installation is in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ That is not recommended due to Microsoft Security/Access issues. Your best bet, since it's a fresh install, is to uninstall and reinstall in a new directory you create just for this purpose (e.g., d:\FSX\) If you're not wild about that idea, one thing you could try is uninstalling and reinstalling just SP2, and THEN adding in the UIAutomationCore.dll fix. EDIT: Wow, you guys type faster than I do Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 6, 2015 at 02:14 AM Author Posted March 6, 2015 at 02:14 AM Running Windows 7 Is there any way to simply "move" FSX? My install involved copying the FSX disks to external drives which I had to name "FSX Disk 1/2" and merging Disk 2 with Disk 1's drive... Let's just say it wasn't fun Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted March 6, 2015 at 02:55 AM Board of Governors Posted March 6, 2015 at 02:55 AM Not that I know of, sorry. Not sure that is the problem here. Least intrusive suggestion: Try uninstalling and reinstalling just SP2, and THEN adding in the UIAutomationCore.dll fix. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Josh Glottmann Posted March 6, 2015 at 03:00 AM Author Posted March 6, 2015 at 03:00 AM Seems to be working now... Thanks everyone! Link to comment Share on other sites More sharing options...
Recommended Posts