That is correct. Use this for "non-realtime" moves.

Mike

I believe your high level dispatch callback should only recieve the SIMCONNECT_RECV_ID_EXTERNAL_SIM_SIMULATE data when you should be simulating. I believe this is how the SDK's ExternalSim sample is setup.

Mike

Ok, I'm a little confused. Your other thread implies your dispatch callback function never gets called, but here you say you are actually receiving at least some events. My suggestion would be to investigate any differences between your implementation and the sample, which appears to handle your scenario appropriately as far as I can tell.

Mike

My assumption is that it shouldn't matter, as long as the function being registered in SimConnect_CallDispatch() is static.

Mike

Following up on SIMCONNECT_DATATYPE_INITPOSITION: I added this to the example code from ExternalSim.cpp upon receving on the create notification.

1st:

SimConnect_AddToDataDefinition(g_hSimConnect, INIT_DEF, "Initial Position", "NULL", SIMCONNECT_DATATYPE_INITPOSITION, 0);

2nd:

SIMCONNECT_DATA_INITPOSITION Init;
Init.Altitude = 5000.0;
Init.Latitude = 47.64210;
Init.Longitude = -122.13010;
Init.Pitch = 0.0;
Init.Bank = 0.0;
Init.Heading = 180.0;
Init.OnGround = 1;
Init.Airspeed = 0;

SimConnect_SetDataOnSimObject(g_hSimConnect, INIT_DEF, SIMCONNECT_OBJECT_ID_USER, 0, 0, sizeof(Init), &Init );

SimConnect_AddToDataDefinition() throws SIMCONNECT_EXCEPTION_NAME_UNRECOGNIZED followod by IMCONNECT_EXCEPTION_BLOCK_TIMEOUT.

What is SIMCONNECT_EXCEPTION_NAME_UNRECOGNIZED complaining about?

Hi Mike,

If the SimConnect_AddToDataDefinition() call throws, the init must throw, and yes, it did too.

I worked from the compiled ExternalSim.cpp, loaded it completely as in the SDK. It worked 100%. Then I removed the dll loading from the sim.cfg and compiled ExternalSim.cpp as an external standalone EXE. Then as described.

Next I'll try to load the new code via the sim.cfg as a DLL....