Data of Offset is different to Sim (After we write it by the input).
FSUIPC V5 CODE
Here you need a "advanced" code to manage this cause a input situation occure in a "abnormal Situation". But they also want that they can Write the SAME Offset by a Input (Mobiflight) to change a function in the Sim. Some guys use a script that will show a value (Mostly read from a Lvar) on a Offset. So it looks like offset is not writeable whatever it would be written for a millisecond (One internal process poll) ! But your AddOn "reset" it in same moment. In That case your Command is send by Mobiflight. If Data is different to the AddOn reset the Internal Sim System to AddOn status. And Additional it immediatly rewrite your entry cause the logic say. Aslong Master Battery Switch IN Addon is On write the FSUIPC Offset (or the FSX/P3D internal Data) to 1 ! When you NOW try to write these Offset to 0 by your switch the command can not be executed in AddOn Aircraft cause it ignore basicly the FSUIPC/P3D values. If for example a AddOn Aircraft have a codeline that say "Overwrite Data XY when its different to AddOn internal Data" then you get in trouble.įor example a AddOn can say. FSUIPC gets data basicly from the FSX/P3D internal process and support it on its offsets. Here i say again you must check your script and your AddOn Aircraft. But your data show the system is presuably not the problem ! Sure P3D have a higher performance needness that can explane why it work fine in FSX but not in P3D. Then i think we can exclude the Hardware from our list. And CPU Usage is not reach the magical 100% on one Core. So remove your own scripts for testing (And all entrys like in the FSUIPC Ini files that start your scripts) and run P3D with a standard Aircraft. Does the problem gone if you NOT use your completly LUA Stuff while running P3D. I got a 2000$ Computer ! My Processors work nice" You realy test it and report data. Its realy nice if a user cooperate by this high level. So I think the problem comes from Lua with P3D 4.5 and FSUIPC 5.151. I've reinstalled FSX and tested my script, it works normally, all my simu functions are OK and MF has returned to normal speed with FSX. While doing a test with Linda (latest version) I see that offsets are written in loop, in fact all the ones I use in my script and it's impossible to write values in. I saw today that other offsets no longer react (impossible to write) especially those of COM and NAV frequencies) I havn't check yesturday, working on an "information auto screen). Charge: #0 67%, #1, #2 and #3 between 12% and 22%Ĥ- Graphic card GTX750Ti at 49☌, everything seems normal. I can’t enlarge the MF window with the mouse when P3D is displayed.ģ- The temperatures of my processor (i5 6600K): #0 44☌, #1 46☌, #2 42☌, #3 45☌ after 10 minutes.
![fsuipc v5 fsuipc v5](https://mluqluuzvvfe.i.optimole.com/q9jXyDM.9hXA~42308/w:auto/h:auto/q:auto/https://www.fsipanel.com/wp-content/uploads/2020/12/desc4.jpg)
1- My script works very well under FSX (I reinstalled FSX last night to check)Ģ- I mean that the operation of MF (loading and link with FSUIPC and my homecockpit) is very slow, scrolling and refreshing the MF window is also slow.