radioguy

FSUIPC seems to have solved the issue. That and lots of input from Paul. Thanks so much for all the comments. Alan

Thanks for the info Jim. Not a fix for the control issues, but valuable just the same!! Alan

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

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

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

The Win 7 install is 2 weeks old. But I'll check. Good suggestion..thanks. Alan

Thanks for the clarification, Paul. Makes sense..crosstalk. Funny though, I didn't have the PFC yoke connected and G-Stick was doing fine. It was only after I installed PMDG 737NGX that it all went haywire. So it kind of leads me to believe that something in the PMDG software might induce some sort of a corruption somewhere. Though where and what baffles me. Now, is there a "Jahman tutorial" available somewhere? I did some playing earlier and deleted the rudder axis assignment from within the FSX options menu. Then went to FSUIPC (I think it's 4.34?) and tried to assign it from there. The program didn't see a rudder input signal, i.e. nothing happened. But it was there BEFORE I deleted the FSX assignment. Admittedly, I'm a complete novice when it comes to using Pete's program outside of basic setups, as in the PFC throttles and so on. A more in-depth look would be quite useful. Alan

Bob, A bit confused here. Did Pete suggest that you clear/delete all assignments in FSX prior to re-assigning in FSUIPC? Alan

Thanks for the suggestions thus far. I'll get to them shortly and report back on my experience. Just wanted to make sure you guys did't think I'm ignoring you!

I'm in the process of setting up FSX for the umpteenth time. Currently using Flight Link G Stick III with collective and pedals for helo control. Also have PFC Jetliner yoke, throttle, and Cirrus rudders on the rig. In doing this initial setup, I had all controls attached to the system. When I went to fly the helo, I was getting "stray" inputs on the cyclic. This disappeared as soon as I unplugged the Jetliner yoke's USB connection. So far, so good. Still had the Cirrus pedals/throttle combo connected and the Flight Link controllers worked fine. The other night, I installed the PMDG 737NGX and all hell broke loose. Now, even with just the F/L controls connected (everything else disconnected), I'm back to getting those stray inputs, except this time on the rudders. Re-calibration through both FSX and FSUIPC have had no influence. So just after takeoff, the helo begins to spin on axis and is rendered virtually uncontrollable though there have been NO inputs to the rudders. I even uninstalled the PMDG a/c but still have the problem. Also re-built the fsx.cfg file from scratch...no help. I don't think it has anything to do with the PMDG install, though I could be wrong. Any thoughts??? Alan

Dag Bert,>Alan, nice try... but when I rename the PMDG737-700 folder, I end up with whatever panel I had in the previous airplane... in my case, a Cessna 172. So you better get that beer on ice! Being from Holland originally, I kind of like Grolsch, but a Canadian microbrewery beer will do fine as well!

Bert (& Pete),I just loaded a 737-600 full panel/cabin views and the main panel came right up. So Bert, I think you might have lost the bet had we actually shook on it. I've renamed lots of aircraft folders with no problem. Granted, most of the dupes are pointed to panel aliases residing in the fsfsconv folder so they do have an actual "proper" target whilst this one could be looking for the "proper" folder that was renamed. But if that's so, then why did it come up OK now? I hadn't reverted back to the original folder names as supplied by PMDG.Just for the heck of it, where can I find the folder containing the actual panel so I can alias it to an fsfsconv folder?Bert, I'll buy you the beer anyway. What's your pleasure? Now that we can get REAL Budweiser in Canada (the Czechs finally woke up and changed the name so they could get around Auggie Busch's "copyright" on his otherwise poor imitator) you might want some of it. Where are you "coming here" from?Pete, could you possibly tell me how I can contact ATC without mousing to the VIEW menu in FS9? There are no so-called radio buttons on the panel and I'm wondering if there's a direct keyboard input poossible.I'll keep on monitoring the situation and let you know if I run into any more panel glitches.Thanks again for your input, guys.

>No I don't know why, but I know what might solve it. (Don't>hit me for this ;-)) Use the removal tool on the PMDG website,>and reinstall the NG, and apply the SU 1-1 patch. Hopefully>that should fix whatever broke =)Thanks for the replies so far, guys.Fred,I neglected to mention in my original post that the patch was applied during the initial installation of the package as per the PMDG instructions. And the panel showed up just fine on the first go. It was on subsequent FS9 sessions after I had installed some different liveries that the troouble began.One other thing that might be of influence (though I doubt it). I renamed the PMDG default "Titles" in the sircraft folder of FS9. I like to keep all of my aircraft listed according to real world manufacturer with the ui manufacturer as a part of the folder title. So the Boeings are all listed as BOEING 7xx-xxx. In this case, it's BOEING 737-600 PMDG. This is only a folder name change. The aircraft cfg file ui manufacturer is also listed as Boeing PMDG. Now, the panel cfg refers to the alias PMDG 737-600 panel. Any idea where this actual panel file is located?Thanks for your input.

Hi folks,I've just installed the 737-6/700 into FS9. When I first loaded the a/c, all was fine. A couple of FS sessions later, the a/c loaded with a guageless C-172 panel. I tried to load another a/c type and return to the PMDG 737 but no luck. Still had that shadow of a Cessna panel there. I then re-booted the system, loaded a DC-9 that showed its panel just fine. Loaded the 737 again and it sisplayed the DC-9 panel!! Closed FS9, re-started, loaded a 737 and the proper panel was there....HUH? Anyone else encounter this problem?I've got the latest FSUIPC version installed (registered, thanks Pete)and a fairly speedy system, almost brand new. I've noticed this with other a/c and panel before so I imagine it's not exclusive to the PMDG a/c or even caused by it. Just wondering if anyone knows WHY.Thanks,Alan