John Dowson

Do you know when this occurs? Can you provide steps to reproduce? I have been using FSUIPC7 on a multi-monitor set-up (3 monitors) with FSUIPC7 positioned on different monitors and I haven't noticed it losing the monitor or correct position so far. Are you maybe using nvidia surround configuration? Are your monitor ids changing? If you can let me know how I can reproduce I'll look into it.

Ok, thanks for reporting back.

@pilotjohn Rather than confusing the button/key definition with adding syntax for a delay, I've decided to add a pause control (C1152). You can use this to add a delay either before or after a keypress or button assignment, by overloading the assignment. Here's an example of inserting a delay between two controls being sent (to control the 3-way off->Taxi->LNG lights toggle in the TBM930): The parameter to the control is the delay in milliseconds (600ms in the above example). (NB. there is minor issue in that the FSUIPC added controls are currently not annotated/commented correctly) This added control is available in version 7.0.2a attached below. Cheers, John FSUIPC7.exe

I have added a pause control now, so you can add the pause in the assignments if you like rather than using the lua. These assignments would do the same as the lua (update index numbers accordingly): Of course, you can continue using the lua, but the pause control will be available if you need it for anything similar in the future. Its in the following version, and will be released officially when I release 7.0.2: FSUIPC7.exe

I'm not familiar with that device, so not sure how the "throttle cursor" is seen by FSUIPC. If its an axis, you can assign to the left/right brake axis and calibrate. If its a button, then you could look into using the lua posted here:

Hi, I presume that you are talking about mouse macros. I'm not sure why this would reduce your FPS so much. Does it return to normal once you have finished creating the mouse macro? Can you still create the mouse macro? I don't have any fslabs aircraft, but I think there are quite a few people who are using FSUIPC6 with them. You may be better off asking over on the FSLabs forums. There's also a good guide to using FSUIPC with the FSL A3xx aircraft on their forums: https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/

The usual way to find out if there are any controls/events assignable is to activate logging of non-axis events. You can then see what events are being used when you activate the UI control, and use the same event when you program your button or switch. However, there are currently many reasons why this may not work: - some functions may be performed internally by the guage software. If this is the case, you won't see any events. In previous FS versions, such functionality could be handled by using lvars (local variables), if provided. Currently in MSFS/FSUIPC7 there is no access to such variables - some events that are triggered by activating controls in the UI have no affect when sending them via SimConnect. This is a known issue for many events (e.g. view and slew controls) - some controls work in some aircraft but not others. The airliners seem to suffer from this the most, especially the A320Neo. This is probably due to the fact that they model more of the systems than relying on the internal models. There are various tricks, tips and mods around, especially for the A320Neo it seems. Try searching the forums (here and the msfs/asobo ones). Duplicating mouse wheel operations (to program functions not available via SimConnect or using lvars) was a feature of previous versions of FSUIPC (i.e. in v4, 5 and 6). However, the functionality to implement this is currently not available in the MSFS SDK. We will look into adding this back once the functionality is available in the SDK. Please remember that even though MSFS is now released, the SimConnect SDK (which is what third party products rely on to communicate to the FS) is still at version 0.7.1. Things should improve as the SDK develops. John

With auto-connect disabled, it will only connect when you tell it to. You can only connect once FSUIPC7 has detected MSFS is running, and you can connect as soon as MSFS' SimConnect interface is ready, which occurs sometime during loading. However, if connecting manually, best to do it once MSFS has loaded and is on the home screen. You don't have to have an aircraft loaded, although other things (e.g. WideServer, luas, etc) won't be started until an aircraft is loaded.

Just checked this in P3Dv4/5 and FSUIPC5/6. Its the same problem there, but as FSUIPC5/6 is a dll rathe rthan a separate application, the controller works when P3D has the focus but not when other applications have the focus. As I said, I will look into this but it may take a while.

Sorry, that is only for the polling of your button assignments. In the HidDemo.luia, adjust the Pollrate variable instead.

Hi Nigel, ok, I can see the issue. With my xbox game controller, connecting via bluetooth its reported as: whereas cabled: However, in both cases it suffers from the problem that FSUIPC7 only recognises inputs from this device when FSUIPC7 has the focus. I'll look into it and get back to you, although this may take a while. I'll also talk to Oliver/Lorby. Thanks for reporting this, regards, John

Not sure. You could try looking at the Rotaries.lua example to see if that helps. You could also try adjusting the PollInterval in your [Buttons] section of your ini.

Looking at your registry entries, it seems that both the xbox controller and your CLSE NG Yoke have duplicate entries. Can you: - disconnect the CLSE NG Yoke and cbox controller - remove any software or additional drivers that you have installed for the yoke. - reboot (leaving devices still disconnected). - start regedit, and make a back-up of your registry - create a ,reg file (e.g. removeDevs.reg) wth the following content: - run the regedit file (i.e. double click it in windows explorer You can then connect your devices again and install any software or drivers needed for the Yoke. Delete your current FSUIPC7.ini file and restart FSUIPC7. Then lets see what devices are reported in your FSUIPC7.log, .ini and .Joyscan.csv files.

If the wheel is the middle button, then 2 would be click - 8 is middle button click and drag. You can also look into use 14, 15 and 12. Anyway, you've found the codes on page 33 of the User guide so just try different sequences to see if any work. It may be easier and more reliable to use controls or lvars, if available.

Could you see any movement of the axis on the axis assignment dialog? So pause works, which indicates that button input and also sending events/controls to the sim. You don't have any errors in your log, simconnect or otherwise. Does this occur all the time, or occasionally? Have you changed anything recently? You seem to keep having issues that get resolved, only to re-appear several days later.... You could try changing this: NormalStallTime=-2 to NormalStallTime=1 in the [General] section of your ini, although I don't think this will make any difference in this case (as there are no stall messages and simconnect seems to still be working). You could also try re-activating the SimConnect log file, to see if that reports anything.

I could add such an option. At the moment its tied to the 'Auto-Connect to FS' option, so if you disable that it will start maximised. John

It is showing 2 xbox controllers, not 4 - the other 2 entries are the joy letter assignments. The problem is with your registry, with duplicate entries for the xbox one controller. I'll take a look later today and provide you with a script to run to remove the duplicate entries.

So you can seem them in the windows game controller properties panel? Do they show as buttons or axes? You can also check your FSUIPC log file to see how many buttons/axes are recognised. I have an X-55 which has 35 buttons, so there aare 3 that I cannot access using the FSUIPC assignments panel:

Hi Robin. in nearly all cases this is due to entering incorrect information in the provided fields. However, there was one report where the registration was valid but it could not be validated on the user's system. This tuned out to be due to a corrupt installation of the VC++ redistributables. To check this, could you just try running FSUIPC (using the FSUIPC7.exe, not the link or .bat file that starts MSFS + FSUIPC) to see if it starts (unregistered). If it does, we can try manually adding the fsuipc7.key file.

No. Even if FSUIPC tries to mask the input events so that they are not seen by MSFS, they still are, so assignments in MSFS also have an affect.

Maybe check your logfile (FSUIPC7.log) file to see what controllers fsuipc has found, and you can check the FSUIPC7.ini file to see what letters have been assigned to available controllers. but something must have changed. They were initially empty and now show joy# E and Axis # Z. If you move that axis, the numbers in the In and Out fields should change. If its not your throttle, clicking Ignore Axis will ignore that axis, so then click rescan and move your throttle. You should then get a different axis # and possibly a different joy#.

Yes, sounds like that axis is continually sending something. You can ignore that axis for the current assignment session (i.e. until you close the panel or clear) by clicking the Ignore Axis button. You can still assign to that axis though, if you wish.

Can you attach your FSUIPC7.ini please.

Ok, thanks for reporting back. I've had several complaints around this and similar issues, and they all turn out to be due to a corrupt windows installation, mainly regarding the windows VC++ redistributables. Once this is confirmed , I usually advise to uninstall the 2019, 2017 and 2015 VS++ redistributables and then re-install - 2015 then 2017 and finally 2019. However, the issue is confused by using the link that starts MSFS and then FSUIPC7 later after quite a long delay which seems to confuse folks. This is explained in the provided documentation though. Anyway, glad your problems are now resolved. John

Please remember to attach your newly generated log file when you have made changes and still have an issue. It may be a corrupt weather file. Try deleting the wxstationlist.bin file from your ...\AppData\Roaming\Microsoft\FSX folder (it will be regenerated on start-up). After doing that and re-starting, if you get issues again please remember to attach you FSUIPC4.log file. If it crashes so soon, you may also have corrupted the SimConnect.xml file somehow when you edited it. What editor did you use? Check the file again, and make sure that it has the correct/original encoding. Its difficult to advise without seeing your log file....