Out of control after repair

I am not sure if this is a bug, I just report in anyway.

So, during my last night's BlueFlag flight I ended up conquering Gudauta with my fellow comrades after first taking Sochi, flying back and forth etc.. imagine this was a rather long flight. When I touched down on Gudauta I touched down too hard and damaged the bird.

I shut it down with LWin+End and took my long desired pause to stretch myself ;)

After the herd gathered again were ready to go for Sukhumi, I powered the bird up with LWIn+Pos1 and all was fine, ParkBrake engaged as usual. I released the brake, applied collective, some right rudder and right+back on the stickj as usual and expected a nice lift-off

but the Mi-8 rolled HEAVILY to the left, very heavy, I settled back, checked AP-middle was GREEN and it was so I tried again, same result, I almost couldnt get the bird up without having the rotor scratch the ground left side. So I lifted up, flew half a round over Gudauta and really had to struggle to keep it level, the Mi-8 wanted to nose-dive heavily as wellas roll left heavy ( like cyclic FULL FOWARD and a lot of LEFT).

I then thought..OK...smack her down, repair again and see what happens...so I smacked her down, broke the nose wheel off intentionally and repaired again, same result.

Well, since we needed the chopper badly I had to fly to Sukhumi the way it was, constantly trying to nose over and heavy left cyclic tendency.

I am pretty sure I did not dial any bad values, forgot a switch or anything like that.

Has anyone else registered this odd behaviour yet ?

I have the track, its 227MB in size so I can only send it via email through iCloud service and I would have to check when this happened so you dont have to look through all the track.

PM me so I can send the track via iCloud service ( up to 25GB allowed ).

I have not yet had the time to try to reproduce it and I had no F2 view to check if something did NOT get repaired ( BF rules ).

Otherwise, God..I love this bird !!!

Bit

It's been a while since I flew the Hip, but Im assuming that it's an issue with the automatic start up, and shut down procedures, and the AP box. Im guessing something in the automatic shut-down procedure script is not working properly and as a result the AP is not being initialized or reset correctly.

It can be a hassle but you should really take the time to learn the start-up and shut down procedures of the Mi-8

I thought so too, but it never happened before and I often shut it down and restart it in the field to stop the rotor disc and hide somewhere until the AAA has been cleared or such.

Thanks for the advice :)

Startup:

I basically know it, at least I knew it a while back and I am always reminding myself to do it again and more often until its set. I can do it for so many airframes and the Mi-8 is actually not that complicated, in fact none is. I find the Ka-50 for example a very easy to start bird where most say it's complex, I dont think so tbh.

Indeed, a shame I dont !

I think it might be some error with the repair function. I had a hard landing and lost my tail rotor. After getting repaired and all systems were resetted I tried to start the Hip again, but the Batteries were dry and external power was needed. Despite having ground power, the engines wouldn´t start.

Had to switch to a "fresh" Hip and the start up worked fine.

No idea really but did you check what your control surfaces were doing? Could be they were off set?

Sounds like a trim issue. The AP alone doesn't have enough authority to cause such a severe upset.

If it's reproducible, file a bug report and the BS guys will look into it.

Trim settings looked ok BitMaster?

The joystick cheat showed no holding or offsetting of the neutral position?

Hasnt occured since so I guess it was a script error.

Control surfaces were correct, aka I reset trim while waiting for those repairs and rearms.

If it happens again I will post.