Kalnon

Hello, I'm not sure if this is an FSUIPC4 problem but I can't figure out what else may be causing my issues so I wanted to start here. I set up my Thrustmaster TWCS HOTAS throttle to use as the collective in a helicopter and it seems something is fighting it, as if another axis is interfering or something (the collective in the helicopter keeps moving up and down by itself) but I double and triple checked and I have absolutely nothing else bound to the throttle command except the TWCS throttle axis. I checked in Windows Devices and Printers to make sure the TWCS throttle axis isn't spiking and it's not. I made sure no axis's where bound in the FSX control settings causing conflicts, there are none. I also tried deleting the FSUIPC4.ini file and rebound all my controls but this didn't help either. My HOTAS drivers are up to date as is Windows 10 itself and FSUPIC4, all are updated to the latest versions. I just can't figure out what the heck else is causing this. I would greatly appreciate any help, with this or at least try to rule out FSUIPC as the problem, thank you. (I can't recall all the files you require to troubleshoot so if you need a different file uploaded, let me know) FSUIPC4 Install.log FSUIPC4.ini

Thank you so much John! I will give the trial a try first then and see how it goes. From your answer to my question, I have a good feeling FSUIPC 7 is exactly what I need to give me more control on adjusting sensitivity. I really appreciate the info on how to change sensitivity in the .ini file, I had no idea I could do that. I will probably be tinkering with those values a lot I have a feeling. As I said before, I have never been able to get airplanes to feel right when using my yoke in MSFS and for that reason, I haven't used MSFS a lot. FSX, P3Dv5 and X-Plane 11 and 12 feel much more realistic to me. I hope FSUIPC will help, it certainly did for FSX and P3D. Thank you for your time and all your efforts that allows me to use those sims to their full potential.

I have a Honeycomb Alpha flight yoke and for MSFS I'm having a hard time setting up the sensitivity so that it feels more realistic. If I set the yoke sensitivity, especially for the roll axis, just using the in game sensitivity settings to match the VC yoke, airplanes feel way too twitchy and oversensitive. I did some web searches and found a bunch of people trying to figure this out but no one seems to have found any real solutions in all the different forum posts I've read except to turn the sensitivity way down. Of course, then it doesn't match the VC yoke which I find extremely annoying. I want the aircraft to respond as realistically as possible to yoke inputs and I am just wondering if using FSUIPC 7 to set up the yoke axis's works better would make the aircraft feel more realistic than using just the in game settings? I do not own it yet but if it does, I will definitely buy it. I do use FSUPIC 4 for FSX:SE and FSUIPC 6 for P3Dv5 and I have no issues with yoke sensitivity and using FSUIPC to set up my yoke in those sims. It feels realistic and it actually matches the VC yoke. All I have to do is adjust the sensitivity setting within FSUIPC to match the yoke of whatever plane I'm flying at it feels perfect. I just want to know if FSUIPC 7 would do the same for MSFS that it does for FSX and P3D?

Ok, I was actually going to give that a try but now I no longer see the error message when I start FSX, it seems to have fixed itself. If it happens again, I will try that.

Interesting, thank you so much. Unlike the others, when I click yes FSX still loads just fine and FSUIPC still seems to be working ok.

Also here's the install.log in case it's also helpful FSUIPC4 Install.log

Hi, I just booted up FSX:SE today and received the error message in the screenshot below. It says there's something wrong with the FSUIPC.dll file. I've uploaded my .ini and .log files if it will help. I even tried reinstalling it but I still get the same error message. I appreciate any help, thanks. FSUIPC4.ini FSUIPC4.log

Well, I think I have the yoke fixed and working properly now. The slope I had adjusted it to was causing the issue with FSUIPC not correctly reading my ailerons axis. What is strange though is for me, when the slope is set to 15, it's even less sensitive and setting it to -15 made it more sensitive which is backwards from what you just explained it's supposed to work. I believe you when you said setting it to -15 would give very little movement, after all you are the creator of FSUIPC but for some strange reason, for me it's backwards. After a little tinkering, I found that when the slope to about -7 makes it just sensitive enough to perfectly match the VC yoke the entire way and it now sees the entire axis unlike before. If you would like, I could create a little YouTube video showing what it does when I adjust slope if you would like to see, just let me know. Otherwise, my issues now seem to be solved. Thank you so much for all of your help, I greatly appreciate it. And again, thanks for making such great software that allows me to use my yoke with FSX. Without it, the yoke sensitivity is so far off, I would never be able to fly with my yoke at all. Edit: I also changed the input setting to Send direct to FSUIPC Calibration as you suggested.

I also switched to a USB 2.0 port (different one than origanlly) and I updated to the current version of FSUIPC.

Here's with the yoke plugged in. FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log

I have all axis of the 16000M assigned directly to FSX, I never assigned it to FSUIPC at all. It is the Alpha yoke that I had assigned using FSUIPC but just the ailerons. I do however have the pitch for the Alpha assigned directly to FSX since the pitch seems to work just fine that way so I never assigned that axis to FSUIPC. I did have the Alpha unplugged when I was testing the 16000M so maybe that could be why? It's necessary for me to unplug the Alpha when I switch to the 16000M due to the limited room on my desk. I keep the 16000M and TWCS throttle always plugged in because I use it more often than the yoke since I also use it for games like IL-2 Sturmovik BOS and Star Citizen. If you think it would help, I can reconnect the yoke and then send you the log files again.

Ok I did what you instructed and in the FSUIPC interface it doesn't recognize the joystick at all but it does recognize the throttle. I am not too worried about this since it works fine just binding it using the regular FSX control settings, though it would be nice to have that option if I ever needed it. I don't know if there was ever an issue with it before since I haven't yet tried to bind it using FSUIPC until now. There is another issue I am having regarding my yoke that I've always had since I first started using it with FSX is that FSUIPC doesn't seem to recognize the full length of the axis for the ailerons or it thinks the axis is shorter than it is. At least from what I see the VC yoke doing. When I turn all the way to the left, the VC yoke goes almost all the way except for maybe only a quarter to a half an inch worth of the last bit of travel which is good enough to me but when I turn it all the way to the right, the VC yoke stops traveling or maxes out when I still have around 2 inches worth of travel still left on the Alpha yoke. I can still fly just fine most of the time unless I'm stunting with a yoke aircraft, which is rare. I was just wondering if that is a normal issue with this yoke or is it just me? FSUIPC4.log FSUIPC4.ini FSUIPC4.JoyScan.csv

Well, you were right. It seems to have been related to the particular USB port I had it plugged in to. I just simply switched USB ports and it seems to be reading the yoke just fine now. I know you said to plug it into a USB 2.0 port but that's what I was already using. Instead I plugged it into a USB 3.0 port. I'm wondering if maybe my particular yoke needs the extra power that a USB 3.0 or 3.1 port can provide. I don't know if you are familiar with my particular yoke but it does have a bunch of LED lights and the whole front panel lights up, plus it has a bunch of switches on it so maybe it just needed the extra power to run correctly, either that or I have a USB port going bad. I've added those log files again just in case you would like to go through them to make sure everything's looks good there now. Thank you for your help I greatly appreciate it. And thanks for making such an important software so that I'm able to use my new yoke and other controls properly with FSX. FSUIPC4.log FSUIPC4.ini FSUIPC4.JoyScan.csv

Could you possibly tell me what to check for in the registry that may be causing the issue? I do know basic stuff about using it and how to change values and stuff, and of course, always make a backup, as I learned the hard way once 🙂

Here is the file you asked for. I will check into the things you've mentioned as soon as I have the time to troubleshoot the USB issue and test and get back to you. It is plugged directly into a USB port. I did previously have it assigned but like I said I just did a complete reinstall because my FSX install went to hell. I was having issues with it crashing often and it was running much worse than it usually did to performance wise. I ran the verify files utility on Steam and it found over 8,000 files missing somehow. I did however have the yoke assigned before it did and it worked fine until recently. I was having all these issues as well as the yoke stop working at the same time. Weird thing is that in MSFS it works just fine. Happy New Years to you as well. Cheers! FSUIPC4.JoyScan.csv