FSUIPC4 in dll.xml

[Daniel Delande]

Hi,

I have developped a module for FSX that connects to SimConnect, of course.

I had difficulties to make may module work when FSUIPC is enabled in dll.xml: in most cases, my DispatchProc (passed to SimConnect in SimConnect_CallDispatch(...)) was never called back.

Finally, I discovered that everything worked OK, provided in dll.xml, the section relevant to FSUIPC4 was placed after the section relevant to my own module.

Note that my own module can also connect to FSUIPC, but connection to FSUIPC or not has no impact on this problem.

Can you explain this? Can this be due to some kind of hook made by FSUIPC to FSX?

Regards,

Daniel Delande

[Pete Dowson]

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle.

Hi,

I have developped a module for FSX that connects to SimConnect, of course.

I had difficulties to make may module work when FSUIPC is enabled in dll.xml: in most cases, my DispatchProc (passed to SimConnect in SimConnect_CallDispatch(...)) was never called back.

Finally, I discovered that everything worked OK, provided in dll.xml, the section relevant to FSUIPC4 was placed after the section relevant to my own module.

Note that my own module can also connect to FSUIPC, but connection to FSUIPC or not has no impact on this problem.

Can you explain this? Can this be due to some kind of hook made by FSUIPC to FSX?

No. It is (or rather was) a bug in SimConnect. It sounds like you've not yet installed FSX SP1, as that pretty well fixed it (using a work-around).

If you have problems like this you really need to use the SimConnect logging facilities to see what is going on.

SP2 / Acceleration fixes it good and proper, I believe.

Regards

Pete

[Daniel Delande]

Thank you for answering, Pete.

I have installed FSX SP1 for long.

I actually used the SimConnect logging facility and observed that everything was OK, i.e. the expected events showed (e.g. AddToDataDefinition, ObjectData: RequestID=..., Menu: EventID=...), a menu was actually added in FSX menu. But there was no other effect. My debugger showed no call to my DispatchProc, clicking on the menu had no effect.

I'll check what happens when the SP2 is released. Anyway, I have a work-around to make both FSUIPC and my module work.

Regards,

Daniel