John Dowson

No I don't... I am not sure it is... I also tried duplicating the sync script and ran 3 copies without issue. Access (read and write) to lvars is already protected (by a mutex) to prevent any issues with multi-thread access. I will add similar thread protection to the calls that send calc code so you can check with this to see if that makes a difference - I will post a new version for you to try later today. John

I can't see how the GSX_AUTO script can affect things, and I have had it running here together with your other 2 scripts for several hours without issue. I have also taken a look at your simconnect.log file. There are errors/exceptions from FenixBootStrapper (which has 5 connections, or 5 copies running....), PilotsDeck, FSUIPC7_AItraffic (expected occasionally), and some from the FSUIPC_WASM_IF (WAPI). However, the WAPI exceptions are not related to your issue, as they relate to the lvar names and values CDAs. Not sure what is causing those (I will investigate further when time permits), but I don't think there is an issue there. There don't seem to be any exceptions logged from a SetClientData call. Are you sure there wasn't a later log file (e.g. SimConnect4.log)? So, sorry, but I am at a loss what is causing this issue, and not sure what to advise or how to investigate further at the moment. I really need to be able to reproduce this issue to investigate further...

Sorry, are you saying that you now don't get the error when the GSX_AUTO script is not running?

Can you also try without the GSX_AUTO lua script running, to see if that makes a difference....

In an unrelated issue, you have a missing joystick: as the GUID of this device has changed: You could have corrected this, but it looks like you have already re-assigned quite a few thinks to the F device. To correct this, review all your assignments to D, and either delete or change them to F. Then remove those two D entries. If this happens again, you can recover by copying the GUID value of the new entry to the old one, and then remove the new entries,

If I can't reproduce here, I will need to see your SimConnect.log file. See the FAQ section on how to enable this: They will be very large... Also, check the max number of simconnect clients allowed in your SimConnect.xml file (MaxClients), and set to a minimum of 64 if not already.

How long? Its been running here for > 30mins without an issue so far, and the Auto script is also running, and I have assigned buttons to toggle the flags, and can't reproduce the error whatever I do. So this does seem peculiar to your set-up somehow...

I cannot reproduce here - both scripts seem to run just fine... Are you using any other WAPI clients at the same time? If so, do you have any WAPI log files for those? What are these programs that you are also running: ? Can you try with those disabled to see if that makes a difference please. And this change occurred when you set trace logging? If you go back to Debug or Info logging, does iiiit revert to previous behaviour? This is all very strange....

Unfortunately your logs still don't reveal much. I will need to see a SimConnect.log file, but it may be easier if I can reproduce the issue here. You say: How do you trigger these functions? By setting a flag (1-8)?

Sorry, I meant if this was a new issue in 7.3.23, or if this was working in a previous version and if so what version that was.

Could you try the attached version please. There is a minor change, but I don't think this will resolve your issue. but I have added extra logging which should help me track this down. Can you activated logging for Extras and show me the log file from this version. Thanks. John FSUIPC7.exe

License sent. John

I have moved your post to the FSUIPC7 support sub-forum. You should really try FSUIPC7 before purchasing - a trial license is available via a topic/post at the top of this forum. The SDK is only one part of FSUIPC, and that is for developers and free to use (ie. no license required). Start with the FSUPC7 User guide, which will have been installed in a FSUIPC7 folder of your Windows Documents folder. This should explain how to assign and calibrate an axis. John

👍

Is this a new issue with 7.3.24? Could you try the attached version please - I have just updated the logging to log the error number for the failed execute calc code call. Can you repeat your test with this version, set Debug level logging un the WAPI, and then show me your updated FSUIPC7.log file, as well as your FSUIPC7.ini file and your FSUIPC_WASM.log file. Maybe also a good idea to set Debug level logging in the WASM as well. John FSUIPC7.exe

You don't need to put them anywhere, you just need to look at the header file if you want to use the PMDG custom controls as the numbers you need are defined there - see the following FAQ entry on how to use these: However, it is far easier to use the available PMDG presets, and if you update to the latest version of FSUIPC you will see a Find Preset... button which should help in finding available presets. John

I also need to see your FSUIPC7.log file with relevant logging - see my previous comment. You are als0 using a very old version of FSUIPC7 (7.3.10) - please update to the latest version, 7.3.24, before anything else. Your 737_Oprions.ini file is also strangely empty. You should re-install the PMDG just in case, and also check you are using the latest version, 3.0.72

I don't understand why you are getting these: Are those logged before or after you exit MSFS? Open the logging console window and check the messages before exiting. As you are in the main menu, FSUIPC should not be sending events... I will look further tomorrow, but for now can you update to the latest version of FSUIPC7, 7.3.24, which I released earlier, and try with that. John

I didn't....!

Ok, but no problem showing those here, they are only useful to me and SimMarket. I have checked your keys here and they validate just fine. Are you sure that you are using the correct WideFS7 key, the one starting with T?

Let me know your order numbers for FSUIPC6 and WideFS7 and I can check them here. Use the main support forum (one up from this): https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Yes, it is the correct version - it works with FSUIPC4, 5, 6 & 7, and the simulators they support. You need all 3 parts - key, name and address/email, and they must all match the details specified in your simmarket purchase email or account. If the name or/and address/email differ from your FSUIPC6 details, you need to check the appropriate box and enter those details as well. Did you re-run the FSUIPC6 installer to register your WideFS7 license? Did your FSUIPC6 key validate ok? Btw, you posted in the FSUIPC7 / MSFS sub-forum for some reason. Please use the main support forum in future if your issue is related to FSUIPC6 / P3D, although I do accept WideFS7 questions in both forums.

Could you try changing these in your FSUIPC7.ini file's [General] section: TrafficStallTime=10 InitialStallTime=30 to TrafficStallTime=-5 InitialStallTime=-5 to see if that makes a difference. If you get the same issue, can you attach your FSUIPC7.ini file (again) together with your FSUIPC7,log file.

No, it is MSFS that starts FSUIPC7 anyway, via the EXE.xml file. It is strange - I can't see how they can be added back - how would FSYUPC know what to add back if it was removed? Something else must be going on....

It is better to keep the default profiles, and just create a new (and empty) profile for your devices for FSUIPC. What axis controls are you assigning to? There are several to choose from - if one doesn't work, try another. You can also try activating logging for Axes Controls (Log -> Axes Controls), open the logging console (Log -> Open Console), and see what is logged when you move the axis in the VC, and then use that. But I don't have the ProSim 737 fir MSFS, so it is difficult for me to advise. I think there is/was an 'FSUIPC compatibility' mode that you may need to activate in ProSim. You should consult the ProSim documentation or ask on the ProSim forums