what am I missing?

[DayGlow]

Just trying to learn how to fly the damn thing; if I take over a tutorial mission I can fly alright, trim works, hover hold works, etc.

 

Now I created a practice mission in th editor by placing a player controlled KA-50 on the runway. Start up the mission and the engines are up and running and ready to go. Now if I try to take off it's like trying to balance a beachball on a pole, I'm all over the place, I hit trim and the bird pitches up as soon as I let go of the stick, hover hold doesn't work etc.

 

What setting am I missing in the cockpit that the tutorials have on that is off when you start on the runway as I feel this will probably be important once I try to fly and fight in missions :joystick:

[Golgotha]

Have you the Pitch, yaw and roll, augmentation switches engaged, lit blue on the autopilot panel by your right knee?

[159th_Viper]

Just trying to learn how to fly the damn thing; if I take over a tutorial mission I can fly alright, trim works, hover hold works, etc.

 

Now I created a practice mission in th editor by placing a player controlled KA-50 on the runway. Start up the mission and the engines are up and running and ready to go. Now if I try to take off it's like trying to balance a beachball on a pole, I'm all over the place, I hit trim and the bird pitches up as soon as I let go of the stick, hover hold doesn't work etc.

 

What setting am I missing in the cockpit that the tutorials have on that is off when you start on the runway as I feel this will probably be important once I try to fly and fight in missions :joystick:

 

Post a Track :)

[slowhand]

try using the right ctrl/enter to open your control indicator...read up on it in your manual..that should help with staying in line..5x5

[DayGlow]

just did a quick test with the controller window open. Open tutorial mission and I press trim (mapped to button A on my X52) and it works. In the regular mission press trim and it doesn't.

[Distiler]

There are two modes, "game" and "real", and you need to check if keys are assigned for each mode. Also, there are missions configured to play in one or other mode, you can "set options for all missions" in the options menú so all missions play with the same configuration regardless how they have been built.

 

This is a recursive question in the forum.

[Speedbrake]

One other thing to think about. If you have the ABBRIS set to follow waypoints (and pressed the "R" route key or hotas key if you have one set up) you may be fighting the autopilot if you are trying to make the helicopter go somewhere other than the next waypoint.

[DayGlow]

Double checked my settings. Controls are set for Real KA-50, in gameplay easy flight is ticked off. When I start up the tutorial mission for hover I take control right away. While sitting on the tarmac with collective at idle I open up the controller box. If I tilt the cyclic in any direction and hit trim either on my stick or with 't' on the keyboard it holds the cyclic position.

 

Now I start up any mission from the mission screen, let's say Altitude (or Alttitude I forget) and sit on the pad with the engines going. Do the same, collective at idle, tilt the cyclic forward and hit trim, either on stick or keyboard and it will not set.

 

WTF?

 

edit, autopilot is engaged for all 3 axis as well for both missions.

Edited June 1, 2009 by DayGlow

[EvilBivol-1]

In training missions the controls are pre-mapped, because it is a Track, not a Mission. When you enter a single mission, the simulation loads your control profile. Go through your profiles again and make sure everything is mapped properly. Make sure you have disconnected any other devices that might be causing input (like a racing wheel, a gamepad, etc.).

[Nate--IRL--]

Is the "Use these options for any mission" Ticked in the gameplay options?

 

Nate

[DayGlow]

I remapped trim to the A button on my stick. It works in the tutorial mission. In the mission neither the stick remap or the default 't' button works. :notify:

 

double checked my profiles. Both the 't' and button are mapped to trim in them, but they don't work in the missions.

[HitchHikingFlatlander]

In training missions the controls are pre-mapped, because it is a Track, not a Mission. When you enter a single mission, the simulation loads your control profile. Go through your profiles again and make sure everything is mapped properly. Make sure you have disconnected any other devices that might be causing input (like a racing wheel, a gamepad, etc.).

 

 

I still think your problem lies here!

[DayGlow]

I also have hover hold mapped to the 'c' button. It works in both the tutorial and regular missions. Why would trim not work? Even the default mapping of 't' isn't working verified by the controller window.

[DayGlow]

Is the "Use these options for any mission" Ticked in the gameplay options?

 

Nate

 

yes

[Nate--IRL--]

edit:- too slow answered above^^^^

[DayGlow]

verified again, 'use these options' is checked. Openned up the Altitude mission itself. It is set to real flight.

 

No idea why trim will not work.

[Nate--IRL--]

I also have hover hold mapped to the 'c' button. It works in both the tutorial and regular missions. Why would trim not work? Even the default mapping of 't' isn't working verified by the controller window.

 

Hmmm you say "T" isn't shown in the controller window, could you take a quick screen grab of that and attach it to a post. Try assigning it again in the controller options also.

 

Nate

[EvilBivol-1]

Even the default mapping of 't' isn't working verified by the controller window.

Are you sure you don't have other controllers interfering? Racing wheel, gamepad? You can try either unplugging the unused controllers or disabling the FF in-game function in the configuration files. To do so, open \...\Config\Producer.cfg and change the “ForceFeedbackEnabled” line from “true” to “false”.

[DayGlow]

that did it, turning off FF made it work.

 

Damn and I had a nice set of screenshots showing all of my settings and how it was working in the tutorial and not the missions.

 

Such a stupid little thing. At least now I won't give up on flying the damn thing so quickly :)

 

Thanks everyone for the help.

[EvilBivol-1]

Glad that worked. FYI, that solution was quoted from our User FAQ. I'm sure you'll find many other useful pieces of information there. ;)

http://forums.eagle.ru/showthread.php?t=33527

Edited June 1, 2009 by EvilBivol-1

[DayGlow]

was confused because it worked fine in one part of the sim, but not another.

[BTTW-DratsaB]

Arrrg,:crash: I was having this exact same problem after setting up my FFB G25 racing wheel to use for rudder pedals with my x52. Was driving me mad 'till I found this. Thanks!:cheer3nc:

[HetzerII]

Sorry guys i have to go back on this topic...

 

I have the same problem... Its working without any problems in the tutorials but not in the normal flights.

 

What this is all about? I mean it works in the tutorials... why i should not in the normal mode? Why i dont have to disable this in the tutorials? Where is the difference? I dont even have anything else installed, just my stick.

 

Please... hhheeelp ;)