Aerofly FS 2 Steam Previous Alpha Builds

    • Official Post

    We updated the Steam Alpha version with a couple of bug fixes.


    Please re-check the previous issues with the navigation as well as user sceneries.


    The aircraft should no longer constantly turn left at some waypoints and the GPS 430 / 530 units should display the magnetic desired track.

    The course display in the other aircraft (e.g. learjet) should be correct again, the next waypoint distance should also show the correct distance again.


    Other changes:

    • Changed location dialog altitude slider mouse wheel direction flipped to be more intuitive
    • Fixed an issue with helicopter yaw compensation with profi mode off and when close to the ground
    • Fixed A320 GPWS too low gear did not trigger when flaps were at landing configuration
  • Jet-Pack (IPACS)

    Changed the title of the thread from “Aerofly FS 2 Steam Alpha Update Now Available” to “Aerofly FS 2 Steam Alpha Update 2020-07-31”.
  • Ich Frage mal hier.


    Habe auch die Alpha Version über Steam.

    Auch wenn man Lacht,entweder bin ich zu Doof oder habe keine Ahnung!!!:D


    Beim 320 habe ich immer Umgerschupp beim zurücksetzen vom Gate benutzt.Leider geht das nicht mehr, meine Frage wie kann ich das Flugzeug vom Gate zurücksetzen. Peinlich;);)


    Danke schon mal, und super Update.:thumbup::thumbup:


    MFG

    • Official Post

    Keiner der Standardflugplätze hat eine Position am Gate, daher sollte das kein Problem darstellen :P

    Fehlender Umkehrschub wurde bereits gemeldet als Bug :)

  • KMRY to KSNS no waypoints in Arrow (as per post #38)


    Initial track from takeoff somewhat right of course. GPS 430 displayed DTK and actual track, which differed, but AP did not correct actual to DTK effectively. When the DIS to waypoint reached 0, it entered a continuous left turn with DTK changing all the time. This differs from the previous build, when it overflew the waypoint with no heading change (and which did not display DTK). Below you can see it has turned left past the course to KSNS (actually this was taken after it had already flown one full circle, and then passed the desired course again).


    • Official Post

    KMRY to KSNS no waypoints in Arrow (as per post #38)


    Initial track from takeoff somewhat right of course. GPS 430 displayed DTK and actual track, which differed, but AP did not correct actual to DTK effectively. When the DIS to waypoint reached 0, it entered a continuous left turn with DTK changing all the time. This differs from the previous build, when it overflew the waypoint with no heading change (and which did not display DTK). Below you can see it has turned left past the course to KSNS (actually this was taken after it had already flown one full circle, and then passed the desired course again).


    If you leave the flight and go to the navigation menu and resume the flight, does that restore the waypoints?

    But apart from the autopilot, were the indications on the display satisfactory?

  • Departing KSNS RWY 31, no SID, routing KMRY APP R10RY (as per post #37)


    Turned out left as expected, but came out of turn on heading 265 not 255 as per DTK. Flew straight on heading 265 for a while, then DTK changed to 271 at which time a/c turned right to heading 285 (see pic). When the distance to ZEBED reached 0 (although not at ZEBED due to incorrect track flown), the aircraft started turning very slowly to the left (about 1 degree every 2 seconds). Eventually the turn rate increased to rate 1, then the turn reversed to the right. The DTK seemed to be changing periodically, with the AP trying to follow it but never coming out of the turn even when the track was same as DTK.


    • Official Post

    It seems the autopilot in the JF aircraft are using the output track directly which now is a true track no longer a magnetic track. That means we will have to adjust the code accordingly and keep the magnetic output for them and change the display again. Ok, give us some time to fix this next week.


    Do you observe the same issue with the autopilot in our default aircraft?

  • Jan,

    Will all this mag vs true and NAV details delay the delivery of the EC-135? Meaning is the NAV update and EC-135 different teams working more or less independently.

    A steely-eyed Sierra Hotel record setting F-15E Strike Eagle simulator pilot. 8o
    Out now: Hawaiian Islands 8) Part 1: Kauai + Niihau v2 and Part 2 Oahu Island.

    On short final Part 3: Molokai, Maui, Lanai, Kohoolawe + Molokini Crater



  • Hello

    If you click in the Navigation menu in the Route section in the upper area (ORIG, RWY, DEO) or in the lower area (ARR, APP, RWY, DEST), then a waypoint (in the scroll area) is also clicked. You can see this by the fact that the flag belongs to the waypoint appears or disappears in the map.


    There is automatically generated waypoint at start of final (not using STAR) when a runway is selected and it is not possible to delete it. That's very annoying, because this waypoint often not fit. The starting point of a final depends of the present area, the aircraft type und determine aerodrome circuit.


    I also use SkyDemon for flight planning. SkyDemon allow me to set every waypoint, also at each corner of aerodrome circuit and don't generate a waypoint automatically. That's good.


    Would it possible that you allow the user to delete this automatically generated waypoint?


  • If you leave the flight and go to the navigation menu and resume the flight, does that restore the waypoints?

    But apart from the autopilot, were the indications on the display satisfactory?

    I repeated flight in post #73 to test this. Note that the waypoints on the GPS screen appeared correct at all times. It was just the DTK and DIStance that were incorrect. Going into Nav menu and back to flight (without actually changing the programmed Nav info) did not have any effect.


    The distance to and DTK to waypoint ZEBED changed very suddenly. See pics below. First pic, 18 nm to ZEBD on DTK 255. Second pic, a couple of seconds later, shows 1.34 nm to ZEBED on DTK 272. However, ZEBED is still displayed in the same position on the GPS. Also NB that the ETE has changed from 13 mins to 4 mins and GPS mode has changed from TERM to APR. Otherwise, GPS indications appear correct. Going into Nav screen and back to flight did not change anything.


    Happy bug hunting, Jan!



    • Official Post

    Jan,

    Will all this mag vs true and NAV details delay the delivery of the EC-135? Meaning is the NAV update and EC-135 different teams working more or less independently.

    Since there is no set release date it can't really delay it :D

    Some of us are continuing work on the EC whilst other do the navigation improvements.

    • Official Post

    Is the engine start up in the A320 meant to be that fast? I remember being a passenger the start up took way longer😄

    No but in real life there is also a huge instability in the compressor stage and limited amount of power in the starter. You can't start engines that quickly IRL because of that. At the moment the starter is using a magic crystal as power source ^^

  • Is the destination landing runway shown above the first FMGC waypoint of the flight a bug or is like real life?


    I did a new test now with the A320 and now the waypoint names are appearing correctly in the ND since the beginning of the flight. There is still some difficulty in staying on the route in waypoint changes that need bigger curves but it didn’t disable NAV mode this time.