ahmedam

Thank you so much for the info, Pete. It turned out the Terrain and g3d crashes were not related to SimConnect at all. However, after a few rounds of bugfixing, there's one crash left. There seems to be a COMException with the error code: 0xC000020D STATUS_CONNECTION_RESET happening on ReceiveMessage(), with the Source listed as mscorlib. It seems to happen intermittently (after 0-2 hours) and does not leave a crash log anywhere-- I'm catching the exception in code and writing it manually to a text file. Does this sound like a familiar problem at all? I would be happy to pay you for your consultation time, as I know this is regarding a version of Prepar3d you don't support. Thank you very much, Ahmed

Hi, I am working on a SimConnect project using Prepar3d v1.3 (not using FSUIPC yet,) and am finding that Prepar3d intermittently crashes quietly with a terrain.dll or g3d.dll crash dump in the windows event viewer. It's always on an access violation exception, and I've been noticing that people who used FSUIPC reported the same thing until Pete deployed a fix. What I'm wondering is if I change the custom software from connecting directly to simconnect, and have it ask FSUIPC for that data instead, would these problems go away? I'm trying to understand the scope of the fix that was put in place for FSUIPC-- from what I've gathered, this has been a problem for anyone trying to connect to SimConnect. Also, since I'm required to used Prepar3d v1.3, would it be possible to buy a version of FSUIPC that works with that old of a version of Prepar3d? Thanks everyone, Ahmed