ipc.writeSTR (0x3380, "test") and ipc.writeSW (0x32FA, 0) function

[Amaniera]

Hello Pete,

I have a problem with the latest version of FSUIPC (FSUIPC6).
My program worked very well with Prepar3D v4 and FSUIPC5 but now that I have switched to Prepar3D v5, I am forced to switch to FSUIPC6.
The problem is that when I use the ipc.writeSTR (0x3380, "test") and ipc.writeSW (0x32FA, 0) function, my fps drop suddenly when displayed and they don't go back up.
Is this a display optimization problem with FSUIPC6? It worked very well with FSUIPC5 and Prepar3D v4.
Thanks in advance.

Regards,
Patrice."

[Pete Dowson]

22 minutes ago, Amaniera said:

The problem is that when I use the ipc.writeSTR (0x3380, "test") and ipc.writeSW (0x32FA, 0) function, my fps drop suddenly when displayed and they don't go back up.
Is this a display optimization problem with FSUIPC6?

No. All FSUIPC does is send the request on to SimConnect, within P3D. FSUIPC is in no way involved in the actual display itself, it is just a simple function call -- as documented for the SimConnect Text interface.

These same display facilities are also used by the Lua plug-in "ipc.display" calls.  Try, for example, the "VAS_Monitor.lua" plug-in provided in the Example LUA plug-ins ZIP in your FSUIPC6 documents folder. Or, perhaps easier, try a keypress assigned to the FSUIPC control "list LVars" which displays the current cockpit local variables. 

Another check is try with your "test" changed to "test\n2" so that two lines are requested, forcing the use of a different SimConnect function.

... [LATER]
I've just tried your exact sequence with P3D5 HF2 and FSUIPC 6.0.9, and the green static line showing "test" appears and the frame rate doesn't change at all.

I think you must have something else happening there. Maybe to do with your video driver or settings?

Pete