John Dowson

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....

It doesn't. But naming a controller after a profile indicates that you are not familiar with profiles or how they are used. Of course, you may perfectly understand how they work, but then its a strange name to give a profile... Ok, then we are talking about assignments to your xbox controller. FSUIPC also uses direct input, so it may be the same issue. I have an xbox controller so I'll take a look next week sometime. xbox controllers are handled pretty well in the default MSFS assignment profile, so why don't you use this? I thought/assumed that you were trying to set up your Saitek Pro Flight X-55 Rhino Stick, but this seems no longer connected.

Yes, why not? The different entries are just for different protocols.

One of those log files shows that there was a sSimConnect problem. There is a know issue with SimConnect having issues during long flights due to the number of clients being exceeded. You could try increasing the maximum number of SimConnect clients allowed - please see the following (from a related post):

Btw you have one profile called MSFS XBOX1 CONTROLLER. It is not a good idea to name your profiles after a controller, after all they apply to ALL your controllers. It is best to name them after a specific aircraft or an aircraft type (e.g. single prop, jet, etc). Also, for the xbox controller, I find it better to use this as set-up by default in MSFS.

I don't think so... If you are using LINDA you really need LINDA support. You could try without LINDA - just temporarily disable (i.e. rename your ipcReady.lua) and activate button logging in FSUIPC7 and see if it recognises your buttons reliably without LINDA. John Later: also make sure you are using the latest version of FSUIPC7 (i.e. download and re-install, just in case). May also be worth removing the contents of the [General] section of your FSUIPC7.ini and let that get re-built.

Hi Nigel, could you remove the contents of the [General] section from your FSUIPC7.ini. This will be rebuilt with the updated defaults the next time you run FSUIPC7. Your ini shows that you only have assignments to your xbox controller. Are these not working? Your log shows no other device is recognised, i.e. your X-55 Rhino stick was not connected. If you have installed the saitek software and/or drivers, you should remove these and try again. You should also check the power management settings on your usb hubs, to make sure windows isn't putting them to sleep. If you are still having problems getting your stick recognised, please show me your FSUIPC7.Joyscan.csv file.

@lauri1526 I have just sent you a message. Please follow the advices there. I repeat it here: SimMarket handle all sales. Ask them, but I doubt it - see their policy. You certainly haven't! I don't even know what your problem is at the moment. Please follow my advise and report back. And please use the forums for support. I do not provide support via private messages, and only use messages to verify keys. You key is obviously ok so you should first download the latest version and re-install and register. Once that is done, try running the FSUIPC7.exe, as advised, and any issues use the forums. John

As I keep saying, please contact SimMarket. They handle all sales.

If they are recognized by windows, they should be recognized by FSUIPC. Where are you looking? Usually rotaries are actually buttons, and have two buttons that register in each direction. So they should appear in the buttons & switches assignments tab. However, if they have been assigned button numbers > 32 they will not be seen in the assignments panels, and you will have to resort to lua if you want to use them with FSUIPC. There is an example lua script provided called HidDemo.lua that you can try if this is the case

Really? This problem relates to an old issue when the SimConnect.dll file was required to be installed. This has not been required for at least 3 months, so this is certaibly not your issue. Its a batch file, of course its not either 32 or 64 bit, but works on both systems (although FSUIPC7 is obviously 64 bit). Sorry, but I have no idea what your problem is. I suggest you at least read the provided documentation (Installation and Registration guide + the README.txt) and if you are still having issues then check the forums and post again giving details of your issue. Did you use exactly the same details as provided by SimMarket? Did you click the Register button? If so, what did the pop-up say when you did this? If not, do that. I am closing this topic. John

I just added it to the general [Auto] section to test. If you only want it in a profile, add it to the profile specific auto section (e.g. [Auto.xxxx] where xxxx is the profile name) instead. If the profile-specific Auto section doesn't exist (it won't unless already added), then add it.

Hi Dave, so the AI traffic tables are populated, but there is a problem with the From/To columns...I will look into it. But how come you are not able to read any data? It must be there if it is displayed in TrafficLook! John