John Dowson

You can always zip/compress files that are too large to attach directely. But I don't need to see any files at the moment - you have already attached a log an ini, both of whuch show rhat your controllers are recognised and acquired. But I still am not sure what your issue is... Yes - but if another joystick/axis is recognised, you have to Rescan. If the same joystick/axis is always recognised, you have to Ignore Axis as the axis is "jittering", i.e. continually sending values. Or are you saying that you move an axis and nothing is recognised in the joystick and axis fields, i.e. they remain empty?

License sent.

sent

Great! Thanks for all your help tracking this one down! I will release a new beta tomorrow, as a full installer (including WASM + updated documentation). The additional log messages I added for this will be removed, and input parameter values will be logged correctly. Please update to this version once released. I will probably release this version officially the following week, if no other issues are reported. Cheers, John

Ok - that log shows that there is an issue with the lvar values lock/mutex: That lock us never obtained. This looks to be due to successive config updates being received before the previous one is fully processed. Hopefully this is corrected in the attached version. Any issues, can you attach the log file again - maybe two copies, one the file when you get the hang, and again after you have killed/stopped FSUIPC7. Thanks. John FSUIPC7.exe

Does it not still open? But the image you attached shows that the Y axis on device A (Bravo Throttle Quadrant) was recognised. If you want to assign to a different axis, click Rescan. If the same axis/device keeps showing, click the Ignore Axis button. You can either use the UI - move the assigned axis lever so that the assignment is shown, then click Clear. Otherwise you can just delete the lines in the FSYUPC7.ini file in an editor - make sure that either FSUIPC7 is not running, or if it is then do this with the Axis Assignment panel open and click Reload all assignments when you have saved the file.

ipc.keypressplus( (and ipc.keypress) send keys to the FS, as it says in the documentation. You cannot use those functions to test for a keypress. They also do not return any value. Use event.key - see the Lua Library documentation in how to use this function. John

Can you test with the main window open - I would like to know if the UI responds when you get this hang/freeze. You access the logging console via Log->Open Console. This shows a real-time view of the FSUIPC7.log file. I would like to know if messages are till logged after the freeze, so keep that open. Yes please - I would like to see the state of the logs when you get the freeze. I suspect there may be a lock contention issue, and certain threads (not all!) are paused waiting for a lock that is never released. Could you try with the attached version. Also activate logging for extras (Log->Extras), as this will also log thread information. I have also attached an updated WASM - save the WASM to your Community/fsuipc-lvar-module/modules/ folder, and the layout.json and manifest.json to Community/fsuipc-lvar-module/ FSUIPC7.exe FSUIPC7_WASM.wasm layout.json layout.json manifest.json

The more I look at your log files, the more confused I am... Can you explain exactly what happens please, and what you do.... The WASM log file indicates that you went back to the main menu: But there is no indication of this in your FSUIPC log file, it just loses the WASM config and is waiting for new data: [timestamp 209297 is approx 14:23:35 + 3m29s = 14:27:04, and the 1 hour difference is due to different time zones being used] Did you go back to the main menu, and if so when? Before or after FSUIPC stopped responding or was killed? It looks like it just stays like this until it is killed. Are you sure there is no response from the UI? What is the message in the FSUIPC7 main window when this happens? If you keep the logging console window open, is this still logging messages, and if not what is the last message logged? And the WASM log looks like it has been uploaded AFTER MSFS has exited. When your issue occurs again. can you attach all files before you do anything else, so I can see the contents when the issue occurred. You also have a lot of stuff running using simconnect connections: Not sure why you are running so much Fenix stuff when you are not even using that aircraft - have you considered moving this out of your Community folder if not being used, and not running any additional software for that aircraft if not being used? Easy to do with the MSFS Add-on manager. Note sure why you are using/running the WASMClient either - twice! You really don't need this - everything that does can be done in FSUIPC. And you seem to be running 'Couatl' twice... I have cleaned-up a couple of things, but nothing that could be related to your issue. I will provide you with a new version to try, including WASM, probably tomorrow now. John

I have just re-read this thread and it seems the issue has changed since the initial report. Can you confirm that the issue now is that FSUIPC7 seems to hang, and that there is no response from the UI? If you kill and restart, does it then work? Do you only get this issue when GSX is running? How frequent is this issue, both when GSX running and when not? Do you see any events (warning or error) related to this issue in the windows event viewer? I am going to run some extended tests in the debugger to see if I can catch anything with this... John

Well, that last log has thrown a spanner in the works... What was the issue - did FSUIPC hang? Could you access the UI? In all your previous logs, the last line logged has always been: However, this time this is the last line logged, out of the blue: And I can't see how that can be logged with no other log message indicating why it was closed.... This is all very strange and I am at a loss as to what could cause this.... It would be useful if I could see a SimConnect log file. Could you configure to generate one - see Also please switch back to WAPI Trace level logging, and show me the files again, including the simconnec.log (it will be quite large and will need zipping/compressing, and still may be too large to attach....). I have also noticed an issue in the WASM from your WASM log. However, this does not cause any actual problems, but I will correct this in the next release. John

The MF HubHop website is very useful resource - it contains the calculator code/presets found by the community and is very useful for a repository of calculator code for various aircraft. You should certainly use this for calc. code examples. The MF discord server (MSFS2020 channel) is also the place to ask questions on calc code syntax and how to determine the calc code to be used for specific functions. Calc code is pretty new to me as well, and I am by no means an expert in this area. I help out if I can, and if I can't I will try and point you in the right direction. I am extremely busy at the moment and don't have time to look into such things (that are really out-of-scope of the support I provide for FSUIPC) in detail.

It isn't - this is the support forum for FSUIPC7.

This doesn't make any sense - uninstalling from windows app management will call the same uninstaller anyway, so it is exactly the same as running the uninstaller manually. And you should not uninstall if/when re-installing anyway - the installer will detect if currently installed and run the uninstaller anyway, And all of this has nothing to do with your original problem, which I guess was because you didn't register your license, hence the need to re-run the installer. John

?

Can you show me a log when you get a hang using the following version, where more logging has been added: FSUIPC7.exe Just use WAPI Debug level logging, not Trace. I will consider adding the extra option to run programs, but I do not know when I will have time to look into this - it will go in the backlog/to-investigate list. John

Can you please ALWAYS attach your FSUIPC6.log and FSUIPC6.ini files - there is no point in reporting issues with assignments if you do not provide these files, and every time please as they are changed/updated each time you run FSUIPC. You also have controllers active in P3D. If assigning in FSUIPC, it is better to disable controllers in P3D. As a minimum, you need to check that any axis assigned in FSUIPC is NOT assigned in P3D. And be aware that P3D can sometimes automatically re-assign an axis if controllers are not disabled. You have no assignments to your throttle in FSUIPC, so this MUST be assigned elsewhere, probably in P3D You say you have been flying a long time and this is a new issue. What has changed? Why do you only have two axis (aileron and elevator) assigned in FSUIPC? Are the rest assigned in P3D? If so, why are you even using FSUIPC - if everything else is assigned in P3D, why not just assign the aileron and elevator there, as you do not seem to be using anything else in FSUIPC? I suggest you try assigning in FSUIPC with controllers disabled in P3D. For PMDG aircraft, you should not calibrate if the axis is assigned in P3D or elsewhere, and should only be calibrated if assigned in FSUIPC with 'Direct to FSUIPC Calibration'. Sometimes even this can give issues, and if so you should assign using 'send to FS as normal axis; and not calibrate.

Haven't you already asked this question? The only way to send an event with more than one parameter is via calculator code. As to the exact RPN format if the calculator code for such an update, I am not sure. Check the Asobo documentation or ask on the Asobo forums. Does that work? If not. try: ipc.execCalcCode(“4 (>K:3:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)”) Maybe also check out some of the MF presets that are already using this - just search for ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE at https://hubhop.mobiflight.com/presets/

Ok, I will look into this next week...I will provide you another exe with additional logging to try and track this down,.,, John

If you get this issue again. post again, and try and catch it with appropriate logging... If there is no problem, why add another option? Everything is already very complicated as FSYUPC can be started in carious sim states, I would rather not add additional functionality for no perceived benefit... And this functionality has been around for many years and this hasn't been requested before, so I doubt it is that useful... Would this be to delay the starting further (until simconnect is ready)? If so, why not just add a delay?

From the Advanced User guide: You said: So READY obviously wasn't working as it should, and is why it has been corrected. If you want the programs to be started earlier, remove the READY. No - remove the READY, you don't seem to want to use this, so just remove it. John

Yes - the READY parameter wasn't working correctly, and this has been corrected in the latest beta. It does list the other changes in the beta release note: If you want it to start earlier, remove the READY. The beta version you are using (7.3.26e) has some issues - please update to the latest beta, 7.3.26g, and test with that. John

Are you using Project Magenta? These offsets are in the reserved area for PM. A cannot help with this, sorry. This offset is in an area free for general use. It is therefore not controlled directly by FSUIPC, and myst be written/read by some other tools you are using. As these offsets are controlled by other software, I cannot really help you any further with this. Try PM support. You should also mention that you are using PM in your description and in the title, as that may then attract other PM users whi may be able to help. I have no knowledge or experience with PM (and very little with FSX!), so am unable to help any further with this, sorry. John

Ok. Looking at the script you posted (always better to attach than paste!), why are you doing this: ? You should use the event.timer function.. Using that, you shouldn't need to sleep, but if you do want to add a random delay, use ipc.sleep and not os.execute.

First, using a prop. aircraft, you should use offsets 0x3B70 and 0x3AB0, as the comments in the FSUIPC offset document states: Those offsets are two-byte ints - I am not sure if they are signed or not (i.e. can they be negative?). If signed, you would use the function ipc.writeSW(offset, value), and if unsigned, you would use ipc.writeUW(offset, value). I suspect they are signed, so try that first. Note that a value of 16384 - 860 C, so you would need to scale your values of -9 to + 9 to the range temperatures that you want (e.g. -16384 to + 16384). If using offsets 0x3B70 and 0x3AB0, these hold 64bit/8-byte floating point numbers, so you would use ipc.writeDBL(offset, value). These offsets are in degrees Rankine, so you should also convert your -9 to +9 value to the variation range toy want to see in these units. John