I

now after 2 flights with V1.0.6 I experienced that when I want to descend manually with the vertical speed it set the manual -/+ vs to 0. Idk if this is  a bug

i did have the same problem during descent yesterday. i couldn´t use V/S since it reset to 0 everytime after ca 30sec.

also if already descending activating V/S didn´t assume the current rate but reset to zero, though i don´t know if this is wrong or not

20 hours ago, Acempeter said:

i did have the same problem during descent yesterday. i couldn´t use V/S since it reset to 0 everytime after ca 30sec.

also if already descending activating V/S didn´t assume the current rate but reset to zero, though i don´t know if this is wrong or not

Same issue here. Vertical speed , manual setting, rest to 0. I have to use just the Level Change as turnaround 😞

 

I'm also having the same issue. Very annoying!

Hi guys,

Same issue here, just flying now on the A300...

This is soo annoying 😞

Also, on the chrono, i can't see hours, only minutes.
Today's flight from LSGG-EDDV lasts 1h29m.
On this screenshot as you can see it shows only 29m.

Yep. Same here. Vertical speed resetting to zero every 20/30 seconds

Any news from inibuilds about these issues?
🙂

Edited February 12, 20242 yr by Andreabarbs2000

same here ... while flying across the land on vatsim ....

Same V/S issue with V1.0.6

experienced same issue today flying V1.0.6

Any news from inibuilds?

 

Hopefully they will fix it sooner than later. To me, v/s is one of those modes that's imperative, especially when flying in an ATC/multiplayer environment. V/s, LNAV, Dir to, autothrottle have to be rock solid. Its disappointing that V/S is bugged now as its honestly one of the more basic functions. 

Seems to be a bigger issue, otherwise we would hear something. Hope it will be fixed soon, flying without proper V/S makes no fun at all. I will keep the A300 in the hangar until this is fixed.

After opening the INI Manager today i was suprised, an update was shown. BUT: It shows update to 1.0.5 and then to 1.0.6. I will test the A300 now, maybe the V/S Bug is solved.

Yes, sorry for the late reply, this is a known issue and will be fixed in the next version 🙂