Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Jump Ahead

Featured Replies

Decided to test the 'Jump Ahead' function - mid flight and at cruise altitude, I selected the waypoint further ahead in the flight and hit go...

I was teleported to where I should be (hurrah!) but in a +9000(or more) V/S climb and immediately hit with an accompanying 15s auto-save - needless to say, things went rather south quite rapidly after I 'regained control of the aircraft'....

Poor passengers..! XD

  • Staff
15 minutes ago, ukfuzz said:

Decided to test the 'Jump Ahead' function - mid flight and at cruise altitude, I selected the waypoint further ahead in the flight and hit go...

I was teleported to where I should be (hurrah!) but in a +9000(or more) V/S climb and immediately hit with an accompanying 15s auto-save - needless to say, things went rather south quite rapidly after I 'regained control of the aircraft'....

Poor passengers..! XD

This gave me a good chuckle. Will pass along to the team for further testing.

Thanks!

Kyle - Community Manager

iniBuilds Ltd. | inibuilds.com

Hello, I have the same observations here (but at -5000 feet). I think the jump function uses the FMS data of the respective waypoint. In my case, FL400 was reached and the jump went to the waypoint just before the ToD. The flight planning for this waypoint was at FL350, and exactly at this height the A380 came out. Subsequently, the AP was not working / stopped working and lost all managed modes. I think the behavior of the systems is understandable; therefore, the pilot has to check twice under which circumstances to jump forward.

Edited by cpschulz

  • Author
1 hour ago, cpschulz said:

Hello, I have the same observations here (but at -5000 feet). I think the jump function uses the FMS data of the respective waypoint. In my case, FL400 was reached and the jump went to the waypoint just before the ToD. The flight planning for this waypoint was at FL350, and exactly at this height the A380 came out. Subsequently, the AP was not working / stopped working and lost all managed modes. I think the behavior of the systems is understandable; therefore, the pilot has to check twice under which circumstances to jump forward.

Oh, interesting. It had been my intention to skip/cut out about 3-4 hours of flight time by 'jumping' from identical altitudes to a point 30 mins prior to TOD, it appears similar to your decision. I do recall that I did 'despawn' and then 'respawn' at 40,000ft in the circumstances I explained, but I cannot say that I checked whether the flight conditions would have been the same at both points - I did not consider whether the new flight positions may present the aircraft with difficulties if they were different to those anticipated by the FMS - which is something that could potentially confuse the simulation!?

Edited by ukfuzz
Grammar

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.