Weather and auto-turn-to-target

[bengo]

Last night we flew a multiplayer mission that had some wind in it. We noticed that auto-turn-to-target no longer worked.

Later, we removed the weather settings from the mission and auto-turn-to-target worked again.

Anyone else seen this behaviour also ?

Edited June 12, 2010 by bengo

[EinsteinEP]

Hmm...no. In fact, we have several missions with wind where auto-turn-to-target works just fine.

 

Track?

[bengo]

Here's the mission.

Another thing I'd like to add : the helicoptre's handling felt completely different as oposed to in single player. For example : when preparing for take-off : while keeping the wheelbrakes pressed, the slightest forward press of the cyclic starts the chopper rolling forward. I immediatly tested to see if my settings weree screwed by loading a singlplayer mission, but everything was allright in there.

client-20100611-231318.miz

Edited June 12, 2010 by bengo

[MTFDarkEagle]

Was the heading channel engaged?

 

On the take-off: I'm guessing its a trim issue..

[bengo]

Heading-channel was engaged. I checked.

 

On the take-off : I had the controls-window up, and the diamond was smack in the middle of the cross, and the rudder was centered as well.

[EinsteinEP]

Bengo,

 

Just ran your mission and auto-turn-to-target worked just fine for me. I agree with DarkEagle in that it sounds like a trim issue. Depending on your heading you may need some rudder trimmed in to maintain a steady heading. If you're trimming in ZERO rudder, the AP may be using its full 20% to just point straight and not be able to provide more rudder to make the commanded turn.

 

If you can post a track with your virtual control display (Rctrl-Enter) on I can take a closer look.

[Frederf]

Heading-channel was engaged. I checked.

 

On the take-off : I had the controls-window up, and the diamond was smack in the middle of the cross, and the rudder was centered as well.

 

Diamond centered is not neutral ground handling. With the controls at 0/0 there is some forward roll tendency in the taxi state.

[bengo]

Diamond centered is not neutral ground handling. With the controls at 0/0 there is some forward roll tendency in the taxi state.

Agreed. But with brakes pressed I should be able to trim the cyclic 1/3 forward to perform a good take-off and not roll forwar, right ?

[EinsteinEP]

Diamond centered is not neutral ground handling. With the controls at 0/0 there is some forward roll tendency in the taxi state.

Hmm...I think it's the other way around: diamond centered horizontally and vertically is ground-centered, and slight forward is flight-centered (which would give you a forward roll in taxi with the wheelbrakes off). I had assumed bengo was referring to a horizontally centered diamond, since the issue is auto-turn-to-target and turn trim, and a diamond centered during flight would result in a strong backwards pitching moment with or without AP help!

 

In any event, an actual track file would help, as there's nothing in the mission file that prevents auto-turn-to-target from working. In this spirit, here's my track file, showing auto-turn-to-target working.

[bengo]

Thanks for the replies guys. I'll try to put up a track as soon as i can.

Einstein, did you need to do anything special to make the auto-turn-tgt to work, like trim for example ?

 

Diamond centered usually gives a slow movement forward when you release brakes/parkingbrake.

In my case it started off with quite some speed and trimming backwards immediately rose the nose up. Like it's oversensitive to input. Same with collective. Compared to singleplayer I needed to input a lot of collective to see it alter altitude. And when it started to change altitude it did it violenty : it immediatly went to climbs or dives of + 10 m/s !

It did so when someone else was hosting this mission. It did so when I hosted the mission and was the only pilot in the mission. I tried one of the stock missions in singleplayer and did not have the problem. I never had this problem before in multiplayer or singleplayer.

Edited June 12, 2010 by bengo

[bengo]

Well, I think I might have solved this problem, but some more testing is needed. I'll keep you posted.

 

Here's the track showing things going wrong.

client-20100611-231318.miz.trk

Edited June 12, 2010 by bengo

[bengo]

Solved.

Problem was caused by the mission being developed on a machine where patch 1.0.2 was not applied on a clean install, but on top of a 1.0.1-install.:doh:

[EinsteinEP]

Einstein, did you need to do anything special to make the auto-turn-tgt to work, like trim for example ?

I *try* to always make sure I'm trimmed so that the AP is "centered", so to speak, but I didn't find I had to do anything unique in your mission.

 

Compared to singleplayer I needed to input a lot of collective to see it alter altitude.

I noted that in your mission, too. I chalked it up to the anti-ice protection on top of the the full weapons load and 100% fuel. What airfield was it at? - I don't recall. If it was high altitude, that would result in a performance hit as well.

 

And when it started to change altitude it did it violenty : it immediatly went to climbs or dives of + 10 m/s !

Also sounds like a trim/autopilot implementation issue. If you get it frequently, post a thread and someone will take a look at it for ya.

 

Problem was caused by the mission being developed on a machine where patch 1.0.2 was not applied on a clean install, but on top of a 1.0.1-install.

I don't see how the problem had anything to do with patches, but the point is now moot: I'm glad your problem has gone away, bengo, and you can, once again, enjoy this great simulation!

 

See ya in the virtual skies! :pilotfly: