• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

SinCommect AccessViolationException

F

flying-w

Messages
42
Country
wales
Can anyone help with this exception? My application connected once and all was well, but now I get this every time. The exception is in response to (managed code):

simHandle = new SimConnect(appName, this.Handle, WM_USER_SIMCONNECT, null, 0);

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at SimConnect_Open(Void** , SByte* , HWND__* , UInt32 , Void* , UInt32 )
at Microsoft.FlightSimulator.SimConnect.SimConnect..ctor(String szName, IntPtr hWnd, UInt32 UserEventWin32, WaitHandle hEventHandle, UInt32 ConfigIndex)

Thanks
Simon
 
This turned out to be a mismatch between FSX server and client levels. FSX was running with SP1, but somehow the SP2 client had got installed on the same machine. SuperTrafficBoard always latches on to the most uplevel client, and hence the problem.

Regards
Simon
 
You must log in or register to reply here.
Back
Top