July 30, 201213 yr Author Simeon, I updated the NGX to SP1c, installed the 600-700, and a bunch of liveries. Flew it for a brief time just to see what it was like. I was too lazy to change controllers, so I used the Flight Link helo controls . All seemed to work OK Then, I changed back to a Bell 206. KABOOM! First, the sound of the 737 was still present in the helo. And when I went to fly it, the rudders began getting those phantom inputs. You can see them "twitch" on the VC even though there is no actual physical input from the pedals. In looking at the file in FSUIPC, you can see the raw data change on its own. I'm wondering what would be causing that? Meanwhile, I uninstalled the 737 and had FSX rebuild the cfg file hoping that would solve the issue. Unfortunately, I think some resident file may have gotten clobbered somehow because the phantom inputs are still there. Hope that clarifies it for you. Thanks, Alan
July 30, 201213 yr Commercial Member Out of curiosity, your throttle quadrant....is it a serial port device? If so are you using a serial to USB converter. The symptoms you are having sound similar to those I was experiencing a few years ago when I was trying to convert all devices to USB. I switched back to a serial card in my PC and never had a problem. You can also check this out, I too just built a new rig and had plugged my USB hub into a USB 3.0 slot and my yoke inputs became very erratic...just something to have a quick look at. KROSWYND a.k.a KILO_WHISKEYMajestic Software Development/Support Sys 1: AMD 7950X3D, NOCTUA D15S, Gigabyte Elite B650, MSI 4090, 64Gb Ram, Corsair 850 Power Supply, 2x2TB M.2 Samsung 980s, 1x4TB WDD M.2, 6xNoctua 120mm case fans, LG C2 55" OLED running at 120Hz for the monitor, Win11. Sys 2: i7 8700k, MSI GAMING MBoard, 32Gigs RAM, MSI 4070Ti & EVGA 1080Ti. Hardware: Brunner CLS-E-NG Yoke, Fulcrum One yoke, TM TPR Rudder Pedals, Yoko TQ6+ NEO, StreamDeck, Tobii Eye Tracker, Virpil VPC MongoosT-50CM3 Base with a TM gripSIMULATORS: MSFS2020/XP12/P3D v5.4 & v6: YouTube Videos
July 30, 201213 yr Use FSUIPC and setup all your controls through it. By far the best solution. I fought this for years - and then one day I got smart..... I definitely agree 1000%!
July 30, 201213 yr Author Jim & Philip..I played with the USB ports..no joy..no difference. There's really nothing in the troubleshooting guiude of the GStick III that addresses the issue. Honestly, I don't think it's a problem with the device. Simeon..funny you should mention that. The PFC quadrant is a serial connection (pedals connect through the same box) and it was/is connected directly to a serial port. I also tried the serial/USB converter connector a long time back with no luck. So that's not an influence on this situation. Actually, I have disconnected those devices and am still getting the crosstalk/phantom inputs. I was explaing to Paul in a PM that even with no physical input on the helo rudder pedals, you can see the raw data numbers "jumping" when FSUIPC is opened up. Of course, FSUIPC is only "reporting" what it sees. So the question remains..what is causing those phantom inputs? Alan
July 30, 201213 yr Hi Radio Guy, I take it from all the inputs you are still using FSX axis controls to support your equipment. Those input spikes can come from a number of places, poor or bad USB connections, line noise, interrupts and the list goes on. You were right on about FSUIPC only reports what it sees, not WHY. i too had all the issues you have stated over your posts. As i said solved all of them by letting FSUIPC control, my input devices. I know that reading the FSUIPC guide can be a little daunting. One night I just gota good strong drink (lol), and dug into it. Pete has made it a little easier, by setting up profiles. Going step by step through it, and even trial and error, should solve your problem. On my system now when I go into FSUIPC and look at the signal they are solid as a rock. Take my advice and study the FSUIPC guide and use the offer from Paul and get your profile setup. Good Luck Bob
July 30, 201213 yr The Win 7 install is 2 weeks old. But I'll check. Good suggestion..thanks. Alan Windows has the basic drivers for USB ports but there are drivers for USB 3.0 Host Controllers. For instance, I have driver version 2.1.36.0 and Firmware Version 3025 for the Renesas Electronics USB 3.0 Host Controller. Those are not updated by Windows so you need to go to the manufacturer of your motherboard or system and see if they have updated drivers. If you have USB 3.0 ports provided by Renesas Electronics, you can visit their site for the latest updates. Here's the Intel site to the drivers - http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=19880 and the link to Renesas since most of the modern boards use Renesas - http://am.renesas.com/applications/key_technology/connectivity/usb/index.jsp. Probably won't fix your hardware problem but just wanted to clarify the reason why I suggested updated your USB drivers. Best regards, Jim
July 30, 201213 yr Author Jim..Thanks for clarifying. I'll check with the guy who built my system. There are a couple of USB 3.0 ports there, but I'm definitely using the USB 2 for this connection. Bob..I'm hoping to dig a bit deeper into the FSUIPC guide with some assistance from Paul this afternoon. In anticipation, I'm prepping a cold Vernors from the stash (in stock since my last Motown visit). What happened to Strohs????? This seems like a quest to find the proverbial needle in the haystack. Thanks to all who have chimed in so far. Most appreciated! Alan
July 30, 201213 yr Moderator I updated the NGX to SP1c, installed the 600-700, and a bunch of liveries. Flew it for a brief time just to see what it was. All seemed to work OK Then, I changed back to a Bell 206. KABOOM! First, the sound of the 737 was still present in the helo. And when I went to fly it, the rudders ... Not sure if this will make any difference with the control problems you have, but anytime you fly the NGX in FSX it needs to be the only plane flown in that session. If you load another plane first then switch to the NGX or fly the NGX first then switch to another plane you're going to have problems. Happens to me and is documented by PMDG. After an NGX flight you really need to quit the sim and start it again with whatever plane you want to fly since some of the NGX guages/sounds/etc, wont close or off load when you load a new plane. So basically when you start FSX for a session it NGX only, or the sim needs to be rebooted if your going to fly something else. Avsim Board of Directors | Avsim Forums Moderator
July 31, 201213 yr Author Thanks for the info Jim. Not a fix for the control issues, but valuable just the same!! Alan
August 2, 201213 yr Author FSUIPC seems to have solved the issue. That and lots of input from Paul. Thanks so much for all the comments. Alan
August 2, 201213 yr Hi Al, Glad that Paul got you going with FSUIPC. People keep posting why should I pay for the registered version of FSUIPC, here is one good example, the profiles and axis controls are outstanding. BTW, I was raised on Vernor's, when every I had an upset stomach my mother always gave me Vernors, great ginger ale. Strogh's got bought out by either Millers or some other brewery. I use to drink it long time ago. Now its Bud or Miller's LOL Bob
August 2, 201213 yr Al's being modest, Guys.... I worked in IT as a SysAdmin for years, and I always preferred to work with a second person alongside me - and that's all I was to Al. He was a slight bit unsure at first, but within a real short time he was plugging numbers in like nobody's business. The issue was how to stop FSX from doing it's own thing with the controls, and once they were all got rid of and a couple of axes assigned - he was doing it without any input from me. Buttons, switches, the whole she-bang! Bring 'e on! I take none of the blame! :lol: i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
Create an account or sign in to comment