Osprey - Wing stow process has "jumping" proprotor
I have now seen this multiple times … but I am not sure if this can be reproduced in 100% all cases:
- I shut down the engines … APU running
- Nacelles are at … say 70 deg
- I go to the "blade fold wing stow" menu on one of the MFDs
- I activate Rotor break
- I activate the Full stow process
- I watch the action from the outside and see:
- A) Nacelles going up to 90 deg
- B) Then the proprotor jumps (snaps) to a special position
- C) … etc
I remember that in "older" releases step (B) did not jump but the rotor actually did slowly rotate into the necessary position.
@nenenuiAfter a number of tests I have the feeling that there is a difference if the nacelles are at 90 deg when the fold-stow process starts. In that case I could see a proprotor angle pre-adjustment (rotation action) prior to the folding animation.
In all the cases where the nacelles first needed to be rotated fron angle X to the 90 deg angle … that phase was not visible. Instead I get the "jump" from the random blade position after the engine shuts down … to the angle where the fold animation starts.
EDIT:
I am no longer so sure that there is a "90 deg difference" … it feels like the main difference is that I can not switch to the external camera fast enough in the 90 deg case in order to see the jump.I am now trying to find out if activating "Rotor lock" prior to the "Full stow" is part of the "jump" reason. But that seems to be similar to the 90 deg case. Hmm.
- In reply tonenenui⬆:@nenenui
So in order to avoid the delay in cam switching I now picked a parking location and a sun position where I can clearly see the shadow of the rotor blades on the ground right from the pilot position.
- Image 1 = pre pressing the "Rotor lock" button
- Image 2 = post rotor lock
… and I could clearly see that the moment I press the "Rotor lock" button I see the blade shadows jumping. So the jump also happens in the 90 deg position.
In reply tonenenui⬆:Miltech Simulations @MiltechSimulationsI haven't had a chance to take a look at this, but thanks for the detailed report. I'll try to replicate the issue and get back to you