Hi! The Flight Path Marker on the PFD appears to be fundamentally wrong, not pointing where the aircraft goes.
Example 1:
In VTOL mode, pitch down so your nose is below horizon, while adding enough power to climb. Even though your VVI shows positive climb, FPM stays below the horizon (as if descending).
Example 2:
In APLN mode, try to maintain level flight or slight descent at low speed / high AOA. While your VVI should be at or slightly below zero, your FPM is high above the horizon.
These are just two examples where the issue is very visible, but it works like this in every mode and flight regime. It seems like the FPM is "glued" to the aircraft datum symbol, moving up and down as the aircraft pitch changes (even if vertical path does not).
It appears to me, though, that the FMP moves correctly in relation to aircraft datum - i.e. it is above the datum symbol while climbing, and below it while descending. If I were to guess, I'd say that the FPM's position is erroneously set relative to the aircraft datum, instead of the horizon line (though I cannot confirm if it's 100% the case).
Please note, however, that I am on the Beta version of MSFS. Not switching back to test this one bug, sorry. Would be nice if someone could try to replicate this on the main release version. Thanks!
Miltech Simulations @MiltechSimulationsThanks for the in-depth explanation.
I have added this issue to the list for further review and investigation, as this is quite a complex topic.
- BIn reply toBiM⬆:@BiM
Hi, I hate to be that guy, but... Only now I have gotten to fly the Osprey after the update, and... it's still not right.
When hovering or maneuvering in VTOL mode, keeping the aircraft horizontal, the FPM seems to be working fine. But the more you pitch above or below the horizon, the more incorrect it gets. So in APLN mode, I can be steadily climbing and yet my FPM stays slightly below horizon. Or I can be descending hard (even diving vertically into the ground), and my FPM still sits happily at the horizon line.
My uneducated guess, the FPM is now derived from the XYZ components of the aircraft's movement vector, but relative to the aircraft's own coordinate system (as opposed to the outside world's). So the aircraft can be descending with its nose down, but from its point of view, it goes "straight forward". No up/down component, thus the FPM stays horizontal.
At least I hope I made sense, it's pretty hard for me to formulate it properly.
On a related note, on the FLIR screen, I have noticed that the green physical horizon deviates from the white horizon line. Again, flying horizontally they match each other but the more you pitch up or down, they start to move apart.
And on a less related note, during my experiments with crashing into the ground, I have noticed that the artificial horizon is blue instead of brown below 60 degrees nose down, both on the PFD and the backup display. Sure, you're not supposed to operate the Osprey at such extreme attitudes, but still.
Sorry to bring up this issue once again but I had to...
Miltech Simulations @MiltechSimulationsThanks for pointing those out, I can certainly replicate both issues. These would fall "outside normal operative ranges" for the aircraft, but I'm adding them to the tracked issues list to be fixed in the upcoming updates.
- BIn reply toBiM⬆:@BiM
Oh look, it's the Annoying FPM Guy again! (I'm seriously starting to feel bad for bringing it up once again...)
Soo, on the PFD screen, the FPM finally seems to do what it should, as far as I can tell - makes flying so much easier! But on the FLIR screen, it seems nothing has changed? The FPM still stays glued to the horizon, as it was before the last update.
In fact, I noticed It is even inverted on the left-right axis as opposed to PFD screen (where is it correct). Not sure if it also was that way before this update or not.
If that's already known and only scheduled for a later update, sorry to bother you (again). Hope we get there eventually :)
- Miltech Simulations @MiltechSimulations
Fixed - will be pushed in the next update :)