Flysimware

I am going to add this topic to my FB group page and see if anyone can help.

I think i have a solution that is better than checking admin rights for 1 program! "Make sure you have your user as a admin." I suggest anyone having issues to make sure there user account is in fact a admin. Here is a video to explain how to change this option. There are not too many reasons to have your computer a non admin computer unless your sharing your computer and do not want the other users to have full rights. So i would follow this vid. It first show hows to check on W10 if you are in admin full control. Then it will show you how to change this option. I bet this will fix all FSX:SE crash issues! It worked for me using W7 last year!

As i thought it is a personal computer permission issue. And this is why only some are having issues. I too last year had to ad admin rights or FSX:SE would crash as soon as i loaded anything. The Grumman had a DLL and this is going to need full permission from FSX or your computer will refuse to read or write to the DLL and cause a crash. So seems that when you added the rights it worked then failed after you removed it. There are tutorials online for how to add rights to programs without just checking the admin box. This will most likely fix your issue as i think your specific windows is confused and is not allowing admin rights to FSX:SE.

Removed!

Try this as a quick test. In the windows search box enter "UIAnimation.dll" to confirm you have this DLL. This could be the cause if you do not have this DLL.

I agree it's not the MDL files and it also makes sense it's not the MT_XMLSound files because this file is the same for the MU-2B which works for FLHXRider. I do know there is 1 difference with this product than all others. This was the first made with 3DS MAX and not GMAX. But since the MDL files made no difference this is ruled out as mentioned above. So again i think it's a admin permission issue. But this was tested too. Can you guys confirm this? The mystery continues as this one has me stumped!

Make sure you have followed these instructions and see if this fixes the issue. It covers almost every reason FSX:SE could crash! I would skip the simconnects section! First make sure you are running steam as admin(fsx requires admin rights for itself, and some addons) make sure your video card drivers are up to date, dont just assume they are, check to make sure. SKIP ======================================================================= step 1, Install all the simconnects that DTG doesnt automatically install for you keep in mind these are simconnect.msi files...just double click to install where my FSX:SE is installed into my E:\ drive there are actually (4) simconnects in FSX:SE E:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\lib (install this one first) E:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM (install this one 2nd) E:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1 (install this one 3rd) E:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK (YOU SHOULD NOT NEED TO INSTALL THIS ONE) DTG now includes the install for the xpack since the last update/patch =============================================================================== the 2nd thing to do is install the C++ redistributable E:\SteamLibrary\steamapps\common\FSX\_CommonRedist\vcredist\2005 there are 2 files here vcredist_x86.msi (to install for 32 bit) vcredist_x64.msi (to install for 64 bit) just double click on the pertinant one for your system,should be 64bit If you can't find them in your directory can you please go to this website, download and install these two files. http://www.microsoft.com/en-us/download/details.aspx?id=3387 http://www.microsoft.com/en-us/download/details.aspx?id=21254 Please make sure you install them to the same drive where you have FSX installed. It doesn't need to be same folder or anything. Just the same hard drive. just to make sure it is installed, the XML parser should also be installed, it should have been loaded already by fsx E:\SteamLibrary\steamapps\common\FSX\Installers msxml.msi double click this file to install It looks like the game needs the MSXML 4.0 dlls installed for x86 and they aren't included in the redistribution or are failing to install as part of the Steam setup on Win 8.1 Pro. I downloaded the MSXML 4.0 SP2 and SP2 Hotfix from Microsoft and everything then worked. Get the files from: MSXML 4.0 Service Pack 2 (Microsoft XML Core Services) - http://www.microsoft.com/en-us/download/details.aspx?id=19662 Security Update for MSXML 4.0 Service Pack 2 (KB954430) - http://www.microsoft.com/en-us/download/details.aspx?id=14623 install Directx 9.0c E:\SteamLibrary\steamapps\common\FSX\_CommonRedist\DirectX\Jun2010 i know it seems a bit overkill, but these steps usually correct issues for most people If you had a side by side FSX:BOXED and FSX:SE install, it could be registry/directory structure/files issue, some have had suces with side by side, others have had nothing but headaches

I agree, but i do not have any tools to read a dump file and i can't create a dump file because i do not have this issue which means to me it has something to do with a specific computer and not the rest of the customers. But we do have a clue from a tool. And this statement to me means DLL is causing the issue because the location is outside the aircraft folder and needs permission to use it. "The thread tried to read from or write to a virtual address for which it does not have the appropriate access"

Ok now try to borrow a model file from an other airplane and rename it to the exterior and interior models 1 at a time to see if any of the model files are the cause. So make a backup of the 2 model files. Grumman_G-44A_interior Grumman_G-44A Now copy any model file like from the MU and paste it here and name it Grumman_G-44A_interior. and try it. Then try the other name and test it.

I just posted a simple test to try for now. Hope to get some feedback soon since i do not get the fatal error.

When i read this to me it means you have admin issues. And i bet Windows 10 is what both of you guys are using. "The thread tried to read from or write to a virtual address for which it does not have the appropriate access" But it's odd that the MU works and the Grumman does not because they both use the same DLL. Maybe try doing some tests. ==================================================================================================== Open the Grumman panel folder / panel cfg. in notepad. Make a backup. TEST Remove this line: gauge04=MT_XMLSound!MT_XMLSound, 0,0,1,1 from: [Vcockpit01]

I think you need read the last entry as they explain why this can happen. Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. https://steamcommunity.com/app/314160/discussions/0/458604254443920608/ I too am at a loss as my FSX:SE runs the Grumman with no issues.

By hard coding the lights then the fuselage works as a solid polygon to prevent the light from reflecting inside the interior model just like an invisible polygon as you mentioned. So for some reason P3D V4 is no longer stopping light from bleeding effects that are hard coded and this new change upsets me because the hard coding was the trick to stopping any bleeding of light. So i hope someone will pass this info to P3D so they know that some developers hard coded effects so they will not bleed and now your latest version is no longer working. And again this hard coded trick works on all the previous versions. Can anyone confirm that the previous versions of P3D do not bleed with my products?

Thanks for the compliments. I just wanted to let you know that if you open the Aircraft.cfg file and check the fltsim sections we have the manufacturer named as the actual manufacturer and our name Flysimware under the ui_createdby. So i am totally confused by your comment on this topic.

Actually PC Aviator emailed me on the 12th confirming they have updated the last 11 updates. This also includes the C402 V2.3 to V2.3a. I have no control when a store updates but we do send then the updated products at the same time.