John Dowson

Yes, you will need to give it a value...probably also a good idea to use repeat when assigning to that preset as well.

But why? Why not just do the correction I suggested? It was detected: However, it was not acquired as you now have registry issues: Continually unplugging and changing USB ports can cause registry issues. Please go back to your previous ini, make the changes I suggested and try again. If you still get issues, please attach your log and ini files again please, as well as the JoyScan.csv file. No, it is due to registry issues. If assi9gning in FSUIPC, we recommend that you disable controllers completely in P3D. If you don't do this, please make sure that you don't have dual assignments, i.e. an axis or button/switch assigned in both FSUIPC and P3D. Also, P3D has a tendency to auto-detect your controllers (if not disabled) and then make default assignments, which can cause issues if already assigned in FSUIPC. John

So it looks like those lvars are acting like a control/event - you set it to 1, this triggers the brightness increase or decrease and then the lvar gets reset back to 0. If you want to inc / dec again, you can set it to 1 again. Does it not work like that? If not, ask on the Inbuilds forums on how those lvars are supposed to work. I don't have this aircraft so cannot take a look here, sorry. John

Those are just events that are being logged....FSUIPC logs ALL events applied to the FS. Why do you think that those are coming from FSUIPC or WideClient? If you have no assignments in FSUIPC / WideFS, they won't be coming from there... Try setting logging for Buttons & Switches - that will log any button press that is triggering an assignment. If those events are being sent from your device and you don't want them to be sent, remove whatever you are using that is sending them. Note that many aircraft in MSFS continually emit certain events, and these event are different for each aircraft. These events are just noise really, and you can prevent them being logged using the DontLogThese ini parameter. No, as they are most probably not coming from FSUIPC or WideFS. FSUIPC is just logging them, not sending them.

You can try setting ButtonScanInterval=0 From the WideFS User guide:

All offsets in the documentation start with 0x and not $. But also only the starting offset is documented (together with the size), so rather than searching for a specific offset, just scroll down to you find the entry that documents the range for the offset you are interested in. Yes - almost all the offsets that have been allocated to 3rd party software use was done many years ago, before my time, and I have no idea what these offsets are used for in most cases! Cheers, John

Note that I also need to see the WideServer.log files for issues with WideFS... However, it should be obvious why it didn't connect the first time you ran FSUIPC7 if you look at your log file: FSUIPC7 never connected to MSFS and the WideServer was never started. Note that, by default, WideServer is not started until FSUIPC7 is connected and you have an aircraft loaded and ready-to-fly. The first thing you need to do is to delay the start of SPAD,next and vPilot until at lease FSUIPC is connected top the FS (i.e. add the CONNECTED keyword). vPilot could be started even later, using the READY keyword. Once that is corrected, try again and take a look at your log file. If you see the following message: 48891 **** SimConnect open event not received in required time limit: Re-connecting now... then you should adjust the DetectToConnectDelayAuto ini parameter. Please see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, or the following FAQ entry: John

Was this ever working then? Keysend works via windows messages. How are you starting the Discord PTT program? Have you tried directing the keypress to the Discord PTT program? If not, see the WideFS Technical guide from section Directing Key Strokes more precisely and onwards, John

Well, it cannot create the ini file if it isn't running. P3D starts FSUIPC from either the DLL.xml file or the Documents\Prepar3d v? Add-ons\FSUIPC6\add-on.xml file (depending on P3D version and maybe the components selected during installation), which are either modified or created when you install and has absolutely nothing at all to do with your ini file. Check you InstallFSUIPC6.log file for details. Changing the ini file can in no way affect the starting of FSUIPC6, so you must have also done something else. You can always try re-installing FSUIPC6 to see if that helps, and if not then show me / attach your InstallFSUIPC6.log file. John

Yes - its 5.1.4.

7.5.2e is a beta version, and you should not have received any notification for this as only official releases will prompt a message to download, When you re-install, it is far easier to just install into the same folder. This will then just replace the installed files and leave all other files (e.g. settings, key, lua sctipts, macros, dlls, etc). 7.5.2 is the latest official release, and it should say that 7.5.2 is available, and not 7.5.2e. If you are using 7.5.2e, then you are using the last beta of 7.5.2. You should ypdate to the latest official release (hence the message), although there will be no actual difference in the versions (7.5.2e was the last beta and was released as 7.5.2). Please also use the FSUIPC7 support sub-forum for all issues/questions with FSUIPC7, and not the main support forum. I have moved your post. John

Again, all information on offsets is in the FSUIPC7 Offset Status document - why don't you look at that? I provide extensive documentation so that I do not have to spen all day responding to such questions. Please ALWAYS consult the documentation (as well as checking these forums) before posting questions.

No hay ningún problema con su licencia: Consulte la documentación - Installation and Regisuration guide. Los problemas de validación siempre se deben a: - introducir los datos incorrectos - no tener instalados los redistribuibles de VC++ correctos - problemas con el antivirus Todo esto se explica en la documentación, aunque solo está disponible en inglés.

Does that even work? Should be: i.e. presets names should be preceded by 'P:'. Macros are ran in the main thread, and will block that thread until it has finished. If a macro is going to take more than a few hundred ms to complete (and you have an 8 second delay there!), you should use a lua script instead. Lua scripts are ram om separate threads. John

👍

Ah - maybe these are 'scoped' local variables? See https://devsupport.flightsimulator.com/t/how-to-access-scoped-lvars-l-with-simconnect/12540/20

This issue is continually getting reported, and my answer is always the same. Please see one of the other many posts on exactly the same issue: ...etc Basically read the documentation and follow the advise there, and also check out the many posts on exactly the same issue.

So it looks like the GUIDs have changed, not only for that device but also for your Saitek Pro Flight X-55 Rhino Stick, which now has two device letters D and E. If the GUID if your MIAP STD is now that in the C entry, but your assignments are referencing B, then switch the GUIDs and remove the C entry, ie. You should also do similar for your Saitek Pro Flight X-55 Rhino Stick. Also, please attach the full ini file next time rather than posting extracts, and also attach your FSUIPC7.log file for any further issues. John

From the FSUIPC7 Offset status document - 3584 bytes starting at offset 0x5200: i.e. Offset 0x5428 is in an offset area that has been allocated to Project Magenta, and you need to look at the PM documentation or ask them what that offset is used for. John

It is not actually hanging is it, its just waiting for a connection, no? Does it connect automatically when you restart FSUIPC, or do you have to also restart the WideClient? Can you please show me / attach your FSUIPC7.log and WideServer.log files, both from when it initially fails to connect (and after you have exited FSUIPC7) and also from after when you restart it and it connects.

You should sort out the disconnection issues shown on your log. There are no changes from any version that cause performance issues - your problem lies elsewhere. You can try an older version if you like (not that this will help!) - current/latest version is: https://fsuipc.com/download/Install_FSUIPC7.5.2.zip previous version: https://fsuipc.com/download/Install_FSUIPC7.5.1.zip older versions: https://fsuipc.com/download/Install_FSUIPC7.5.0.zip https://fsuipc.com/download/Install_FSUIPC7.4.17.zip https://fsuipc.com/download/Install_FSUIPC7.4.15.zip etc.

It doesn't make sense to allow this in FSUIPC due to the way calibration works in FSUIPC. FSUIPC calibrates to an FS control, and as there is no specific control/event when assigning to a preset, it does not know the range to calibrate to. Max/min/scaling etc can easily be handled, either in the RPN itself. or you can just write the axis value to an offset and do whatever you want with it before using it in a preset.

All I can see in those images is that one has an FPS of 127 and the other of 110. Isn't an FPS of 110 enough? The log file you attached is very strange, as it just shows FSUIPC connecting and disconnecting, It makes no sense to me, and you have not provided any context. What actually happened? What/why is FSUIPC closing shortly after being started: ?

The log file you attached was attached when FSUIPC was still running and also stops after 30 seconds. You are also using an old an unsupported version of FSUIPC. Only the latest version is supported - please update. And your ini file shows that you are not actually using FSUIPC for anything. You only have one (strange) button assignment, you have profiles but they are empty, and you [MacroFiles] section is very weird... Are you assigning in MobiFlight? i cannot support mobiflight - please use their support channels (discord) for issues with MF.

How have you assigned? There can be toggle controls, set controls that take a parameter (on/off) and separate on/off controls. So it depends on how you have assigned. You can also use offset conditions to check the state of a button before changing it, if require. Please show me / attach your ini file so that I can see your assignments.