FSX or CH Pro Pedals problem??

[Bass]

When I am flying FSX and taxing on the ground you can see the rudder move left and right but once you are airborne you no longer see it move but the effects are still there. I just dismissed the issue and figured it was supposed to work that way. I thought it was a model problem .
If you want to see a strange effect try holding full left or right rudder during take off. You will see the rudder full left or right until the wheels leave the ground then the rudder goes to neutral and no longer moves. I do not know why it works this way but it does this in both FSX and FS9.

Never seen that Gary!
I got my rudder pointed to my ANT ELEV on Hotas Cougar, and they'll stay where i left 'em when going airborne. If i forget that, i'll soon find out when the ac is drifting! That ANT ELEV is working like your pedals. (I think)

[cardinalbrian]

garymbuska, Hmm. I can see the utility of the sim programming of such a shortcut.. The only time I can think of where the rudder would actually be deflected enough to see the difference would be on a vicious slip on final to lose altitude, and then I'm busy watching the panel and runway threshold! But my problem is in an uncommanded right turn on the runway. The rudder pedals initially work correctly as I compensate for p-effect when I release the brakes at full throttle (I've only got 2200 feet here at KCGS and a bunch less when I go to 2w2...). Since my bird's been in the shop nearly 6 months I'm a little rusty, so the first few feet down the runway involves a bit of correcting - and the rudders work correctly for a few seconds and then I'm off through the grass on the right side. I'm looking into PREPAR3D as a fix, but it looks like they lock you into 1 computer -and my monster lost its sound capability (both options) and I like being able to revert to my Dell backup/utility box when I fiddle with the Alienware doohicky!

[garymbuska]

garymbuska, Hmm. I can see the utility of the sim programming of such a shortcut.. The only time I can think of where the rudder would actually be deflected enough to see the difference would be on a vicious slip on final to lose altitude, and then I'm busy watching the panel and runway threshold! But my problem is in an uncommanded right turn on the runway. The rudder pedals initially work correctly as I compensate for p-effect when I release the brakes at full throttle (I've only got 2200 feet here at KCGS and a bunch less when I go to 2w2...). Since my bird's been in the shop nearly 6 months I'm a little rusty, so the first few feet down the runway involves a bit of correcting - and the rudders work correctly for a few seconds and then I'm off through the grass on the right side. I'm looking into PREPAR3D as a fix, but it looks like they lock you into 1 computer -and my monster lost its sound capability (both options) and I like being able to revert to my Dell backup/utility box when I fiddle with the Alienware doohicky!

This might be a brake problem or a torque problem if this is a propeller driven aircraft. I know that the default Baron is bad about doing this. It is one of the hardest aircraft to control on the ground. You really have to hold heavy left rudder and a little right brake as well just to keep it straight.
Jet air craft usually do not have this problem but I found out they can if the engines are not defined the same way. This drove me crazy It was a B737-200 I had downloaded and it wanted to go to the right. You can imagine my surprise when I discovered the designer of the aircraft had made a key stroke error in the engine section of the aircraft cfg file. He had miss typed the numbers for one engine the right engine was stronger than the left engine. Something you might want to look into.

[cardinalbrian]

garymbuska, Interesting hypothesis, but I flew with the C177rg addon for years without such a problem. Maybe it was the frozen O-rings.. I will go dig around looking for .cfg parameters that might have gone astray. I've had that problem. Worst case I'll buy the P3D product...

[zswobbie1]

The p3d Professional License is $199 and the Academic License is $49.
There's very little in the Prepar3D site to explain any functional difference between the 2.
Why pay 4x for the same thing?
No difference at all. Apart from the watermark, that you cannot really notice..
$150.00 extra?? Here in South Africa, that is worth R1500.00.. A huge amount that can go towards addons etc.

[cardinalbrian]

Zswobbie1, Thanks, you've convinced me - unless I get a Lockheed Martin retiree's discount! One bother I think I see is that I switch computers occasionally, and I'm on the backup now. P3D's distribution method seems chosen to discourage multiple installations, but may also make going back to my "Monster" a bit touchy..

I might wind up doing my practice in the real C177RG!

[cardinalbrian]

Zswobbie1, Thanks, you've convinced me - unless I get a Lockheed Martin retiree's discount! One bother I think I see is that I switch computers occasionally, and I'm on the backup now. P3D's distribution method seems chosen to discourage multiple installations, but may also make going back to my "Monster" a bit touchy..

I might wind up doing my practice in the real C177RG!

[cardinalbrian]

Many thanks to all who offered suggestions. I solved the problem by going to Prepar3D (Professional). Problem went away. Still existed in FSX just before I installed P3D. Pleased to see P3D has newer topology around my airport (KCGS). Did my usual fiddling around with the panel window and eye point to get a decent view out the windscreen, but P3D wouldn't le me lower the eye point as much as I would have liked.. Haven't got all my controls set up properly yet, but I'd say first impression is very good!

[cardinalbrian]

OK, I have to revisit the problem. The P3D experience started fair, I hadn't tweaked all the parameters so I was happy. After tweaking things started to fall apart. I found I was fighting with the Thrustmaster Force Feedback with a great deal more persistence than should be necessary. So I went to check the calibration. To my surprise my "Simple Calibration (full sensitivity, null @ null)" had gotten switched! On the Pro Pedals the Simple Calibration box was unchecked, the sensitivity was zero, and the null was 1/2 on all axis!!! On the Thrustmaster the aileron axis was no longer assigned as well as the "Simple Calibration (full sensitivity, null null) had gotten switched! My next stumble will be to send CH and Trustmaster emails and query them about their AI application!!!! And go back to FSX and look for the same symptoms there. Again, the problem hasn't occurred in CSF.

[cardinalbrian]

Pfoo! My last post explaining what and how is failing didn't actually get posted. Short version: Problem doesn't occur with stock FSX C172s. I still think it's a controller type problem, but can't understand who is getting into the controller. My FSX expert mentioned FSUIPC as a possible solution and I'd like any to hear of any experience with that protecting controller settings. I never needed this before, the add-on aircraft in question has worked wonderfully for over 5 years. But I remember when my MS Sidewinder Joystick mysteriously began changing control settings then became useless when my attempt to set it right resulted in discovering it wouldn't install... So I suspect some cleverness on the part of Windows 7...

[cardinalbrian]

Mea culpa! I went so long without thinking that I forgot some important elements. Mainly that N177RG worked for years on my AlianWare Area 51 which has Crossfired Radeon 5900s driving a 30 inch 2950x1600 monitor. I think it was squishing the instrument panel window on the 24 inch 1900x1200 monitor on this box that caused the problem. When I went back to Brett Henderson's stock N177MJ the problem went away. Thanks again for all you helpful folks that made suggestions. I might get airborne in N52851 next week and get to be confused with my new suite of Garmins. First lessons will be radio frequencies and transponder settings so I can come home to the DC SFAR!