nbillo

1409408 was the first purchased with FSUIPC4 2883400 was yesterday. Kind Regards

Thanks John, I thought I boobed, straight after I'd bought it. I will contact Peter to see if he feels generous. Merry Christmas mate.

John, Peter, Can you tell me if I bought an extra copy of WIDEFS without needing to? I had purchased WIDEFS along with FSUIPC5, at least I think it was and this version. Anyway, this purchase also registered and worked without issue into my FSUIPC6 purchase. I purchased FSUIPC7 for MSFS and tried to use my reg key but I was told this version wasn't compatible, so I carried on and didn't give it a second thought. When I needed the Wide client to connect to MSFS whilst attempting to get my flightdeck working in the sim, I tried again to register my version. This failed telling me it wasn't a valid registration key. I went and purchased another copy of WIDEFS7 from SimMarket yesterday, and when inputting my new key, I was greeted with the same 'registration key not valid' pop up. Reading the user pdf, it mentioned about adding your key to the .key file, which is what I did and now I have the WideFS tab function within FSUIPC7. My question is, would I have had the same result, if I had entered my original WIDEFS7 key into the .key file, negating the need to purchase a second copy? Kind Regards Nigel

Hi John, Thank you for your interest in this issue. Okay, I understand now why I haven't had any problems running the controller with either P3Dv4/5 Thanks for your time. Kind Regards Nigel

Hi John, Thanks for your time. I could use the MSFS built in system, but it will not allow me to utilise the rudder axis to the triggers on the Xbox1 controller for some reason. I can only assign digital yaw inputs which are just terrible and virtually uncontrollable. This is the main reason why I wanted to use FSUIPC in MSFS, apart from the fact, I've been using it for many years and I am just so used to liking the flexibility it brings. I do use the Saitek X-55 Rhino stick and rudder combo, but that is while I am somewhere else which is usually shorter periods. Where I spend most of my working time, I don't have these items with me. It looks like this is the same issue that I had previously and to do with the Xinput api. You mention that you have an Xbox1 controller and will test it this week. I would certainly appreciate if you would consider using both api's, I'm sure there are plenty of people who own these and use them in the other sims and would like to use them in MSFS. Because of my work and travel, I find using this controller much more easy to carry about, and I guess I have gotten quite used to using it, giving me the option to pan and view with one stick and control the aircraft with the other, is so nice. Kind Regards Nigel

Hi John, Well, I deleted the ini file and started again. I've created a new profile without any reference to the controller, although I can't see why that would make any difference. I have a profile loaded using the MSFS built-in system, but that is using the view commands, which I am using for my left stick only. I have set up a profile in FSUIPC for my right stick and that is assigned to the ailerons/elevator, and the triggers are set for the rudder. These are direct to FSUIPC, which is what I normally use in P3D. If I have the FSUIPC window open and its in focus, I can see the controls moving quite normally. If I click into the sim and FSUIPC is not in focus, the controls stop working. I had a similar issue when using AaO from Lorbi during the beta phase of MSFS and he very kindly did some testing and told me the XBOX1 Controller uses the Xinput API, and he was using DirectInput for his program. He did some changes and managed to get the XBOX1 controller working in the sim. I guess you will be using the same for FSUIPC, and so it won't ever work for my XBOX1 Controller. Do you think that is the reason? Kind Regards Nigel FSUIPC7.JoyScan.csv

Hi John, Pete I've purchased and downloaded FSUIPC7 to use with MSFS2020. I have installed the program and can connect to the sim and I create a new profile. I go through the set up to add my axis which appears in the program as per the manual. However, when I make the sim window active again, the axis do not work nor do any of the mapped buttons from my controller. If I have FSUIPC window in focus/on top, the aircraft control surfaces move, yet when I click back in the sim and FSUIPC is not in focus, the controls no longer function. Am I doing something wrong? I have read through the manual and everything seems to configure correctly, but when I have the sim window active, the controls stop working. I have tried this with the sim using full screen and in windowed mode but it's the same. I have a complete clear profile set up within MSFS so there are no conflicts anywhere. I am using an XBOX1 controller, while working away and I use my gaming laptop for my flying. I have been using FSUIPC since v3 so I am certainly no novice when it comes to the FSUIPC program. I also use FSUIPC6 with P3Dv5, on the same machine and I have no issues with assigning and calibrating my XBOX1 controller in that. It's just with FSUIPC7. I've also tried assigning another JOY ID number using JoyID but that doesn't make any difference. I end up having to stop using FSUIPC and re-enable the axis back in MSFS, but that is just terrible, especially for rudder control. I've attached my log files in case they shed any light on the issue. Have you any idea as to why this is happening? Kind Regards Nigel Bilton FSUIPC7.log FSUIPC7.ini

Yeah, not to worry mate, I was trying to break the ice with some Brit Sarcasm 🤣 It's going to take time to evolve, but oh boy! what a sim this is going to be 😱 I'm just pleased that after 32 years of simming, I get to see something as glorious as this!! What a bright future the youngsters are going to have with this wonderful hobby 😂👌

😂 You're certainly not a chip off the old block are you 👍

I had exactly the same problem only yesterday with my x55 combo. Everything was fine and fsuipc was seeing the axis and buttons one day, and the next day for no apparent reason, Windows stopped seeing the axis and buttons. Both devices were shown as healthy and the icons were visible so it looked like everything was working normal. So It's nothing to do with fsuipc, it's Windows that's causing the problem. I surmise you are using Windows 10. There appears to be a problem with the madcatz drivers and windows 10. I've got a support ticket out with them and they are looking into it. Anyway, after endless searching I read a thread on Avsim a while back where someone was having a similar problem and they fixed it by changing the device ID's in Windows. I downloaded and installed this brilliant little utility called JoyIDsInstall.exe which enables you to change the device ID in Windows. As soon as I changed both the throttle and stick ID's, Windows allowed both devices to calibrate as normal and because Windows could now do this, fsuipc could also see the axis and buttons again. Everything was back to normal with fsuipc. Hope this helps ☺