Rise: The Vieneo Province - User contributions [en]

LRS

2026-10-30T21:44:50Z

reskin:

{{Inventory|source=Supplied as standard installed avionics with non-ground, non-container vehicles|weight=12.701|price_text=Included with vehicle|image=lrs}}

==Long Range Sensor==
This system is used to detect the presence of other [[:Category:Vehicles|vehicles]] in the vicinity (320km) using each vehicle's operational [[VPT]]. The data is fed to a [[contact list]] which is sorted by distance. This system also correlates friend/foe data according to the pilot’s identification settings.

This system also feeds data to the [[TCAS]] system (for closure rate), target bug, [[:Category:Weapons|weapons]] tracking, and [[TVM]] computers.

[[Category:Avionics]]

== Source ==
The Long-Range Scanner is supplied as installed vehicle equipment. Ground vehicles receive the [[SRS|Short-Range Scanner]] instead. No separate shop purchase is required.

[[Category:Inventory]]

File:Lrs.png

2026-10-30T21:44:26Z

reskin:

File:Srs.png

2026-10-30T21:44:06Z

reskin:

SRS

2026-10-30T21:43:54Z

reskin:

{{Inventory|source=Supplied as standard installed avionics with ground vehicles|weight=1.588|price_text=Included with vehicle|image=srs}}

The '''Short-Range Scanner''' ('''SRS''') is the standard scanner installed in ground vehicles. It appears among the vehicle's avionics rather than as personal baggage.

The scanner is supplied with the vehicle; no separate shop purchase is required. Other non-container vehicle classes receive the [[LRS|Long-Range Scanner]] instead.

[[Category:Inventory]]
[[Category:Avionics]]

File:Polaroid.png

2026-10-30T21:42:26Z

reskin: reskin uploaded a new version of File:Polaroid.png

File:Polaroid.png

2026-10-30T21:41:42Z

reskin:

Polaroid

2026-10-30T21:41:30Z

reskin:

{{Inventory|source=Searchable in [[O-4|O-4 Salvage]] (random special find)|weight=0|price_text=Not sold at retail|image=polaroid}}

'''Polaroid''' is a collectible photograph found during [[O-4]] salvage. It is also called '''Risque Polaroid''' or '''Polaroid Picture''' in inventory displays.

A successful special-item search can add the photograph to the salvage territory's inventory. Open '''Inventory Management''' at the site to load available items into a vehicle. Finding a particular item is random.

The photograph has no implemented healing or other active Use effect. It is an inventory collectible, with zero recorded carrying weight.

[[Category:Inventory]]

File:Voucher.png

2026-10-30T21:34:36Z

reskin:

E-11 Upgrade Voucher

2026-10-30T21:34:20Z

reskin:

{{Inventory|source=Historical one-time owner gift to players who had purchased an [[E-10]] when the voucher program was introduced; one per player|weight=0|price_text=Gift; not sold at retail|image=voucher}}

The '''E-11 Upgrade Voucher''' pays for one [[E-10]] to [[E-11 Saint|E-11]] hull upgrade at [[CPOC|Cutter's Port]].

== Source and eligibility ==
The voucher was gifted to players who had already purchased an E-10 at the time of the upgrade program. Each eligible player received '''one voucher in total''', regardless of how many E-10s they owned. It was a one-time owner gift, not an ongoing quest reward, salvage find or reward for every later E-10 purchase.

== Redemption ==
Carry the voucher in '''personal inventory''' and take the E-10 to Cutter's Port's '''Deluge Port''' for the hull upgrade. The upgrade consumes one voucher instead of charging the normal '''1,222,680 [[CR]]''' upgrade fee. The fee is the value of the service being redeemed, not a retail price for buying another voucher.

[[Category:Inventory]]

File:Backpack.png

2026-10-30T21:27:33Z

reskin:

Backpack

2026-10-30T21:27:14Z

reskin:

{{Inventory|source=Searchable in [[O-4|O-4 Salvage]] (random special find)|weight=1.633|price_text=Not sold at retail|image=backpack}}

A '''Backpack''' is a [[:Category:Inventory|personal inventory]] item that increases the total weight allowance checked when transferring items from a vehicle into personal baggage.

With a backpack already in personal inventory, this allowance is '''(Strength modifier + 10) × 15 lb''', compared with '''(Strength modifier + 10) × 8 lb''' without one. It does not add inventory slots or remove the separate per-item lifting limit. No Use command is required for the carrying allowance.

== Source ==
The backpack is a possible random special find at [[O-4|O-4 Salvage]]. Salvage finds enter the territory inventory and can then be loaded through the site's '''Inventory Management''' menu. No current retail purchase route is documented; the item's reference value is not a shop offer.

[[Category:Inventory]]

File:Candy-cane.png

2026-10-30T21:25:08Z

reskin:

Candy Cane

2026-10-30T21:24:58Z

reskin:

{{Inventory|source=Seasonal event reward from Santa at [[Christmas Town]]|weight=0.045|price_text=Event reward; not sold at retail|image=candy-cane}}

'''Candy Cane''' is a seasonal [[:Category:Inventory|inventory]] item awarded for visiting Santa. It is intended to restore the character's health in the same way as a [[First Aid Kit]].

== Source ==
Visit [[Christmas Town]] and choose '''Sit on Santa's Lap''' during the annual December event. The award window is '''December 11–24 inclusive''', using the player's local calendar date. The visit awards a candy cane subject to the event's repeat-visit restriction and available personal inventory space. The naughty/nice message does not change the item awarded.

== Use ==
Select the candy cane in the [[Manifest|cargo manifest]], under personal baggage or the vehicle cabin, and use '''Shift+U (Use)''' while injured. Its intended healing capacity is '''255 hitpoints''', equivalent to one full health bar in total. Only the requested healing is used; remaining capacity stays in the item, and the item is removed when depleted. It is not used at full health or inside the flight simulator.

'''Known issue (October 30, 2026):''' affected server versions can reject a candy cane with an incorrect distance message. A server correction has been prepared, but its availability on the running server has not yet been confirmed. Moving closer to another vehicle is not the intended requirement for healing.

[[Category:Inventory]]

File:Cigarrettes-carton.png

2026-10-30T21:24:13Z

reskin:

Carton of Cigarettes

2026-10-30T21:24:01Z

reskin:

{{Inventory|source=Searchable in [[O-4|O-4 Salvage]] (random special find)|weight=0.318|price_text=Not sold at retail|image=cigarrettes-carton}}

A '''Carton of Cigarettes''' is a collectible [[:Category:Inventory|inventory]] item that may be found during [[O-4]] salvage. It is listed as '''Cigarettes, Carton''' in some displays.

The carton is a random special find, deposited into the salvage territory inventory. Available items can be loaded into a vehicle through '''Inventory Management''' at the site. It has no implemented smoking, healing or other active Use effect. No current retail purchase route is documented.

[[Category:Inventory]]

Tutorial

2026-10-30T20:29:41Z

reskin: /* Start Moving */

''Excerpt from <u>Deois - Opportunities Await!</u>, pamphlet, distributed 2243/44''
<br>
<br>
<p class="rise-important" >Welcome to Vieneo, and welcome to the City of Deois!</p>

[[Deois]] is filled with possibilities and opportunities for enterprising citizens. Whether you are a colonist arriving through [[TAC]], a recent parolee, or you come from any number of other beginnings, all must start small and work their way up! Such is life in most colonies across [[United Stellar Republic]]-controlled space, and such it is here on [[Vieneo Province|Vieneo]].

Luckily, the city of Deois, late Provincial Governor Alan Parval, and current Provincial Governor Andrew Iodal have your back!

==Provided Amenities==

Incoming citizens are provided with two fantastic amenities by the city of Deois: a [[C-2A Dasher]] for transportation, and an apartment to call home in the [https://www.bradburybuilding.com Bradbury Building]! Furthermore, the apartment is located in and overlooks the bustling Transit District of Deois! Upon arriving inside, you will notice the Intermedia in the upper-right corner of the interface (if not, please notify your immigration supervisor). The Intermedia is the primary means of interfacing with the world in and around Vieneo and most major functions about the moon are hooked into the Intermedia Network.
<br>
<br>
Common functions provided by the Intermedia are fuel and cargo transfers, simulation access, banking teller operations, inspecting land, and accessing services provided by citizen-run colonies. If ever in doubt with what can be accomplished in a given area, take a look at the Intermedia.
<br>
<br>
Note that Intermedia behavior is context-sensitive to the area in which the citizen is currently operating. In other words, if you are in the industrial district you will be able to "Trade Cargo" via the Intermedia. If you are near [[Veridian Bank]], you will be able to access tellers via the Intermedia.
<br>
<br>
To leave the apartment and jump into that shiny, new Dasher, step into the front foyer in the apartment and check the [[Intermedia]] dialog window!
<br>
<br>
;DISCLAIMER
:<p class="rise-disclaimer">It has been made clear in your immigration paperwork (notably section 2.3 and partly 2.5) that this property is not owned by the incoming citizen. The titles and deeds of all provided living aids remain under the direct control of the city of Deois, in connection with [[Veridian Bank]]. Neither the apartment nor the vehicle need be paid off in any manner, so long as the citizen remains upon Vieneo or one of its orbital structures (exceptions are made for off-moon vacations but must be cleared with the Deois Department of Land Management to avoid [[repossession]]).</p>

== A Quick Word ==
Let's take a moment and be honest with ourselves. You're here to fly! You want to talk your way through a textbook ATC departure, plunge upward into the clouds at a 30 degree angle, and exit to find [[Yonmara]] blazing overhead. You want to enter orbit at 5 km/S, match trajectory with TAC at an altitude of 1000 km and dock to ferry new citizens back down to the surface. Perhaps one day you will gaze upon the beautiful, electric sphere of [[Vieneo]] from 3000 km away before seamlessly re-entering its thick atmosphere and sticking the perfect landing during a thunderstorm at Deois airport.
<br>
<p class="rise-important">You can AND WILL do all of this!</p>
But first, you need to establish yourself, and that takes credits. The City of Deois recommends taxi-driving as an efficient means of beginning your time in the city and on the moon. The simple truth is that there are many things to learn out there before you fly off into [[orbit]]! You need to become familiar with Deois, how to work the Intermedia, make some money, rent from Rusty's, and most importantly, get to know some of the frequent flyers (for example, [[User:rana|rana]]) that can help you step up in society (and will be glad to do so)!
<br>
<br>
Keep this all in mind as you begin to ferry around the other citizens of Deois!

;DISCLAIMER
:<p class="rise-disclaimer">Space flight is a highly dangerous endeavor. All previously mentioned activities can and have proved fatal to pilots due to user error. The City of Deois is not responsible for the lives of its citizens if lost due to user error in flight. Please note that the provided Dasher C-2 and apartment will be repossessed upon death.</p>

== Being a Taxi Driver ==
You should now be sat in your first vehicle outside of the [[Bradbury Apartments]]. The best way to start yourself off is to do the basic task of taxi driving, this will earn you only a little money whilst getting you used to the [[Deois|city layout]], the [[controls]] and use of the player interface.

Make sure to add a [[waypoint]] to your [[Bradbury Apartments|apartment]] before you start moving, read more on [[waypoint|waypoints]] on the [[Waypoint Management]] page.

== Start Moving ==
[[File:C-2A_Dash.png|thumb|The C-2A Dashboard]]
Before you start moving look around the Dashboard. You will see the Speedometer,
The gear indicator and to the right a compass with a bearing to bug and distance.
Using the [[Waypoint|Waypoints]] you can see were you need to head to go were you want.
The [[controls]] for the [[C-2 Dasher]] are pretty straight forward:
* Up and Down arrows to increase or decrease throttle
* Left and Right arrows to steer
* Spacebar to apply brakes
* "/" and "*" on the ten-key pad to shift gears
**The [[C-2A Dasher]] has a manual transmission
*** Park
*** Reverse
*** Neutral
*** 1st
*** 2nd
*** 3rd

Park to 1st gear is * * *

Additional none movement related controls:
* "P" toggle to start or turn off the engine
* "L" toggle headlights
* "O" toggle overhead lamps
* "R" toggle wipers

(it is suggested that you deactivate your overhead lamps (key: 'O'), as it is much easier to see outside the windshield without the glare the overhead lamps generate)

A [[game controller]] can also be used to control steering and throttle.

Once you drive a short distance away from your [[Bradbury Apartments|apartment]] your will enter the Transit District. When you enter the Transit District your [[Intermedia]] display will update with new options, now to start your first ride as a cab driver go for option ''2] Curbside Taxi''

The dispatch message confirms your new fare and tells you which building your passenger wants to go to and in what district this building is located. Now would be a good time to check out the map of [[Deois]] for the location of different buildings and get the [[coordinate]]s for the building your passenger wants to go to.

== Watch Those Curbs! ==
The curbs will hurt you and your vehicle if you hit them at speed so be careful! If you go off-road, slow down and leave room to steer around rocks; low speed alone does not guarantee a clear path. If you did hit a curb too hard and you are wounded or your car is damaged just press "Shift+R" to repair yourself, and if you have managed to land upside down press "F3". If you die you lose any money and cargo you have on you at that time.

Clients with surface-rock collision treat generated rocks as solid obstacles for vehicles, including aircraft close to the ground. Leave clearance around them when driving, taxiing, hovering or landing. In clients with triangle-based rock contact, collisions follow the rock surface, but the vehicle collision outline is still approximate; leave clearance around the vehicle. Surface-rock collision is disabled in the in-world simulator.

Once you arrived at the destination building, drive around it until you get a ''#] Unload Passenger'' option in the [[Intermedia]] menu.
'''Congratulations''', you just earned your first 25 [[CR]] on [[Vieneo]]!

== Banking Those Credits ==
I suggest the next step you take is taking your credits to the bank, that way you don't only earn interest on them, they are also safe and secure and not lost when you die. Load up the coordinates to the [[Deois]] [[Veridian Bank]] into your [[Waypoint Management|Waypoint Manager]] and drive to it.

Once you arrive at the [[Veridian Bank]] building, select ''1] Open Account'' from the [[Intermedia]] menu, now you have an account with [[Veridian Bank]] and you received a 50 [[CR]] bonus as a welcome gift. Now you can simply deposit your money into your account by going into ''2] Teller Functions'' and then use ''1] Deposit''. The same menu can be used to withdraw money from your account or to transfer money to another player.

<embedvideo service="youtube" description="Driving a Taxi to make credits">https://youtu.be/kI-yLTooWXQ</embedvideo>

== A World of Possibilities ==
'''Congratulations''' you got the hang of the basics of ''Rise: The Vieneo Province''. A world of possibilities is now open for you to explore, here are some ideas to get you started:

*[[Tow Illegal Vehicles]]
*[[:Category:Colonies|Start a Farm]]
*[[Transport Passengers]]
*[[Cargo|Trade Cargo]]
*Transport Prisoners
*Contracts

== Final Words ==
There is much more to do than drive around in a car just ask any other player. There are also [[:Category:Alliances|alliances]] in-game, some of which loan [[:Category:Aerospace Vehicles|aerospace vehicles]] in return for work, keep that in mind.

Our established players will pretty much jump up and down to provide answers for you and give you a little direction in your in-game career, we would love nothing more than to have you up in the air with us and exploring the world, we enjoy this game and would love it if you do too. You '''must''' ask questions, no question is a stupid question, this game is complex and there is much to be learned, don't have a bad time because you don't know what to do, ask someone - we won't bite!

See you in-game!<br />

== See Also ==
[[Keycard]]

[[Category:Getting Started]]

Tutorial

2026-10-30T20:17:39Z

reskin: /* A Quick Word */

''Excerpt from <u>Deois - Opportunities Await!</u>, pamphlet, distributed 2243/44''
<br>
<br>
<p class="rise-important" >Welcome to Vieneo, and welcome to the City of Deois!</p>

[[Deois]] is filled with possibilities and opportunities for enterprising citizens. Whether you are a colonist arriving through [[TAC]], a recent parolee, or you come from any number of other beginnings, all must start small and work their way up! Such is life in most colonies across [[United Stellar Republic]]-controlled space, and such it is here on [[Vieneo Province|Vieneo]].

Luckily, the city of Deois, late Provincial Governor Alan Parval, and current Provincial Governor Andrew Iodal have your back!

==Provided Amenities==

Incoming citizens are provided with two fantastic amenities by the city of Deois: a [[C-2A Dasher]] for transportation, and an apartment to call home in the [https://www.bradburybuilding.com Bradbury Building]! Furthermore, the apartment is located in and overlooks the bustling Transit District of Deois! Upon arriving inside, you will notice the Intermedia in the upper-right corner of the interface (if not, please notify your immigration supervisor). The Intermedia is the primary means of interfacing with the world in and around Vieneo and most major functions about the moon are hooked into the Intermedia Network.
<br>
<br>
Common functions provided by the Intermedia are fuel and cargo transfers, simulation access, banking teller operations, inspecting land, and accessing services provided by citizen-run colonies. If ever in doubt with what can be accomplished in a given area, take a look at the Intermedia.
<br>
<br>
Note that Intermedia behavior is context-sensitive to the area in which the citizen is currently operating. In other words, if you are in the industrial district you will be able to "Trade Cargo" via the Intermedia. If you are near [[Veridian Bank]], you will be able to access tellers via the Intermedia.
<br>
<br>
To leave the apartment and jump into that shiny, new Dasher, step into the front foyer in the apartment and check the [[Intermedia]] dialog window!
<br>
<br>
;DISCLAIMER
:<p class="rise-disclaimer">It has been made clear in your immigration paperwork (notably section 2.3 and partly 2.5) that this property is not owned by the incoming citizen. The titles and deeds of all provided living aids remain under the direct control of the city of Deois, in connection with [[Veridian Bank]]. Neither the apartment nor the vehicle need be paid off in any manner, so long as the citizen remains upon Vieneo or one of its orbital structures (exceptions are made for off-moon vacations but must be cleared with the Deois Department of Land Management to avoid [[repossession]]).</p>

== A Quick Word ==
Let's take a moment and be honest with ourselves. You're here to fly! You want to talk your way through a textbook ATC departure, plunge upward into the clouds at a 30 degree angle, and exit to find [[Yonmara]] blazing overhead. You want to enter orbit at 5 km/S, match trajectory with TAC at an altitude of 1000 km and dock to ferry new citizens back down to the surface. Perhaps one day you will gaze upon the beautiful, electric sphere of [[Vieneo]] from 3000 km away before seamlessly re-entering its thick atmosphere and sticking the perfect landing during a thunderstorm at Deois airport.
<br>
<p class="rise-important">You can AND WILL do all of this!</p>
But first, you need to establish yourself, and that takes credits. The City of Deois recommends taxi-driving as an efficient means of beginning your time in the city and on the moon. The simple truth is that there are many things to learn out there before you fly off into [[orbit]]! You need to become familiar with Deois, how to work the Intermedia, make some money, rent from Rusty's, and most importantly, get to know some of the frequent flyers (for example, [[User:rana|rana]]) that can help you step up in society (and will be glad to do so)!
<br>
<br>
Keep this all in mind as you begin to ferry around the other citizens of Deois!

;DISCLAIMER
:<p class="rise-disclaimer">Space flight is a highly dangerous endeavor. All previously mentioned activities can and have proved fatal to pilots due to user error. The City of Deois is not responsible for the lives of its citizens if lost due to user error in flight. Please note that the provided Dasher C-2 and apartment will be repossessed upon death.</p>

== Being a Taxi Driver ==
You should now be sat in your first vehicle outside of the [[Bradbury Apartments]]. The best way to start yourself off is to do the basic task of taxi driving, this will earn you only a little money whilst getting you used to the [[Deois|city layout]], the [[controls]] and use of the player interface.

Make sure to add a [[waypoint]] to your [[Bradbury Apartments|apartment]] before you start moving, read more on [[waypoint|waypoints]] on the [[Waypoint Management]] page.

== Start Moving ==
[[File:C-2A_Dash.png|thumb|The C-2A Dashboard]]
Before you start moving look around the Dashboard. You will see the Speedometer,
The gear indicator and to the right a compass with a bearing to bug and distance.
Using the [[Waypoint|Waypoints]] you can see were you need to head to go were you want.
The [[controls]] for the [[C-2 Dasher]] are pretty straight forward:
* Up and Down arrows to increase or decrease throttle
* Left and Right arrows to steer
* Spacebar to apply brakes
* "/" and "*" on the ten-key pad to shift gears
**The [[C-2 Dasher|C-2]] has a manual transmission
*** Park
*** Reverse
*** Neutral
*** 1st
*** 2nd
*** 3rd

Park to 1st gear is * * *

Additional none movement related controls:
* "P" toggle to start or turn off the engine
* "L" toggle headlights
* "O" toggle overhead lamps

(it is suggested that you deactivate your overhead lamps (key: 'O'), as it is much easier to see outside the windshield without the glare the overhead lamps generate)

A [[game controller]] can also be used to control steering and throttle.

Once you drive a short distance away from your [[Bradbury Apartments|apartment]] your will enter the Transit District. When you enter the Transit District your [[Intermedia]] display will update with new options, now to start your first ride as a cab driver go for option ''2] Curbside Taxi''

The dispatch message confirms your new fare and tells you which building your passenger wants to go to and in what district this building is located. Now would be a good time to check out the map of [[Deois]] for the location of different buildings and get the [[coordinate]]s for the building your passenger wants to go to.

== Watch Those Curbs! ==
The curbs will hurt you and your vehicle if you hit them at speed so be careful! If you go off-road, slow down and leave room to steer around rocks; low speed alone does not guarantee a clear path. If you did hit a curb too hard and you are wounded or your car is damaged just press "Shift+R" to repair yourself, and if you have managed to land upside down press "F3". If you die you lose any money and cargo you have on you at that time.

Clients with surface-rock collision treat generated rocks as solid obstacles for vehicles, including aircraft close to the ground. Leave clearance around them when driving, taxiing, hovering or landing. In clients with triangle-based rock contact, collisions follow the rock surface, but the vehicle collision outline is still approximate; leave clearance around the vehicle. Surface-rock collision is disabled in the in-world simulator.

Once you arrived at the destination building, drive around it until you get a ''#] Unload Passenger'' option in the [[Intermedia]] menu.
'''Congratulations''', you just earned your first 25 [[CR]] on [[Vieneo]]!

== Banking Those Credits ==
I suggest the next step you take is taking your credits to the bank, that way you don't only earn interest on them, they are also safe and secure and not lost when you die. Load up the coordinates to the [[Deois]] [[Veridian Bank]] into your [[Waypoint Management|Waypoint Manager]] and drive to it.

Once you arrive at the [[Veridian Bank]] building, select ''1] Open Account'' from the [[Intermedia]] menu, now you have an account with [[Veridian Bank]] and you received a 50 [[CR]] bonus as a welcome gift. Now you can simply deposit your money into your account by going into ''2] Teller Functions'' and then use ''1] Deposit''. The same menu can be used to withdraw money from your account or to transfer money to another player.

<embedvideo service="youtube" description="Driving a Taxi to make credits">https://youtu.be/kI-yLTooWXQ</embedvideo>

== A World of Possibilities ==
'''Congratulations''' you got the hang of the basics of ''Rise: The Vieneo Province''. A world of possibilities is now open for you to explore, here are some ideas to get you started:

*[[Tow Illegal Vehicles]]
*[[:Category:Colonies|Start a Farm]]
*[[Transport Passengers]]
*[[Cargo|Trade Cargo]]
*Transport Prisoners
*Contracts

== Final Words ==
There is much more to do than drive around in a car just ask any other player. There are also [[:Category:Alliances|alliances]] in-game, some of which loan [[:Category:Aerospace Vehicles|aerospace vehicles]] in return for work, keep that in mind.

Our established players will pretty much jump up and down to provide answers for you and give you a little direction in your in-game career, we would love nothing more than to have you up in the air with us and exploring the world, we enjoy this game and would love it if you do too. You '''must''' ask questions, no question is a stupid question, this game is complex and there is much to be learned, don't have a bad time because you don't know what to do, ask someone - we won't bite!

See you in-game!<br />

== See Also ==
[[Keycard]]

[[Category:Getting Started]]

Tutorial

2026-10-30T20:15:27Z

reskin: /* Provided Amenities */

''Excerpt from <u>Deois - Opportunities Await!</u>, pamphlet, distributed 2243/44''
<br>
<br>
<p class="rise-important" >Welcome to Vieneo, and welcome to the City of Deois!</p>

[[Deois]] is filled with possibilities and opportunities for enterprising citizens. Whether you are a colonist arriving through [[TAC]], a recent parolee, or you come from any number of other beginnings, all must start small and work their way up! Such is life in most colonies across [[United Stellar Republic]]-controlled space, and such it is here on [[Vieneo Province|Vieneo]].

Luckily, the city of Deois, late Provincial Governor Alan Parval, and current Provincial Governor Andrew Iodal have your back!

==Provided Amenities==

Incoming citizens are provided with two fantastic amenities by the city of Deois: a [[C-2A Dasher]] for transportation, and an apartment to call home in the [https://www.bradburybuilding.com Bradbury Building]! Furthermore, the apartment is located in and overlooks the bustling Transit District of Deois! Upon arriving inside, you will notice the Intermedia in the upper-right corner of the interface (if not, please notify your immigration supervisor). The Intermedia is the primary means of interfacing with the world in and around Vieneo and most major functions about the moon are hooked into the Intermedia Network.
<br>
<br>
Common functions provided by the Intermedia are fuel and cargo transfers, simulation access, banking teller operations, inspecting land, and accessing services provided by citizen-run colonies. If ever in doubt with what can be accomplished in a given area, take a look at the Intermedia.
<br>
<br>
Note that Intermedia behavior is context-sensitive to the area in which the citizen is currently operating. In other words, if you are in the industrial district you will be able to "Trade Cargo" via the Intermedia. If you are near [[Veridian Bank]], you will be able to access tellers via the Intermedia.
<br>
<br>
To leave the apartment and jump into that shiny, new Dasher, step into the front foyer in the apartment and check the [[Intermedia]] dialog window!
<br>
<br>
;DISCLAIMER
:<p class="rise-disclaimer">It has been made clear in your immigration paperwork (notably section 2.3 and partly 2.5) that this property is not owned by the incoming citizen. The titles and deeds of all provided living aids remain under the direct control of the city of Deois, in connection with [[Veridian Bank]]. Neither the apartment nor the vehicle need be paid off in any manner, so long as the citizen remains upon Vieneo or one of its orbital structures (exceptions are made for off-moon vacations but must be cleared with the Deois Department of Land Management to avoid [[repossession]]).</p>

== A Quick Word ==
Let's take a moment and be honest with ourselves. You're here to fly! You want to talk your way through a textbook ATC departure, plunge upward into the clouds at a 30 degree angle, and exit to find [[Yonmara]] blazing overhead. You want to enter orbit at 5 km/S, match trajectory with TAC at an altitude of 1000 km and doc to ferry new citizens back down to the surface. Perhaps one day you will gaze upon the beautiful, electric sphere of [[Vieneo]] from 3000 km away before seamlessly re-entering its thick atmosphere and sticking the perfect landing during a thunderstorm at Deois airport.
<br>
<p class="rise-important">You can AND WILL do all of this!</p>
But first, you need to establish yourself, and that takes credits. The City of Deois recommends taxi-driving as an efficient means of beginning your time in the city and on the moon. The simple truth is that there are many things to learn out there before you fly off into orbit! You need to become familiar with Deois, how to work the Intermedia, make some money, rent from Rusty's, and most importantly, get to know some of the frequent flyers (for example, [[User:rana|rana]]) that can help you step up in society (and will be glad to do so)!
<br>
<br>
Keep this all in mind as you begin to ferry around the other citizens of Deois!

;DISCLAIMER
:<p class="rise-disclaimer">Space flight is a highly dangerous endeavor. All previously mentioned activities can and have proved fatal to pilots due to user error. The City of Deois is not responsible for the lives of its citizens if lost due to user error in flight. Please note that the provided Dasher C-2 and apartment will be repossessed upon death.</p>

== Being a Taxi Driver ==
You should now be sat in your first vehicle outside of the [[Bradbury Apartments]]. The best way to start yourself off is to do the basic task of taxi driving, this will earn you only a little money whilst getting you used to the [[Deois|city layout]], the [[controls]] and use of the player interface.

Make sure to add a [[waypoint]] to your [[Bradbury Apartments|apartment]] before you start moving, read more on [[waypoint|waypoints]] on the [[Waypoint Management]] page.

== Start Moving ==
[[File:C-2A_Dash.png|thumb|The C-2A Dashboard]]
Before you start moving look around the Dashboard. You will see the Speedometer,
The gear indicator and to the right a compass with a bearing to bug and distance.
Using the [[Waypoint|Waypoints]] you can see were you need to head to go were you want.
The [[controls]] for the [[C-2 Dasher]] are pretty straight forward:
* Up and Down arrows to increase or decrease throttle
* Left and Right arrows to steer
* Spacebar to apply brakes
* "/" and "*" on the ten-key pad to shift gears
**The [[C-2 Dasher|C-2]] has a manual transmission
*** Park
*** Reverse
*** Neutral
*** 1st
*** 2nd
*** 3rd

Park to 1st gear is * * *

Additional none movement related controls:
* "P" toggle to start or turn off the engine
* "L" toggle headlights
* "O" toggle overhead lamps

(it is suggested that you deactivate your overhead lamps (key: 'O'), as it is much easier to see outside the windshield without the glare the overhead lamps generate)

A [[game controller]] can also be used to control steering and throttle.

Once you drive a short distance away from your [[Bradbury Apartments|apartment]] your will enter the Transit District. When you enter the Transit District your [[Intermedia]] display will update with new options, now to start your first ride as a cab driver go for option ''2] Curbside Taxi''

The dispatch message confirms your new fare and tells you which building your passenger wants to go to and in what district this building is located. Now would be a good time to check out the map of [[Deois]] for the location of different buildings and get the [[coordinate]]s for the building your passenger wants to go to.

== Watch Those Curbs! ==
The curbs will hurt you and your vehicle if you hit them at speed so be careful! If you go off-road, slow down and leave room to steer around rocks; low speed alone does not guarantee a clear path. If you did hit a curb too hard and you are wounded or your car is damaged just press "Shift+R" to repair yourself, and if you have managed to land upside down press "F3". If you die you lose any money and cargo you have on you at that time.

Clients with surface-rock collision treat generated rocks as solid obstacles for vehicles, including aircraft close to the ground. Leave clearance around them when driving, taxiing, hovering or landing. In clients with triangle-based rock contact, collisions follow the rock surface, but the vehicle collision outline is still approximate; leave clearance around the vehicle. Surface-rock collision is disabled in the in-world simulator.

Once you arrived at the destination building, drive around it until you get a ''#] Unload Passenger'' option in the [[Intermedia]] menu.
'''Congratulations''', you just earned your first 25 [[CR]] on [[Vieneo]]!

== Banking Those Credits ==
I suggest the next step you take is taking your credits to the bank, that way you don't only earn interest on them, they are also safe and secure and not lost when you die. Load up the coordinates to the [[Deois]] [[Veridian Bank]] into your [[Waypoint Management|Waypoint Manager]] and drive to it.

Once you arrive at the [[Veridian Bank]] building, select ''1] Open Account'' from the [[Intermedia]] menu, now you have an account with [[Veridian Bank]] and you received a 50 [[CR]] bonus as a welcome gift. Now you can simply deposit your money into your account by going into ''2] Teller Functions'' and then use ''1] Deposit''. The same menu can be used to withdraw money from your account or to transfer money to another player.

<embedvideo service="youtube" description="Driving a Taxi to make credits">https://youtu.be/kI-yLTooWXQ</embedvideo>

== A World of Possibilities ==
'''Congratulations''' you got the hang of the basics of ''Rise: The Vieneo Province''. A world of possibilities is now open for you to explore, here are some ideas to get you started:

*[[Tow Illegal Vehicles]]
*[[:Category:Colonies|Start a Farm]]
*[[Transport Passengers]]
*[[Cargo|Trade Cargo]]
*Transport Prisoners
*Contracts

== Final Words ==
There is much more to do than drive around in a car just ask any other player. There are also [[:Category:Alliances|alliances]] in-game, some of which loan [[:Category:Aerospace Vehicles|aerospace vehicles]] in return for work, keep that in mind.

Our established players will pretty much jump up and down to provide answers for you and give you a little direction in your in-game career, we would love nothing more than to have you up in the air with us and exploring the world, we enjoy this game and would love it if you do too. You '''must''' ask questions, no question is a stupid question, this game is complex and there is much to be learned, don't have a bad time because you don't know what to do, ask someone - we won't bite!

See you in-game!<br />

== See Also ==
[[Keycard]]

[[Category:Getting Started]]

Airspace

2026-10-25T13:24:59Z

reskin: /* Runway incursions */

Currently we have two (2) types of controlled airspace in the game.

[[Image:DeoisClassBravo.png|thumb|right]]
= Deois =
[[Deois]] has what is very similar to an Enhanced Class B airspace (37km laterally and 5.5km vertically) with a procedural area (where the menus start appearing) at 55.5km and 18.25km respectively.

Speed limit is 125 m/s [[IAS]]. Air Traffic Control cannot clear you to go faster.

[[Image:JamesGarrett.png|48px|right]]
== Choosing Approach or Departure ==

Choose the controller according to where your flight is going, not simply whether you are taking off or landing.

* '''Approach Clearance:''' Use Deois Approach when your destination is inside Deois controlled airspace. This includes a flight whose origin and destination are both inside the airspace, such as flying from an east colony pad to a west colony pad or a district landing zone. Select the appropriate local destination when asked for your intentions.
* '''Departure Clearance:''' Use Deois Departure when leaving Deois controlled airspace. The EAST and WEST departure choices describe the direction in which you intend to leave the terminal area; they are not the choices for a local flight between Deois landing sites.
* '''Transition Clearance:''' This is intended for a flight passing through Deois controlled airspace with both its origin and destination outside the airspace. It is not intended for a local flight or for departing from a Deois landing site. '''As of October 24, 2026, this menu option is displayed but is not implemented. Selecting it does not obtain a clearance to enter the airspace.'''

'''Local flights still need takeoff or dustoff clearance.''' When starting on the ground in controlled airspace, contact the appropriate controller, state your destination, and wait for explicit takeoff or dustoff clearance before lifting off. Selecting Approach, making initial radio contact, or hearing "radar contact" is not a takeoff clearance.

If you selected Departure but intend to land somewhere else inside Deois airspace, use '''Flight Options > Change Destination''' and select the local landing destination. ATC can then handle the flight with Approach. Follow the new instructions and acknowledge them.

== Personnel ==
Shifts lengths can be up to 10 hours. Controllers must not work more than 6 consecutive days.

* Veena Russell - SATCS (retired)
* Swathi Patel - SATCS (active)
* James Garrett - SATCS (retiring October 3!)
* Lee Bush - ATCS (starting October 4!)
* Julie Williams - ATCS (started 6-18-2249)

== Procedures ==
=== Arrivals ===
* [[Media:VDEO LHEED1 (Chart 2-1).pdf|LHEED ONE]]
* [[Media:VDEO RUSTY1 (Chart 2-2).pdf|RUSTY ONE]]
* [[Media:VDEO FLEET2 & MUVER4 (Chart 2-3).pdf|FLEET TWO and MUVER FOUR]]
=== Approaches ===
* [[Media:VDEO ILS 36 (Chart 1-1).pdf|ILS 36]]
=== Airport ===
* [[Media:VDEO Airport Diagram (Chart 4-3).svg|Airport Diagram]]

=== Runway incursions ===
[[File:Deois Port District runway protection.png|thumb|right|360px|Runway Environment Protection]]

A runway incursion occurs when an aircraft or ground vehicle enters or occupies the runway without appropriate clearance or interferes with an authorized runway operation. Even an aircraft that has landed normally can keep the runway occupied until it has vacated completely.

Tower is responsible for the Port District runway and its taxiway entry and exit areas. '''Hold short''' means keeping the entire aircraft clear of the runway, including its nose, wings and tail. Being on the frequency or hearing "radar contact" does not authorize runway entry or takeoff. Wait for the appropriate clearance, and keep ground vehicles clear of the runway during flight operations.

'''Automated monitoring rollout:''' As of October 25, 2026, the runway-occupancy checks described below are implemented but awaiting deployment and in-game verification.

The surface check includes aircraft that have not contacted ATC, aircraft whose ATC service has ended, and ground vehicles. It checks the vehicle's footprint and whether its movement is about to carry it onto the runway. Aircraft parked on the ramp or waiting on the parallel taxiway do not block the runway unless their footprint or projected movement reaches it.

* '''Departures:''' Tower can instruct an aircraft to hold short, or hold position if it is already on the runway. A waiting takeoff clearance can be cancelled when an obstruction appears. Wait for a fresh clearance after the runway is clear.
* '''Arrivals farther out:''' Tower can allow the approach to continue while withholding landing clearance, explaining that traffic is on or approaching the runway. "Continue approach" is not a landing clearance.
* '''Close or already-cleared arrivals:''' If the runway becomes obstructed, tower can instruct the aircraft to go around. Follow the missed-approach instructions and acknowledge subsequent vectors.
* '''Takeoff already underway:''' An aircraft moving quickly on its takeoff roll or already airborne receives a traffic caution rather than an automatic stop instruction.

This protection covers runway use. A separate ground-control service for ramp movements and taxi routes is planned for later.

<div style="clear:both;"></div>

=== Departures ===
* [[Media:VDEO CARGO4 (Chart 3-2).pdf|CARGO FOUR]]
* [[Media:VDEO PRIMA1 (Chart 3-1).pdf|PRIMA ONE]]

= Docks =
The docks have what is similar to a Class C airspace except that it is a sphere around the facility with a 20km procedural zone and a 18.5km perimeter.

Special Commands

2026-10-25T12:17:52Z

reskin: Undo revision 5055 by reskin (talk)

These commands are entered in the [[Communications]] window and are not regurgitated to other players. First hit "Enter" to focus the chat line, then enter the commands below, then hit "Enter" again to send the request. If the request cannot be accommodated (for example no unoccupied vehicles of a specific type) the server will send a reply in the chat history.

==Players==
<br />
'''000DESTRUCT0'''

Initialize auto-destruct sequence (commit suicide)

Using this command has the same implications as a normal [[deaths|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.
<br /><br />
'''000WEIGHT<percent>'''

Artificially set your vehicle's fuel and payload loading for flight testing. Administrators can use this in their current vehicle; other players can use it only while in a [[Flight Simulators|simulator]].

Enter a whole-number percentage directly after the command, without a percent sign, for example '''000WEIGHT125'''. '''Values above 100 are supported''' and allow overweight testing. Use ordinary decimal digits without leading zeros in the percentage; fractional percentages are not supported.

The percentage applies to the normal fuel-and-payload allowance: '''maximum gross weight minus empty weight'''. The requested load is:

:<code>(maximum gross weight - empty weight) * percent / 100</code>

Fuel is filled first, up to tank capacity, and any remaining load becomes payload. Fuel is never set below 2% of tank capacity by this command. The extra load above 100% is not capped at maximum gross weight.

* '''000WEIGHT0''': zero payload and 2% fuel; slightly above empty weight.
* '''000WEIGHT50''': half the normal fuel-and-payload allowance, subject to the minimum fuel load.
* '''000WEIGHT100''': the normal maximum-gross fuel-and-payload loading.
* '''000WEIGHT125''': 125% of the normal fuel-and-payload allowance.
* '''000WEIGHT150''' or '''000WEIGHT200''': 150% or 200% of that allowance for heavier overload tests.

For example, a vehicle with an empty weight of 6,000 lb and a maximum gross weight of 10,000 lb has a 4,000 lb allowance. '''000WEIGHT150''' loads 6,000 lb of fuel plus payload, giving 12,000 lb gross before any additional ice weight. It does not mean 150% of maximum gross weight.

This is a one-time loading adjustment, not a weight lock: fuel continues to burn, and subsequent server loading updates can replace the fuel and payload values. To return to normal maximum-gross loading, enter '''000WEIGHT100'''; for minimum loading, enter '''000WEIGHT0'''. Neither command restores the exact fuel and payload carried before the test.

==Admins Only==
<br />
'''111VEHICLETYPE##'''
<br>

Requests transfer to the nearest, unoccupied, active, empty vehicle not owned by Rusty's (preference for vehicles you have access to)
of the requested type in the same reference frame within 320 km

Types are listed here:

*C98 = 1,
*DIHV = 2,
*E10 = 3,
*P13 = 4,
*A4 = 5,
*C2 = 6,
*T120 = 7,
*E11 = 8,
*//T1 = 9, // UNUSED
*ARJ_PAX = 10,
*ARJ_CNST = 11,
*ARJ_CARGOAFT = 12,
*ARJ_FUEL = 13,
*ARJ_CARGOTOP = 14,
*ARJ_MUNITIONS = 15,
*ARJ_ENUM = 19, // ARJs reserved 10-1
*Apartment = 20, // reserved
*C2A = 21, // new dasher
*T27 = 22, // mammoth
*BeishtKione = 23,
*W6Manx = 24,
*SimBay = 25, // reserved
*ControlTower = 26, // reserved
*T19 = 27, // stratomaster
*FloatingMan = 28,
*T121 = 29 // steerhead

<br />
'''111VEHICLE#####'''
<br>

Requests transfer to the specified IVR as long as it is unoccupied, active vehicle

'''111VEHICLERETURN'''

Requests transfer back to original vehicle before 111VEHICLETYPE## was ever used as long as it is within 320 km

'''111REFUELME'''

Refuels your current vehicle to the maximum allowable for the vehicle type

'''111DIHVSTATUS#'''

Queue up arrival or departure animation for the DIHV ship
(does not affect newspaper, loading/unloading of materials from TAC)

* 0 = Undock and depart
* 1 = Arrive and dock

'''000COMMANDW0'''

Repositions you to the currently selected waypoint.

It will appear that you died but that death doesn't get reported ... it is just to give the system time to calculate new barycentric velocity, etc.

'''000COMMANDO0'''

Repositions you 500 km above the surface at your current location (for space-capable vehicles only) in a stable orbit

'''000COMMANDD0'''

Repositions you to the currently selected dock (for space-capable vehicles only)

'''000COMMANDSIM0'''

Toggles whether your current vehicle is a [[Flight Simulators|simulator]] or not (only available on the E-11, T-19, and W-6 models currently)

'''000COMMANDVISX.XXX'''
Control the visibility in kilometers (0.500 for 500 metres; 2.000 for 2 km; -1 to restore live weather)

'''000COMMANDBCLX.XXX'''
Sets the cloud bases in kilometers AGL (-1 to reset, 0 is on ground level, 1.5 would be 1500 meters)

'''000COMMANDACL0'''

Re-positions you 20 km straight up from your current position

'''000COMMANDSUNvalue''' and '''000COMMANDSUN-1'''

Administrator-only visual sun-position override for your client. With an updated client, enter a number from 0 to 1 directly after <code>000COMMANDSUN</code>, using a decimal point for fractions. For example, <code>000COMMANDSUN0.5</code> puts the sun on the local horizon.

* <code>000COMMANDSUN0</code>: directly below you, on the opposite side of the planet (-90 degrees elevation).
* <code>000COMMANDSUN0.25</code>: 45 degrees below the local horizon.
* <code>000COMMANDSUN0.5</code>: on the local tangent horizon (0 degrees elevation).
* <code>000COMMANDSUN0.75</code>: 45 degrees above the local horizon.
* <code>000COMMANDSUN1</code>: directly overhead (+90 degrees elevation).
* <code>000COMMANDSUN-1</code>: remove the override and restore the current natural orbital position.

Intermediate values change elevation continuously; they are not brightness percentages or times of day. The sun keeps its natural bearing where that bearing is defined. The selected elevation follows your current location, including during flight and in orbit. At altitude, the visible planetary limb lies below the local tangent horizon, so 0.5 need not put the sun on the limb.

The solar disc, sky, clouds and scene lighting share the overridden direction. Clouds, terrain and atmospheric visibility can still obscure the sun. The game clock continues to follow the natural orbit. This retains the existing administrator sun override in the simulator. The override remains active until reset or client restart; <code>000COMMANDSUN-1</code> is the reset command. Invalid values leave the previous setting unchanged and write usage guidance to the client log.

'''000COMMANDALPHA0''' and '''000COMMANDALPHA1'''

Controls the alpha screen level (to simulate being in with 400m viz or out of the clouds with 42.16km viz)

'''<nowiki>000COMMANDGAMMA<strength></nowiki>''' or '''000COMMANDGAMMA-1'''

Administrator only. In the experimental plasma-envelope client, use a strength from 0 to 1, including decimals with a dot: for example, '''000COMMANDGAMMA0.5''' requests half target strength. The preview is visible through the windshield and external camera mounts. While the preview is active, its flow runs from nose to tail, fixed to the ship, at a constant animation rate independent of actual airspeed, orbital direction and wind. This flow override does not change the vehicle's velocity or attitude. Changing the strength changes brightness, not animation speed. GAMMA1 requests full target strength, GAMMA0 forces it off, and GAMMA-1 cancels the override and restores automatic brightness and the actual air-relative direction. Malformed or out-of-range values are ignored without changing the active override; no extra parameters are accepted. The preview is suppressed in the simulator and cleared on simulator entry; it is also unavailable in building/windowless interiors or while carried inside another vehicle. Clouds may obscure it.

The GAMMA value also sets the local radio-blackout fraction: 0 means no plasma-induced radio loss, 0.5 masks half the characters in ordinary radio-chat messages and halves scanner range, and 1 masks all message text and reduces scanner range to zero. Text loss is rounded down to whole characters and applies independently when transmitting and receiving; both ends of a link can impair a message. Your local sent-message history keeps the original typed text; the transmitted copy is garbled. This is a linear diagnostic scale, not an electron-density measurement or a prediction of a real radio-frequency cutoff. Direct/private messages, waypoint attachments and cockpit voice audio retain their existing behavior. GAMMA-1 restores the automatic radio-blackout calculation along with automatic glow and airflow. Simulator entry clears the override and blackout.

It does not establish a safe entry speed or temperature. Earlier clients use the cockpit-glass effect and require the ALPHA cloud overlay to be disabled to see that preview.

'''000COMMANDELMO0''' and '''000COMMANDELMO1'''

Controls the St. Elmo's Fire effect (must also have 000COMMANDALPHA enabled)

'''000COMMANDRAINXX'''

Overrides the the precipitation level locally. 2 to turn off, 16 is maximum, -1 to remove override.

'''000COMMANDBOLT'''

A bolt of lightning 50% intensity and between 0 km and 64 km distant (average of 16 km)

'''000COMMANDCLOUDBOLT1''' and '''000COMMANDCLOUDBOLT0'''

Administrator-only, client-local orbital lightning visibility test (updated client required). Enter <code>000COMMANDCLOUDBOLT1</code> to start or restart a 30-real-second test; <code>000COMMANDCLOUDBOLT0</code> stops it immediately. No spaces or additional parameters are needed.

The test starts two cloud-lightning events per second, with anchors within a 100 km surface radius beneath the moving ship. Each event can flash through up to three connected sections inside existing cloud moisture. The path stays fixed to the planet after spawning. Look down at the clouds, preferably at night or twilight. The client log reports whether the command started or why it was refused.

It requires real flight above the highest supported cloud layer (currently 22 km MSL), the volumetric cloud renderer and a loaded global weather map. It is disabled in the in-world simulator. Expiry, cancellation, simulator entry, renderer reset, missing weather, reconnect, or descent to the diagnostic altitude limit clears the test. Stalls skip missed events; the 30-second wall-clock deadline does not restart.

The diagnostic forces storm-strength events without changing the convection map, cloud shape or natural planetary event schedule. Empty cloud regions may skip events. It produces cloud illumination only: no exposed bolt, server event, thunder or damage. Natural lightning still depends on live convection; see [[Weather#Cloud lightning|Weather: Cloud lightning]].

'''000COMMANDRADIO'''

Temporarily toggles whether the current vehicle is equipped with a [[JVC Radio]]

'''000COMMANDNVG'''

Temporarily toggles whether the current vehicle is equipped with [[Night Vision Goggles]]

Special Commands

2026-10-25T12:17:15Z

reskin:

These commands are entered in the [[Communications]] window and are not regurgitated to other players. First hit "Enter" to focus the chat line, then enter the commands below, then hit "Enter" again to send the request. If the request cannot be accommodated (for example no unoccupied vehicles of a specific type) the server will send a reply in the chat history.

==Players==
<br />
'''000DESTRUCT0'''

Initialize auto-destruct sequence (commit suicide)

Using this command has the same implications as a normal [[deaths|death]]. You will also be refueled but there are limitations ... for example, you can't self-destruct to get fuel, sell all the fuel, and then expect to be awarded a full tank on subsequent self-destruct ... you must burn fuel awarded through self-destruct in order to get fuel in the future.
<br /><br />
'''000WEIGHT0''' through '''000WEIGHT100'''

Artificially set your vehicle weight ([[Flight Simulators|flight simulators]])

Set your vehicle weight between "empty weight" and "max gross weight" for flight testing (admins) or when in the [[Flight Simulators|simulator]] (all other players).

==Admins Only==
<br />
'''111VEHICLETYPE##'''
<br>

Requests transfer to the nearest, unoccupied, active, empty vehicle not owned by Rusty's (preference for vehicles you have access to)
of the requested type in the same reference frame within 320 km

Types are listed here:

*C98 = 1,
*DIHV = 2,
*E10 = 3,
*P13 = 4,
*A4 = 5,
*C2 = 6,
*T120 = 7,
*E11 = 8,
*//T1 = 9, // UNUSED
*ARJ_PAX = 10,
*ARJ_CNST = 11,
*ARJ_CARGOAFT = 12,
*ARJ_FUEL = 13,
*ARJ_CARGOTOP = 14,
*ARJ_MUNITIONS = 15,
*ARJ_ENUM = 19, // ARJs reserved 10-1
*Apartment = 20, // reserved
*C2A = 21, // new dasher
*T27 = 22, // mammoth
*BeishtKione = 23,
*W6Manx = 24,
*SimBay = 25, // reserved
*ControlTower = 26, // reserved
*T19 = 27, // stratomaster
*FloatingMan = 28,
*T121 = 29 // steerhead

<br />
'''111VEHICLE#####'''
<br>

Requests transfer to the specified IVR as long as it is unoccupied, active vehicle

'''111VEHICLERETURN'''

Requests transfer back to original vehicle before 111VEHICLETYPE## was ever used as long as it is within 320 km

'''111REFUELME'''

Refuels your current vehicle to the maximum allowable for the vehicle type

'''111DIHVSTATUS#'''

Queue up arrival or departure animation for the DIHV ship
(does not affect newspaper, loading/unloading of materials from TAC)

* 0 = Undock and depart
* 1 = Arrive and dock

'''000COMMANDW0'''

Repositions you to the currently selected waypoint.

It will appear that you died but that death doesn't get reported ... it is just to give the system time to calculate new barycentric velocity, etc.

'''000COMMANDO0'''

Repositions you 500 km above the surface at your current location (for space-capable vehicles only) in a stable orbit

'''000COMMANDD0'''

Repositions you to the currently selected dock (for space-capable vehicles only)

'''000COMMANDSIM0'''

Toggles whether your current vehicle is a [[Flight Simulators|simulator]] or not (only available on the E-11, T-19, and W-6 models currently)

'''000COMMANDVISX.XXX'''
Control the visibility in kilometers (0.500 for 500 metres; 2.000 for 2 km; -1 to restore live weather)

'''000COMMANDBCLX.XXX'''
Sets the cloud bases in kilometers AGL (-1 to reset, 0 is on ground level, 1.5 would be 1500 meters)

'''000COMMANDACL0'''

Re-positions you 20 km straight up from your current position

'''000COMMANDSUNvalue''' and '''000COMMANDSUN-1'''

Administrator-only visual sun-position override for your client. With an updated client, enter a number from 0 to 1 directly after <code>000COMMANDSUN</code>, using a decimal point for fractions. For example, <code>000COMMANDSUN0.5</code> puts the sun on the local horizon.

* <code>000COMMANDSUN0</code>: directly below you, on the opposite side of the planet (-90 degrees elevation).
* <code>000COMMANDSUN0.25</code>: 45 degrees below the local horizon.
* <code>000COMMANDSUN0.5</code>: on the local tangent horizon (0 degrees elevation).
* <code>000COMMANDSUN0.75</code>: 45 degrees above the local horizon.
* <code>000COMMANDSUN1</code>: directly overhead (+90 degrees elevation).
* <code>000COMMANDSUN-1</code>: remove the override and restore the current natural orbital position.

Intermediate values change elevation continuously; they are not brightness percentages or times of day. The sun keeps its natural bearing where that bearing is defined. The selected elevation follows your current location, including during flight and in orbit. At altitude, the visible planetary limb lies below the local tangent horizon, so 0.5 need not put the sun on the limb.

The solar disc, sky, clouds and scene lighting share the overridden direction. Clouds, terrain and atmospheric visibility can still obscure the sun. The game clock continues to follow the natural orbit. This retains the existing administrator sun override in the simulator. The override remains active until reset or client restart; <code>000COMMANDSUN-1</code> is the reset command. Invalid values leave the previous setting unchanged and write usage guidance to the client log.

'''000COMMANDALPHA0''' and '''000COMMANDALPHA1'''

Controls the alpha screen level (to simulate being in with 400m viz or out of the clouds with 42.16km viz)

'''<nowiki>000COMMANDGAMMA<strength></nowiki>''' or '''000COMMANDGAMMA-1'''

Administrator only. In the experimental plasma-envelope client, use a strength from 0 to 1, including decimals with a dot: for example, '''000COMMANDGAMMA0.5''' requests half target strength. The preview is visible through the windshield and external camera mounts. While the preview is active, its flow runs from nose to tail, fixed to the ship, at a constant animation rate independent of actual airspeed, orbital direction and wind. This flow override does not change the vehicle's velocity or attitude. Changing the strength changes brightness, not animation speed. GAMMA1 requests full target strength, GAMMA0 forces it off, and GAMMA-1 cancels the override and restores automatic brightness and the actual air-relative direction. Malformed or out-of-range values are ignored without changing the active override; no extra parameters are accepted. The preview is suppressed in the simulator and cleared on simulator entry; it is also unavailable in building/windowless interiors or while carried inside another vehicle. Clouds may obscure it.

The GAMMA value also sets the local radio-blackout fraction: 0 means no plasma-induced radio loss, 0.5 masks half the characters in ordinary radio-chat messages and halves scanner range, and 1 masks all message text and reduces scanner range to zero. Text loss is rounded down to whole characters and applies independently when transmitting and receiving; both ends of a link can impair a message. Your local sent-message history keeps the original typed text; the transmitted copy is garbled. This is a linear diagnostic scale, not an electron-density measurement or a prediction of a real radio-frequency cutoff. Direct/private messages, waypoint attachments and cockpit voice audio retain their existing behavior. GAMMA-1 restores the automatic radio-blackout calculation along with automatic glow and airflow. Simulator entry clears the override and blackout.

It does not establish a safe entry speed or temperature. Earlier clients use the cockpit-glass effect and require the ALPHA cloud overlay to be disabled to see that preview.

'''000COMMANDELMO0''' and '''000COMMANDELMO1'''

Controls the St. Elmo's Fire effect (must also have 000COMMANDALPHA enabled)

'''000COMMANDRAINXX'''

Overrides the the precipitation level locally. 2 to turn off, 16 is maximum, -1 to remove override.

'''000COMMANDBOLT'''

A bolt of lightning 50% intensity and between 0 km and 64 km distant (average of 16 km)

'''000COMMANDCLOUDBOLT1''' and '''000COMMANDCLOUDBOLT0'''

Administrator-only, client-local orbital lightning visibility test (updated client required). Enter <code>000COMMANDCLOUDBOLT1</code> to start or restart a 30-real-second test; <code>000COMMANDCLOUDBOLT0</code> stops it immediately. No spaces or additional parameters are needed.

The test starts two cloud-lightning events per second, with anchors within a 100 km surface radius beneath the moving ship. Each event can flash through up to three connected sections inside existing cloud moisture. The path stays fixed to the planet after spawning. Look down at the clouds, preferably at night or twilight. The client log reports whether the command started or why it was refused.

It requires real flight above the highest supported cloud layer (currently 22 km MSL), the volumetric cloud renderer and a loaded global weather map. It is disabled in the in-world simulator. Expiry, cancellation, simulator entry, renderer reset, missing weather, reconnect, or descent to the diagnostic altitude limit clears the test. Stalls skip missed events; the 30-second wall-clock deadline does not restart.

The diagnostic forces storm-strength events without changing the convection map, cloud shape or natural planetary event schedule. Empty cloud regions may skip events. It produces cloud illumination only: no exposed bolt, server event, thunder or damage. Natural lightning still depends on live convection; see [[Weather#Cloud lightning|Weather: Cloud lightning]].

'''000COMMANDRADIO'''

Temporarily toggles whether the current vehicle is equipped with a [[JVC Radio]]

'''000COMMANDNVG'''

Temporarily toggles whether the current vehicle is equipped with [[Night Vision Goggles]]

Rusty's Rentals

2026-10-22T19:28:58Z

reskin: /* Accessories */

[[Image:Rusty's.gif]]

'''Rusty's''' rents and sells [[:category:vehicles|vehicles]].

== Prices ==
Last updated: March 20, 2232
=== Vehicles ===
{| style="width:400px;" border=1 cellpadding=0 cellspacing=0
! [[:Category:Vehicles|Vehicles]]
! Daily Rate
! Sale Price
|-
| [[C-2]]
| 11 [[CR]]
| 7,258 [[CR]]
|-
| [[T-120]]
| 24 [[CR]]
| 15,574 [[CR]]
|-
| [[MuVER]]
| 42 [[CR]]
| 27,510 [[CR]]
|-
| [[A-4]]
| 182 [[CR]]
| 120,988 [[CR]]
|-
| [[W-6]]
| Unavailable
| 3,989,373 [[CR]]
|-
| [[E-10]]
| Unavailable
| Retired
|-
| [[E-11_Saint]]
| Unavailable
| 10,900,477 [[CR]]
|-
| [[P-13]]
| Unavailable
| 409,508 [[CR]]
|}

=== Accessories ===
*[[JVC Radio]]: 120 [[CR]] (available for all vehicle types)
*[[Remote_Assay|Remote Assay]]: 13,989 [[CR]] (available only in aircraft and aerospace vehicles)
*[[Weather_Radar|Weather Radar]]: 25,995 [[CR]] (available only in aircraft and aerospace vehicles)

We install these free of charge but you need to bring the target vehicle to our lot!

==Rental Return==
*To return your vehicle, please leave the vehicle in the confines of Rusty's lot.
*If you do not purchase fuel to fill the fuel tank you will be assessed a premium rate (15%) for fuel.

[[Category:Deois]]

Orbit

2026-10-22T18:49:07Z

reskin:

The '''Digital Orbital Resolver (DOR)''' is the spacecraft's orbital guidance and control system. Its '''Orbit MFD''' shows your current trajectory, the selected target's trajectory, and a proposed maneuver around [[Vieneo]]. Use it to change your orbit, rendezvous with a station or another spacecraft, or pass over a selected surface point. '''DOR executes the selected valid orbital plan'''; circularizing is one possible plan.

The full-page instrument is installed in the E-10, E-11, P-13, W-6, and EVA displays.

'''About the illustrations:''' These are labeled scenario renders from the implemented instrument's layout, orbital planner and guidance code, using synthetic example conditions. They are not screenshots of live flights. Each uses the native 420 × 320 layout enlarged for reading. Example times, fuel and delta-V are not a performance promise for your vehicle. Some dated illustrations use earlier labels (MIN ROUTE ALT, TO GO / USED and ATM PASS) and omit the live MECO estimate; the current readouts are described below.

'''Ground rendezvous:''' Select '''MODE RENDEZVOUS''' on the ground to plan and fly VTOL launch, ascent, parking-orbit insertion and transfer to an orbital station or spacecraft as one DOR mission. See [[#Ground-to-rendezvous mission|Ground-to-rendezvous mission]]. Standalone '''MODE PARKING ORBIT''' ends at the parking orbit. Ground-to-ground SURFACE PLAN remains planning-only.

'''Client versions and limits:''' Orbital adjustment, rendezvous and overflight have executable plans. [[#Surface journey planning|SURFACE PLAN]] remains planning-only for ground and low-atmospheric departures. The [[#Automated entry alpha|automated-entry alpha]] adds '''REENTRY''' execution from orbit to an atmospheric handoff, followed by altitude, heading and TAS hold. It does not fly the final descent or land. This requires the client with '''ENTRY READY'''; earlier calibration clients show '''REENTRY PLAN / PLAN ONLY''' and support manual REC capture only.

== Open and operate the page ==
The page is identified as '''DOR''' at the upper left. On the ground, the launch header shows '''SEARCH''' while comparing candidates and '''ARMED''' while DOR is awaiting comparison or departure. '''NO FIT''' or '''FUEL''' identifies an unavailable or fuel-short launch estimate. While executing, '''EXEC''' at the upper right and the active phase ('''ALIGN''', '''WAIT''', '''BURN''', '''COAST''' or '''ARRIVAL''') blink together: one second visible, one second hidden. Normal active phases are green; a separate red warning does not turn BURN or ARRIVAL red. The phase and its MECO estimate blink together. The DOR page identifier, other numerical readouts and atmospheric warnings stay steady. ESTIMATE, NO PLAN and completion/fault indications do not use this execution blink.

''Older orbital illustrations show ORB1 and DOR-prefixed phases. Static illustrations do not demonstrate the execution blink.''

Select the Orbit page on a supported vehicle's MFD. Choose the station, spacecraft or surface waypoint on your usual target-selection instrument; Orbit reads that selection. You do not enter a second waypoint on this page.

{| class="wikitable"
! Control !! Action
|-
| Shift + Up / Down || Select a row in the side controls. The highlighted row's actions appear along the bottom.
|-
| Shift + Left / Right || Change the highlighted option or decrease/increase its value.
|-
| Shift + C, with the eccentricity row selected || Request a circular orbit (e = 0).
|-
| Your configured DOR on/off control || Engage or disengage a valid executable plan. SURFACE PLAN stays planning-only. The automated-entry alpha can execute an ENTRY READY reentry; after handoff, the same control cancels its TAS hold.
|}
The controls require cockpit power and do not take these keys while text entry is active. Changing VIEW does not alter the plan or interrupt DOR. Changing a planning value does interrupt execution: review the new solution before engaging DOR again. Standalone PARKING ORBIT offers STEER AFCS / ORBIT as a live heading-source choice during the climb. Ground RENDEZVOUS selects its staging orbit and orbital steering automatically.

'''Administrator diagnostics:''' REC and automatic local CSV capture are available only to administrator accounts. Other accounts have no REC row and their DOR flights are not recorded automatically. Losing administrator permission ends an active capture without changing DOR guidance.

Selecting Orbit does not replace or acknowledge [[EICAS]] indications. With EICAS powered and serviceable, its gear, engine, trim and crew-alert indications remain independent of the MFD page. If these disappear only while ORB1 is selected, that is a rendering fault, not evidence that the underlying condition has cleared.

== Select an objective ==
{| class="wikitable"
! MODE !! Use
|-
| RENDEZVOUS || An orbiting station or free-flying vessel is selected. Reach its trailing staging point and match its velocity. On the ground, this includes launch, ascent and insertion followed automatically by the orbital transfer.
|-
| OVERFLY || A surface waypoint or grounded vessel is selected. Pass above that rotating ground point at the requested altitude and time.
|-
| SURFACE PLAN || A surface target is selected for a ground or low-atmospheric departure. Compare atmospheric, suborbital and orbital journeys using TRIP duration before departure and a PASS countdown afterwards. Planning only.
|-
| REENTRY || The surface-arrival objective for an orbital/high-altitude departure, including while docked at a station. Compare direct powered entry with coast-then-entry, ending upstream of the waypoint at the selected HANDOFF altitude and TAS. The automated-entry alpha can execute a qualifying ENTRY READY plan after undocking.
|-
| PARKING ORBIT || Before orbit is established, perform VTOL liftoff or take over an airborne climb to a selected circular parking orbit. Main-engine pitch guidance uses current mass and atmospheric conditions. This standalone mode ends at insertion; choose RENDEZVOUS before launch for the continuous trip to an orbital target.
|-
| ADJUST ORBIT || Change your own orbit independently of the selected target. Available through MODE once the current bound orbit has its periapsis above the surface, including when a target is selected. It is not offered on the ground.
|}
'''A newly selected surface target defaults to the surface-arrival objective.''' It is labeled SURFACE PLAN for a ground/low-atmospheric departure or REENTRY for an orbital/high-altitude departure. An entry keeps its identity through the atmospheric handoff rather than becoming a new ground-departure plan. Use MODE to choose OVERFLY for an orbital pass or ADJUST ORBIT to change your own orbit. An explicitly selected ADJUST ORBIT objective remains independent of the target.

With an orbital target selected on the ground, MODE offers RENDEZVOUS and PARKING ORBIT. Once established in a bound orbit with periapsis above the surface, it offers RENDEZVOUS and ADJUST ORBIT; PARKING ORBIT is no longer offered. Without a target, choose PARKING ORBIT before orbit is established, ADJUST ORBIT in orbit, or select a navigation target elsewhere. A docked or contained target is not treated as an independent free-flying spacecraft. An undocked spacecraft inside a station's control area remains a valid target. An atmospheric-flight target may still have a predicted trajectory, but it is marked with an atmospheric warning.

Rendezvous is more than matching orbital size and shape. Two spacecraft can have identical orbital parameters and remain far apart. Rendezvous also solves for position and velocity at the same future time, including the difference between their orbital planes.

== Read the picture and numbers ==
The graphic area stays the same size in every mode. In the ascent altitude/distance view, green is measured flight history and amber is the powered forecast (see [[#Ground and ascent|Ground and ascent]]). In orbital views, '''green''' is your current trajectory; '''cyan''' is the target; '''amber dashed''' lines show the proposed transfer. Dim amber shows the destination orbit, and gray dashed lines show a planned coast before departure. AP and PE mark apoapsis and periapsis. In orbital plans, numbered amber markers identify burns; T identifies the target's current position. Ground-departure surface previews instead number phase boundaries and mark the future arrival point B. REENTRY uses D for deorbit, E for the 100 km crossing and H for atmospheric handoff; the legend identifies them.

{| class="wikitable"
! VIEW !! What it helps you see
|-
| ORBIT || Your orbital plane viewed face-on: shape, apsides and transfer path.
|-
| PLANE 3D || Plane orientation, with Vieneo's equator and north axis as references. The NODE line indicates the intersection of the current and target orbital planes.
|-
| EDGE-ON || Your orbital plane viewed from its edge. Useful for seeing how far the target or transfer leaves that plane; it compresses the shape of your own orbit into a line.
|-
| TRACK || Latitude/longitude ground tracks, including Vieneo's rotation. Useful for a surface overflight. This is a schematic grid, not terrain imagery.
|}

{| class="wikitable"
! Readout !! Meaning
|-
| AP / PE || Highest / lowest altitude of the orbit above the spherical Vieneo reference surface, in km. A negative PE means the unpowered trajectory intersects that surface.
|-
| e || Eccentricity: 0 is circular; larger values produce a more elongated ellipse.
|-
| SIZE … km MSL || Orbit size expressed as altitude above mean sea level. For a circle, this is the orbit altitude; for an ellipse, it is (AP altitude + PE altitude) / 2, not the time-average altitude. The planner adds Vieneo's 2939.6 km reference radius internally.
|-
| i / PLANE DIF || Inclination to Vieneo's equator, or the angle between your plane and the target's plane, in degrees.
|-
| TP / nu || Orbital period in seconds / true anomaly in degrees, locating you around the current orbit relative to periapsis.
|-
| CURRENT > FINAL || Current AP/PE/e followed by the proposed final orbit after all burns. Older captures say CURRENT > PLAN. This is not the transfer minimum. CURRENT > REQUEST is an editable goal for which no valid plan exists yet.
|-
| PLAN MIN ALT || Lowest checked planned-route altitude in km MSL above the spherical reference surface. Includes any waiting coast, transfer and continuing final orbit; an OVERFLY circularization check also includes its arrival-response allowance. This is separate from final PE and from the actual unpowered coast.
|-
| B1 / B2 || Planned burn time and delta-V in m/s. The IDEAL line gives duration in seconds and fuel in kg for the main-engine maneuver; it does not include all attitude control, RCS trims or later corrections.
|-
| TOTAL / IDEAL FUEL || Total planned delta-V and ideal main-engine fuel. The calculation uses current vehicle mass and engine performance, with mass decreasing as fuel is consumed. Real execution can use more fuel for alignment, RCS, finite burns and corrections.
|-
| LEFT / ALL USED || During orbital DOR execution: the active guidance correction remaining, in m/s, and all fuel consumed since engagement, in kg. ALL USED includes the armed wait and ascent when starting from the ground, as well as alignment, both burns, coast and corrections; it is not a B1-only or B2-only measurement.
|-
| MECO ~mm:ss || Estimated time to cutoff of the current orbital burn, shown beside BURN or ARRIVAL. It follows measured convergence and throttle-down, not the original B1/B2 duration. It may increase after a correction. --- means no reliable recent convergence estimate. ALIGN, WAIT, COAST, continuous ascent and reentry do not show this timer. Cutoff is controlled by guidance, not by the countdown; another correction may subsequently fire.
|}

=== Minimum route altitude ===
Read '''PLAN MIN ALT''' directly below the graphic before engaging DOR. The graphic retains its size, and the OWN / TARGET / PLAN legend sits alongside the readout. It appears in every orbital view, including ascent detail when an orbital route is available. It uses the planner's checked arc minima, not the lowest vertex of the drawn curve.

* '''Red''' means the planned minimum is below 100 km MSL.
* '''Amber''' means the minimum is at least 100 km but the planned route has an atmospheric warning or is blocked by the clearance check.
* Neutral gray is an unflagged estimate, not flight clearance. '''---''' means no checked route minimum is available; it never substitutes the final PE or current-coast minimum.

'''CURRENT > FINAL''' distinguishes the destination AP/PE from this route minimum. A final PE of 118 km does not establish the approach's minimum altitude, and pressure warnings depend on air-relative speed as well as altitude. The pressure advisory threshold is 10 Pa; a 118 km orbit is not automatically atmospheric. Atmospheric and surface-planning policies remain those of the selected mode; this display change does not add a new restriction to RENDEZVOUS or ADJUST ORBIT. SURFACE PLAN keeps its separate phase legend and planning-only readouts.

During EXEC, '''PLAN MIN ALT''' continues to describe the committed instantaneous-burn plan. '''COAST MIN''' describes the current unpowered trajectory if no more burns occur; '''CORRECTION MIN''' describes the live powered-correction forecast. These are km MSL and need not agree: a planned minimum of 118 km can coexist with a negative COAST MIN while later burns are still needed. A negative value means the mathematical coast intersects Vieneo. These warnings remain separate from the green execution phase and any retained red abort reason. A fresh preview after an abort shows the new plan; the old abort reason remains available independently.

'''Finite-burn limitation:''' PLAN MIN ALT still describes the instantaneous-burn plan, not the live powered recovery. DOR checks a finite powered response separately, including alignment time rather than an unpowered coast for the entire correction. A negative current PE during a burn can therefore coexist with a viable recovery, while still warning what would happen if thrust stopped. A neutral planned minimum or final PE is not assurance that DOR can complete the whole maneuver. See [[#Powered correction clearance|Powered correction clearance]].

[[File:Orbit-MFD-rendezvous-min-route-alt-20261016.png|thumb|center|600px|'''Scenario 18: route minimum and final orbit.''' Fresh labeled render from the actual planner/display code. This synthetic rendezvous has a final PE and route minimum both at 118 km. With the 10 Pa advisory threshold, its route minimum is neutral gray; LONG BURN - ESTIMATE and the independent reversal caution remain visible. This is not a live flight, a reconstruction of player telemetry or a guarantee of execution.]]
<div style="clear:both"></div>

=== Orbital direction cautions ===
A steady amber caution beside the graphic's view title identifies the direction of the proposed plan. It remains visible during EXEC, including the hidden half of the execution blink, and does not replace atmospheric, fuel or finite-burn cautions.

* '''ORBIT REVERSAL''' means a departure or arrival burn changes the orbital angular-momentum direction by more than 90 degrees. It compares the directions before and after the burn; it is not based on which way the nose or thrust vector points. An ordinary backward braking burn that preserves orbital direction does not trigger it.
* '''RETROGRADE ORBIT''' means the transfer or final orbit runs against Vieneo's modeled rotation. A ship that already travels retrograde can keep that direction without an ORBIT REVERSAL. Polar motion alone is not classified as retrograde.
* '''RETROGRADE / REVERSAL''' shows both conditions. An intermediate retrograde transfer still warns even if the final orbit returns to prograde. The committed plan retains its caution during execution.

The OVERFLY automatic initial PASS search excludes plans that reverse orbital direction. Manual previews remain available with the caution. Direction caution alone does not block DOR, but the independent OVERFLY atmospheric-clearance requirements still apply. Blocked atmospheric previews retain their direction caution. If reversal was unintended, change the arrival/departure time or the overflight exit behavior and inspect the resulting plan before engaging DOR. A large delta-V can suggest reversal, but the warning is calculated from the trajectories rather than a speed threshold.

See the updated blocked-overfly illustration under [[#Overfly atmospheric clearance|Overfly atmospheric clearance]]. It replaces the older example that allowed the same low-periapsis route as a warning-only plan.
<div style="clear:both"></div>

== Ground and ascent ==
For a ground RENDEZVOUS or standalone PARKING ORBIT, the default ORBIT view shows '''ASCENT / ALTITUDE VS DISTANCE'''. The vertical axis is altitude in km MSL; the bottom axis is accumulated horizontal ground distance in km since departure. This is distance along the flown ground track, not range to the destination or slant distance. Taxi distance is excluded; a vertical VTOL climb remains at zero ground distance.

* '''PLAN EST''' (amber) is the estimated powered climb through insertion, using the ascent controller, current loaded mass, gear configuration, wind, atmosphere and engine limits. Computation runs in the background. '''COMPUTING PLAN...''' and '''PLAN UNAVAILABLE''' identify missing forecasts. It is an advisory estimate, with approximate aircraft response, fixed weather/configuration and no terrain or obstacle check.
* '''ACTUAL''' (green) is the measured flight history, with a diamond at the latest position. Samples are retained approximately every kilometre horizontally, or earlier after a kilometre of altitude change or five seconds, preserving slow and vertical flight. The display updates approximately once a second. Long histories are progressively coarsened while retaining the departure point.
* The departure plan stays fixed after liftoff so deviations remain visible. Changing the orbit/steering/target regenerates the remaining forecast from the current distance; '''FROM ... km''' identifies that starting point. The forecast may update on the pad as the launch recommendation or aircraft setup changes.
* History is collected for every pilot without REC, including manual departure. If observation starts airborne, '''DIST FROM PICKUP (km)''' identifies its origin. Landing, a vehicle/simulator change or a flight-state reset starts a new history. REC is separately restricted to administrators and writes diagnostic files.

The axes scale to fit both traces. The ascent profile remains available in the default ORBIT view through parking-orbit insertion, including above 100 km. Change VIEW to PLANE 3D, EDGE-ON or TRACK to inspect orbital geometry without cancelling the climb. At the RENDEZVOUS insertion handoff, the display changes to the transfer plan. The header says ASCENT / INSERTION during the initial leg.

With an orbital target selected on the surface, choose '''RENDEZVOUS''' for launch through arrival, or '''PARKING ORBIT''' to stop after insertion. ADJUST ORBIT replaces PARKING ORBIT once an orbit is established.

For a vacuum orbital objective such as ADJUST ORBIT, '''ASCENT PROFILE REQUIRED''' means that objective has no executable powered launch. Choose '''MODE RENDEZVOUS''' for a complete trip to an orbital target, or '''MODE PARKING ORBIT''' for a separate powered climb ending at a parking orbit. Older clients require manual ascent. Any ordinary vacuum transfer estimate starts from your measured position and velocity; it does not include lift or drag in that predicted path.

Outside an executable powered-ascent leg, the local ASCENT DETAIL / COAST view still shows the measured-state unpowered coast below 100 km. It returns to the selected orbital view at 100 km. This does not certify insertion: a periapsis intersecting Vieneo still indicates a suborbital trajectory. A descending vehicle is not automatically shown as ascending.

For '''SURFACE PLAN''', the default view shows a fitting estimated powered ascent as '''ASCENT / PLAN ONLY'''. A rejected candidate is labeled '''ASCENT / INVALID PREVIEW'''. Change VIEW to PLANE 3D, EDGE-ON or TRACK to inspect the entire journey before takeoff; changing VIEW does not change the selected trip timing. The local surface view rotates with the departure location, so a vertical climb is not mistaken for sideways travel caused by Vieneo's rotation.

There is no hard atmospheric boundary at 75 or 100 km. The planner's warning estimate uses the client's density model and air-relative speed. The 100 km ascent-view transition is a display rule. OVERFLY separately uses 100 km as a minimum clearance policy and also checks dynamic pressure; neither use defines a physical atmospheric boundary.

=== Ground-to-rendezvous mission ===
Use this procedure to fly from the surface to an orbital station such as TAC without selecting a new plan in orbit.

# Select TAC on the navigation/target instrument and choose '''MODE RENDEZVOUS''' on DOR. Initially MEET shows '''FASTEST (AUTO)''' while DOR finds its earliest accepted arrival estimate. You can then adjust the countdown for a later or earlier meeting. DOR uses a 200 km MSL intermediate parking orbit and selects the target's orbital direction automatically; there are no ORBIT or STEER setup rows in this mission. '''STAGING 200km MSL / AUTO''' reports this intermediate goal, which is not the station's altitude or an optimized choice among parking altitudes.
# Review '''FACE ... deg T''' for the intended launch direction. The target's current bearing and closing range are not the required insertion heading or launch time. If ATC requires a different departure route, leave DOR off and fly that route manually; engage the retained rendezvous mission when cleared to proceed toward the orbital direction. Standalone PARKING ORBIT retains the optional HDG/NAV steering selection.
# Compare the launch recommendation, '''INSERT IN''', '''ASC / XFER / TOTAL''' fuel and '''MEET -5m / +5m''' alternatives. During '''FINDING FASTEST RENDEZVOUS''' or '''COMPARING LAUNCH TIMES...''', numbers may describe a provisional candidate; '''CANDIDATE / NOT COMMITTED''' is not a launch countdown. MEET must leave time for both ascent and transfer. A station that is close and approaching can still have no fitting solution at the chosen MEET.
# Leave '''LAUNCH AUTO''' to wait for the recommended departure. When VTOL is ready and automatic departure is authorized, engage DOR. It can remain armed while the comparison finishes, showing '''ARMED / COMPARING LAUNCHES''' with zero thrust and no attitude command. When a completed, current, fuel-fitting solution is available, '''ARMED / LAUNCH WAIT''' and '''LIFTOFF IN''' show its committed countdown. At zero, DOR starts VTOL automatically. '''LAUNCH NOW''' evaluates immediate departure only; RENDEZVOUS still waits for that completed, fuel-fitting estimate before liftoff.
# Start approximately level on a clear VTOL area with sufficient loaded vertical-thrust authority. Stow flaps and spoilers, close bays and clear icing. DOR lifts to approximately 100 m AGL, builds airspeed, and controls pitch and thrust through ascent and insertion. '''Retract the landing gear yourself after liftoff.''' Monitor IAS/Vne, AFT, fuel and the flight path.
# At settled insertion, leave DOR engaged. '''AUTO TRANSFER AFTER INSERTION''' means it will solve the transfer from the achieved orbit and remaining fuel, keeping the original absolute MEET. If an immediate transfer does not fit, DOR can select a checked coast before the departure burn while keeping MEET unchanged. The display changes from ascent controls to the orbital plan and burn guidance. No MODE change, manual replan or second engagement is needed.
# Continue monitoring through alignment, departure burn, coast and arrival correction. Successful rendezvous ends at the normal roughly 5 km trailing staging point and hands over to '''TVM''' with zero selected closing speed. Obtain clearance and perform close approach/docking separately.

The ground comparison is an estimate, not a guarantee of the flown path, fuel use or completion exactly at MEET. Final settling can take additional time. If the achieved insertion state cannot support the transfer, DOR disconnects with a reason such as '''NO TRANSFER AT INSERTION''', '''TRANSFER FUEL SHORTFALL''' or '''MEET BURN TIME LIMIT'''. An expired MEET or invalid target also stops execution. Take control, review the condition and select a new plan when appropriate; DOR does not silently move MEET or declare rendezvous complete at the parking orbit.

=== Automated ascent alpha ===
'''MODE PARKING ORBIT''' provides a standalone powered climb ending at a circular parking orbit, including VTOL liftoff. The same ascent controller flies the first leg of a ground RENDEZVOUS mission. During atmospheric climb, DOR supplies heading and pitch targets to the ordinary AFCS HDG/PIT controllers and controls thrust. The FMA shows HDG and PIT on those axes. FPA remains available for pilot-selected flight. Select RENDEZVOUS before launch when the whole trip to an orbital target should continue automatically.

# Select '''MODE PARKING ORBIT''' on DOR when you want to stop at a parking orbit. Set '''ORBIT 200 km MSL''' for the first test; the range is 150–1000 km in 50 km steps.
# Use '''STEER AFCS''' to follow the selected HDG or NAV heading for an assigned departure. This chooses the source of the commanded heading, not whether control surfaces or RCS are used. DOR controls attitude and thrust while following that heading. The magenta orbital heading bug and the airborne '''ORBIT HDG … deg T''' readout show the desired orbital direction separately. Set the assigned heading or navigation route before engaging.
# Start approximately level on a clear VTOL departure area, with sufficient vertical-thrust authority for the current loaded weight. Flaps and spoilers must be stowed; icing and open bays are unsupported. A runway takeoff remains manual; PARKING ORBIT can also take over an airborne climb.
# In clients with the '''LAUNCH''' row, leave '''LAUNCH AUTO''' selected to arm the recommended departure: engage DOR to await the comparison and its recommended departure. While comparing it shows ARMED / COMPARING LAUNCHES with no thrust or attitude command. After accepting a completed, current, fuel-fitting estimate it shows '''ARMED / LAUNCH WAIT''' and '''LIFTOFF IN''' until departure, then starts VTOL automatically. Choose '''LAUNCH NOW''' for immediate departure instead. Earlier clients without this row launch immediately on engagement. VTOL first lifts approximately level to 100 m AGL, then transitions to a climb using lift and pitch to direct the main engines. '''Retract the gear yourself after liftoff.''' DOR does not operate it.
# When cleared to turn toward the orbital direction, change '''STEER''' to '''ORBIT'''. This is allowed during execution. No automatic turn is authorized merely by passing 17 km. AFCS may be selected again if needed; monitor the changed flight path.
# Monitor IAS/Vne, AFT, pitch, thrust, fuel and AP/PE. The controller uses current mass, measured aerodynamic forces and separate thrust limits. Pitch and wing lift are preferred for a supported climb, with vertical RCS retained for VTOL, insufficient lift and recovery. Small vertical-thruster corrections are reduced while lift is available and climb rate is tracking. Attitude RCS assistance fades as the available wing/control-surface lift reserve grows, and remains available for VTOL or insufficient aerodynamic authority. Atmospheric heading changes use banked AFCS HDG turns, not orbital flat yaw. DOR keeps HDG/PIT through at least 50 km MSL and until modeled dynamic pressure is at most 500 Pa; a descent to 45 km or pressure rising to 750 Pa restores aircraft steering. These are DOR transition settings, not an atmospheric boundary. If wing reserve runs low before the transition, pitch uses RCS assistance. Above 50 km, a bank limit below one degree shows '''HDG LIMITED / RCS PIT''' on DOR: pitch assistance remains, but significant banked heading changes are unavailable in that interval. The FMA retains HDG/PIT until the orbital handoff. Main thrust can use full available authority when required, but follows the requested airspeed and climb rate, so a partial setting can be normal. Near insertion, small corrections use '''INSERTION / LEVEL TRIM''': level pitch with small main/reverse and translation-RCS corrections. Larger corrections can still require a pitched thrust vector. The initial speed schedule leaves margin below Vne. A short-term forecast at 95% Vne or 200°C AFT removes positive main thrust and shows '''ASCENT LIMIT / IDLE'''; this is a controller margin, not a guarantee against disturbances.
# In standalone PARKING ORBIT, after parking-orbit insertion settles, DOR disconnects with the usual sound and shows '''INSERTION COMPLETE / REPLAN'''. Select RENDEZVOUS and inspect a new plan from the achieved orbit to reach the station. Switching from PARKING ORBIT to RENDEZVOUS preserves the selected absolute MEET deadline. If it is now too soon or has passed, change MEET and review the new plan. Standalone PARKING ORBIT does not automatically complete rendezvous or switch to TVM; ground RENDEZVOUS continues automatically as described above.

During execution, '''GUIDANCE ONLY / NO ETA / NO BUDGET''' means there is no continuously updated full-flight time or fuel guarantee; the ground comparison is an advisory forecast. USED records fuel actually consumed. In the altitude/distance view, the green line is measured flight history and the amber line is the advisory powered-climb forecast described above. The controller has no terrain/obstacle avoidance and does not forecast weather along the route. Ground-to-ground SURFACE PLAN remains a separate preview-only objective.

Changing ORBIT altitude, MEET, MODE or LAUNCH cancels execution. While DOR owns atmospheric HDG/PIT, using the lateral- or vertical-mode cycle key releases DOR and its autopilot engagement, then selects the next ordinary flight-director mode. Re-engage the aircraft autopilot deliberately if wanted. VIEW does not cancel it. STEER can be changed during the powered climb without cancelling it; changing STEER during an armed ground wait cancels that wait. Manual attitude or thrust input overrides powered ascent; invalid/stale required data, unsupported configuration or loss of authority can stop execution. Retain control of the flight after a disconnect.

For administrator accounts, DOR automatically records an executed ascent. A ground RENDEZVOUS keeps the same automatic recording through insertion and the orbital transfer; REC need not be switched on separately. Keep both matching CSV files from OrbitLogs, including ascent commands, the insertion handoff, steering selection and actual engine/RCS response. REC remains available for a continuous flight capture through manual flight and later maneuvers. Use the procedure below when recording a manual profile.

=== Compare launch times with MEET ===
MEET comparison is available in the ascent leg of ground RENDEZVOUS and in standalone PARKING ORBIT. Select an orbital station or spacecraft while parked. RENDEZVOUS sets its 200 km staging orbit and orbital steering automatically; standalone PARKING ORBIT additionally offers ORBIT and STEER controls. Use Shift + Up/Down to select MEET and Shift + Left/Right to change it in five-minute steps. MEET counts down to an absolute arrival deadline. Allow the '''COMPARING LAUNCH TIMES...''' indication to finish before comparing results.

A newly selected ground RENDEZVOUS searches for the earliest accepted MEET within six hours, prioritizing arrival time over fuel. It excludes atmospheric and orbit-reversing transfer estimates and checks modeled fuel and a finite burn-time allowance. FASTEST FOUND / ESTIMATE is the earliest accepted sampled solution, not a proof of the physically fastest possible flight. Long burns and final velocity matching can make actual completion substantially later than MEET.

Use the countdown for future appointments: for a meeting six hours from now, select 360:00 (minutes:seconds). Adjustments are in five-minute steps, within 30 seconds to six hours. Times are not capped at the most economical meeting; later times remain available even if their fuel cost rises again. An explicit edit keeps your chosen absolute MEET. Switching back into ground RENDEZVOUS starts a new automatic fastest search.

The comparison models a VTOL climb to the selected parking orbit and an orbital transfer from its predicted insertion state to the normal five-kilometre trailing rendezvous point. After you explicitly choose MEET, LAUNCH AUTO searches departure times for the lowest modeled total fuel at that meeting among the sampled candidates. LAUNCH NOW evaluates immediate departure only, including the neighboring MEET comparisons. This is a bounded estimate, not a proof of the globally best window or a guarantee of completing the flight at MEET. More time can save fuel, but orbital geometry means fuel need not decrease smoothly with every later deadline.

{| class="wikitable"
! Readout !! Meaning
|-
| SEARCH; CANDIDATE / NOT COMMITTED || The comparison is still running. Displayed fuel, heading and insertion figures are provisional. Engaging DOR can arm the wait for completion; it does not launch on these provisional figures.
|-
| ARMED / COMPARING LAUNCHES || DOR is armed with zero thrust and no attitude command while the comparison finishes. An accepted completed solution starts the committed launch countdown automatically. A completed comparison with no viable solution disconnects DOR with NO LAUNCH AT SELECTED MEET.
|-
| LAUNCH IN || Recommended remaining time before departure for the selected MEET. With LAUNCH AUTO, engaging DOR commits that departure time. A passed recommendation must be refreshed.
|-
| ARMED / LAUNCH WAIT; LIFTOFF IN || DOR is engaged on the ground and waiting for the committed departure. The countdown stays fixed rather than following newly optimized recommendations. Thrust remains at zero until departure. DOR off cancels it.
|-
| FACE ... deg T / AFCS or ORBIT || Initial true heading for that candidate. AFCS assumes the currently selected departure heading is retained throughout the modeled climb; it does not predict future NAV/ATC route turns. ORBIT follows the selected target's orbital direction. The target's current line-of-sight bearing is not the insertion heading.
|-
| INSERT IN || Estimated time from now to parking-orbit insertion, including the suggested ground wait.
|-
| ASC / XFER / TOTAL || Estimated fuel in kg: waiting plus powered ascent, the subsequent ideal orbital transfer, and their sum. A shortfall is shown separately. These figures are not all-inclusive fuel reserves.
|-
| MEET -5m / MEET +5m || Estimated fuel for deadlines five minutes earlier and later. The initial fastest result compares these at its selected departure; a manual-MEET search compares sampled departures for each deadline. Change the MEET row to select one of those deadlines and recompute its departure recommendation. NO FIT means no accepted candidate was found in that comparison, not proof that every possible trajectory is impossible.
|}

The comparison uses current loaded mass, available thrust, engine spool, airfoil curves, Vieneo rotation/gravity and the current measured atmospheric conditions with an altitude temperature/density model. It keeps the current landing-gear drag throughout the forecast and holds the chosen steering policy; retracting gear or changing steering alters the flown result. Changing weather, turbulence, clouds, terrain, detailed bank/elevator dynamics, attitude-RCS fuel and later rendezvous correction fuel are not included. The orbital transfer portion uses the existing instantaneous-burn estimate with a finite-burn time allowance. A ground RENDEZVOUS automatically solves that portion again from actual insertion state and fuel. Standalone PARKING ORBIT ends at insertion and requires selecting RENDEZVOUS separately.

A '''VTOL READY''' indication describes current ascent-controller readiness. It does not turn an unavailable or fuel-short MEET comparison into an approved whole-trip plan. The altitude/distance plot compares the modeled powered climb with measured flight history; a forecast is not a guarantee of the flown path. The ground comparison normally stops after liftoff. If manual departure occurs before the automatic MEET search finishes, DOR can estimate the remaining climb from the measured airborne state. Airborne ascent shows live pitch, thrust, target TAS/climb, IAS/AFT and fuel used.

=== Scheduled launch and airborne pickup ===
'''LAUNCH AUTO''' is the default. Select it with the normal Shift + arrow controls. With VTOL ready, engaging DOR during a pending comparison arms '''ARMED / COMPARING LAUNCHES'''. It issues no thrust or attitude command until a completed solution has been accepted and its launch countdown reaches zero. A completed estimate must have been checked against current inputs within 30 seconds, offer a future departure (or a current NOW recommendation), and fit the modeled fuel. '''NO LAUNCH AT SELECTED MEET''', '''REFRESH LAUNCH ESTIMATE''', '''LAUNCH TIME PASSED''' or '''LAUNCH FUEL SHORTFALL''' means DOR has not accepted the departure. Review the condition and re-engage after correcting it. '''LAUNCH NOW''' evaluates immediate departure when you choose the takeoff time yourself; ground RENDEZVOUS still requires the completed, fuel-fitting immediate-departure estimate. Standalone PARKING ORBIT NOW does not require a rendezvous estimate.

While armed, DOR commands no thrust or attitude change and does not operate the brakes. Remain parked on the clear departure area. Engagement authorizes automatic liftoff at the committed time; it does not obtain ATC clearance. If clearance is still pending, leave DOR off. DOR off or manual attitude/thrust input cancels the wait. Leaving the ground early also cancels it. Changes to the target/trajectory, steering, plan, power, vehicle/configuration, or material weather/performance inputs can cancel the wait rather than launch using an invalid forecast. Idle fuel use is accounted for. A missed timer requires rearming; DOR does not launch late automatically.

'''Manual ATC departure:''' select MODE RENDEZVOUS and MEET while still on the ground, leave DOR off, and take off manually. The pending ascent leg is retained for airborne pickup. Choose standalone MODE PARKING ORBIT instead if you want guidance only as far as a parking orbit. Once you want DOR to take over and ASCENT READY is shown, engage it. Airborne engagement immediately initializes guidance from your current position, velocity, attitude and loaded mass; LAUNCH AUTO does not make an airborne vehicle wait for the old ground time or repeat the ground liftoff. For RENDEZVOUS, engage only when cleared to follow the orbital direction. In standalone PARKING ORBIT, STEER AFCS can retain the assigned HDG/NAV departure until you select STEER ORBIT.

Pickup still needs valid current vehicle/air data and the supported configuration. Engagement is refused above 95% Vne, at 200°C AFT or hotter, or more than 50 km above the selected parking-orbit altitude. Those are controller eligibility limits, not proof that every accepted flight can recover. The ground timing/fuel forecast no longer describes a manually flown departure. A retained ground RENDEZVOUS continues automatically after insertion, using the achieved orbit and original absolute MEET; an infeasible transfer stops with a reason. Standalone PARKING ORBIT ends at insertion. For administrators, automatic mission recording includes the armed wait and launch countdown.

=== Recording an ascent ===
These recording controls require an administrator account.
In clients with '''REC ON (FLIGHT)''', administrators can use REC in every objective, including when '''ASCENT PROFILE REQUIRED''' is displayed. Recording observes the flight; it does not engage DOR, supply an automatic ascent pitch/throttle schedule or change ATC routing. A recording is calibration evidence, not an executable profile loaded into the ship.

# Before takeoff, select the intended station or spacecraft and open DOR. Select '''REC''' with Shift + Up/Down, then press Shift + Left/Right. With no proposed path, the row reads '''REC ON (FLIGHT)'''.
# Fly your normal comfortable ascent using manual controls or appropriate existing Autoflyte modes. Follow ATC headings/fixes and make your normal gear, flap, throttle and pitch changes. There is no required 15-degree or 60-degree test attitude.
# Leave REC on through the thin-atmosphere transition and orbital insertion, including any later DOR maneuver. Changing target, planning controls, VIEW or MFD page does not stop a FLIGHT recording. It remains flight-only even if a plan subsequently becomes available.
# Once established in the intended orbit, turn '''REC OFF'''. Keep both matching '''DOR-N.csv''' and '''DOR-N-plan.csv''' from '''OrbitLogs''' beside the running executable. Note the vehicle, starting load and any unusual weather or ATC interruption when returning the files.

The flight CSV records current mass/fuel, available and delivered thrust, actual pitch/roll/heading, angle of attack, air-relative flight-path angle, radial climb speed, tangential inertial and ground-relative speed, air-data freshness, IAS/TAS, dynamic pressure, AFT, configuration and Autoflyte modes. It distinguishes vehicle attitude from velocity direction. The companion file contains the capture origin and any available current/target trajectory context; '''it contains no invented reference ascent'''. Recording stops on REC OFF, loss of administrator permission, vehicle/simulator state reset, client exit, a file error or the size cap. Copy both files before further tests reuse their slot.

If a proposed path exists when REC starts, the row instead reads '''REC ON (REF)'''. That captures a frozen reference and follows the stop rules under [[#Recording a manual entry test|manual reference recording]]. REF recordings end when the target or planning controls change, or when DOR execution begins.

== Change or circularize your orbit ==
[[File:Orbit-MFD-adjust-size-msl-20261016.png|thumb|center|600px|'''Scenario 3: circularize using MSL altitude.''' With e = 0, the selected SIZE of 937.0 km MSL matches the final AP and PE. The nearly circular starting orbit needs only a small correction. Fresh labeled scenario render from the instrument code, not a live flight.]]
# Select '''MODE → ADJUST ORBIT'''.
# Choose '''LOCK NONE''', '''LOCK AP''' or '''LOCK PE'''. Locking an apsis preserves its selected radius while you change eccentricity. It does '''not''' mean “wait to burn at that apsis.”
# Change '''e'''. With LOCK NONE, also change '''SIZE'''. Shift+C on the e row requests a circle; without an apsis lock it uses the planned first-burn radius when available, otherwise your current radius.
# Choose the departure rule under '''START'''. Compare the green current orbit with the amber requested orbit, AP/PE, burn count, fuel and warnings.
# Engage DOR when satisfied with a valid plan, or use the plan as a reference for manual flying.

'''START NOW''' asks for a solution from your current position; you do not have to wait for apoapsis or periapsis. '''START AUTO''' compares a limited set of candidate departure times, including apsides for orbital adjustment, and chooses the lowest delta-V among valid candidates. It is not a search of every possible launch window. '''START AT TIME''' exposes an '''IN''' countdown that you can adjust.

If the requested orbit does not pass through the departure point, the planner may propose a transfer and a second burn to establish the new shape. A request that intersects the surface is rejected. SIZE changes in 100 km MSL-altitude steps, from 100 to 50,000 km MSL; e changes in 0.01 steps. For example, SIZE 600.0 km MSL with e = 0 requests a 600 km circular orbit. You do not add the planetary radius. With nonzero e, SIZE is the midpoint of the AP and PE altitudes, so check both endpoints and PLAN MIN ALT before execution.
<div style="clear:both"></div>

== Rendezvous with a station or spacecraft ==
For a surface departure, use [[#Ground-to-rendezvous mission|Ground-to-rendezvous mission]]. The steps below describe a rendezvous beginning in free flight, after the ascent leg is complete.

Orbital pressure advisories trigger above '''10 Pa'''. This operating tolerance applies consistently to current-coast, transfer, target and live DOR pressure checks, including OVERFLY's pressure criterion. [[YSP]] at 118 km produces approximately 6.3 Pa in the existing client density model, so its orbit alone no longer raises ATMOSPHERIC TARGET. The separate red below-100-km warning and OVERFLY minimum altitude still apply. Targets explicitly in atmospheric-flight reference mode still receive a target warning. Fuel, thrust, orbital-direction and finite-burn checks remain separate; this threshold change does not alter station fuel use or simulate heating.

[[File:Orbit-MFD-plane-20261015.png|thumb|center|600px|'''Scenario 4: a station in a different plane.''' PLANE DIF is about 38°. The cyan orbit and amber transfer leave the green orbital plane; the station does not need to be directly overhead.]]
# Select the target on the navigation/target instrument, then choose RENDEZVOUS here.
# Set '''MEET''' to the desired future arrival time. Each adjustment changes the requested interval by five minutes and establishes a new countdown. The adjustment uses the remaining time currently shown, with limits of 30 seconds to six hours.
# Compare START NOW, AUTO or AT TIME. If no clear transfer is found, change the arrival or departure time.
# Use PLANE 3D or EDGE-ON to inspect the plane change, and ORBIT to inspect the transfer shape. Review both burns and the fuel estimate.
# Engage DOR to execute the selected solution. Continue monitoring the target and warnings.

The planned meeting point is approximately '''5 km behind the target along its trajectory'''. It is a rendezvous staging point, not a docking port or a command to fly into the station's center. Stations follow their modeled motion. Another spacecraft is predicted to coast; if it maneuvers, the original prediction is no longer reliable.

After rendezvous, use the normal close-approach and docking procedures. The Orbit page does not obtain docking clearance or perform docking. [[TVM]] remains a separate target-relative velocity control.
<div style="clear:both"></div>

=== Planning inside a station control area ===
[[File:Orbit-MFD-bubble-20261016.png|thumb|center|600px|'''Scenario 11: undocked inside a station control area.''' The ORBIT phase and maneuver estimate remain available. This labeled scenario uses a reconstructed station-relative position and velocity.]]
Within a station's control area, a station-relative coordinate frame is used for smooth motion. Entering it does '''not''' mean the ship is docked. You can plan and execute orbital maneuvers while undocked inside it, and select another undocked spacecraft in a station control area as a rendezvous target. Entering or leaving the control area alone does not cancel DOR. Actual docking at a station permits planning but blocks DOR arming and execution. Previews use the ship's current position and velocity carried by the station. You can inspect RENDEZVOUS, ADJUST ORBIT, OVERFLY and SURFACE PLAN, including their time controls, while attached. Undock before engaging an executable orbital plan; undocking alone does not arm DOR. The selected deadline remains a countdown, so review the updated solution before engagement. Docking during execution cancels DOR.

Orbit reconstructs a ship's state from the station's modeled instantaneous motion plus the ship's measured relative motion. This avoids the jumping orbital elements caused by subtracting two rounded station positions to estimate velocity. It applies regardless of whether the selected target is a station, a spacecraft or a ground point; no display smoothing delays the values.
<div style="clear:both"></div>

=== Follow DOR through the burns ===
DOR follows the selected executable orbital plan. '''SURFACE PLAN cannot engage DOR''', even when a route says MODEL FIT. [[#Automated entry alpha|REENTRY in the automated-entry alpha]] has a separate powered-entry controller. During ALIGN and active burns of executable orbital plans, DOR steers pitch and yaw with rotational RCS, points the nose along the commanded burn direction for forward main-engine thrust, and rolls wings level relative to Vieneo's local horizon. The existing flight director receives burn pitch/heading targets and a level-roll reference; Orbit adds no separate attitude-command panel. In WAIT/COAST these remain guidance for the next burn, not a direction the ship must hold. Near a vertical burn, the horizon roll reference is ambiguous, so the controller preserves a stable roll orientation. DOR does not turn on the aircraft Autoflyte autopilot to do this.

<gallery widths="420" heights="354" mode="traditional">
File:Orbit-MFD-burn1-20261015.png|'''Scenario 5: departure, 30 seconds after engagement.''' DOR BURN; TO GO is about 487 m/s. The B1/B2 rows retain the planned burn budgets.
File:Orbit-MFD-coast-20261015.png|'''Scenario 6: the same transfer coasting.''' B1 is DONE. DOR COAST applies no translation thrust and prepares guidance for the next burn; TO GO now refers to that next correction.
File:Orbit-MFD-burn2-20261015.png|'''Scenario 7: arrival correction.''' DOR ARRIVAL has begun before the planned meeting time. Live TO GO differs from the original B2 estimate as guidance corrects the actual trajectory.
</gallery>

[[File:Orbit-MFD-dor-align-20261016.png|thumb|center|600px|'''Scenario 19: ALIGN before thrust.''' A fresh, labeled scenario render from the actual executor, attitude controller and instrument drawing code, not a live client screenshot. DOR is engaged, EXEC and ALIGN are in their visible blink phase, and translation commands are held off while the ship turns. START NOW does not bypass alignment.]]

'''ALIGN''' uses rotational RCS before allowing a burn. It captures within 2 degrees with total angular rate below 0.5 degree/second for at least half a second; more than 5 degrees of attitude error or 2 degrees/second of angular rate returns it to ALIGN. The commanded slew rate is limited to 5 degrees/second per body axis, with braking based on available torque. These are Rise control settings, not an Earth aircraft envelope. Small velocity trims below 2 m/s within the same burn phase retain the established nose direction instead of chasing a reversing near-zero vector; bounded translation controls handle those trims.

The controller uses the vehicle's existing RCS force caps, inertia, lever arms, current mass, installed augmentation-system health, wing damage, electrical power and wear. Rotational effort consumes fuel through the existing propulsion model. DOR can use installed rotational RCS independently of the manual augmentation toggle and its IAS fade. It does not teleport attitude or grant extra torque. Main-engine spool-down and translation-RCS filtering still take time; holding commands off is not an instantaneous removal of residual thrust. The main engines do the bulk orbital acceleration. While aligned, transverse RCS supplies a proportional correction to the thrust direction; small terminal trims retain their separate translation authority. IDEAL duration/fuel and ALL USED measure different things: the former is a main-engine estimate, while the latter includes the fuel actually consumed by all thrusters and idle operation since engagement.

'''WAIT and COAST allow free attitude control.''' You may turn the ship in pitch, yaw and roll to look around while DOR remains engaged and the route stays armed. DOR does not force an immediate return to the next burn direction. With the controls released, gentle rotational RCS follows the changing local horizon, lowering the nose as a forward-facing ship travels around Vieneo. It preserves your chosen attitude relative to that changing horizon rather than forcing the nose onto the flight path or restoring level roll. This uses measured motion and planet rotation, not an Earth orbit rate or an altitude cutoff.

When the executor requests a departure, correction or arrival burn, DOR switches to '''ALIGN''', reacquires the burn direction and level roll, and waits for pointing/rate capture before allowing translation thrust. WAIT/COAST alone never command translation thrust. START NOW or reaching a scheduled burn time does not bypass ALIGN. Looking away may therefore add alignment time before the next burn, and the clearance check can refuse that delay. During active burns, remaining delta-V is recalculated from the actual state; it need not decrease smoothly or equal the original burn budget. Completion requires the controller to settle near its goal, so finite burns can finish later than the initial estimate.

==== Rendezvous completion and TVM ====
After a successful '''RENDEZVOUS''', DOR automatically hands control to [[TVM]] with '''TVM SET 0.000 km/s''', keeping the same selected station or spacecraft. The page reports '''RENDEZVOUS COMPLETE / TVM''' and the normal Autoflyte disconnect sound plays once as DOR switches off. This happens when the final position and velocity correction settles, not simply when MEET reaches zero or B2 starts.

TVM commands a velocity match with the selected target; it does not hold the 5 km trail position or provide collision avoidance or automatic docking. Monitor separation and take control for the final docking approach. A manual DOR cancellation or an automatic abort does not engage TVM. ADJUST ORBIT and OVERFLY finish with their normal DOR disengagement.

==== Powered correction clearance ====
DOR rechecks each correction from the measured state using a finite powered forecast with Vieneo gravity and the same guidance retargeting law. It budgets alignment as unpowered coast, reserves engine spool and reverser response time, then credits bounded available thrust. Main-engine authority includes current mass, wear, engine health, power and the existing engine derating; small trims use the weaker translation limit. WAIT and COAST receive no hypothetical thrust credit.

The powered-correction check retains surface clearance for RENDEZVOUS and ADJUST ORBIT and the stricter '''100 km / 10 Pa''' requirements for OVERFLY. OVERFLY still checks the remaining approach and continuing orbit and reduces optional position-closing commands that would spoil clearance.

The forecast is a bounded two-body estimate with constant mass and ideal steering after alignment. It is not a complete actuator, drag, lift, terrain or heating simulation. DOR rechecks when actual measurements change; unavailable authority, inadequate alignment time, or an unsafe powered response can still disconnect it. This vacuum correction forecast applies to the orbital leg. Powered launch/ascent and REENTRY use their separate controllers; final descent and landing remain manual.

[[File:Orbit-MFD-dor-powered-recovery-msl-20261016.png|thumb|center|600px|'''Scenario 20: powered recovery remains engaged.''' Fresh labeled render from the actual planner, executor and drawing code. ADJUST ORBIT requests a 500 km circle from a slow suborbital state; the unrelated selected station is not the objective. The negative current PE and red ATM PASS warning describe the unpowered coast. The powered correction passes its separate check. An independent finite-thrust regression with ideal steering and engine spool completes above 419.3 km, despite repeated rejection by the old coast-only guard. Synthetic example, not a live flight or reconstructed player telemetry.]]

If no qualifying correction exists, DOR clears its thrust and attitude commands, disconnects with the existing sound, and retains a reason such as '''DOR: NO CLEAR CORRECTION''', '''DOR: CORRECTION MARGIN LOST''', '''DOR: FINAL ORBIT UNSAFE''' or '''DOR: COAST CLEARANCE LOST'''. A delayed departure can report '''DOR: DEPARTURE COAST UNSAFE'''. Alignment checks the measured unpowered path for the estimated turning time and engine response, followed by the powered correction: '''DOR: ALIGN MARGIN LOST''' means it cannot safely spend that time turning. OVERFLY retains its atmospheric-clearance requirement; other orbital objectives retain their existing surface-clearance checks and atmospheric cautions. '''DOR: NO ATTITUDE CONTROL''' means the attitude data or required rotational authority is unavailable. '''Disconnecting does not recover an unsafe trajectory.''' Inspect your actual PE and warnings, then take over or select a different valid recovery plan.

Use DOR off to take over. Manual thrust-increase/decrease key commands also disengage it. Pitch/yaw/roll inputs in WAIT or COAST leave DOR engaged. During ALIGN or either active burn (BURN or ARRIVAL), a pitch, yaw or roll key command disconnects DOR immediately; joystick pitch, roll or yaw input outside the configured dead zone also disconnects it. Those disconnects use the existing Autoflyte disconnect sound. Stale guidance, invalid control data and Flight Freeze suppress rotational commands. Normal control resumes through the existing manual controls after disconnect. Changing planning values, losing/changing a rendezvous target, losing cockpit power, docking/landing, or changing/resetting the vehicle's flight state cancels execution. After a cancellation, inspect the reason and solve again before re-engaging. VIEW changes alone are safe to make during execution.

Every transition from DOR on to off plays the existing Autoflyte disconnect sound once. This includes normal plan completion, automatic aborts, manual takeover, switching to [[TVM]], and a disconnect caused by loss of cockpit power. Completion and abort messages remain visible so you can inspect the reason. Remaining off does not repeat the sound, and restoring power does not replay it; engaging DOR again re-arms the next disconnect. This behavior follows DOR engagement, without an altitude or airspeed cutoff, and also applies in the simulator.

== Pass over a ground point ==
[[File:Orbit-MFD-overfly-20261015.png|thumb|center|600px|'''Scenario 8: overfly.''' A surface point is selected, with a 900 km pass in 40 minutes and EXIT COAST. The ground track accounts for Vieneo rotating beneath the flight path.]]
# Select a surface waypoint, then choose '''OVERFLY'''.
# Set '''ALT''' above the spherical reference surface, in 100 km steps, and '''PASS''' time, in five-minute steps.
# Select '''EXIT COAST''' to continue on the transfer orbit after the crossing, or '''EXIT CIRCULARIZE''' to establish a circular orbit after passing the waypoint.
# Set START, inspect the ground track and orbit views, and review the burn estimates before using DOR.

On entering OVERFLY, the planner searches for an early viable PASS time using the selected ALT, EXIT and START settings. It checks the route and continuing orbit against the OVERFLY clearance requirements below, available fuel and the preview's burn-duration limits. Automatic PASS suggestions also exclude orbital reversals. It searches up to six hours ahead in 30-second intervals, refines the first viable interval to one second, and adds up to 30 seconds of headroom when that later candidate also passes the checks. This is a useful starting estimate, not a guaranteed global minimum or a guarantee of flight performance. Very narrow windows can be missed. It does not minimize fuel.

While searching, '''FINDING PASS TIME''' replaces the plan and DOR cannot engage it. '''NO VIABLE PASS IN 6H''' means no candidate met these criteria in the bounded search; it does not prove that no possible route exists. Change ALT, EXIT or START, or choose a manual PASS time to inspect other estimates. Weather at the selected point is not an input to the transfer solver.

The initial countdown stays fixed once selected. Until you edit PASS directly, changes to ALT, EXIT or START/IN request a new suggestion. After a direct PASS edit, your chosen deadline is retained, including an invalid or warning-producing one; the planner does not silently move it back into a valid window. Decrease or increase the displayed remaining time in five-minute steps (30 seconds to six hours). To request another automatic starting estimate, leave OVERFLY and select it again. VIEW changes do not restart the search. Automatic suggestions never change an executing DOR plan; manually changing planning values still cancels execution.

''The older illustration above demonstrates the layout, not automatic PASS initialization. The clearance illustration below is a labeled code-generated scenario, not a live-flight capture.''

'''Why a low pass may have no clear transfer:''' Reaching 200 km above the point is not enough if the approach dips into the atmosphere or the continuing orbit returns there. EXIT COAST requires the full continuing orbit to remain bound and clear. EXIT CIRCULARIZE adds an arrival burn, but cannot make an earlier atmospheric dip acceptable. Changing PASS, ALT or EXIT may produce a valid route. Manual PASS retains your requested deadline and may display a blocked trajectory; it cannot override OVERFLY atmospheric clearance. Long-burn estimates can still be inspected manually.

Overfly meets a moving ground location at a chosen time; it does not hover above it. A circularization burn belongs after the crossing and can change where the spacecraft travels afterward. The pass altitude is not clearance above local terrain.
<div style="clear:both"></div>

=== Overfly atmospheric clearance ===
OVERFLY checks the waiting coast, approach to the waypoint and continuing orbit. Each must stay at or above '''100 km MSL''' and have a conservative dynamic-pressure bound of '''10 Pa or less'''. EXIT CIRCULARIZE also checks the unbraked arrival path over an estimated response interval before crediting the final circular orbit. A clear later circle does not excuse an earlier low pass. The solver prefers a qualifying transfer over a cheaper atmospheric alternative.

The pressure estimate uses the client's 3.063 kg/m³ surface density, 7.5 km scale height and a conservative bound on air-relative speed at the lowest point of the checked arc. At orbital speed, this can require clearance higher than 100 km. These are operational planning checks, not a validated heating envelope, drag-integrated trajectory or guarantee of finite-burn performance. Vieneo's nitrogen/sulfur-dioxide/oxygen atmosphere is retained; no Earth heating coefficients or new atmospheric boundary are introduced. The published [[Vieneo]] scale height is 7.5 km, matching the client and server models.

Steady red '''PLAN MIN''', '''COAST MIN''' or '''CORRECTION MIN''' identifies which trajectory falls below 100 km, with its minimum altitude in km MSL. '''EXEC PATH <100km''' identifies another low path checked by the executor. These can warn while your present altitude is much higher. The current-coast indication clears at 105 km to prevent flicker; its displayed number remains the actual predicted minimum during that hysteresis interval. This does not relax the solver's 100 km limit. Ground/reset state clears stale orbital warnings. Pressure advisories such as '''COAST ATM q>10Pa''' stay amber when there is no low-altitude warning. Warnings remain visible during both EXEC blink phases and after an abort.

A blocked preview shows '''NO PLAN''', '''ATM PASS - NO PLAN''' and '''MIN … km / BLOCKED''' where a rejected trajectory is available. DOR cannot engage that preview. Atmospheric penetration remains possible to display for other orbital objectives, and the atmospheric stages of SURFACE PLAN remain planning-only; this OVERFLY restriction is not a blanket exclusion of atmospheric flight or reentry.

Cockpit '''Q''' is forward dynamic pressure in lb/ft²: Q = 2 is about 96 Pa, not 2 Pa. It is not a direct temperature or burn-up indication, and the planner's conservative arc-pressure bound is not the same as that instantaneous cockpit component.

[[File:Orbit-MFD-overfly-clearance-blocked-20261016.png|thumb|center|600px|'''Scenario 17: atmospheric overfly blocked.''' Fresh labeled render from the actual planner and instrument code. A synthetic 905 km orbit requests a 200 km COAST pass in 180 minutes, but the candidate falls to 65.3 km. The red MIN ROUTE ALT 65.3km MSL, atmospheric warning and NO PLAN identify the rejection before engagement; the independent retrograde/reversal caution remains visible. This is not a live client screenshot or a reconstruction of player telemetry.]]
<div style="clear:both"></div>

== Surface journey planning ==
For a ground or low-atmospheric departure, select point B on the normal target instrument. On this page choose MODE '''SURFACE PLAN''', then ROUTE and TRIP while on the ground, or PASS when already airborne. For a departure from orbit or an orbital station, use the [[#Reentry and atmospheric entry|REENTRY]] controls below instead. Docking prevents execution, not planning. SURFACE PLAN remains planning-only after undocking; a qualifying REENTRY plan in the automated-entry alpha can be executed.

'''Local trips:''' SURFACE PLAN shows '''NO PLAN / TOO SHORT''' when the departure and destination are less than 5 km apart, including their height difference. It does not generate a climb path, fuel estimate or initial time search for these trips. A coincident destination on the ground shows '''ALREADY AT B'''. Fly the local hop using ordinary flight controls or suitable Autoflyte modes; changing TRIP/PASS or forcing ATM, SUB or ORB does not create a local takeoff/hover/landing profile. This is a limit of the surface planner, not a vehicle flight limit. Orbital REENTRY and an entry already in progress are exempt.

{| class="wikitable"
! ROUTE !! Proposed profile
|-
| AUTO || Compare the three route families at the selected TRIP duration or PASS deadline. Choose the lowest estimated fuel among candidates that pass the simplified model checks. AUTO may choose a different family when the selected time changes.
|-
| ATM || A powered atmospheric profile, climbing to 20 km MSL, traversing toward B, then descending. Only offered for departures at or below 40 km in this initial model. It is not a simulation of wing-borne cruise.
|-
| SUB || Powered climb and boost, a ballistic coast with a surface-intersecting osculating orbit, then powered braking and descent. The coast ends before the intersection.
|-
| ORB || Powered climb and boost, a circular coast nominally at 400 km MSL, then powered braking and descent. This need not complete a revolution.
|}

'''TRIP is the requested travel duration before departure.''' While on the ground with REC off, it stays steady: TRIP 30:00 means a 30-minute journey starting when you depart. Waiting on the ground does not consume that allowance or make the same route require more thrust and fuel. At liftoff the deadline is fixed and the row becomes '''PASS''', counting down to arrival. For administrators, starting '''REC''' also fixes the reference at capture start, even if you are still on the ground; it must not slide forward during a calibration recording. Ending REC while still grounded restores the selected TRIP duration. Landing with REC off also restores duration planning. An already-airborne surface preview uses PASS from the time it is selected.

Adjust TRIP/PASS in five-minute steps using the value shown (30 seconds to six hours). This is a timing constraint, not an AUTO preference switch. The comparison shows each family's estimated fuel and MODEL FIT, THRUST LIMIT, FUEL LIMIT, IAS LIMIT or another reason. A forced ATM/SUB/ORB choice is retained even when invalid; AUTO does not silently replace it. If nothing fits, AUTO can display a rejected candidate for inspection. The upper-right header says '''INVALID''' in red; '''PLAN ONLY''' is reserved for a fitting preview, and '''NO PLAN''' means no candidate is available. The rejected path and estimates remain visible to help you adjust the timing; they are not achievable flight commands. Longer times are not guaranteed to help: gravity support consumes fuel and the search covers only a limited family of profiles.

On first selecting this objective, the module searches for an initial model-fitting trip time up to six hours: two-minute trial spacing, ten-second refinement of the first fitting bracket, and up to 30 seconds of headroom if that candidate also fits. FINDING TRIP TIME identifies the grounded search; NO FITTING TRIP IN 6H means this bounded search found none, not that every possible trajectory is impossible. Airborne previews use FINDING INITIAL PASS / NO FITTING PASS IN 6H. A manual edit keeps your chosen duration or deadline, including an invalid one. Changing ROUTE requests a new suggestion only before the time has been edited manually. Leaving and reselecting SURFACE PLAN restarts automatic initialization. The search never rewrites an executing orbital plan.

The amber path joins the measured initial state to B's position at PASS, accounting for Vieneo's rotation. PLANE 3D and TRACK can show the whole journey even before takeoff. For space profiles, markers 1–4 indicate the end of climb, start of coast, start of braking and start of descent/entry; B is the future destination. These are preview phase boundaries, not flight-director commands. ATM has only its final B marker. The top flight-phase label describes your current state, independently of the proposed route.

{| class="wikitable"
! Surface readout !! Meaning
|-
| RANGE || Current great-circle distance to B, in km; not full path length. Below 10 km, one decimal place is shown (for example, 0.5 km).
|-
| TOP || Highest sampled profile altitude, km MSL above the spherical reference surface.
|-
| TOTAL || Integrated powered acceleration, expressed as delta-V in m/s, including gravity support and modeled body drag. This can greatly exceed the vehicle's speed; it is not a cruise-speed command.
|-
| FUEL || Estimated kg for the selected ideal profile, including idle flow during coasts.
|-
| THRUST || Peak fraction of available main-engine thrust. More than 100% is shown in red and invalidates the candidate. If IAS also exceeds its limit, the reason reads IAS / THRUST LIMIT so neither failure is hidden.
|-
| MAX q || Highest sampled dynamic pressure in kPa, based on mass density and air-relative speed. It is informational, not a validated heating or structural limit.
|}

'''MODEL FIT is not flight clearance.''' The preview uses Vieneo gravity and rotation, the client's 3.063 kg/m³ surface density and 7.5 km density scale height, vehicle main thrust, altitude efficiency, fuel flow, wear and empirical body drag. The published [[Vieneo]] scale height matches the 7.5 km used by both client and server. Cruise at 20 km, the 100 km powered-segment interface and nominal 400 km orbital coast are planning choices, not atmospheric boundaries.

These ground-departure powered segments assume ideal thrust direction. They do not simulate RCS-axis limits, vehicle attitude changes, spool response, wing lift, wing/tail/wave drag, wind, clouds, weather avoidance, heating or terrain. ATM supports weight with thrust, so its fuel estimate is not a prediction of ordinary wing-borne Autoflyte cruise. Sampled geometry checks a reference sphere; it does not establish terrain clearance or that point B is a suitable landing site. Fuel comparisons and AUTO's choice are therefore comparisons within this simplified model, not a global optimum or a recommendation to fly the displayed path. Direction reversals remain visibly cautioned.

'''PLAN ONLY / ATM HANDOFF''' means the atmospheric stages require separate pilot/Autoflyte operation. SURFACE PLAN provides no automatic mode handoff, takeoff, atmospheric guidance, hover or landing. Orbital REENTRY has its own alpha controller described below. The end-state is an ideal planning endpoint at B, not a landing command. Pressing DOR on a surface preview leaves execution off and plays the Autoflyte disconnect cavalry sound once to acknowledge the refusal. Holding the key does not repeat the sound. Existing executable ADJUST ORBIT, RENDEZVOUS and OVERFLY plans remain separate.

The dated scenario illustrations below use the earlier PASS label before takeoff; current ground previews display TRIP.

<gallery widths="420" heights="354" mode="traditional">
File:Orbit-MFD-surface-atm-20261016.png|'''Scenario 13: ATM, 500 km in 60 minutes.''' Local ascent preview and route comparison. The large TOTAL includes ideal powered gravity support. Labeled synthetic render, not a live flight.
File:Orbit-MFD-surface-sub-20261016.png|'''Scenario 14: SUB at the same PASS.''' Whole-route PLANE 3D view while still on the ground, with ballistic coast and numbered phase boundaries. Labeled synthetic render.
File:Orbit-MFD-surface-auto-20261016.png|'''Scenario 15: AUTO, 4000 km in 90 minutes.''' ORB fits the simplified model while ATM and SUB exceed thrust. This demonstrates the PASS constraint, not certified flight performance. Labeled synthetic render.
</gallery>

== Reentry and atmospheric entry ==
Select the intended surface waypoint on the usual navigation instrument. For an orbital departure, choose '''REENTRY'''. Planning is available while docked; undock before engaging DOR. The automated-entry alpha can fly an '''ENTRY READY''' profile from at least 100 km MSL to its atmospheric handoff. It requires current air data, main/reverse and translation thrust, and a clean configuration: gear, flaps and spoilers retracted, bay closed and no significant icing. A plan lacking those inputs, or newly planned below 100 km, remains '''PLAN ONLY'''. Earlier calibration clients label this mode REENTRY PLAN and cannot execute it.

The initial handoff is '''30 km MSL''' at '''0.5 km/s TAS''', upstream of the selected surface point. These are adjustable test conditions, not universal safe limits. The handoff is level flight aimed toward the surface point; it is not touchdown. '''HANDOFF''' counts down to that atmospheric transition, not touchdown at the waypoint. The planner estimates the remaining glide reach using the vehicle's clean-air aerodynamic data. FINAL HOLD retains that general-purpose handoff. The arrival-planning alpha also offers runway/hover previews described below. None establishes obstacle clearance or an achievable unpowered glide all the way to B.

{| class="wikitable"
! Control !! Meaning
|-
| ROUTE AUTO || Compare direct powered entry and coast-then-entry at the selected handoff time. Among model-fitting candidates, choose the lower estimated fuel requirement. This is a bounded search, not a global optimum.
|-
| ROUTE ORB || Remain on the measured current orbit for a selected coast, then enter. The preview does not first force the ship into a nominal 400 km orbit.
|-
| ROUTE SUB || Begin a direct powered entry after allowing time to align, without a discretionary orbital coast. Its feasibility depends on the requested time, position, velocity, weight and available thrust.
|-
| H ALT || Atmospheric handoff altitude, km MSL. Adjust in 5 km steps, from 15 to 60 km.
|-
| H TAS || Air-relative handoff speed, km/s. Adjust in 0.1 km/s steps, from 0.1 to 1.5 km/s. This is not IAS or orbital speed.
|-
| HANDOFF || Requested remaining time, adjusted in five-minute steps. A shorter time may require greater powered acceleration or braking, or have no fitting candidate.
|-
| REC || Administrator-only: record a manual test and the selected reference plan without engaging DOR. See below.
|}

ATM remains an atmospheric-departure option in SURFACE PLAN. It is not offered as an orbital entry shortcut. Ground/low-atmospheric SURFACE PLAN retains its separate AUTO / ATM / SUB / ORB route families and TRIP/PASS arrival at B; the new entry controls describe an atmospheric handoff before B.

'''D''' marks deorbit/start of the powered profile, '''E''' the sampled crossing of 100 km, and '''H''' the atmospheric handoff. The 100 km marker is an operating reference, not a hard atmosphere boundary. Gray is the planned coast on the current orbit; amber is the proposed powered entry. The graphic area remains the same size in every view.

'''REV''' and '''RCS''' show peak required fractions of the corresponding available thrust. The entry model uses current loaded mass, fuel consumption, main-engine condition, separate forward/reverse and up/down/side limits, engine response, Vieneo gravity/rotation/density, and the client's clean wing/tail/body and Mach-dependent aerodynamic model. It estimates AFT from the client's heat-transfer model. '''MAX q''' is the modeled effective aerodynamic pressure in kPa, including the client's Mach augmentation; it is distinct from ambient-density dynamic pressure. Cockpit Q is in lb/ft². '''LOAD''' is estimated non-gravitational acceleration in standard Earth g units.

The alpha's preview reports peak IAS as a percentage of Vne and peak predicted AFT. It requires at most '''95% of Vne''', '''200°C predicted AFT''' and '''95% of each available thrust axis''', plus its engine-response and attitude-rate checks. These are controller settings for validation, not newly established vehicle limits. AFT forecasting uses Vieneo's model and the current measured temperature/wind; it does not forecast changing weather, clouds or turbulence along the route. '''ALPHA / NO TERRAIN CHECK''' remains a limitation: the profile has no terrain or obstacle database and no automated final-descent or landing controller. Keep [[Atmospheric_Reentry|entry procedures]], AFT, IAS/Vne and flight path in view.

'''Entry readiness and configuration:''' A route can fit the fuel, thrust and temperature limits while the ship is not ready to execute it. '''PLAN ONLY''' with an amber '''CONFIG LANDING GEAR''', '''CONFIG FLAPS''', '''CONFIG SPOILERS''', '''CONFIG AIRFRAME ICE''' or '''CONFIG CARGO BAY''' identifies the configuration that must be corrected. Air, thermal or performance data problems have their own messages. Retract gear, flaps and spoilers fully, close the bay and clear icing before entry. Landing gear must also have confirmed status: a GEAR DISAGREE condition or unknown gear status prevents entry even if the gear appears retracted. The DOR page continues to show CONFIG LANDING GEAR. '''READY / ENTRY READY''' and '''ARM DOR TO EXECUTE''' indicate that the entry readiness checks pass; selecting AUTO does not engage DOR.

If gear prevents engagement, DOR remains off, announces its disconnect sound and queues '''"Config. Landing gear."''' The refusal is also shown in red. Extending gear or losing confirmed gear status during an executing entry invalidates the clean profile and disconnects DOR, releasing its attitude and thrust commands with the same specific alert. '''Take control after a disconnect; DOR does not retract gear or automatically re-engage.''' A new entry still requires an origin at or above 100 km MSL. The queued gear phrase is discarded if the gear is confirmed fully retracted, power is lost, or the relevant vehicle/plan changes before playback. Normal gear use after the achieved atmospheric handoff does not trigger this entry-specific warning; the ordinary aircraft-mode limits still apply.
=== Automated entry alpha ===
# Start with a clean ship in orbit and select the surface destination. Use AUTO, H ALT 30 km and H TAS 0.5 km/s for the initial test.
# Adjust HANDOFF until the preview says '''ENTRY READY'''. Shortening it asks for a faster journey; '''IAS RESERVE''', '''AFT RESERVE''', '''THRUST RESERVE''', '''ATTITUDE RATE''' or '''SPOOL LIMIT''' identifies why a candidate is rejected. A longer time is not guaranteed to fit every geometry. Check fuel and the whole proposed path.
# Undock if necessary, then engage DOR. AUTO selects a route; it does not engage DOR by itself. For administrators, an accepted entry starts a CSV capture automatically, so REC is not required for this test. Other accounts fly the same entry without diagnostic recording.
# During coast DOR pre-aligns for entry. During '''POWERED ENTRY''' it keeps the nose into the air-relative direction of travel with a small positive angle of attack, using forward or reverse mains and bounded translation RCS. Braking does not require pointing the tail into the airflow. Manual attitude input during ALIGN or powered entry disconnects DOR.
# '''ENTRY LIMIT / BRAKING''' means the short-term forecast predicts excessive IAS or AFT. DOR gives braking and descent control priority over the requested time; HANDOFF may be missed. This is active protection, not a guarantee against every disturbance or an instruction to ignore warnings.
# At the achieved handoff, expect the ordinary DOR disconnect sound once. FINAL HOLD transfers to ALT/HDG/TAS hold; a valid runway FINAL selection transfers to ALT/NAV/TAS hold on the inbound course. The autopilot holds the selected MSL altitude and the entry autothrottle holds the selected TAS. It does not descend toward or land at B. HANDOFF PASSED alone is not completion: altitude, airspeed, descent rate, position and attitude must also converge.
# To resume normal flight, cancel the entry TAS hold with the DOR control or by moving a physical throttle lever. The altitude and heading holds remain until changed or disconnected. Disconnecting the aircraft autopilot also ends the TAS hold. In the arrival/FPA alpha, TAS hold continues with HDG, NAV or LOC and PIT, VS, ALTm, ALTa, FPA or G/S. Selecting SpeedPitch, Roll, an off mode or TVM ends it. Ordinary gear/flap/spoiler changes after handoff retain TAS hold with updated drag compensation; icing, an open bay, unavailable/stale air data or lost authority still cancel it. Change H TAS on the DOR page to adjust the held speed. Take over for ATC routing, descent and approach; a fixed TAS can produce increasing IAS as you descend, so reduce it appropriately.

For administrators, automatic recording continues through the handoff holds until they are cancelled. Retain both matching CSV files for review of the actual response, predicted heat/IAS, force commands, available thrust and handoff modes. Start testing with a comfortable preview, then shorten the requested time on subsequent flights; the alpha is not a certified fastest possible entry.

=== Arrival planning and final approach ===
These controls require the arrival/FPA alpha, which is newer than the ascent-recording alpha. They are available on REENTRY, not on ground-departure SURFACE PLAN. Choose '''FINAL''' with the usual Shift + arrow controls before engaging DOR. A new surface target resets FINAL to HOLD; selecting a destination does not silently authorize an approach or landing.

{| class="wikitable"
! FINAL !! Preview and handoff
|-
| HOLD || The default: atmospheric entry followed by ALT/HDG/TAS hold.
|-
| ILS (PLAN) || Select a live, fully serviceable runway ILS or an outer-marker/LOM waypoint with one unambiguous associated inbound runway. The preview uses the marker's distance when available, otherwise the selected final distance (initially 10 km). Its final gate is 50 m below the nominal 3° beam for an eventual level intercept. The displayed ≤30° intercept is a planning objective for the manual final, not an automatically enforced capture condition.
|-
| VISUAL (PLAN) || Select a runway threshold with a published inbound heading. A second FINAL row adjusts the extended-centerline distance from 6 to 30 km in 2 km steps; the initial value is 10 km. The gate follows a 3° ray above the runway's local tangent plane, corrected for Vieneo's curvature. Ten km is approximately 0.54 km above the runway; the readout is MSL, so runway elevation is added.
|-
| VTOL (PLAN) || Preview a hover gate 100 m above the selected surface point. Current vertical-thrust authority must exceed the weight-support requirement at the loaded mass. This is not a terrain-clearance check or a commanded hover/landing.
|}

Runway selections position the atmospheric entry handoff upstream on the runway's extended centerline and point its ground-relative path inbound. The automated portion still ends at '''H ALT / H TAS''' (initially 30 km / 0.5 km/s), not at the low final gate. A successful runway entry transfers to '''ALT NAV SPD / FINAL MANUAL'''. The gray final line and '''FINAL … km MSL / MANUAL''' altitude are advisory geometry. DOR does not execute that line, descend to the LOM, arm LOC/G/S, flare or touch down. VTOL also retains the atmospheric altitude/heading/speed handoff; it does not switch to TVM or descend automatically.

After handoff, manage the remaining energy and descent with the aircraft controls. For an instrument approach, select the correct runway/radio course and use the normal LOC/G/S controls when appropriately positioned below the glidepath, within a 30° inbound intercept and at a suitable speed. A LOM is a fix, not the runway threshold or the origin of the ILS beam. Airport names and proximity alone do not identify a runway. '''SELECT RUNWAY / LIVE ILS''' or '''SELECT RUNWAY THRESHOLD''' means the required data are absent or ambiguous. Changing associated approach data during DOR entry stops execution with '''APPROACH DATA CHANGED'''.

=== Flight path angle (FPA) ===
The normal vertical flight-director cycle is '''PIT → FPA → VS → SPD → ALTm → ALTa → PIT'''. FPA follows Pitch directly when available. At ground contact, below 0.010 km/s horizontal groundspeed, or with invalid path data, the vertical-mode key skips FPA and continues to VS, SPD and the available altitude modes. ALTa is skipped when the required ground-height data are unavailable; G/S remains separately armed. FPA captures the current ground-relative climb/descent angle. Use the existing vertical-target increase/decrease controls to adjust it; the selected signed angle appears in the flight-mode display. The selectable range is −15° to +20°. For a descending 3° path, select −3°.

FPA is the angle of travel relative to the local ground tangent, not nose pitch or angle of attack. The controller adjusts pitch as the measured path changes; its pitch command changes by at most 3°/s. Aircraft response, wind, lift and available thrust still determine whether it can achieve the selected path. FPA controls neither lateral course nor speed, and does not provide terrain avoidance, a flare or touchdown. It can be used as a flight-director cue or with the normal aircraft autopilot; it is not an orbital insertion solver or a DOR ascent profile.

At ground contact, below 0.010 km/s horizontal groundspeed, or with invalid path data, FPA returns to PIT at the current pitch. It does not automatically re-arm: select FPA again after establishing forward flight. This prevents a hover or nearly vertical trajectory from being treated as an ordinary forward flight path. Ground-relative geometry remains defined at high speed, but selecting FPA does not establish atmospheric control authority in suborbital coast or orbit.

The CSV records selected FPA/course, AFCS ground/vertical speeds, arrival choice, final-gate geometry and its advisory status. The companion plan file labels the final line '''final_advisory_not_executed'''. Actual lateral/vertical thruster output remains recorded; a human's recorded firings are not replayed as the optimal control sequence.

=== Recording a manual entry test ===
These recording controls require an administrator account.
# Select the target, route, handoff time, altitude and TAS; wait for an inspectable proposed path.
# Select REC and press Shift + Left/Right once to turn recording on. With the proposed path available, the row reads REC ON (REF). This does not engage DOR or command the ship.
# Fly the test manually or with appropriate existing Autoflyte modes. Changing VIEW or leaving the MFD page does not stop recording. The CSV reference stays fixed at recording start even while the live preview updates.
# Turn REC off to finish. Changing planning controls, changing target, resetting/changing the vehicle, or engaging an executable DOR plan also ends the manual capture. A new test requires REC on again.
# Return both matching files from the '''OrbitLogs''' directory beside the running executable: '''DOR-N.csv''' and '''DOR-N-plan.csv'''. The first contains actual flight data and timed comparison values; the second contains the frozen reference trajectory.

Four reusable file slots bound retention; older captures can be replaced by subsequent starts. A slot stops at 128 MiB rather than discarding its beginning. REC FILE ERROR or REC FILE FULL means capture has stopped. Current clients can start REC ON (FLIGHT) without a reference; older entry-calibration clients instead display REC WAIT FOR PLAN. Copy the pair you want to keep before beginning more tests. No automatic upload occurs.

New captures separately integrate main-engine, translational-RCS, attitude-RCS and idle fuel consumption, and record the available orbital MECO estimate. The tank-based ALL USED remains the measure of fuel actually lost; integrated component totals can differ slightly because of fuel-tank rounding.

The CSV includes time, target, mass/fuel, position/velocity, engine and RCS outputs, air-relative velocity, IAS, Mach, dynamic pressure, measured AFT and reference errors. The automated-entry alpha also records the predicted AFT/IAS reference, the live protection forecast, controller limits, force requests and handoff holds. Earlier calibration captures contain measured AFT but no predicted temperature reference. An expired HANDOFF or end of recording does not prove that the entry was completed successfully.

== Warnings and unavailable plans ==
{| class="wikitable"
! Message !! Meaning / next action
|-
| VACUUM ESTIMATE || An orbital estimate is available. It assumes two-body coasting between instantaneous planned burns.
|-
| LONG BURN - ESTIMATE / FINITE BURN NOT CORRECTED || The preview's instantaneous-burn approximation is weak for the estimated duration. Live DOR corrects from actual state, but the original time, path and fuel are estimates.
|-
| PLAN ATM PASS / COAST ATM q>10Pa / CORRECTION ATM q>10Pa / CURRENT ATM q>10Pa / ATMOSPHERIC PASS / ATMOSPHERIC TARGET || Pressure advisory above 10 Pa, or a target explicitly in atmospheric-flight reference mode. The actual predicted coast is refreshed during execution. Other orbital modes can retain atmospheric estimates; OVERFLY must satisfy its stricter clearance requirements.
|-
| PLAN MIN / COAST MIN / CORRECTION MIN / EXEC PATH <100km || Steady red low-altitude warning identifying the affected trajectory. The numerical minima are km MSL. COAST MIN assumes no further burns and can differ from PLAN MIN ALT. The current-coast warning clears at 105 km; this is annunciation hysteresis only.
|-
| ATM PASS - NO PLAN / MIN … km / BLOCKED || An inspectable OVERFLY candidate fails atmospheric clearance. Change PASS, ALT or EXIT; DOR cannot execute it.
|-
| DOR: TIMING INTERRUPTED || A simulation frame took more than one second. DOR disconnects because its previous control commands cannot safely cover the interruption. Check the current flight state before re-engaging; this message does not identify the cause of the client stall.
|-
| DOR: NO CLEAR CORRECTION / CORRECTION MARGIN LOST / FINAL ORBIT UNSAFE / COAST CLEARANCE LOST / DEPARTURE COAST UNSAFE || Execution stopped because the updated trajectory or correction fails its checks. Thrust commands are cleared and the disconnect sounds once. The existing trajectory still needs pilot attention.
|-
| SURFACE INTERSECTION / NO CLEAR TRANSFER || The requested shape intersects Vieneo, or no acceptable transfer was found. Raise the requested periapsis or change the timing/objective.
|-
| INSUFFICIENT FUEL / PERFORMANCE UNAVAILABLE || Fuel or propulsion data do not support execution. A geometric estimate alone is not an executable DOR plan.
|-
| BURN TIME PASSED / ARRIVAL TIME PASSED || The selected deadline has passed. Edit the time to request a new one; these are real countdowns, not indefinitely rolling delays.
|-
| SELECT NAV TARGET / NO TARGET TRAJECTORY || Select a usable target, or choose ADJUST ORBIT.
|-
| DOR: UNDOCK TO EXECUTE || An orbital plan can be previewed while attached to a station, but DOR cannot arm or execute it until undocked. Undocking does not engage DOR automatically. SURFACE PLAN remains planning-only. A qualifying automated-entry REENTRY still requires undocking before execution.
|-
| NO DEPARTURE STATE / POWER OFF || The departure reference is unavailable or unsupported, or cockpit power is off. A valid station attachment permits previews; an unsupported containment frame does not.
|-
| ASCENT PROFILE REQUIRED || The selected vacuum orbital objective has no powered launch solution. Choose [[#Ground-to-rendezvous mission|MODE RENDEZVOUS]] for a continuous launch to an orbital target, or [[#Automated ascent alpha|MODE PARKING ORBIT]] for a standalone parking-orbit climb. Older clients require a manual ascent.
|-
| VTOL READY / ASCENT READY || The ascent controller is ready with the current inputs. Ground LAUNCH AUTO can arm while its comparison is running, but requires a completed, current, fuel-fitting solution before committing departure; ground RENDEZVOUS requires one for LAUNCH NOW too. This is not a full-flight fuel, time or terrain-clearance guarantee. See [[#Scheduled launch and airborne pickup|scheduled launch and airborne pickup]].
|-
| VTOL LIFT / ATTITUDE LIMIT / ASCENT DATA INVALID || Check loaded vertical-thrust authority, level ground attitude, configuration and valid current air data.
|-
| ASCENT LIMIT / IDLE || The short-term ascent forecast is at its IAS or AFT guard. Positive main thrust is reduced; monitor the actual path.
|-
| INSERTION COMPLETE / REPLAN || Standalone PARKING ORBIT has ended at the parking orbit. Select and review RENDEZVOUS separately to continue. A mission begun in ground RENDEZVOUS instead transfers automatically.
|-
| DOR: NO TRANSFER AT INSERTION / TRANSFER FUEL SHORTFALL / MEET BURN TIME LIMIT || The achieved insertion state cannot support the transfer at the original MEET with the remaining fuel/time. DOR stops; review the condition and a new plan before re-engaging.
|-
| DOR: MEET MISSED DURING ASCENT / MEET MISSED AT INSERTION / ASCENT TARGET INVALID / INSERTION TARGET INVALID || The mission has insufficient remaining MEET time or no usable orbital target. DOR stops rather than changing the deadline or treating parking insertion as rendezvous completion.
|-
| PLAN ONLY / ATM HANDOFF || The displayed candidate is preview-only; DOR cannot execute it. Ground-departure SURFACE PLAN remains preview-only. REENTRY needs a qualifying ENTRY READY profile in the automated-entry alpha.
|-
| INVALID / MODEL FIT / THRUST LIMIT / FUEL LIMIT / IAS LIMIT / IAS / THRUST LIMIT || Result of the surface preview’s simplified checks. MODEL FIT does not certify terrain, heating, weather, maneuverability or landing.
|-
| NO TERRAIN / HEAT CHECK || SURFACE PLAN and older calibration previews omit these checks. Automated-entry REENTRY predicts heat but still displays ALPHA / NO TERRAIN CHECK.
|-
| ENTRY READY / IAS RESERVE / AFT RESERVE / THRUST RESERVE / ATTITUDE RATE / SPOOL LIMIT || Automated-entry preview result. READY passes the modeled checks; other messages identify a rejection. None certifies terrain clearance or landing.
|-
| ENTRY DATA / CONFIG || Entry cannot execute with the current air data, configuration or departure altitude. Check clean configuration, valid measurements and an orbital departure.
|-
| ENTRY LIMIT / BRAKING || Active entry protection prioritizes braking and arresting descent over the requested handoff time. Monitor the actual trajectory.
|-
| MODEL FIT / HEAT UNCHECKED || Older calibration-client preview; it does not support automated entry.
|-
| HANDOFF BELOW TARGET || Raise H ALT above the destination elevation.
|-
| ENTRY DATA UNAVAILABLE / ENTRY GEOMETRY / NO COAST / ENTRY FIT || Required performance data or a fitting entry candidate is unavailable. Inspect the selected time, route and handoff settings.
|-
| REC FILE ERROR / REC FILE FULL || Capture stopped because of a file error or size cap. See [[#Recording a manual entry test|recording instructions]].
|-
| ENTRY FIRST / NO ROUTE AT THIS PASS || Direct ATM is outside its initial departure-height range, or no candidate was available at this deadline. Change ROUTE/PASS or use separate entry procedures.
|}

[[Category:Getting Started]]

Orbit

2026-10-22T18:48:48Z

reskin:

The '''Digital Orbital Resolver (DOR)''' is the spacecraft's orbital guidance and control system. Its '''Orbit MFD''' shows your current trajectory, the selected target's trajectory, and a proposed maneuver around [[Vieneo]]. Use it to change your orbit, rendezvous with a station or another spacecraft, or pass over a selected surface point. '''DOR executes the selected valid orbital plan'''; circularizing is one possible plan.

The full-page instrument is installed in the E-10, E-11, P-13, W-6, and EVA displays. It is not installed in the A-4. Older clients may still show the small numerical Orbit readout.

'''About the illustrations:''' These are labeled scenario renders from the implemented instrument's layout, orbital planner and guidance code, using synthetic example conditions. They are not screenshots of live flights. Each uses the native 420 × 320 layout enlarged for reading. Example times, fuel and delta-V are not a performance promise for your vehicle. Some dated illustrations use earlier labels (MIN ROUTE ALT, TO GO / USED and ATM PASS) and omit the live MECO estimate; the current readouts are described below.

'''Ground rendezvous:''' Select '''MODE RENDEZVOUS''' on the ground to plan and fly VTOL launch, ascent, parking-orbit insertion and transfer to an orbital station or spacecraft as one DOR mission. See [[#Ground-to-rendezvous mission|Ground-to-rendezvous mission]]. Standalone '''MODE PARKING ORBIT''' ends at the parking orbit. Ground-to-ground SURFACE PLAN remains planning-only.

'''Client versions and limits:''' Orbital adjustment, rendezvous and overflight have executable plans. [[#Surface journey planning|SURFACE PLAN]] remains planning-only for ground and low-atmospheric departures. The [[#Automated entry alpha|automated-entry alpha]] adds '''REENTRY''' execution from orbit to an atmospheric handoff, followed by altitude, heading and TAS hold. It does not fly the final descent or land. This requires the client with '''ENTRY READY'''; earlier calibration clients show '''REENTRY PLAN / PLAN ONLY''' and support manual REC capture only.

== Open and operate the page ==
The page is identified as '''DOR''' at the upper left. On the ground, the launch header shows '''SEARCH''' while comparing candidates and '''ARMED''' while DOR is awaiting comparison or departure. '''NO FIT''' or '''FUEL''' identifies an unavailable or fuel-short launch estimate. While executing, '''EXEC''' at the upper right and the active phase ('''ALIGN''', '''WAIT''', '''BURN''', '''COAST''' or '''ARRIVAL''') blink together: one second visible, one second hidden. Normal active phases are green; a separate red warning does not turn BURN or ARRIVAL red. The phase and its MECO estimate blink together. The DOR page identifier, other numerical readouts and atmospheric warnings stay steady. ESTIMATE, NO PLAN and completion/fault indications do not use this execution blink.

''Older orbital illustrations show ORB1 and DOR-prefixed phases. Static illustrations do not demonstrate the execution blink.''

Select the Orbit page on a supported vehicle's MFD. Choose the station, spacecraft or surface waypoint on your usual target-selection instrument; Orbit reads that selection. You do not enter a second waypoint on this page.

{| class="wikitable"
! Control !! Action
|-
| Shift + Up / Down || Select a row in the side controls. The highlighted row's actions appear along the bottom.
|-
| Shift + Left / Right || Change the highlighted option or decrease/increase its value.
|-
| Shift + C, with the eccentricity row selected || Request a circular orbit (e = 0).
|-
| Your configured DOR on/off control || Engage or disengage a valid executable plan. SURFACE PLAN stays planning-only. The automated-entry alpha can execute an ENTRY READY reentry; after handoff, the same control cancels its TAS hold.
|}
The controls require cockpit power and do not take these keys while text entry is active. Changing VIEW does not alter the plan or interrupt DOR. Changing a planning value does interrupt execution: review the new solution before engaging DOR again. Standalone PARKING ORBIT offers STEER AFCS / ORBIT as a live heading-source choice during the climb. Ground RENDEZVOUS selects its staging orbit and orbital steering automatically.

'''Administrator diagnostics:''' REC and automatic local CSV capture are available only to administrator accounts. Other accounts have no REC row and their DOR flights are not recorded automatically. Losing administrator permission ends an active capture without changing DOR guidance.

Selecting Orbit does not replace or acknowledge [[EICAS]] indications. With EICAS powered and serviceable, its gear, engine, trim and crew-alert indications remain independent of the MFD page. If these disappear only while ORB1 is selected, that is a rendering fault, not evidence that the underlying condition has cleared.

== Select an objective ==
{| class="wikitable"
! MODE !! Use
|-
| RENDEZVOUS || An orbiting station or free-flying vessel is selected. Reach its trailing staging point and match its velocity. On the ground, this includes launch, ascent and insertion followed automatically by the orbital transfer.
|-
| OVERFLY || A surface waypoint or grounded vessel is selected. Pass above that rotating ground point at the requested altitude and time.
|-
| SURFACE PLAN || A surface target is selected for a ground or low-atmospheric departure. Compare atmospheric, suborbital and orbital journeys using TRIP duration before departure and a PASS countdown afterwards. Planning only.
|-
| REENTRY || The surface-arrival objective for an orbital/high-altitude departure, including while docked at a station. Compare direct powered entry with coast-then-entry, ending upstream of the waypoint at the selected HANDOFF altitude and TAS. The automated-entry alpha can execute a qualifying ENTRY READY plan after undocking.
|-
| PARKING ORBIT || Before orbit is established, perform VTOL liftoff or take over an airborne climb to a selected circular parking orbit. Main-engine pitch guidance uses current mass and atmospheric conditions. This standalone mode ends at insertion; choose RENDEZVOUS before launch for the continuous trip to an orbital target.
|-
| ADJUST ORBIT || Change your own orbit independently of the selected target. Available through MODE once the current bound orbit has its periapsis above the surface, including when a target is selected. It is not offered on the ground.
|}
'''A newly selected surface target defaults to the surface-arrival objective.''' It is labeled SURFACE PLAN for a ground/low-atmospheric departure or REENTRY for an orbital/high-altitude departure. An entry keeps its identity through the atmospheric handoff rather than becoming a new ground-departure plan. Use MODE to choose OVERFLY for an orbital pass or ADJUST ORBIT to change your own orbit. An explicitly selected ADJUST ORBIT objective remains independent of the target.

With an orbital target selected on the ground, MODE offers RENDEZVOUS and PARKING ORBIT. Once established in a bound orbit with periapsis above the surface, it offers RENDEZVOUS and ADJUST ORBIT; PARKING ORBIT is no longer offered. Without a target, choose PARKING ORBIT before orbit is established, ADJUST ORBIT in orbit, or select a navigation target elsewhere. A docked or contained target is not treated as an independent free-flying spacecraft. An undocked spacecraft inside a station's control area remains a valid target. An atmospheric-flight target may still have a predicted trajectory, but it is marked with an atmospheric warning.

Rendezvous is more than matching orbital size and shape. Two spacecraft can have identical orbital parameters and remain far apart. Rendezvous also solves for position and velocity at the same future time, including the difference between their orbital planes.

== Read the picture and numbers ==
The graphic area stays the same size in every mode. In the ascent altitude/distance view, green is measured flight history and amber is the powered forecast (see [[#Ground and ascent|Ground and ascent]]). In orbital views, '''green''' is your current trajectory; '''cyan''' is the target; '''amber dashed''' lines show the proposed transfer. Dim amber shows the destination orbit, and gray dashed lines show a planned coast before departure. AP and PE mark apoapsis and periapsis. In orbital plans, numbered amber markers identify burns; T identifies the target's current position. Ground-departure surface previews instead number phase boundaries and mark the future arrival point B. REENTRY uses D for deorbit, E for the 100 km crossing and H for atmospheric handoff; the legend identifies them.

{| class="wikitable"
! VIEW !! What it helps you see
|-
| ORBIT || Your orbital plane viewed face-on: shape, apsides and transfer path.
|-
| PLANE 3D || Plane orientation, with Vieneo's equator and north axis as references. The NODE line indicates the intersection of the current and target orbital planes.
|-
| EDGE-ON || Your orbital plane viewed from its edge. Useful for seeing how far the target or transfer leaves that plane; it compresses the shape of your own orbit into a line.
|-
| TRACK || Latitude/longitude ground tracks, including Vieneo's rotation. Useful for a surface overflight. This is a schematic grid, not terrain imagery.
|}

{| class="wikitable"
! Readout !! Meaning
|-
| AP / PE || Highest / lowest altitude of the orbit above the spherical Vieneo reference surface, in km. A negative PE means the unpowered trajectory intersects that surface.
|-
| e || Eccentricity: 0 is circular; larger values produce a more elongated ellipse.
|-
| SIZE … km MSL || Orbit size expressed as altitude above mean sea level. For a circle, this is the orbit altitude; for an ellipse, it is (AP altitude + PE altitude) / 2, not the time-average altitude. The planner adds Vieneo's 2939.6 km reference radius internally.
|-
| i / PLANE DIF || Inclination to Vieneo's equator, or the angle between your plane and the target's plane, in degrees.
|-
| TP / nu || Orbital period in seconds / true anomaly in degrees, locating you around the current orbit relative to periapsis.
|-
| CURRENT > FINAL || Current AP/PE/e followed by the proposed final orbit after all burns. Older captures say CURRENT > PLAN. This is not the transfer minimum. CURRENT > REQUEST is an editable goal for which no valid plan exists yet.
|-
| PLAN MIN ALT || Lowest checked planned-route altitude in km MSL above the spherical reference surface. Includes any waiting coast, transfer and continuing final orbit; an OVERFLY circularization check also includes its arrival-response allowance. This is separate from final PE and from the actual unpowered coast.
|-
| B1 / B2 || Planned burn time and delta-V in m/s. The IDEAL line gives duration in seconds and fuel in kg for the main-engine maneuver; it does not include all attitude control, RCS trims or later corrections.
|-
| TOTAL / IDEAL FUEL || Total planned delta-V and ideal main-engine fuel. The calculation uses current vehicle mass and engine performance, with mass decreasing as fuel is consumed. Real execution can use more fuel for alignment, RCS, finite burns and corrections.
|-
| LEFT / ALL USED || During orbital DOR execution: the active guidance correction remaining, in m/s, and all fuel consumed since engagement, in kg. ALL USED includes the armed wait and ascent when starting from the ground, as well as alignment, both burns, coast and corrections; it is not a B1-only or B2-only measurement.
|-
| MECO ~mm:ss || Estimated time to cutoff of the current orbital burn, shown beside BURN or ARRIVAL. It follows measured convergence and throttle-down, not the original B1/B2 duration. It may increase after a correction. --- means no reliable recent convergence estimate. ALIGN, WAIT, COAST, continuous ascent and reentry do not show this timer. Cutoff is controlled by guidance, not by the countdown; another correction may subsequently fire.
|}

=== Minimum route altitude ===
Read '''PLAN MIN ALT''' directly below the graphic before engaging DOR. The graphic retains its size, and the OWN / TARGET / PLAN legend sits alongside the readout. It appears in every orbital view, including ascent detail when an orbital route is available. It uses the planner's checked arc minima, not the lowest vertex of the drawn curve.

* '''Red''' means the planned minimum is below 100 km MSL.
* '''Amber''' means the minimum is at least 100 km but the planned route has an atmospheric warning or is blocked by the clearance check.
* Neutral gray is an unflagged estimate, not flight clearance. '''---''' means no checked route minimum is available; it never substitutes the final PE or current-coast minimum.

'''CURRENT > FINAL''' distinguishes the destination AP/PE from this route minimum. A final PE of 118 km does not establish the approach's minimum altitude, and pressure warnings depend on air-relative speed as well as altitude. The pressure advisory threshold is 10 Pa; a 118 km orbit is not automatically atmospheric. Atmospheric and surface-planning policies remain those of the selected mode; this display change does not add a new restriction to RENDEZVOUS or ADJUST ORBIT. SURFACE PLAN keeps its separate phase legend and planning-only readouts.

During EXEC, '''PLAN MIN ALT''' continues to describe the committed instantaneous-burn plan. '''COAST MIN''' describes the current unpowered trajectory if no more burns occur; '''CORRECTION MIN''' describes the live powered-correction forecast. These are km MSL and need not agree: a planned minimum of 118 km can coexist with a negative COAST MIN while later burns are still needed. A negative value means the mathematical coast intersects Vieneo. These warnings remain separate from the green execution phase and any retained red abort reason. A fresh preview after an abort shows the new plan; the old abort reason remains available independently.

'''Finite-burn limitation:''' PLAN MIN ALT still describes the instantaneous-burn plan, not the live powered recovery. DOR checks a finite powered response separately, including alignment time rather than an unpowered coast for the entire correction. A negative current PE during a burn can therefore coexist with a viable recovery, while still warning what would happen if thrust stopped. A neutral planned minimum or final PE is not assurance that DOR can complete the whole maneuver. See [[#Powered correction clearance|Powered correction clearance]].

[[File:Orbit-MFD-rendezvous-min-route-alt-20261016.png|thumb|center|600px|'''Scenario 18: route minimum and final orbit.''' Fresh labeled render from the actual planner/display code. This synthetic rendezvous has a final PE and route minimum both at 118 km. With the 10 Pa advisory threshold, its route minimum is neutral gray; LONG BURN - ESTIMATE and the independent reversal caution remain visible. This is not a live flight, a reconstruction of player telemetry or a guarantee of execution.]]
<div style="clear:both"></div>

=== Orbital direction cautions ===
A steady amber caution beside the graphic's view title identifies the direction of the proposed plan. It remains visible during EXEC, including the hidden half of the execution blink, and does not replace atmospheric, fuel or finite-burn cautions.

* '''ORBIT REVERSAL''' means a departure or arrival burn changes the orbital angular-momentum direction by more than 90 degrees. It compares the directions before and after the burn; it is not based on which way the nose or thrust vector points. An ordinary backward braking burn that preserves orbital direction does not trigger it.
* '''RETROGRADE ORBIT''' means the transfer or final orbit runs against Vieneo's modeled rotation. A ship that already travels retrograde can keep that direction without an ORBIT REVERSAL. Polar motion alone is not classified as retrograde.
* '''RETROGRADE / REVERSAL''' shows both conditions. An intermediate retrograde transfer still warns even if the final orbit returns to prograde. The committed plan retains its caution during execution.

The OVERFLY automatic initial PASS search excludes plans that reverse orbital direction. Manual previews remain available with the caution. Direction caution alone does not block DOR, but the independent OVERFLY atmospheric-clearance requirements still apply. Blocked atmospheric previews retain their direction caution. If reversal was unintended, change the arrival/departure time or the overflight exit behavior and inspect the resulting plan before engaging DOR. A large delta-V can suggest reversal, but the warning is calculated from the trajectories rather than a speed threshold.

See the updated blocked-overfly illustration under [[#Overfly atmospheric clearance|Overfly atmospheric clearance]]. It replaces the older example that allowed the same low-periapsis route as a warning-only plan.
<div style="clear:both"></div>

== Ground and ascent ==
For a ground RENDEZVOUS or standalone PARKING ORBIT, the default ORBIT view shows '''ASCENT / ALTITUDE VS DISTANCE'''. The vertical axis is altitude in km MSL; the bottom axis is accumulated horizontal ground distance in km since departure. This is distance along the flown ground track, not range to the destination or slant distance. Taxi distance is excluded; a vertical VTOL climb remains at zero ground distance.

* '''PLAN EST''' (amber) is the estimated powered climb through insertion, using the ascent controller, current loaded mass, gear configuration, wind, atmosphere and engine limits. Computation runs in the background. '''COMPUTING PLAN...''' and '''PLAN UNAVAILABLE''' identify missing forecasts. It is an advisory estimate, with approximate aircraft response, fixed weather/configuration and no terrain or obstacle check.
* '''ACTUAL''' (green) is the measured flight history, with a diamond at the latest position. Samples are retained approximately every kilometre horizontally, or earlier after a kilometre of altitude change or five seconds, preserving slow and vertical flight. The display updates approximately once a second. Long histories are progressively coarsened while retaining the departure point.
* The departure plan stays fixed after liftoff so deviations remain visible. Changing the orbit/steering/target regenerates the remaining forecast from the current distance; '''FROM ... km''' identifies that starting point. The forecast may update on the pad as the launch recommendation or aircraft setup changes.
* History is collected for every pilot without REC, including manual departure. If observation starts airborne, '''DIST FROM PICKUP (km)''' identifies its origin. Landing, a vehicle/simulator change or a flight-state reset starts a new history. REC is separately restricted to administrators and writes diagnostic files.

The axes scale to fit both traces. The ascent profile remains available in the default ORBIT view through parking-orbit insertion, including above 100 km. Change VIEW to PLANE 3D, EDGE-ON or TRACK to inspect orbital geometry without cancelling the climb. At the RENDEZVOUS insertion handoff, the display changes to the transfer plan. The header says ASCENT / INSERTION during the initial leg.

With an orbital target selected on the surface, choose '''RENDEZVOUS''' for launch through arrival, or '''PARKING ORBIT''' to stop after insertion. ADJUST ORBIT replaces PARKING ORBIT once an orbit is established.

For a vacuum orbital objective such as ADJUST ORBIT, '''ASCENT PROFILE REQUIRED''' means that objective has no executable powered launch. Choose '''MODE RENDEZVOUS''' for a complete trip to an orbital target, or '''MODE PARKING ORBIT''' for a separate powered climb ending at a parking orbit. Older clients require manual ascent. Any ordinary vacuum transfer estimate starts from your measured position and velocity; it does not include lift or drag in that predicted path.

Outside an executable powered-ascent leg, the local ASCENT DETAIL / COAST view still shows the measured-state unpowered coast below 100 km. It returns to the selected orbital view at 100 km. This does not certify insertion: a periapsis intersecting Vieneo still indicates a suborbital trajectory. A descending vehicle is not automatically shown as ascending.

For '''SURFACE PLAN''', the default view shows a fitting estimated powered ascent as '''ASCENT / PLAN ONLY'''. A rejected candidate is labeled '''ASCENT / INVALID PREVIEW'''. Change VIEW to PLANE 3D, EDGE-ON or TRACK to inspect the entire journey before takeoff; changing VIEW does not change the selected trip timing. The local surface view rotates with the departure location, so a vertical climb is not mistaken for sideways travel caused by Vieneo's rotation.

There is no hard atmospheric boundary at 75 or 100 km. The planner's warning estimate uses the client's density model and air-relative speed. The 100 km ascent-view transition is a display rule. OVERFLY separately uses 100 km as a minimum clearance policy and also checks dynamic pressure; neither use defines a physical atmospheric boundary.

=== Ground-to-rendezvous mission ===
Use this procedure to fly from the surface to an orbital station such as TAC without selecting a new plan in orbit.

# Select TAC on the navigation/target instrument and choose '''MODE RENDEZVOUS''' on DOR. Initially MEET shows '''FASTEST (AUTO)''' while DOR finds its earliest accepted arrival estimate. You can then adjust the countdown for a later or earlier meeting. DOR uses a 200 km MSL intermediate parking orbit and selects the target's orbital direction automatically; there are no ORBIT or STEER setup rows in this mission. '''STAGING 200km MSL / AUTO''' reports this intermediate goal, which is not the station's altitude or an optimized choice among parking altitudes.
# Review '''FACE ... deg T''' for the intended launch direction. The target's current bearing and closing range are not the required insertion heading or launch time. If ATC requires a different departure route, leave DOR off and fly that route manually; engage the retained rendezvous mission when cleared to proceed toward the orbital direction. Standalone PARKING ORBIT retains the optional HDG/NAV steering selection.
# Compare the launch recommendation, '''INSERT IN''', '''ASC / XFER / TOTAL''' fuel and '''MEET -5m / +5m''' alternatives. During '''FINDING FASTEST RENDEZVOUS''' or '''COMPARING LAUNCH TIMES...''', numbers may describe a provisional candidate; '''CANDIDATE / NOT COMMITTED''' is not a launch countdown. MEET must leave time for both ascent and transfer. A station that is close and approaching can still have no fitting solution at the chosen MEET.
# Leave '''LAUNCH AUTO''' to wait for the recommended departure. When VTOL is ready and automatic departure is authorized, engage DOR. It can remain armed while the comparison finishes, showing '''ARMED / COMPARING LAUNCHES''' with zero thrust and no attitude command. When a completed, current, fuel-fitting solution is available, '''ARMED / LAUNCH WAIT''' and '''LIFTOFF IN''' show its committed countdown. At zero, DOR starts VTOL automatically. '''LAUNCH NOW''' evaluates immediate departure only; RENDEZVOUS still waits for that completed, fuel-fitting estimate before liftoff.
# Start approximately level on a clear VTOL area with sufficient loaded vertical-thrust authority. Stow flaps and spoilers, close bays and clear icing. DOR lifts to approximately 100 m AGL, builds airspeed, and controls pitch and thrust through ascent and insertion. '''Retract the landing gear yourself after liftoff.''' Monitor IAS/Vne, AFT, fuel and the flight path.
# At settled insertion, leave DOR engaged. '''AUTO TRANSFER AFTER INSERTION''' means it will solve the transfer from the achieved orbit and remaining fuel, keeping the original absolute MEET. If an immediate transfer does not fit, DOR can select a checked coast before the departure burn while keeping MEET unchanged. The display changes from ascent controls to the orbital plan and burn guidance. No MODE change, manual replan or second engagement is needed.
# Continue monitoring through alignment, departure burn, coast and arrival correction. Successful rendezvous ends at the normal roughly 5 km trailing staging point and hands over to '''TVM''' with zero selected closing speed. Obtain clearance and perform close approach/docking separately.

The ground comparison is an estimate, not a guarantee of the flown path, fuel use or completion exactly at MEET. Final settling can take additional time. If the achieved insertion state cannot support the transfer, DOR disconnects with a reason such as '''NO TRANSFER AT INSERTION''', '''TRANSFER FUEL SHORTFALL''' or '''MEET BURN TIME LIMIT'''. An expired MEET or invalid target also stops execution. Take control, review the condition and select a new plan when appropriate; DOR does not silently move MEET or declare rendezvous complete at the parking orbit.

=== Automated ascent alpha ===
'''MODE PARKING ORBIT''' provides a standalone powered climb ending at a circular parking orbit, including VTOL liftoff. The same ascent controller flies the first leg of a ground RENDEZVOUS mission. During atmospheric climb, DOR supplies heading and pitch targets to the ordinary AFCS HDG/PIT controllers and controls thrust. The FMA shows HDG and PIT on those axes. FPA remains available for pilot-selected flight. Select RENDEZVOUS before launch when the whole trip to an orbital target should continue automatically.

# Select '''MODE PARKING ORBIT''' on DOR when you want to stop at a parking orbit. Set '''ORBIT 200 km MSL''' for the first test; the range is 150–1000 km in 50 km steps.
# Use '''STEER AFCS''' to follow the selected HDG or NAV heading for an assigned departure. This chooses the source of the commanded heading, not whether control surfaces or RCS are used. DOR controls attitude and thrust while following that heading. The magenta orbital heading bug and the airborne '''ORBIT HDG … deg T''' readout show the desired orbital direction separately. Set the assigned heading or navigation route before engaging.
# Start approximately level on a clear VTOL departure area, with sufficient vertical-thrust authority for the current loaded weight. Flaps and spoilers must be stowed; icing and open bays are unsupported. A runway takeoff remains manual; PARKING ORBIT can also take over an airborne climb.
# In clients with the '''LAUNCH''' row, leave '''LAUNCH AUTO''' selected to arm the recommended departure: engage DOR to await the comparison and its recommended departure. While comparing it shows ARMED / COMPARING LAUNCHES with no thrust or attitude command. After accepting a completed, current, fuel-fitting estimate it shows '''ARMED / LAUNCH WAIT''' and '''LIFTOFF IN''' until departure, then starts VTOL automatically. Choose '''LAUNCH NOW''' for immediate departure instead. Earlier clients without this row launch immediately on engagement. VTOL first lifts approximately level to 100 m AGL, then transitions to a climb using lift and pitch to direct the main engines. '''Retract the gear yourself after liftoff.''' DOR does not operate it.
# When cleared to turn toward the orbital direction, change '''STEER''' to '''ORBIT'''. This is allowed during execution. No automatic turn is authorized merely by passing 17 km. AFCS may be selected again if needed; monitor the changed flight path.
# Monitor IAS/Vne, AFT, pitch, thrust, fuel and AP/PE. The controller uses current mass, measured aerodynamic forces and separate thrust limits. Pitch and wing lift are preferred for a supported climb, with vertical RCS retained for VTOL, insufficient lift and recovery. Small vertical-thruster corrections are reduced while lift is available and climb rate is tracking. Attitude RCS assistance fades as the available wing/control-surface lift reserve grows, and remains available for VTOL or insufficient aerodynamic authority. Atmospheric heading changes use banked AFCS HDG turns, not orbital flat yaw. DOR keeps HDG/PIT through at least 50 km MSL and until modeled dynamic pressure is at most 500 Pa; a descent to 45 km or pressure rising to 750 Pa restores aircraft steering. These are DOR transition settings, not an atmospheric boundary. If wing reserve runs low before the transition, pitch uses RCS assistance. Above 50 km, a bank limit below one degree shows '''HDG LIMITED / RCS PIT''' on DOR: pitch assistance remains, but significant banked heading changes are unavailable in that interval. The FMA retains HDG/PIT until the orbital handoff. Main thrust can use full available authority when required, but follows the requested airspeed and climb rate, so a partial setting can be normal. Near insertion, small corrections use '''INSERTION / LEVEL TRIM''': level pitch with small main/reverse and translation-RCS corrections. Larger corrections can still require a pitched thrust vector. The initial speed schedule leaves margin below Vne. A short-term forecast at 95% Vne or 200°C AFT removes positive main thrust and shows '''ASCENT LIMIT / IDLE'''; this is a controller margin, not a guarantee against disturbances.
# In standalone PARKING ORBIT, after parking-orbit insertion settles, DOR disconnects with the usual sound and shows '''INSERTION COMPLETE / REPLAN'''. Select RENDEZVOUS and inspect a new plan from the achieved orbit to reach the station. Switching from PARKING ORBIT to RENDEZVOUS preserves the selected absolute MEET deadline. If it is now too soon or has passed, change MEET and review the new plan. Standalone PARKING ORBIT does not automatically complete rendezvous or switch to TVM; ground RENDEZVOUS continues automatically as described above.

During execution, '''GUIDANCE ONLY / NO ETA / NO BUDGET''' means there is no continuously updated full-flight time or fuel guarantee; the ground comparison is an advisory forecast. USED records fuel actually consumed. In the altitude/distance view, the green line is measured flight history and the amber line is the advisory powered-climb forecast described above. The controller has no terrain/obstacle avoidance and does not forecast weather along the route. Ground-to-ground SURFACE PLAN remains a separate preview-only objective.

Changing ORBIT altitude, MEET, MODE or LAUNCH cancels execution. While DOR owns atmospheric HDG/PIT, using the lateral- or vertical-mode cycle key releases DOR and its autopilot engagement, then selects the next ordinary flight-director mode. Re-engage the aircraft autopilot deliberately if wanted. VIEW does not cancel it. STEER can be changed during the powered climb without cancelling it; changing STEER during an armed ground wait cancels that wait. Manual attitude or thrust input overrides powered ascent; invalid/stale required data, unsupported configuration or loss of authority can stop execution. Retain control of the flight after a disconnect.

For administrator accounts, DOR automatically records an executed ascent. A ground RENDEZVOUS keeps the same automatic recording through insertion and the orbital transfer; REC need not be switched on separately. Keep both matching CSV files from OrbitLogs, including ascent commands, the insertion handoff, steering selection and actual engine/RCS response. REC remains available for a continuous flight capture through manual flight and later maneuvers. Use the procedure below when recording a manual profile.

=== Compare launch times with MEET ===
MEET comparison is available in the ascent leg of ground RENDEZVOUS and in standalone PARKING ORBIT. Select an orbital station or spacecraft while parked. RENDEZVOUS sets its 200 km staging orbit and orbital steering automatically; standalone PARKING ORBIT additionally offers ORBIT and STEER controls. Use Shift + Up/Down to select MEET and Shift + Left/Right to change it in five-minute steps. MEET counts down to an absolute arrival deadline. Allow the '''COMPARING LAUNCH TIMES...''' indication to finish before comparing results.

A newly selected ground RENDEZVOUS searches for the earliest accepted MEET within six hours, prioritizing arrival time over fuel. It excludes atmospheric and orbit-reversing transfer estimates and checks modeled fuel and a finite burn-time allowance. FASTEST FOUND / ESTIMATE is the earliest accepted sampled solution, not a proof of the physically fastest possible flight. Long burns and final velocity matching can make actual completion substantially later than MEET.

Use the countdown for future appointments: for a meeting six hours from now, select 360:00 (minutes:seconds). Adjustments are in five-minute steps, within 30 seconds to six hours. Times are not capped at the most economical meeting; later times remain available even if their fuel cost rises again. An explicit edit keeps your chosen absolute MEET. Switching back into ground RENDEZVOUS starts a new automatic fastest search.

The comparison models a VTOL climb to the selected parking orbit and an orbital transfer from its predicted insertion state to the normal five-kilometre trailing rendezvous point. After you explicitly choose MEET, LAUNCH AUTO searches departure times for the lowest modeled total fuel at that meeting among the sampled candidates. LAUNCH NOW evaluates immediate departure only, including the neighboring MEET comparisons. This is a bounded estimate, not a proof of the globally best window or a guarantee of completing the flight at MEET. More time can save fuel, but orbital geometry means fuel need not decrease smoothly with every later deadline.

{| class="wikitable"
! Readout !! Meaning
|-
| SEARCH; CANDIDATE / NOT COMMITTED || The comparison is still running. Displayed fuel, heading and insertion figures are provisional. Engaging DOR can arm the wait for completion; it does not launch on these provisional figures.
|-
| ARMED / COMPARING LAUNCHES || DOR is armed with zero thrust and no attitude command while the comparison finishes. An accepted completed solution starts the committed launch countdown automatically. A completed comparison with no viable solution disconnects DOR with NO LAUNCH AT SELECTED MEET.
|-
| LAUNCH IN || Recommended remaining time before departure for the selected MEET. With LAUNCH AUTO, engaging DOR commits that departure time. A passed recommendation must be refreshed.
|-
| ARMED / LAUNCH WAIT; LIFTOFF IN || DOR is engaged on the ground and waiting for the committed departure. The countdown stays fixed rather than following newly optimized recommendations. Thrust remains at zero until departure. DOR off cancels it.
|-
| FACE ... deg T / AFCS or ORBIT || Initial true heading for that candidate. AFCS assumes the currently selected departure heading is retained throughout the modeled climb; it does not predict future NAV/ATC route turns. ORBIT follows the selected target's orbital direction. The target's current line-of-sight bearing is not the insertion heading.
|-
| INSERT IN || Estimated time from now to parking-orbit insertion, including the suggested ground wait.
|-
| ASC / XFER / TOTAL || Estimated fuel in kg: waiting plus powered ascent, the subsequent ideal orbital transfer, and their sum. A shortfall is shown separately. These figures are not all-inclusive fuel reserves.
|-
| MEET -5m / MEET +5m || Estimated fuel for deadlines five minutes earlier and later. The initial fastest result compares these at its selected departure; a manual-MEET search compares sampled departures for each deadline. Change the MEET row to select one of those deadlines and recompute its departure recommendation. NO FIT means no accepted candidate was found in that comparison, not proof that every possible trajectory is impossible.
|}

The comparison uses current loaded mass, available thrust, engine spool, airfoil curves, Vieneo rotation/gravity and the current measured atmospheric conditions with an altitude temperature/density model. It keeps the current landing-gear drag throughout the forecast and holds the chosen steering policy; retracting gear or changing steering alters the flown result. Changing weather, turbulence, clouds, terrain, detailed bank/elevator dynamics, attitude-RCS fuel and later rendezvous correction fuel are not included. The orbital transfer portion uses the existing instantaneous-burn estimate with a finite-burn time allowance. A ground RENDEZVOUS automatically solves that portion again from actual insertion state and fuel. Standalone PARKING ORBIT ends at insertion and requires selecting RENDEZVOUS separately.

A '''VTOL READY''' indication describes current ascent-controller readiness. It does not turn an unavailable or fuel-short MEET comparison into an approved whole-trip plan. The altitude/distance plot compares the modeled powered climb with measured flight history; a forecast is not a guarantee of the flown path. The ground comparison normally stops after liftoff. If manual departure occurs before the automatic MEET search finishes, DOR can estimate the remaining climb from the measured airborne state. Airborne ascent shows live pitch, thrust, target TAS/climb, IAS/AFT and fuel used.

=== Scheduled launch and airborne pickup ===
'''LAUNCH AUTO''' is the default. Select it with the normal Shift + arrow controls. With VTOL ready, engaging DOR during a pending comparison arms '''ARMED / COMPARING LAUNCHES'''. It issues no thrust or attitude command until a completed solution has been accepted and its launch countdown reaches zero. A completed estimate must have been checked against current inputs within 30 seconds, offer a future departure (or a current NOW recommendation), and fit the modeled fuel. '''NO LAUNCH AT SELECTED MEET''', '''REFRESH LAUNCH ESTIMATE''', '''LAUNCH TIME PASSED''' or '''LAUNCH FUEL SHORTFALL''' means DOR has not accepted the departure. Review the condition and re-engage after correcting it. '''LAUNCH NOW''' evaluates immediate departure when you choose the takeoff time yourself; ground RENDEZVOUS still requires the completed, fuel-fitting immediate-departure estimate. Standalone PARKING ORBIT NOW does not require a rendezvous estimate.

While armed, DOR commands no thrust or attitude change and does not operate the brakes. Remain parked on the clear departure area. Engagement authorizes automatic liftoff at the committed time; it does not obtain ATC clearance. If clearance is still pending, leave DOR off. DOR off or manual attitude/thrust input cancels the wait. Leaving the ground early also cancels it. Changes to the target/trajectory, steering, plan, power, vehicle/configuration, or material weather/performance inputs can cancel the wait rather than launch using an invalid forecast. Idle fuel use is accounted for. A missed timer requires rearming; DOR does not launch late automatically.

'''Manual ATC departure:''' select MODE RENDEZVOUS and MEET while still on the ground, leave DOR off, and take off manually. The pending ascent leg is retained for airborne pickup. Choose standalone MODE PARKING ORBIT instead if you want guidance only as far as a parking orbit. Once you want DOR to take over and ASCENT READY is shown, engage it. Airborne engagement immediately initializes guidance from your current position, velocity, attitude and loaded mass; LAUNCH AUTO does not make an airborne vehicle wait for the old ground time or repeat the ground liftoff. For RENDEZVOUS, engage only when cleared to follow the orbital direction. In standalone PARKING ORBIT, STEER AFCS can retain the assigned HDG/NAV departure until you select STEER ORBIT.

Pickup still needs valid current vehicle/air data and the supported configuration. Engagement is refused above 95% Vne, at 200°C AFT or hotter, or more than 50 km above the selected parking-orbit altitude. Those are controller eligibility limits, not proof that every accepted flight can recover. The ground timing/fuel forecast no longer describes a manually flown departure. A retained ground RENDEZVOUS continues automatically after insertion, using the achieved orbit and original absolute MEET; an infeasible transfer stops with a reason. Standalone PARKING ORBIT ends at insertion. For administrators, automatic mission recording includes the armed wait and launch countdown.

=== Recording an ascent ===
These recording controls require an administrator account.
In clients with '''REC ON (FLIGHT)''', administrators can use REC in every objective, including when '''ASCENT PROFILE REQUIRED''' is displayed. Recording observes the flight; it does not engage DOR, supply an automatic ascent pitch/throttle schedule or change ATC routing. A recording is calibration evidence, not an executable profile loaded into the ship.

# Before takeoff, select the intended station or spacecraft and open DOR. Select '''REC''' with Shift + Up/Down, then press Shift + Left/Right. With no proposed path, the row reads '''REC ON (FLIGHT)'''.
# Fly your normal comfortable ascent using manual controls or appropriate existing Autoflyte modes. Follow ATC headings/fixes and make your normal gear, flap, throttle and pitch changes. There is no required 15-degree or 60-degree test attitude.
# Leave REC on through the thin-atmosphere transition and orbital insertion, including any later DOR maneuver. Changing target, planning controls, VIEW or MFD page does not stop a FLIGHT recording. It remains flight-only even if a plan subsequently becomes available.
# Once established in the intended orbit, turn '''REC OFF'''. Keep both matching '''DOR-N.csv''' and '''DOR-N-plan.csv''' from '''OrbitLogs''' beside the running executable. Note the vehicle, starting load and any unusual weather or ATC interruption when returning the files.

The flight CSV records current mass/fuel, available and delivered thrust, actual pitch/roll/heading, angle of attack, air-relative flight-path angle, radial climb speed, tangential inertial and ground-relative speed, air-data freshness, IAS/TAS, dynamic pressure, AFT, configuration and Autoflyte modes. It distinguishes vehicle attitude from velocity direction. The companion file contains the capture origin and any available current/target trajectory context; '''it contains no invented reference ascent'''. Recording stops on REC OFF, loss of administrator permission, vehicle/simulator state reset, client exit, a file error or the size cap. Copy both files before further tests reuse their slot.

If a proposed path exists when REC starts, the row instead reads '''REC ON (REF)'''. That captures a frozen reference and follows the stop rules under [[#Recording a manual entry test|manual reference recording]]. REF recordings end when the target or planning controls change, or when DOR execution begins.

== Change or circularize your orbit ==
[[File:Orbit-MFD-adjust-size-msl-20261016.png|thumb|center|600px|'''Scenario 3: circularize using MSL altitude.''' With e = 0, the selected SIZE of 937.0 km MSL matches the final AP and PE. The nearly circular starting orbit needs only a small correction. Fresh labeled scenario render from the instrument code, not a live flight.]]
# Select '''MODE → ADJUST ORBIT'''.
# Choose '''LOCK NONE''', '''LOCK AP''' or '''LOCK PE'''. Locking an apsis preserves its selected radius while you change eccentricity. It does '''not''' mean “wait to burn at that apsis.”
# Change '''e'''. With LOCK NONE, also change '''SIZE'''. Shift+C on the e row requests a circle; without an apsis lock it uses the planned first-burn radius when available, otherwise your current radius.
# Choose the departure rule under '''START'''. Compare the green current orbit with the amber requested orbit, AP/PE, burn count, fuel and warnings.
# Engage DOR when satisfied with a valid plan, or use the plan as a reference for manual flying.

'''START NOW''' asks for a solution from your current position; you do not have to wait for apoapsis or periapsis. '''START AUTO''' compares a limited set of candidate departure times, including apsides for orbital adjustment, and chooses the lowest delta-V among valid candidates. It is not a search of every possible launch window. '''START AT TIME''' exposes an '''IN''' countdown that you can adjust.

If the requested orbit does not pass through the departure point, the planner may propose a transfer and a second burn to establish the new shape. A request that intersects the surface is rejected. SIZE changes in 100 km MSL-altitude steps, from 100 to 50,000 km MSL; e changes in 0.01 steps. For example, SIZE 600.0 km MSL with e = 0 requests a 600 km circular orbit. You do not add the planetary radius. With nonzero e, SIZE is the midpoint of the AP and PE altitudes, so check both endpoints and PLAN MIN ALT before execution.
<div style="clear:both"></div>

== Rendezvous with a station or spacecraft ==
For a surface departure, use [[#Ground-to-rendezvous mission|Ground-to-rendezvous mission]]. The steps below describe a rendezvous beginning in free flight, after the ascent leg is complete.

Orbital pressure advisories trigger above '''10 Pa'''. This operating tolerance applies consistently to current-coast, transfer, target and live DOR pressure checks, including OVERFLY's pressure criterion. [[YSP]] at 118 km produces approximately 6.3 Pa in the existing client density model, so its orbit alone no longer raises ATMOSPHERIC TARGET. The separate red below-100-km warning and OVERFLY minimum altitude still apply. Targets explicitly in atmospheric-flight reference mode still receive a target warning. Fuel, thrust, orbital-direction and finite-burn checks remain separate; this threshold change does not alter station fuel use or simulate heating.

[[File:Orbit-MFD-plane-20261015.png|thumb|center|600px|'''Scenario 4: a station in a different plane.''' PLANE DIF is about 38°. The cyan orbit and amber transfer leave the green orbital plane; the station does not need to be directly overhead.]]
# Select the target on the navigation/target instrument, then choose RENDEZVOUS here.
# Set '''MEET''' to the desired future arrival time. Each adjustment changes the requested interval by five minutes and establishes a new countdown. The adjustment uses the remaining time currently shown, with limits of 30 seconds to six hours.
# Compare START NOW, AUTO or AT TIME. If no clear transfer is found, change the arrival or departure time.
# Use PLANE 3D or EDGE-ON to inspect the plane change, and ORBIT to inspect the transfer shape. Review both burns and the fuel estimate.
# Engage DOR to execute the selected solution. Continue monitoring the target and warnings.

The planned meeting point is approximately '''5 km behind the target along its trajectory'''. It is a rendezvous staging point, not a docking port or a command to fly into the station's center. Stations follow their modeled motion. Another spacecraft is predicted to coast; if it maneuvers, the original prediction is no longer reliable.

After rendezvous, use the normal close-approach and docking procedures. The Orbit page does not obtain docking clearance or perform docking. [[TVM]] remains a separate target-relative velocity control.
<div style="clear:both"></div>

=== Planning inside a station control area ===
[[File:Orbit-MFD-bubble-20261016.png|thumb|center|600px|'''Scenario 11: undocked inside a station control area.''' The ORBIT phase and maneuver estimate remain available. This labeled scenario uses a reconstructed station-relative position and velocity.]]
Within a station's control area, a station-relative coordinate frame is used for smooth motion. Entering it does '''not''' mean the ship is docked. You can plan and execute orbital maneuvers while undocked inside it, and select another undocked spacecraft in a station control area as a rendezvous target. Entering or leaving the control area alone does not cancel DOR. Actual docking at a station permits planning but blocks DOR arming and execution. Previews use the ship's current position and velocity carried by the station. You can inspect RENDEZVOUS, ADJUST ORBIT, OVERFLY and SURFACE PLAN, including their time controls, while attached. Undock before engaging an executable orbital plan; undocking alone does not arm DOR. The selected deadline remains a countdown, so review the updated solution before engagement. Docking during execution cancels DOR.

Orbit reconstructs a ship's state from the station's modeled instantaneous motion plus the ship's measured relative motion. This avoids the jumping orbital elements caused by subtracting two rounded station positions to estimate velocity. It applies regardless of whether the selected target is a station, a spacecraft or a ground point; no display smoothing delays the values.
<div style="clear:both"></div>

=== Follow DOR through the burns ===
DOR follows the selected executable orbital plan. '''SURFACE PLAN cannot engage DOR''', even when a route says MODEL FIT. [[#Automated entry alpha|REENTRY in the automated-entry alpha]] has a separate powered-entry controller. During ALIGN and active burns of executable orbital plans, DOR steers pitch and yaw with rotational RCS, points the nose along the commanded burn direction for forward main-engine thrust, and rolls wings level relative to Vieneo's local horizon. The existing flight director receives burn pitch/heading targets and a level-roll reference; Orbit adds no separate attitude-command panel. In WAIT/COAST these remain guidance for the next burn, not a direction the ship must hold. Near a vertical burn, the horizon roll reference is ambiguous, so the controller preserves a stable roll orientation. DOR does not turn on the aircraft Autoflyte autopilot to do this.

<gallery widths="420" heights="354" mode="traditional">
File:Orbit-MFD-burn1-20261015.png|'''Scenario 5: departure, 30 seconds after engagement.''' DOR BURN; TO GO is about 487 m/s. The B1/B2 rows retain the planned burn budgets.
File:Orbit-MFD-coast-20261015.png|'''Scenario 6: the same transfer coasting.''' B1 is DONE. DOR COAST applies no translation thrust and prepares guidance for the next burn; TO GO now refers to that next correction.
File:Orbit-MFD-burn2-20261015.png|'''Scenario 7: arrival correction.''' DOR ARRIVAL has begun before the planned meeting time. Live TO GO differs from the original B2 estimate as guidance corrects the actual trajectory.
</gallery>

[[File:Orbit-MFD-dor-align-20261016.png|thumb|center|600px|'''Scenario 19: ALIGN before thrust.''' A fresh, labeled scenario render from the actual executor, attitude controller and instrument drawing code, not a live client screenshot. DOR is engaged, EXEC and ALIGN are in their visible blink phase, and translation commands are held off while the ship turns. START NOW does not bypass alignment.]]

'''ALIGN''' uses rotational RCS before allowing a burn. It captures within 2 degrees with total angular rate below 0.5 degree/second for at least half a second; more than 5 degrees of attitude error or 2 degrees/second of angular rate returns it to ALIGN. The commanded slew rate is limited to 5 degrees/second per body axis, with braking based on available torque. These are Rise control settings, not an Earth aircraft envelope. Small velocity trims below 2 m/s within the same burn phase retain the established nose direction instead of chasing a reversing near-zero vector; bounded translation controls handle those trims.

The controller uses the vehicle's existing RCS force caps, inertia, lever arms, current mass, installed augmentation-system health, wing damage, electrical power and wear. Rotational effort consumes fuel through the existing propulsion model. DOR can use installed rotational RCS independently of the manual augmentation toggle and its IAS fade. It does not teleport attitude or grant extra torque. Main-engine spool-down and translation-RCS filtering still take time; holding commands off is not an instantaneous removal of residual thrust. The main engines do the bulk orbital acceleration. While aligned, transverse RCS supplies a proportional correction to the thrust direction; small terminal trims retain their separate translation authority. IDEAL duration/fuel and ALL USED measure different things: the former is a main-engine estimate, while the latter includes the fuel actually consumed by all thrusters and idle operation since engagement.

'''WAIT and COAST allow free attitude control.''' You may turn the ship in pitch, yaw and roll to look around while DOR remains engaged and the route stays armed. DOR does not force an immediate return to the next burn direction. With the controls released, gentle rotational RCS follows the changing local horizon, lowering the nose as a forward-facing ship travels around Vieneo. It preserves your chosen attitude relative to that changing horizon rather than forcing the nose onto the flight path or restoring level roll. This uses measured motion and planet rotation, not an Earth orbit rate or an altitude cutoff.

When the executor requests a departure, correction or arrival burn, DOR switches to '''ALIGN''', reacquires the burn direction and level roll, and waits for pointing/rate capture before allowing translation thrust. WAIT/COAST alone never command translation thrust. START NOW or reaching a scheduled burn time does not bypass ALIGN. Looking away may therefore add alignment time before the next burn, and the clearance check can refuse that delay. During active burns, remaining delta-V is recalculated from the actual state; it need not decrease smoothly or equal the original burn budget. Completion requires the controller to settle near its goal, so finite burns can finish later than the initial estimate.

==== Rendezvous completion and TVM ====
After a successful '''RENDEZVOUS''', DOR automatically hands control to [[TVM]] with '''TVM SET 0.000 km/s''', keeping the same selected station or spacecraft. The page reports '''RENDEZVOUS COMPLETE / TVM''' and the normal Autoflyte disconnect sound plays once as DOR switches off. This happens when the final position and velocity correction settles, not simply when MEET reaches zero or B2 starts.

TVM commands a velocity match with the selected target; it does not hold the 5 km trail position or provide collision avoidance or automatic docking. Monitor separation and take control for the final docking approach. A manual DOR cancellation or an automatic abort does not engage TVM. ADJUST ORBIT and OVERFLY finish with their normal DOR disengagement.

==== Powered correction clearance ====
DOR rechecks each correction from the measured state using a finite powered forecast with Vieneo gravity and the same guidance retargeting law. It budgets alignment as unpowered coast, reserves engine spool and reverser response time, then credits bounded available thrust. Main-engine authority includes current mass, wear, engine health, power and the existing engine derating; small trims use the weaker translation limit. WAIT and COAST receive no hypothetical thrust credit.

The powered-correction check retains surface clearance for RENDEZVOUS and ADJUST ORBIT and the stricter '''100 km / 10 Pa''' requirements for OVERFLY. OVERFLY still checks the remaining approach and continuing orbit and reduces optional position-closing commands that would spoil clearance.

The forecast is a bounded two-body estimate with constant mass and ideal steering after alignment. It is not a complete actuator, drag, lift, terrain or heating simulation. DOR rechecks when actual measurements change; unavailable authority, inadequate alignment time, or an unsafe powered response can still disconnect it. This vacuum correction forecast applies to the orbital leg. Powered launch/ascent and REENTRY use their separate controllers; final descent and landing remain manual.

[[File:Orbit-MFD-dor-powered-recovery-msl-20261016.png|thumb|center|600px|'''Scenario 20: powered recovery remains engaged.''' Fresh labeled render from the actual planner, executor and drawing code. ADJUST ORBIT requests a 500 km circle from a slow suborbital state; the unrelated selected station is not the objective. The negative current PE and red ATM PASS warning describe the unpowered coast. The powered correction passes its separate check. An independent finite-thrust regression with ideal steering and engine spool completes above 419.3 km, despite repeated rejection by the old coast-only guard. Synthetic example, not a live flight or reconstructed player telemetry.]]

If no qualifying correction exists, DOR clears its thrust and attitude commands, disconnects with the existing sound, and retains a reason such as '''DOR: NO CLEAR CORRECTION''', '''DOR: CORRECTION MARGIN LOST''', '''DOR: FINAL ORBIT UNSAFE''' or '''DOR: COAST CLEARANCE LOST'''. A delayed departure can report '''DOR: DEPARTURE COAST UNSAFE'''. Alignment checks the measured unpowered path for the estimated turning time and engine response, followed by the powered correction: '''DOR: ALIGN MARGIN LOST''' means it cannot safely spend that time turning. OVERFLY retains its atmospheric-clearance requirement; other orbital objectives retain their existing surface-clearance checks and atmospheric cautions. '''DOR: NO ATTITUDE CONTROL''' means the attitude data or required rotational authority is unavailable. '''Disconnecting does not recover an unsafe trajectory.''' Inspect your actual PE and warnings, then take over or select a different valid recovery plan.

Use DOR off to take over. Manual thrust-increase/decrease key commands also disengage it. Pitch/yaw/roll inputs in WAIT or COAST leave DOR engaged. During ALIGN or either active burn (BURN or ARRIVAL), a pitch, yaw or roll key command disconnects DOR immediately; joystick pitch, roll or yaw input outside the configured dead zone also disconnects it. Those disconnects use the existing Autoflyte disconnect sound. Stale guidance, invalid control data and Flight Freeze suppress rotational commands. Normal control resumes through the existing manual controls after disconnect. Changing planning values, losing/changing a rendezvous target, losing cockpit power, docking/landing, or changing/resetting the vehicle's flight state cancels execution. After a cancellation, inspect the reason and solve again before re-engaging. VIEW changes alone are safe to make during execution.

Every transition from DOR on to off plays the existing Autoflyte disconnect sound once. This includes normal plan completion, automatic aborts, manual takeover, switching to [[TVM]], and a disconnect caused by loss of cockpit power. Completion and abort messages remain visible so you can inspect the reason. Remaining off does not repeat the sound, and restoring power does not replay it; engaging DOR again re-arms the next disconnect. This behavior follows DOR engagement, without an altitude or airspeed cutoff, and also applies in the simulator.

== Pass over a ground point ==
[[File:Orbit-MFD-overfly-20261015.png|thumb|center|600px|'''Scenario 8: overfly.''' A surface point is selected, with a 900 km pass in 40 minutes and EXIT COAST. The ground track accounts for Vieneo rotating beneath the flight path.]]
# Select a surface waypoint, then choose '''OVERFLY'''.
# Set '''ALT''' above the spherical reference surface, in 100 km steps, and '''PASS''' time, in five-minute steps.
# Select '''EXIT COAST''' to continue on the transfer orbit after the crossing, or '''EXIT CIRCULARIZE''' to establish a circular orbit after passing the waypoint.
# Set START, inspect the ground track and orbit views, and review the burn estimates before using DOR.

On entering OVERFLY, the planner searches for an early viable PASS time using the selected ALT, EXIT and START settings. It checks the route and continuing orbit against the OVERFLY clearance requirements below, available fuel and the preview's burn-duration limits. Automatic PASS suggestions also exclude orbital reversals. It searches up to six hours ahead in 30-second intervals, refines the first viable interval to one second, and adds up to 30 seconds of headroom when that later candidate also passes the checks. This is a useful starting estimate, not a guaranteed global minimum or a guarantee of flight performance. Very narrow windows can be missed. It does not minimize fuel.

While searching, '''FINDING PASS TIME''' replaces the plan and DOR cannot engage it. '''NO VIABLE PASS IN 6H''' means no candidate met these criteria in the bounded search; it does not prove that no possible route exists. Change ALT, EXIT or START, or choose a manual PASS time to inspect other estimates. Weather at the selected point is not an input to the transfer solver.

The initial countdown stays fixed once selected. Until you edit PASS directly, changes to ALT, EXIT or START/IN request a new suggestion. After a direct PASS edit, your chosen deadline is retained, including an invalid or warning-producing one; the planner does not silently move it back into a valid window. Decrease or increase the displayed remaining time in five-minute steps (30 seconds to six hours). To request another automatic starting estimate, leave OVERFLY and select it again. VIEW changes do not restart the search. Automatic suggestions never change an executing DOR plan; manually changing planning values still cancels execution.

''The older illustration above demonstrates the layout, not automatic PASS initialization. The clearance illustration below is a labeled code-generated scenario, not a live-flight capture.''

'''Why a low pass may have no clear transfer:''' Reaching 200 km above the point is not enough if the approach dips into the atmosphere or the continuing orbit returns there. EXIT COAST requires the full continuing orbit to remain bound and clear. EXIT CIRCULARIZE adds an arrival burn, but cannot make an earlier atmospheric dip acceptable. Changing PASS, ALT or EXIT may produce a valid route. Manual PASS retains your requested deadline and may display a blocked trajectory; it cannot override OVERFLY atmospheric clearance. Long-burn estimates can still be inspected manually.

Overfly meets a moving ground location at a chosen time; it does not hover above it. A circularization burn belongs after the crossing and can change where the spacecraft travels afterward. The pass altitude is not clearance above local terrain.
<div style="clear:both"></div>

=== Overfly atmospheric clearance ===
OVERFLY checks the waiting coast, approach to the waypoint and continuing orbit. Each must stay at or above '''100 km MSL''' and have a conservative dynamic-pressure bound of '''10 Pa or less'''. EXIT CIRCULARIZE also checks the unbraked arrival path over an estimated response interval before crediting the final circular orbit. A clear later circle does not excuse an earlier low pass. The solver prefers a qualifying transfer over a cheaper atmospheric alternative.

The pressure estimate uses the client's 3.063 kg/m³ surface density, 7.5 km scale height and a conservative bound on air-relative speed at the lowest point of the checked arc. At orbital speed, this can require clearance higher than 100 km. These are operational planning checks, not a validated heating envelope, drag-integrated trajectory or guarantee of finite-burn performance. Vieneo's nitrogen/sulfur-dioxide/oxygen atmosphere is retained; no Earth heating coefficients or new atmospheric boundary are introduced. The published [[Vieneo]] scale height is 7.5 km, matching the client and server models.

Steady red '''PLAN MIN''', '''COAST MIN''' or '''CORRECTION MIN''' identifies which trajectory falls below 100 km, with its minimum altitude in km MSL. '''EXEC PATH <100km''' identifies another low path checked by the executor. These can warn while your present altitude is much higher. The current-coast indication clears at 105 km to prevent flicker; its displayed number remains the actual predicted minimum during that hysteresis interval. This does not relax the solver's 100 km limit. Ground/reset state clears stale orbital warnings. Pressure advisories such as '''COAST ATM q>10Pa''' stay amber when there is no low-altitude warning. Warnings remain visible during both EXEC blink phases and after an abort.

A blocked preview shows '''NO PLAN''', '''ATM PASS - NO PLAN''' and '''MIN … km / BLOCKED''' where a rejected trajectory is available. DOR cannot engage that preview. Atmospheric penetration remains possible to display for other orbital objectives, and the atmospheric stages of SURFACE PLAN remain planning-only; this OVERFLY restriction is not a blanket exclusion of atmospheric flight or reentry.

Cockpit '''Q''' is forward dynamic pressure in lb/ft²: Q = 2 is about 96 Pa, not 2 Pa. It is not a direct temperature or burn-up indication, and the planner's conservative arc-pressure bound is not the same as that instantaneous cockpit component.

[[File:Orbit-MFD-overfly-clearance-blocked-20261016.png|thumb|center|600px|'''Scenario 17: atmospheric overfly blocked.''' Fresh labeled render from the actual planner and instrument code. A synthetic 905 km orbit requests a 200 km COAST pass in 180 minutes, but the candidate falls to 65.3 km. The red MIN ROUTE ALT 65.3km MSL, atmospheric warning and NO PLAN identify the rejection before engagement; the independent retrograde/reversal caution remains visible. This is not a live client screenshot or a reconstruction of player telemetry.]]
<div style="clear:both"></div>

== Surface journey planning ==
For a ground or low-atmospheric departure, select point B on the normal target instrument. On this page choose MODE '''SURFACE PLAN''', then ROUTE and TRIP while on the ground, or PASS when already airborne. For a departure from orbit or an orbital station, use the [[#Reentry and atmospheric entry|REENTRY]] controls below instead. Docking prevents execution, not planning. SURFACE PLAN remains planning-only after undocking; a qualifying REENTRY plan in the automated-entry alpha can be executed.

'''Local trips:''' SURFACE PLAN shows '''NO PLAN / TOO SHORT''' when the departure and destination are less than 5 km apart, including their height difference. It does not generate a climb path, fuel estimate or initial time search for these trips. A coincident destination on the ground shows '''ALREADY AT B'''. Fly the local hop using ordinary flight controls or suitable Autoflyte modes; changing TRIP/PASS or forcing ATM, SUB or ORB does not create a local takeoff/hover/landing profile. This is a limit of the surface planner, not a vehicle flight limit. Orbital REENTRY and an entry already in progress are exempt.

{| class="wikitable"
! ROUTE !! Proposed profile
|-
| AUTO || Compare the three route families at the selected TRIP duration or PASS deadline. Choose the lowest estimated fuel among candidates that pass the simplified model checks. AUTO may choose a different family when the selected time changes.
|-
| ATM || A powered atmospheric profile, climbing to 20 km MSL, traversing toward B, then descending. Only offered for departures at or below 40 km in this initial model. It is not a simulation of wing-borne cruise.
|-
| SUB || Powered climb and boost, a ballistic coast with a surface-intersecting osculating orbit, then powered braking and descent. The coast ends before the intersection.
|-
| ORB || Powered climb and boost, a circular coast nominally at 400 km MSL, then powered braking and descent. This need not complete a revolution.
|}

'''TRIP is the requested travel duration before departure.''' While on the ground with REC off, it stays steady: TRIP 30:00 means a 30-minute journey starting when you depart. Waiting on the ground does not consume that allowance or make the same route require more thrust and fuel. At liftoff the deadline is fixed and the row becomes '''PASS''', counting down to arrival. For administrators, starting '''REC''' also fixes the reference at capture start, even if you are still on the ground; it must not slide forward during a calibration recording. Ending REC while still grounded restores the selected TRIP duration. Landing with REC off also restores duration planning. An already-airborne surface preview uses PASS from the time it is selected.

Adjust TRIP/PASS in five-minute steps using the value shown (30 seconds to six hours). This is a timing constraint, not an AUTO preference switch. The comparison shows each family's estimated fuel and MODEL FIT, THRUST LIMIT, FUEL LIMIT, IAS LIMIT or another reason. A forced ATM/SUB/ORB choice is retained even when invalid; AUTO does not silently replace it. If nothing fits, AUTO can display a rejected candidate for inspection. The upper-right header says '''INVALID''' in red; '''PLAN ONLY''' is reserved for a fitting preview, and '''NO PLAN''' means no candidate is available. The rejected path and estimates remain visible to help you adjust the timing; they are not achievable flight commands. Longer times are not guaranteed to help: gravity support consumes fuel and the search covers only a limited family of profiles.

On first selecting this objective, the module searches for an initial model-fitting trip time up to six hours: two-minute trial spacing, ten-second refinement of the first fitting bracket, and up to 30 seconds of headroom if that candidate also fits. FINDING TRIP TIME identifies the grounded search; NO FITTING TRIP IN 6H means this bounded search found none, not that every possible trajectory is impossible. Airborne previews use FINDING INITIAL PASS / NO FITTING PASS IN 6H. A manual edit keeps your chosen duration or deadline, including an invalid one. Changing ROUTE requests a new suggestion only before the time has been edited manually. Leaving and reselecting SURFACE PLAN restarts automatic initialization. The search never rewrites an executing orbital plan.

The amber path joins the measured initial state to B's position at PASS, accounting for Vieneo's rotation. PLANE 3D and TRACK can show the whole journey even before takeoff. For space profiles, markers 1–4 indicate the end of climb, start of coast, start of braking and start of descent/entry; B is the future destination. These are preview phase boundaries, not flight-director commands. ATM has only its final B marker. The top flight-phase label describes your current state, independently of the proposed route.

{| class="wikitable"
! Surface readout !! Meaning
|-
| RANGE || Current great-circle distance to B, in km; not full path length. Below 10 km, one decimal place is shown (for example, 0.5 km).
|-
| TOP || Highest sampled profile altitude, km MSL above the spherical reference surface.
|-
| TOTAL || Integrated powered acceleration, expressed as delta-V in m/s, including gravity support and modeled body drag. This can greatly exceed the vehicle's speed; it is not a cruise-speed command.
|-
| FUEL || Estimated kg for the selected ideal profile, including idle flow during coasts.
|-
| THRUST || Peak fraction of available main-engine thrust. More than 100% is shown in red and invalidates the candidate. If IAS also exceeds its limit, the reason reads IAS / THRUST LIMIT so neither failure is hidden.
|-
| MAX q || Highest sampled dynamic pressure in kPa, based on mass density and air-relative speed. It is informational, not a validated heating or structural limit.
|}

'''MODEL FIT is not flight clearance.''' The preview uses Vieneo gravity and rotation, the client's 3.063 kg/m³ surface density and 7.5 km density scale height, vehicle main thrust, altitude efficiency, fuel flow, wear and empirical body drag. The published [[Vieneo]] scale height matches the 7.5 km used by both client and server. Cruise at 20 km, the 100 km powered-segment interface and nominal 400 km orbital coast are planning choices, not atmospheric boundaries.

These ground-departure powered segments assume ideal thrust direction. They do not simulate RCS-axis limits, vehicle attitude changes, spool response, wing lift, wing/tail/wave drag, wind, clouds, weather avoidance, heating or terrain. ATM supports weight with thrust, so its fuel estimate is not a prediction of ordinary wing-borne Autoflyte cruise. Sampled geometry checks a reference sphere; it does not establish terrain clearance or that point B is a suitable landing site. Fuel comparisons and AUTO's choice are therefore comparisons within this simplified model, not a global optimum or a recommendation to fly the displayed path. Direction reversals remain visibly cautioned.

'''PLAN ONLY / ATM HANDOFF''' means the atmospheric stages require separate pilot/Autoflyte operation. SURFACE PLAN provides no automatic mode handoff, takeoff, atmospheric guidance, hover or landing. Orbital REENTRY has its own alpha controller described below. The end-state is an ideal planning endpoint at B, not a landing command. Pressing DOR on a surface preview leaves execution off and plays the Autoflyte disconnect cavalry sound once to acknowledge the refusal. Holding the key does not repeat the sound. Existing executable ADJUST ORBIT, RENDEZVOUS and OVERFLY plans remain separate.

The dated scenario illustrations below use the earlier PASS label before takeoff; current ground previews display TRIP.

<gallery widths="420" heights="354" mode="traditional">
File:Orbit-MFD-surface-atm-20261016.png|'''Scenario 13: ATM, 500 km in 60 minutes.''' Local ascent preview and route comparison. The large TOTAL includes ideal powered gravity support. Labeled synthetic render, not a live flight.
File:Orbit-MFD-surface-sub-20261016.png|'''Scenario 14: SUB at the same PASS.''' Whole-route PLANE 3D view while still on the ground, with ballistic coast and numbered phase boundaries. Labeled synthetic render.
File:Orbit-MFD-surface-auto-20261016.png|'''Scenario 15: AUTO, 4000 km in 90 minutes.''' ORB fits the simplified model while ATM and SUB exceed thrust. This demonstrates the PASS constraint, not certified flight performance. Labeled synthetic render.
</gallery>

== Reentry and atmospheric entry ==
Select the intended surface waypoint on the usual navigation instrument. For an orbital departure, choose '''REENTRY'''. Planning is available while docked; undock before engaging DOR. The automated-entry alpha can fly an '''ENTRY READY''' profile from at least 100 km MSL to its atmospheric handoff. It requires current air data, main/reverse and translation thrust, and a clean configuration: gear, flaps and spoilers retracted, bay closed and no significant icing. A plan lacking those inputs, or newly planned below 100 km, remains '''PLAN ONLY'''. Earlier calibration clients label this mode REENTRY PLAN and cannot execute it.

The initial handoff is '''30 km MSL''' at '''0.5 km/s TAS''', upstream of the selected surface point. These are adjustable test conditions, not universal safe limits. The handoff is level flight aimed toward the surface point; it is not touchdown. '''HANDOFF''' counts down to that atmospheric transition, not touchdown at the waypoint. The planner estimates the remaining glide reach using the vehicle's clean-air aerodynamic data. FINAL HOLD retains that general-purpose handoff. The arrival-planning alpha also offers runway/hover previews described below. None establishes obstacle clearance or an achievable unpowered glide all the way to B.

{| class="wikitable"
! Control !! Meaning
|-
| ROUTE AUTO || Compare direct powered entry and coast-then-entry at the selected handoff time. Among model-fitting candidates, choose the lower estimated fuel requirement. This is a bounded search, not a global optimum.
|-
| ROUTE ORB || Remain on the measured current orbit for a selected coast, then enter. The preview does not first force the ship into a nominal 400 km orbit.
|-
| ROUTE SUB || Begin a direct powered entry after allowing time to align, without a discretionary orbital coast. Its feasibility depends on the requested time, position, velocity, weight and available thrust.
|-
| H ALT || Atmospheric handoff altitude, km MSL. Adjust in 5 km steps, from 15 to 60 km.
|-
| H TAS || Air-relative handoff speed, km/s. Adjust in 0.1 km/s steps, from 0.1 to 1.5 km/s. This is not IAS or orbital speed.
|-
| HANDOFF || Requested remaining time, adjusted in five-minute steps. A shorter time may require greater powered acceleration or braking, or have no fitting candidate.
|-
| REC || Administrator-only: record a manual test and the selected reference plan without engaging DOR. See below.
|}

ATM remains an atmospheric-departure option in SURFACE PLAN. It is not offered as an orbital entry shortcut. Ground/low-atmospheric SURFACE PLAN retains its separate AUTO / ATM / SUB / ORB route families and TRIP/PASS arrival at B; the new entry controls describe an atmospheric handoff before B.

'''D''' marks deorbit/start of the powered profile, '''E''' the sampled crossing of 100 km, and '''H''' the atmospheric handoff. The 100 km marker is an operating reference, not a hard atmosphere boundary. Gray is the planned coast on the current orbit; amber is the proposed powered entry. The graphic area remains the same size in every view.

'''REV''' and '''RCS''' show peak required fractions of the corresponding available thrust. The entry model uses current loaded mass, fuel consumption, main-engine condition, separate forward/reverse and up/down/side limits, engine response, Vieneo gravity/rotation/density, and the client's clean wing/tail/body and Mach-dependent aerodynamic model. It estimates AFT from the client's heat-transfer model. '''MAX q''' is the modeled effective aerodynamic pressure in kPa, including the client's Mach augmentation; it is distinct from ambient-density dynamic pressure. Cockpit Q is in lb/ft². '''LOAD''' is estimated non-gravitational acceleration in standard Earth g units.

The alpha's preview reports peak IAS as a percentage of Vne and peak predicted AFT. It requires at most '''95% of Vne''', '''200°C predicted AFT''' and '''95% of each available thrust axis''', plus its engine-response and attitude-rate checks. These are controller settings for validation, not newly established vehicle limits. AFT forecasting uses Vieneo's model and the current measured temperature/wind; it does not forecast changing weather, clouds or turbulence along the route. '''ALPHA / NO TERRAIN CHECK''' remains a limitation: the profile has no terrain or obstacle database and no automated final-descent or landing controller. Keep [[Atmospheric_Reentry|entry procedures]], AFT, IAS/Vne and flight path in view.

'''Entry readiness and configuration:''' A route can fit the fuel, thrust and temperature limits while the ship is not ready to execute it. '''PLAN ONLY''' with an amber '''CONFIG LANDING GEAR''', '''CONFIG FLAPS''', '''CONFIG SPOILERS''', '''CONFIG AIRFRAME ICE''' or '''CONFIG CARGO BAY''' identifies the configuration that must be corrected. Air, thermal or performance data problems have their own messages. Retract gear, flaps and spoilers fully, close the bay and clear icing before entry. Landing gear must also have confirmed status: a GEAR DISAGREE condition or unknown gear status prevents entry even if the gear appears retracted. The DOR page continues to show CONFIG LANDING GEAR. '''READY / ENTRY READY''' and '''ARM DOR TO EXECUTE''' indicate that the entry readiness checks pass; selecting AUTO does not engage DOR.

If gear prevents engagement, DOR remains off, announces its disconnect sound and queues '''"Config. Landing gear."''' The refusal is also shown in red. Extending gear or losing confirmed gear status during an executing entry invalidates the clean profile and disconnects DOR, releasing its attitude and thrust commands with the same specific alert. '''Take control after a disconnect; DOR does not retract gear or automatically re-engage.''' A new entry still requires an origin at or above 100 km MSL. The queued gear phrase is discarded if the gear is confirmed fully retracted, power is lost, or the relevant vehicle/plan changes before playback. Normal gear use after the achieved atmospheric handoff does not trigger this entry-specific warning; the ordinary aircraft-mode limits still apply.
=== Automated entry alpha ===
# Start with a clean ship in orbit and select the surface destination. Use AUTO, H ALT 30 km and H TAS 0.5 km/s for the initial test.
# Adjust HANDOFF until the preview says '''ENTRY READY'''. Shortening it asks for a faster journey; '''IAS RESERVE''', '''AFT RESERVE''', '''THRUST RESERVE''', '''ATTITUDE RATE''' or '''SPOOL LIMIT''' identifies why a candidate is rejected. A longer time is not guaranteed to fit every geometry. Check fuel and the whole proposed path.
# Undock if necessary, then engage DOR. AUTO selects a route; it does not engage DOR by itself. For administrators, an accepted entry starts a CSV capture automatically, so REC is not required for this test. Other accounts fly the same entry without diagnostic recording.
# During coast DOR pre-aligns for entry. During '''POWERED ENTRY''' it keeps the nose into the air-relative direction of travel with a small positive angle of attack, using forward or reverse mains and bounded translation RCS. Braking does not require pointing the tail into the airflow. Manual attitude input during ALIGN or powered entry disconnects DOR.
# '''ENTRY LIMIT / BRAKING''' means the short-term forecast predicts excessive IAS or AFT. DOR gives braking and descent control priority over the requested time; HANDOFF may be missed. This is active protection, not a guarantee against every disturbance or an instruction to ignore warnings.
# At the achieved handoff, expect the ordinary DOR disconnect sound once. FINAL HOLD transfers to ALT/HDG/TAS hold; a valid runway FINAL selection transfers to ALT/NAV/TAS hold on the inbound course. The autopilot holds the selected MSL altitude and the entry autothrottle holds the selected TAS. It does not descend toward or land at B. HANDOFF PASSED alone is not completion: altitude, airspeed, descent rate, position and attitude must also converge.
# To resume normal flight, cancel the entry TAS hold with the DOR control or by moving a physical throttle lever. The altitude and heading holds remain until changed or disconnected. Disconnecting the aircraft autopilot also ends the TAS hold. In the arrival/FPA alpha, TAS hold continues with HDG, NAV or LOC and PIT, VS, ALTm, ALTa, FPA or G/S. Selecting SpeedPitch, Roll, an off mode or TVM ends it. Ordinary gear/flap/spoiler changes after handoff retain TAS hold with updated drag compensation; icing, an open bay, unavailable/stale air data or lost authority still cancel it. Change H TAS on the DOR page to adjust the held speed. Take over for ATC routing, descent and approach; a fixed TAS can produce increasing IAS as you descend, so reduce it appropriately.

For administrators, automatic recording continues through the handoff holds until they are cancelled. Retain both matching CSV files for review of the actual response, predicted heat/IAS, force commands, available thrust and handoff modes. Start testing with a comfortable preview, then shorten the requested time on subsequent flights; the alpha is not a certified fastest possible entry.

=== Arrival planning and final approach ===
These controls require the arrival/FPA alpha, which is newer than the ascent-recording alpha. They are available on REENTRY, not on ground-departure SURFACE PLAN. Choose '''FINAL''' with the usual Shift + arrow controls before engaging DOR. A new surface target resets FINAL to HOLD; selecting a destination does not silently authorize an approach or landing.

{| class="wikitable"
! FINAL !! Preview and handoff
|-
| HOLD || The default: atmospheric entry followed by ALT/HDG/TAS hold.
|-
| ILS (PLAN) || Select a live, fully serviceable runway ILS or an outer-marker/LOM waypoint with one unambiguous associated inbound runway. The preview uses the marker's distance when available, otherwise the selected final distance (initially 10 km). Its final gate is 50 m below the nominal 3° beam for an eventual level intercept. The displayed ≤30° intercept is a planning objective for the manual final, not an automatically enforced capture condition.
|-
| VISUAL (PLAN) || Select a runway threshold with a published inbound heading. A second FINAL row adjusts the extended-centerline distance from 6 to 30 km in 2 km steps; the initial value is 10 km. The gate follows a 3° ray above the runway's local tangent plane, corrected for Vieneo's curvature. Ten km is approximately 0.54 km above the runway; the readout is MSL, so runway elevation is added.
|-
| VTOL (PLAN) || Preview a hover gate 100 m above the selected surface point. Current vertical-thrust authority must exceed the weight-support requirement at the loaded mass. This is not a terrain-clearance check or a commanded hover/landing.
|}

Runway selections position the atmospheric entry handoff upstream on the runway's extended centerline and point its ground-relative path inbound. The automated portion still ends at '''H ALT / H TAS''' (initially 30 km / 0.5 km/s), not at the low final gate. A successful runway entry transfers to '''ALT NAV SPD / FINAL MANUAL'''. The gray final line and '''FINAL … km MSL / MANUAL''' altitude are advisory geometry. DOR does not execute that line, descend to the LOM, arm LOC/G/S, flare or touch down. VTOL also retains the atmospheric altitude/heading/speed handoff; it does not switch to TVM or descend automatically.

After handoff, manage the remaining energy and descent with the aircraft controls. For an instrument approach, select the correct runway/radio course and use the normal LOC/G/S controls when appropriately positioned below the glidepath, within a 30° inbound intercept and at a suitable speed. A LOM is a fix, not the runway threshold or the origin of the ILS beam. Airport names and proximity alone do not identify a runway. '''SELECT RUNWAY / LIVE ILS''' or '''SELECT RUNWAY THRESHOLD''' means the required data are absent or ambiguous. Changing associated approach data during DOR entry stops execution with '''APPROACH DATA CHANGED'''.

=== Flight path angle (FPA) ===
The normal vertical flight-director cycle is '''PIT → FPA → VS → SPD → ALTm → ALTa → PIT'''. FPA follows Pitch directly when available. At ground contact, below 0.010 km/s horizontal groundspeed, or with invalid path data, the vertical-mode key skips FPA and continues to VS, SPD and the available altitude modes. ALTa is skipped when the required ground-height data are unavailable; G/S remains separately armed. FPA captures the current ground-relative climb/descent angle. Use the existing vertical-target increase/decrease controls to adjust it; the selected signed angle appears in the flight-mode display. The selectable range is −15° to +20°. For a descending 3° path, select −3°.

FPA is the angle of travel relative to the local ground tangent, not nose pitch or angle of attack. The controller adjusts pitch as the measured path changes; its pitch command changes by at most 3°/s. Aircraft response, wind, lift and available thrust still determine whether it can achieve the selected path. FPA controls neither lateral course nor speed, and does not provide terrain avoidance, a flare or touchdown. It can be used as a flight-director cue or with the normal aircraft autopilot; it is not an orbital insertion solver or a DOR ascent profile.

At ground contact, below 0.010 km/s horizontal groundspeed, or with invalid path data, FPA returns to PIT at the current pitch. It does not automatically re-arm: select FPA again after establishing forward flight. This prevents a hover or nearly vertical trajectory from being treated as an ordinary forward flight path. Ground-relative geometry remains defined at high speed, but selecting FPA does not establish atmospheric control authority in suborbital coast or orbit.

The CSV records selected FPA/course, AFCS ground/vertical speeds, arrival choice, final-gate geometry and its advisory status. The companion plan file labels the final line '''final_advisory_not_executed'''. Actual lateral/vertical thruster output remains recorded; a human's recorded firings are not replayed as the optimal control sequence.

=== Recording a manual entry test ===
These recording controls require an administrator account.
# Select the target, route, handoff time, altitude and TAS; wait for an inspectable proposed path.
# Select REC and press Shift + Left/Right once to turn recording on. With the proposed path available, the row reads REC ON (REF). This does not engage DOR or command the ship.
# Fly the test manually or with appropriate existing Autoflyte modes. Changing VIEW or leaving the MFD page does not stop recording. The CSV reference stays fixed at recording start even while the live preview updates.
# Turn REC off to finish. Changing planning controls, changing target, resetting/changing the vehicle, or engaging an executable DOR plan also ends the manual capture. A new test requires REC on again.
# Return both matching files from the '''OrbitLogs''' directory beside the running executable: '''DOR-N.csv''' and '''DOR-N-plan.csv'''. The first contains actual flight data and timed comparison values; the second contains the frozen reference trajectory.

Four reusable file slots bound retention; older captures can be replaced by subsequent starts. A slot stops at 128 MiB rather than discarding its beginning. REC FILE ERROR or REC FILE FULL means capture has stopped. Current clients can start REC ON (FLIGHT) without a reference; older entry-calibration clients instead display REC WAIT FOR PLAN. Copy the pair you want to keep before beginning more tests. No automatic upload occurs.

New captures separately integrate main-engine, translational-RCS, attitude-RCS and idle fuel consumption, and record the available orbital MECO estimate. The tank-based ALL USED remains the measure of fuel actually lost; integrated component totals can differ slightly because of fuel-tank rounding.

The CSV includes time, target, mass/fuel, position/velocity, engine and RCS outputs, air-relative velocity, IAS, Mach, dynamic pressure, measured AFT and reference errors. The automated-entry alpha also records the predicted AFT/IAS reference, the live protection forecast, controller limits, force requests and handoff holds. Earlier calibration captures contain measured AFT but no predicted temperature reference. An expired HANDOFF or end of recording does not prove that the entry was completed successfully.

== Warnings and unavailable plans ==
{| class="wikitable"
! Message !! Meaning / next action
|-
| VACUUM ESTIMATE || An orbital estimate is available. It assumes two-body coasting between instantaneous planned burns.
|-
| LONG BURN - ESTIMATE / FINITE BURN NOT CORRECTED || The preview's instantaneous-burn approximation is weak for the estimated duration. Live DOR corrects from actual state, but the original time, path and fuel are estimates.
|-
| PLAN ATM PASS / COAST ATM q>10Pa / CORRECTION ATM q>10Pa / CURRENT ATM q>10Pa / ATMOSPHERIC PASS / ATMOSPHERIC TARGET || Pressure advisory above 10 Pa, or a target explicitly in atmospheric-flight reference mode. The actual predicted coast is refreshed during execution. Other orbital modes can retain atmospheric estimates; OVERFLY must satisfy its stricter clearance requirements.
|-
| PLAN MIN / COAST MIN / CORRECTION MIN / EXEC PATH <100km || Steady red low-altitude warning identifying the affected trajectory. The numerical minima are km MSL. COAST MIN assumes no further burns and can differ from PLAN MIN ALT. The current-coast warning clears at 105 km; this is annunciation hysteresis only.
|-
| ATM PASS - NO PLAN / MIN … km / BLOCKED || An inspectable OVERFLY candidate fails atmospheric clearance. Change PASS, ALT or EXIT; DOR cannot execute it.
|-
| DOR: TIMING INTERRUPTED || A simulation frame took more than one second. DOR disconnects because its previous control commands cannot safely cover the interruption. Check the current flight state before re-engaging; this message does not identify the cause of the client stall.
|-
| DOR: NO CLEAR CORRECTION / CORRECTION MARGIN LOST / FINAL ORBIT UNSAFE / COAST CLEARANCE LOST / DEPARTURE COAST UNSAFE || Execution stopped because the updated trajectory or correction fails its checks. Thrust commands are cleared and the disconnect sounds once. The existing trajectory still needs pilot attention.
|-
| SURFACE INTERSECTION / NO CLEAR TRANSFER || The requested shape intersects Vieneo, or no acceptable transfer was found. Raise the requested periapsis or change the timing/objective.
|-
| INSUFFICIENT FUEL / PERFORMANCE UNAVAILABLE || Fuel or propulsion data do not support execution. A geometric estimate alone is not an executable DOR plan.
|-
| BURN TIME PASSED / ARRIVAL TIME PASSED || The selected deadline has passed. Edit the time to request a new one; these are real countdowns, not indefinitely rolling delays.
|-
| SELECT NAV TARGET / NO TARGET TRAJECTORY || Select a usable target, or choose ADJUST ORBIT.
|-
| DOR: UNDOCK TO EXECUTE || An orbital plan can be previewed while attached to a station, but DOR cannot arm or execute it until undocked. Undocking does not engage DOR automatically. SURFACE PLAN remains planning-only. A qualifying automated-entry REENTRY still requires undocking before execution.
|-
| NO DEPARTURE STATE / POWER OFF || The departure reference is unavailable or unsupported, or cockpit power is off. A valid station attachment permits previews; an unsupported containment frame does not.
|-
| ASCENT PROFILE REQUIRED || The selected vacuum orbital objective has no powered launch solution. Choose [[#Ground-to-rendezvous mission|MODE RENDEZVOUS]] for a continuous launch to an orbital target, or [[#Automated ascent alpha|MODE PARKING ORBIT]] for a standalone parking-orbit climb. Older clients require a manual ascent.
|-
| VTOL READY / ASCENT READY || The ascent controller is ready with the current inputs. Ground LAUNCH AUTO can arm while its comparison is running, but requires a completed, current, fuel-fitting solution before committing departure; ground RENDEZVOUS requires one for LAUNCH NOW too. This is not a full-flight fuel, time or terrain-clearance guarantee. See [[#Scheduled launch and airborne pickup|scheduled launch and airborne pickup]].
|-
| VTOL LIFT / ATTITUDE LIMIT / ASCENT DATA INVALID || Check loaded vertical-thrust authority, level ground attitude, configuration and valid current air data.
|-
| ASCENT LIMIT / IDLE || The short-term ascent forecast is at its IAS or AFT guard. Positive main thrust is reduced; monitor the actual path.
|-
| INSERTION COMPLETE / REPLAN || Standalone PARKING ORBIT has ended at the parking orbit. Select and review RENDEZVOUS separately to continue. A mission begun in ground RENDEZVOUS instead transfers automatically.
|-
| DOR: NO TRANSFER AT INSERTION / TRANSFER FUEL SHORTFALL / MEET BURN TIME LIMIT || The achieved insertion state cannot support the transfer at the original MEET with the remaining fuel/time. DOR stops; review the condition and a new plan before re-engaging.
|-
| DOR: MEET MISSED DURING ASCENT / MEET MISSED AT INSERTION / ASCENT TARGET INVALID / INSERTION TARGET INVALID || The mission has insufficient remaining MEET time or no usable orbital target. DOR stops rather than changing the deadline or treating parking insertion as rendezvous completion.
|-
| PLAN ONLY / ATM HANDOFF || The displayed candidate is preview-only; DOR cannot execute it. Ground-departure SURFACE PLAN remains preview-only. REENTRY needs a qualifying ENTRY READY profile in the automated-entry alpha.
|-
| INVALID / MODEL FIT / THRUST LIMIT / FUEL LIMIT / IAS LIMIT / IAS / THRUST LIMIT || Result of the surface preview’s simplified checks. MODEL FIT does not certify terrain, heating, weather, maneuverability or landing.
|-
| NO TERRAIN / HEAT CHECK || SURFACE PLAN and older calibration previews omit these checks. Automated-entry REENTRY predicts heat but still displays ALPHA / NO TERRAIN CHECK.
|-
| ENTRY READY / IAS RESERVE / AFT RESERVE / THRUST RESERVE / ATTITUDE RATE / SPOOL LIMIT || Automated-entry preview result. READY passes the modeled checks; other messages identify a rejection. None certifies terrain clearance or landing.
|-
| ENTRY DATA / CONFIG || Entry cannot execute with the current air data, configuration or departure altitude. Check clean configuration, valid measurements and an orbital departure.
|-
| ENTRY LIMIT / BRAKING || Active entry protection prioritizes braking and arresting descent over the requested handoff time. Monitor the actual trajectory.
|-
| MODEL FIT / HEAT UNCHECKED || Older calibration-client preview; it does not support automated entry.
|-
| HANDOFF BELOW TARGET || Raise H ALT above the destination elevation.
|-
| ENTRY DATA UNAVAILABLE / ENTRY GEOMETRY / NO COAST / ENTRY FIT || Required performance data or a fitting entry candidate is unavailable. Inspect the selected time, route and handoff settings.
|-
| REC FILE ERROR / REC FILE FULL || Capture stopped because of a file error or size cap. See [[#Recording a manual entry test|recording instructions]].
|-
| ENTRY FIRST / NO ROUTE AT THIS PASS || Direct ATM is outside its initial departure-height range, or no candidate was available at this deadline. Change ROUTE/PASS or use separate entry procedures.
|}

[[Category:Getting Started]]

Inventory

2026-10-14T22:01:05Z

reskin: Changed redirect target from Manifest to Category:Inventory

#REDIRECT [[Category:Inventory]]

Starskimmer

2026-10-09T16:24:11Z

reskin:

[[Image:starskimmer.jpg]]
== Specifications ==
{{SpaceVehicle
}}

[[Category:Spacecraft]]
[[Category:Development]]

MMAC

2026-10-09T16:23:44Z

reskin:

[[Image:mmac-wide.jpg]]
==== THE KING OF MODULAR MISSIONS RETURNS IN GLORY ====
== MMAC U-104 ==
The Multi-Mission Advanced Conveyance Utility-104 has been redesigned from the ground up as a complete modular system supporting a diverse range of mission specific needs, ensuring its placement for years to come as a workhorse of orbital operations.
<br>
<br>
[[Image:mmac-engine.jpg|512px|left]]
====SMALL PACKAGE. BIG PUSH.====
==ORPEX AP-2101 CLYDESDALE==
Gone are fixed primary thrust ports with overly complex ion shunting. Maneuverable, precise, efficient, and sporting the highest thrust to weight ratio available, the Advanced Propulsion 2101 Clydesdale engine will move your mountains.
<br clear="both"/>

[[Image:mmac-mod-crane.jpg|512px|right]]
====THE RELIEF OF MISSION SPECIFIC MODULARITY====
==DAPTAFORM™==
Continuing in ground-breaking proprietary technologies, our Daptaform™ unified connection system allows a vast number of vessel configurations and functions to meet your every need.
<br clear="both"/>

====INTERIORS THAT MAXIMIZE AWARENESS AND ENHANCE COMFORT====
==GOCLEAR™ ERGONOMICS==

[[Image:mmac-int-dash.jpg]]
====KEEP YOUR FOCUS ON THE WORK AT HAND====
==SPLIT-WRAP LIQUID-FUNCTION CONSOLE==
Gone is peering over and around bulky centered panels and controls. High-dynamic touch displays with user configurable positioning makes the U-104 a truly personal and adaptive experience.
<br clear="both"/>

[[Image:mmac-int-controls.jpg|512px|left]]
====FEEDBACK AND READOUTS AT YOUR FINGERTIPS====
==INTEGRATED CONTROL DISPLAYS==
Haptic feedback with dynamic control readouts give you more than just information. Extending your bio-presence to ship systems give ultimate awareness and natural reaction-states to maneuvers.
<br clear="both"/>

[[Image:mmac-int-panel.jpg|512px|right]]
====FIELD-FORWARD, DEEP-SPACE TOUGH====
==HYBRID MODULAR <br/> AND CORE CONTROLS==
Hardened against the toughest EM environments, and built to withstand the rigors of zero-G shipyards, Orpex has refined instrumentation and controls into a flexible palette to support our ever-expanding modular mission accompaniments.
<br clear="both"/>

====THE MMAC LEGACY IS FOUND IN THE GALAXY'S EVERY NOOK AND CRANNY====
==STOWABLE, INDISPENSABLE==

[[Image:mmac-context-ezdock.jpg]]
====OUT-OF-THE-BOX OPERATIONS ARE GO====
==ORBIT READY==
Whether for long-term station life-cycle planning or sudden operational necessity, the U-104 is quick-launch secure and capable of full-capacity missions without break-in time.

[[Image:mmac-context-bay.jpg|512px|left]]
====PACK'EM AND STACK'EM====
==A CARGO BAY'S FRIEND==
The U-104's core modules easily fit into standard cargo bays. Plenty of standard strap-down hardpoints make transporting the MMAC to and from a site easy and secure.
<br clear="both"/>

[[Image:mmac-int-door.jpg|512px|right]]
====YOU DEMANDED REAL-WORLD SOLUTIONS FOR OFF-WORLD PROBLEMS====
==ORPEX ANSWERED==
In the high-risk world of orbital operations, crew and commanders alike know the importance of reliability and excellence in design. The new MMAC U-104 integrates the latest devleopments in material, propulsive, and control technologies into one package that cannot be beat.

<br clear="both"/>

== Specifications ==
{{SpaceVehicle
|manufacturer=[[:Category:Orpex|Orpex]]
|role=Multi-Mission Advanced Conveyance Utility-104 (U-104); modular orbital work vehicle
|engine=ORPEX AP-2101 Clydesdale
|orbital_capability=Designed for orbital operations
|docking=Daptaform™ unified connection system for mission modules
}}

[[Category:Vehicles]]
[[Category:Spacecraft]]
[[Category:Orpex]]
[[Category:Development]]

DIHV

2026-10-09T16:23:06Z

reskin:

[[Image:DHIV_docked_with_TAC.png|thumb|right|400px|DIHV Docked at TAC Fueling]]

The [[DIHV]] ships (designation T-55) are superluminal [[:Category:Spacecraft|spacecraft]] used to transfer large amounts of passengers and materials between star systems. The DIHV ships currently dock with [[TAC]] when visiting [[Vieneo]] and is the only stop in the [[Yonmara]]n System.

The DIHV ship was invented and constructed as a military initiative by the [[United Stellar Republic]] through association with [[:Category:Luminauticon|Luminauticon]].

==Operation==
A DIHV ship does not exceed the speed of light in the strictest sense. It uses extra dimensional space in order to move between points in three-dimensional space faster than light does. These extra dimensions are described in [https://en.wikipedia.org/wiki/M-theory M-theory], which unites the constituent parts of ''Super String Theory'', which in turn unites ''Quantum Mechanics'' with ''General Relativity''.

== Statistics ==
{{SpaceVehicle
|manufacturer=[[:Category:Luminauticon|Luminauticon]] in association with the [[United Stellar Republic]] military initiative
|role=T-55 interstellar passenger and material transport
|cargo_capacity=217,756 MT
|passengers=6,506
|interstellar_capability=Superluminal travel through extra-dimensional space
|docking=[[TAC]] when visiting [[Vieneo]]; only stop in the [[Yonmara]]n System
}}

[[Image:DIHV Concept.jpg|thumb|500px|DIHV compared to E-10 (concept)]]
[[Image:DihvEffect.png|thumb|500px|DIHV Effect Observed]]

===History===
*3177-A (USV Terrania) has been in service since March 24, 2231
*3811-A (USV Valley Forge) has been in service since August 16, 2244

==Version History==
<mantis>bugid=552,1309,704,1308,804,684,111,56,586,1327</mantis>

[[Category:Spacecraft]]
[[Category:Luminauticon]]

DIHV

2026-10-09T16:22:52Z

reskin:

[[Image:DHIV_docked_with_TAC.png|thumb|right|400px|DIHV Docked at TAC Fueling]]

The [[DIHV]] ships (designation T-55) are superluminal [[:Category:Spacecraft|spacecraft]] used to transfer large amounts of passengers and materials between star systems. The DIHV ships currently dock with [[TAC]] when visiting [[Vieneo]] and is the only stop in the [[Yonmara]]n System.
<br /><br /><br /><br /><br />
The DIHV ship was invented and constructed as a military initiative by the [[United Stellar Republic]] through association with [[:Category:Luminauticon|Luminauticon]].

==Operation==
A DIHV ship does not exceed the speed of light in the strictest sense. It uses extra dimensional space in order to move between points in three-dimensional space faster than light does. These extra dimensions are described in [https://en.wikipedia.org/wiki/M-theory M-theory], which unites the constituent parts of ''Super String Theory'', which in turn unites ''Quantum Mechanics'' with ''General Relativity''.

== Statistics ==
{{SpaceVehicle
|manufacturer=[[:Category:Luminauticon|Luminauticon]] in association with the [[United Stellar Republic]] military initiative
|role=T-55 interstellar passenger and material transport
|cargo_capacity=217,756 MT
|passengers=6,506
|interstellar_capability=Superluminal travel through extra-dimensional space
|docking=[[TAC]] when visiting [[Vieneo]]; only stop in the [[Yonmara]]n System
}}

[[Image:DIHV Concept.jpg|thumb|500px|DIHV compared to E-10 (concept)]]
[[Image:DihvEffect.png|thumb|500px|DIHV Effect Observed]]

===History===
*3177-A (USV Terrania) has been in service since March 24, 2231
*3811-A (USV Valley Forge) has been in service since August 16, 2244

==Version History==
<mantis>bugid=552,1309,704,1308,804,684,111,56,586,1327</mantis>

[[Category:Spacecraft]]
[[Category:Luminauticon]]

T-121 Steerhead

2026-10-09T16:21:49Z

reskin:

[[Image:Steerhead1.JPG|400px|thumb|right|T-121 Steerhead]]

The '''T-121 Steerhead''' is the latest in heavy vehicles generally employed to move [[ARJ]]s or [[Tow_Illegal_Vehicles|tow]] smaller cars (specifically, the [[C-2_Dasher|C-2]]).

{{GroundVehicle
|manufacturer=[[:Category:Fortis|Fortis]]
|role=Heavy vehicle for moving [[ARJ]]s and [[Tow Illegal Vehicles|towing]] smaller cars
|cargo_bays=1 (open-air bed)
|gears=6
|stowage=None
|max_speed=105 km/h (by limiter)
|weight=7,072 kg (curb)
|fuel=818 kg (internal)
|price=106,714 [[CR]]
}}

==Version History==
<mantis>bugid=506,505,118,113,673,1252,1571,1128,667</mantis>

== See Also ==
* [[Tow_Illegal_Vehicles|Tutorial on towing illegal vehicles in Deois]]

[[Category:Vehicles]]
[[Category:Ground Vehicles]]
[[Category:Fortis]]

Mammoth

2026-10-09T16:21:18Z

reskin:

== NEW from Fortis ==
[[Image:Mammoth.png|thumb|right|500px]]
[[Image:Mammoth_crew.png|thumb|right|500px]]
[[Image:Mammoth_crew_2.png|thumb|right|500px]]
==== The ultimate in cargo management tools! ====
*18 Internal Cargo Bays
*Mav-Lev cargo loading and maneuvering tools.
*Massive 4 seat driving crew cab
*Seats and berths for up to 16 workers.
*Kitchenette.
*Able to reach over 90% of the planet surface.
:''Not licensed for City and street operations''.

== Specifications ==
{{GroundVehicle
|manufacturer=[[:Category:Fortis|Fortis]]
|role=Cargo management vehicle
|price=6,278,552 [[CR]]
|fuel=4,071 kg
|payload=306 MT
|max_speed=52 km/h empty on a good haul road
|endurance=10 hours at top speed and full capacity
|weight=231 MT
|cargo_bays=18 (internal)
|seats=4-seat driving crew cab; 16 passenger seats
|passengers=16 (with berths)
|stowage=17 MT
|avionics_bays=4
|ivr_series=27000–28999
|gears=Direct drive: 1 forward, 1 reverse
|suspension=8-wheel independent suspension
|restrictions=Not licensed for city and street operations
}}

== Speed Limitations ==
The '''Mammoth''' is limited to a maximum ground speed of approximately '''52 km/h''' when unladen on a prepared haul road.
This restriction is not due to engine power, but rather to the physics of its enormous 3.238-meter-diameter tires.

Each tire must flex slightly with every rotation to carry the vehicle’s immense weight. At higher speeds, that flexing happens more often per second and builds up internal heat.
Because heat dissipation in rubber is limited by both size and compound, excessive speed can quickly exceed the tire’s '''TKPH''' (''ton-kilometers per hour'') rating—causing rapid degradation or catastrophic failure.

The Mammoth’s smaller-diameter tires already rotate faster than those on the larger BelAZ-class haulers, making them more prone to heat accumulation.
To stay within realistic thermal and structural limits, the vehicle’s top speed is capped dynamically based on '''load, ambient temperature, terrain roughness, and grade'''.

:''In short:'' the Mammoth isn’t slow because of lack of power—it’s slow because even future-grade rubber can only take so much heat.

[[Category:Ground Vehicles]]
[[Category:Fortis]]
[[Category:Vehicles]]

Mammoth

2026-10-09T16:20:51Z

reskin: /* NEW from Fortis */

[[Image:Mammoth.png|thumb|right|500px]]
[[Image:Mammoth_crew.png|thumb|right|500px]]
== NEW from Fortis ==
==== The ultimate in cargo management tools! ====
*18 Internal Cargo Bays
*Mav-Lev cargo loading and maneuvering tools.
*Massive 4 seat driving crew cab
*Seats and berths for up to 16 workers.
*Kitchenette.
*Able to reach over 90% of the planet surface.
:''Not licensed for City and street operations''.

== Specifications ==
{{GroundVehicle
|manufacturer=[[:Category:Fortis|Fortis]]
|role=Cargo management vehicle
|price=6,278,552 [[CR]]
|fuel=4,071 kg
|payload=306 MT
|max_speed=52 km/h empty on a good haul road
|endurance=10 hours at top speed and full capacity
|weight=231 MT
|cargo_bays=18 (internal)
|seats=4-seat driving crew cab; 16 passenger seats
|passengers=16 (with berths)
|stowage=17 MT
|avionics_bays=4
|ivr_series=27000–28999
|gears=Direct drive: 1 forward, 1 reverse
|suspension=8-wheel independent suspension
|restrictions=Not licensed for city and street operations
}}

== Speed Limitations ==
The '''Mammoth''' is limited to a maximum ground speed of approximately '''52 km/h''' when unladen on a prepared haul road.
This restriction is not due to engine power, but rather to the physics of its enormous 3.238-meter-diameter tires.

Each tire must flex slightly with every rotation to carry the vehicle’s immense weight. At higher speeds, that flexing happens more often per second and builds up internal heat.
Because heat dissipation in rubber is limited by both size and compound, excessive speed can quickly exceed the tire’s '''TKPH''' (''ton-kilometers per hour'') rating—causing rapid degradation or catastrophic failure.

The Mammoth’s smaller-diameter tires already rotate faster than those on the larger BelAZ-class haulers, making them more prone to heat accumulation.
To stay within realistic thermal and structural limits, the vehicle’s top speed is capped dynamically based on '''load, ambient temperature, terrain roughness, and grade'''.

:''In short:'' the Mammoth isn’t slow because of lack of power—it’s slow because even future-grade rubber can only take so much heat.

[[Category:Ground Vehicles]]
[[Category:Fortis]]
[[Category:Vehicles]]

Monarch

2026-10-09T16:19:02Z

reskin:

TOP SECRET!

<mantis>bugid=495,497</mantis>

== Specifications ==
{{AirVehicle
|manufacturer=[[:Category:Sashi-Okano Corporation|Sashi-Okano Corporation]]
}}

[[Category:Development]]
[[Category:Sashi-Okano Corporation]]

T-19 Stratomaster

2026-10-09T16:18:04Z

reskin: /* Standard Features */

[[Image:T19_and_w6.png|thumb|400px|right|T-19 Stratomaster]]

The [[T-19 Stratomaster]] is the second in the line of the Transport series of [[:Category:Aircraft|aircraft]], capable of carrying one [[ARJ]] or small [[:Category:Vehicles|vehicle]].<br />
It is effectively the aerial equivalent of the [[T-120 Steerhead]].<br />
It is the cheapest way for [[Tutorial|new players]] to get into the air, with the rental fare from [[Rusty's Rentals]] (182 [[CR]]) easily earned with one day's work doing [[Tutorial#Step_2:_Being_a_Taxi_Driver|taxi runs]].

==Specifications==
{{AirVehicle
|manufacturer=[[:Category:Trimbal-Kneers Aerospace|Trimbal-Kneers Aerospace]]
|role=Transport aircraft
|cargo_bays=1
|stowage=1 MT
|weapon_mounts=0
|avionics_bays=4
|bypass_ratio=50%
|critical_altitude=12 [[kilometer|km]] [[MSL]]
|service_ceiling=20 [[kilometer|km]] (±0.5 km depending on pressure-vessel maintenance; consult owner's manual)
|fuel=9,090 kg
|weight=12,570 kg
|max_weight=39,570 kg (takeoff)
|price=9,028,552 [[CR]]
|length=31.7 [[meter|m]]
|wingspan=30.0 [[meter|m]]
|height=11.3 [[meter|m]]
}}

==Standard Features==
* Retractable Landing Gear
* Trailing edge blown flaps
* [[GPWS]]
* 320 [[kilometer|km]] [[LRS]]

== External Links ==
* [https://docs.google.com/spreadsheets/d/18ic769wFnk34y6oyNKURG0VbfqVoyIp_5NKiniSUtcY/edit?usp=sharing Detailed specifications]

[[Category:Vehicles]]
[[Category:Aircraft]]
[[Category:Trimbal-Kneers_Aerospace]]

A-4 Wanderer

2026-10-09T16:15:28Z

reskin: /* Standard Equipment */

[[Image:A-4.png|thumb|right|500px]]
The [[A-4 Wanderer]] is a light scout [[:Category:Aircraft|aircraft]], capable of carrying one [[ARJ]] or small [[:Category:Vehicles|vehicle]].<br />

=== Statistics ===
{{AirVehicle
|manufacturer=[[:Category:Trimbal-Kneers Aerospace|Trimbal-Kneers Aerospace]]
|role=Light scout aircraft
|cargo_bays=1
|stowage=1 MT
|weapon_mounts=2
|avionics_bays=2
|bypass_ratio=20%
|critical_altitude=6 [[kilometer|km]] [[MSL]]
|service_ceiling=22 [[kilometer|km]] [[MSL]]
|max_speed=225 [[meter|m]]/s
|fuel=9 MT
|weight=17,158 kg
|max_weight=41,067 kg (takeoff)
|price=5,411,199 [[CR]]
|vtol=Yes
|rain_protection=None
}}

===Standard Equipment===
* [[GPWS]]
* [[Autoflyte]]
* 320 [[kilometer|km]] [[LRS]] with [[TCAS]]

== External Links ==
* [https://docs.google.com/spreadsheets/d/1LZlgMvasAq8s136n7vyUHRAif-GTyVNW9jFN70Lf7ug/edit?usp=sharing Detailed specifications]

[[category:vehicles]]
[[category:aircraft]]
[[Category:Trimbal-Kneers Aerospace]]

P-13 Prowler

2026-10-09T16:14:50Z

reskin: /* Standard Equipment */

[[Image:P13_in_flight.png|thumb|right|400px]]
[[Image:ian-sca3.jpg|thumb|right|400px]]

The P-13 Prowler is the first and only Patrol series aerospace vehicle. It was primarily marketed for military and private security.

The P-13 is a [[VTOL]]-capable hybrid spacecraft and aircraft, in so far as it has conventional flight surfaces but is also capable of ascending beyond the atmosphere, maneuvering in [[orbit]] and [[reentry|re-entering]] under its own power.

It is faster and more agile than the [[E-10]] but has significantly lower carrying capacity. Combined with its [[Rusty's Rentals|very high price]] of 4,068,997 [[CR]] when new and lack of [http://rise.unistellar.com/auction.html second hand availability], it is seen more as a toy for the mega-rich than a genuinely useful utility vehicle.

=== Statistics ===
{{AerospaceVehicle
|role=Patrol-series aerospace vehicle
|price=4,068,997 [[CR]] (when new)
|weapon_mounts=2
|avionics_bays=3
|cargo_bays=0
|stowage=1 MT
|passengers=3
|acceleration=20 m/s fully fueled and loaded (source unit needs verification)
|fuel=18,182 kg
|weight=62,647 kg
|vtol=Yes
|orbital_capability=Can ascend beyond the atmosphere, maneuver in [[orbit]], and perform [[reentry]] under its own power
|docking=Rear docking port (as described in the flight review)
|notes=''Specification check: the previous statistics list maximum acceleration in m/s. The value is retained above; its unit needs verification.''
}}

[[Image:P13_on_Bank.png|thumb|right|400px]]

===Standard Equipment===
* [[GPWS]]
* [[Autoflyte]]
* 320 [[kilometer|km]] [[LRS]] with [[TCAS]]

===P-13 Flight Review===

Handling:
Below 118m/sec IAS: crisp and responsive in all 3 axis
Above 120m/sec IAS: the pitch control stops working the nose drops. This
can be counteracted with vertical thrusters.
Above 125 m/sec IAS: the yaw begins to oscillate when entering a turn,
and though thrusting upward will help a little, you will be forced to make
successive, alternating S-turns in order to keep to a straight line.

Solution: the thrust augmentation needs to stay on all the time, or the
throttle needs to be nerfed to keep speed under 117m/sec IAS

Docking
The ship appears to dock on the light bar area.
The docking port is at the rear of the ship.

Instruments
Although well placed the HUD is small and too transparent, in bright
light, such as above the clouds in daylight, the data all but disappears.
The rest of the instruments are still being finished.

Passengers/Prisoners
The transit menus are set up to cancel on a 0 so it is not possible
to load passengers to a 0 [[ARJ]] using the number strip at the top of the
keyboard. You may wish to attempt using the numeric keypad.

==Version History==
<mantis>bugid=546,550,547</mantis>

== External Links ==
* [https://docs.google.com/spreadsheets/d/1syv9tKJkaosioKWtW1SpTbLtxUXVzE7P4vucG9NyfO8/edit?usp=sharing Detailed specifications]

[[category:vehicles]]
[[category:Aerospace Vehicles]]

E-10 Saint

2026-10-09T16:13:51Z

reskin:

The '''E-10 Saint''' model is no longer in production. For current production line please visit [[E-11 Saint]].
<br /><br />
[[Image:hanger-e10-1.jpg|thumb|right|600px]]

== E-10 Saint Class ==
The official blurb: "The ''E-10 Saint'' is the flagship of the fleet. Although she is sluggish, she can take you all the way to [[orbit]] and beyond. With room for over 100 [http://en.wikipedia.org/wiki/Metric_ton MT] of cargo in her hold and standard [[VTOL]] she has all the flexibility you are looking for (if you can get past the sticker price)."

The E-10 is the first of the Explorer line of aerospace vehicles.

The E-10 is a [[VTOL]]-capable [[:Category:Aerospace Vehicles|aerospace vehicle]], in so far as it has conventional flight surfaces but is also capable of ascending beyond the [[atmosphere]], maneuvering in [[orbit]] and [[reentry|re-entering]] under its own power.

The E-10 is the second cheapest [[:Category:Aerospace Vehicles|aerospace vehicle]] available, with second-hand vessels selling for around 967,000 [[CR]] on [[vBay]]. It may be considered effectively the cheapest, as it is very uncommon to find [[P-13]] on [[vBay]]. It also currently has the largest cargo capacity of any vehicle available on [[Vieneo]], and as a result is by far the most popular.

== Statistics ==
{{AerospaceVehicle
|manufacturer=[[:Category:Trimbal-Kneers Aerospace|Trimbal-Kneers Aerospace]]
|role=Explorer-series aerospace vehicle
|availability=No longer in production or available for new sales; superseded by [[E-11 Saint]]
|max_speed=145 [[meter|m]]/s at [[MSL]]
|cruise_speed=369 [[meter|m]]/s at 15 [[kilometer|km]]
|service_ceiling=Indefinite (capable of reaching [[escape velocity]])
|range=Indefinite (capable of reaching [[orbit]])
|thrust=2,746,358 N
|weapon_mounts=2
|engines=3
|cargo_bays=6
|avionics_bays=4
|stowage=7 MT (Bay 0)
|acceleration=1.010 G fully loaded and fueled; depends on weight
|wingspan=48.75 [[meter|m]]
|length=48.75 [[meter|m]]
|height=14.88 [[meter|m]] (with gear)
|wing_area=341 m<sup>2</sup>
|weight=125,909 kg ([[BOW]])
|fuel=27,273 kg ([[Iagreous]])
|payload=112,273 kg
|max_weight=238,182 kg (gross)
|vtol=Yes
|orbital_capability=Capable of reaching [[orbit]] and [[escape velocity]]
}}

===Standard Equipment===
* [[GPWS]]
* [[Autoflyte]]
* 320 [[kilometer|km]] [[LRS]] with [[TCAS]]

[[Image:e10concept.jpg|500px|thumb]]
[[Image:e10compare.jpg|500px|thumb|C-17 compared with the E-10]]

== External Links ==
* [https://docs.google.com/spreadsheets/d/1klZyVkRnXCM8qpCcghM8C3NQGWP4FI1GOc0ox-yrojw/edit?usp=sharing Detailed specifications]

[[category:vehicles]]
[[category:Aerospace Vehicles]]
[[category:Trimbal-Kneers Aerospace]]

E-11 Saint

2026-10-09T16:12:50Z

reskin:

[[Image:E-11_Landing_At_Fleet.png|thumb|right|500px]]

The official blurb: "The [[E-11 Saint]] is the flagship of the fleet. Although she is sluggish, she can take you all the way to [[orbit]] and beyond. With room for over 100 [http://en.wikipedia.org/wiki/Metric_ton MT] of cargo in her hold and standard [[VTOL]] she has all the flexibility you are looking for (if you can get past the sticker price)."

The E-11 is a [[VTOL]]-capable [[:Category:Aerospace Vehicles|aerospace vehicle]], in so far as it has conventional flight surfaces but is also capable of ascending beyond the [[atmosphere]], maneuvering in [[orbit]] and [[reentry|re-entering]] under its own power.

The E-11 first went into production on February 24, 2243 and supersedes the [[E-10 Saint|E-10]] model. It is the second in the Explorer class of aerospace vehicles.

== Statistics ==
{{AerospaceVehicle
|manufacturer=[[:Category:Trimbal-Kneers Aerospace|Trimbal-Kneers Aerospace]]
|role=Explorer-series aerospace vehicle
|max_speed=146 [[meter|m]]/s at [[MSL]]
|cruise_speed=393 [[meter|m]]/s at 15 [[kilometer|km]]
|service_ceiling=Indefinite (capable of reaching [[escape velocity]])
|range=Indefinite (capable of reaching [[orbit]])
|thrust=3,134,393 N
|weapon_mounts=2
|engines=3
|cargo_bays=6
|avionics_bays=5
|stowage=7 MT (Bay 0)
|acceleration=1.343 G at GTOW
|price=10,900,477 [[CR]]
|wingspan=48.75 [[meter|m]]
|length=48.751 [[meter|m]]
|height=14.877 [[meter|m]] (with gear)
|wing_area=341 m<sup>2</sup>
|weight=113,933 kg ([[BOW]])
|fuel=27,273 kg ([[Iagreous]])
|payload=124,248 kg
|max_weight=238,182 kg (gross)
|vtol=Yes
|orbital_capability=Capable of reaching [[orbit]] and [[escape velocity]]
}}

===Standard Equipment===
* [[GPWS]]
* [[Autoflyte]]
* 320 [[kilometer|km]] [[LRS]] with [[TCAS]]

[[File:E-11 Parked.png|thumb|500px]]
[[Image:e10compare.jpg|355px|thumb|500px|C-17 compared with the E-11]]
[[File:Hawaiian_Clipper.png|thumb|500px]]

==Known Issues==
<mantis>bugid=508,683,820,847</mantis>
== External Links ==
* [https://docs.google.com/spreadsheets/d/1cloDgSMSADpG7jgm6WMtb2LLQzwdo_GBCONwaQvGo80/edit?usp=sharing Detailed specifications]

[[category:vehicles]]
[[category:Aerospace Vehicles]]
[[category:Trimbal-Kneers Aerospace]]

Flight Simulators

2026-10-09T15:41:33Z

reskin: Created page with "'''Flight simulators''' in ''Rise: The Vieneo Province'' provide a place to learn aircraft controls, practise landings, and explore flight without risking a real vehicle or your character's life. The simulators are '''free of charge'''; you do not need to own or rent the aircraft you want to practise flying. == Location and access == The simulator bay is inside the '''Unistellar Industries, LLC building''' in the '''Financial District''' of Deois, at approximately..."

'''Flight simulators''' in ''Rise: The Vieneo Province'' provide a place to learn aircraft controls, practise landings, and explore flight without risking a real vehicle or your character's life. The simulators are '''free of charge'''; you do not need to own or rent the aircraft you want to practise flying.

== Location and access ==

The simulator bay is inside the '''Unistellar Industries, LLC building''' in the '''Financial District''' of [[Deois]], at approximately '''S4.209 W26.106'''. Look for '''UI Building (Taxi, Flight Simulators)''' in the [[Waypoint Management|Waypoint Manager]]. Older help text may call it the ''Deois UI Building (Taxi Fares)''.

# Drive to the building in your C-2A Dasher or another ground vehicle small enough to enter the garage.
# Select '''1] Enter Simulator Bay''' from the [[Intermedia]] menu when it appears.
# Walk through the bay to the simulator you want to use. The Intermedia menu changes as you approach each simulator entrance.
# Select '''Enter T-19 Simulator''', '''Enter W-6 Simulator''', or '''Enter E-11 Simulator'''.

If the selected simulator is already occupied and no unit of that type is available, you will receive a message that it is in use. Try another type or return when one becomes available.

== Available simulators ==

The bay offers three vehicle types:

{| class="wikitable"
! Simulator
! Vehicle type
! Useful practice
|-
| [[T-19 Stratomaster]]
| Atmospheric aircraft
| Conventional takeoffs and landings, circuit flying, approaches, and aircraft handling.
|-
| [[W-6 Manx]]
| Aerospace vehicle with limited [[VTOL]] capability
| Atmospheric flight, ascent to [[orbit]], orbital manoeuvring, and [[reentry]]. VTOL performance depends on the aircraft's weight and available thrust.
|-
| [[E-11 Saint]]
| VTOL-capable aerospace vehicle
| Vertical takeoffs and landings, handling a large transport, orbital flight, and reentry.
|}

The T-19 is a useful starting point for learning conventional flight. The W-6 and E-11 provide opportunities to practise the transition between atmospheric and orbital operations. See each vehicle's article for its capabilities and operating information.

== Starting and pausing a session ==

A new session begins at the takeoff position for '''Deois Runway 36''', with the simulation '''paused'''. Check your controls and aircraft configuration before beginning.

Press '''Pause/Break''' to unfreeze the simulation. Press it again to freeze the flight while you study the instruments or prepare your next action. This is the default flight-freeze binding; use your configured binding if you have changed it.

The simulator uses controlled training conditions, with no wind, turbulence, or lightning. Practise the aircraft's controls and procedures here, and allow for weather conditions when you later operate outside the simulator.

== Repositioning and restarting ==

While seated in a simulator, the Intermedia displays the following options:

{| class="wikitable"
! Menu option
! Function
|-
| '''1] Exit Simulator'''
| Ends the simulator session and returns you to the simulator bay.
|-
| '''2] Reposition Runway'''
| Returns the simulated aircraft to the takeoff position for Deois Runway 36. Use this to repeat a departure or restart after a crash.
|-
| '''3] Reposition Final'''
| Places the simulated aircraft on the approach to Deois, approximately 5 km before the LUMEN final approach fix. Use this to practise approaches and landings without flying an entire circuit.
|-
| '''4] Reposition to Active Waypoint'''
| Moves the simulated aircraft to your active [[Waypoint Management|waypoint]]. Activate the waypoint and select it as your navigation target first. This option uses ground placement and is intended for surface locations.
|}

Repositioning replenishes the simulated aircraft's fuel, repairs simulated damage, and pauses the simulation again. It also resets aircraft configuration, so check the landing gear, flaps, parking brake, and other controls before pressing '''Pause/Break''' to continue.

To leave the building after selecting '''Exit Simulator''', walk back to an exit foyer and choose '''1] Exit to Street'''. You return to the ground vehicle you brought to the bay.

== Crashes and deaths ==

'''Deaths in the simulator do not count against your character's death total or [[Reputation|reputation]].''' A simulated crash does not trigger the normal death penalties or destroy an aircraft you own.

The simulator can still represent a crash or aircraft failure. When that happens, use a reposition option to reset the exercise, or select '''Exit Simulator''' to leave. This makes the bay a useful place to learn from mistakes and repeat difficult manoeuvres.

Simulator activity is for training. Normal cargo, fuel, cash, and inventory transfers are unavailable while you are operating a simulator.

== Simulated time and actual flight time ==

Simulator flights are identified as '''simulated''' in your [[Logbooks|logbook]]. They record practice in a simulator and are distinguished from flights made in actual aircraft and aerospace vehicles in the game world.

The current time-tracking system also distinguishes '''total connected playtime''' from '''operational time'''. Operational time is credited in 0.1-hour (six-minute) intervals when qualifying activity occurs; simply sitting idle in the simulator does not build operational time.

The old aggregate simulator/non-simulator hour counters have been retired. This does not remove the simulated designation from individual logbook entries. See '''[[Logbooks]]''' for the explanation of current time tracking and preserved legacy experience.

== See also ==

* [[Logbooks]]
* [[Waypoint Management]]
* [[T-19 Stratomaster]]
* [[W-6 Manx]]
* [[E-11 Saint]]
* [[Tutorial]]

[[Category:Getting Started]]

File:C2timex.png

2026-10-09T14:08:14Z

reskin:

Timex

2026-10-09T14:08:01Z

reskin:

[[Image:timex.gif]]

[[Vieneo]] runs about a 14.4 hour day which means we can keep time to the second on a 24 hour clock if we sacrifice the top 24 minutes of every hour.

The natural circadian rhythm is 25 hours, and 14.4 hours is close to half that, a typical work day consists of a 14.4 hour continuous duty followed by a 14.4 hour off duty period.
<br /><br />
The moon is divided into 15 time zones of just under 1 hour each.
<br />
[[Image:clockproposal.gif]]

[[Image:c2timex.png]]

[[Category:Sponsorship]]

File:Lockheedhangar.png

2026-10-09T13:57:18Z

reskin:

Lockheed Martin

2026-10-09T13:57:01Z

reskin:

[[Image:Lockheed.gif]]

* Temporary [[Runway Lights]]
* [[RVR]]
* [[ILS]]

[[Image:lockheedhangar.png]]

== External Links ==
* http://www.lockheedmartin.com
[[Category:Deois]]
[[Category:Sponsorship]]

ATI

2026-10-09T13:54:21Z

reskin: /* External Links */

[[Image:ATI.jpg]]

[[Image:AtiBuilding.png]]

==External Links==
* https://www.amd.com/en.html

[[Category:Sponsorship]]
[[Category:Deois]]

File:Laeyeworksbuilding.png

2026-10-09T13:52:12Z

reskin:

L.a. Eyeworks

2026-10-09T13:51:41Z

reskin:

[[Image:laeyeworks.jpg]]

l.a. Eyeworks [[sunglasses]] are a fashionable and functional accessory!

[[Image:laeyeworksbuilding.png]]

==External Links==
* https://www.laeyeworks.com/

[[Category:Sponsorship]]
[[Category:Deois]]

Deployment Checklist

2026-10-09T13:32:46Z

reskin:

=Mesh and Texture Asset=
#Make sure production warnings are turned on
#Potentially delete the type.dat from the root Ian's Folder for the type you are exporting (ships, docks, etc) depending on if you need to rebuild all assets to remove textures from sharing across modules or removing models altogether. If the file doesn't exist, all assets of that type must be run through the "Match Textures" routine.
#3 or 4 sided polys only
#limited poly count
#no intersecting geometry
#where geometry meets the coordinates should be identical
#Production warnings (canvas size mismatches)
#Shading assessment (gouraud vs. lambertian)
==Vehicles==
===Before Deployment===
Need to ensure the scaling of the textures is approximately correct if it is coming from third-party tooling
====Exteriors====
#Before doing anything we need to do a reality check regarding the CG
#Cockpit/cab windshield is "outside cockpit" type so that it it operates with dome light
#Check gross extents (i.e. a license plate that flies away when extended or retracted)
#Bounding sphere analysis
#Headlights and/or landing lights
#Texture utilization (i.e. duplicate names, unnecessary "ambient" light maps)
#Bay doors
#Bay interiors

=====Aircraft and Aerospace Vehicles=====
#Lifting bodies "left wing" "right wing" "tail"
#Engines "left" "right" "center"
#Flight controls and their proper deflections
#Landing gear (nose gear, nose wheels, main gear, main wheels)
#Dynamic lights (navigation lights, anti-collision strobes, landing lights)[[Image:aircraftlighting.bmp|thumb|right]]
##Including the correct normals!
#Nose art

=====Ground Vehicles=====
#Brake lights
#Steering wheels need to be "Landing Gear -> Nose Wheel" type, no deflections
#Wheels (other than for steering) need to be "Landing Gear -> Main Wheel" type
#License plates (front and rear) "dynamic" type (unless large signage)
#Windshield wipers

====Interiors====
#Eye location (0,0,0)
#Chair extent
#Monitor source and instance assignment
#Master warning and caution buttons
#Controls assignment and motion
## Pitch
## Roll
## Yaw
## Steering
#Thrust controls assignment and motion
## Accelerator and brakes
## Thrust lever(s)
#Nameplate
#Windshield layout
##Reentry
##St. Elmo's Fire
#Display package
## XML
## Overmonitor picture
#Sound effects package
##Start
##Ambient
##Engine
##Touchdown
##Gear extension
## Flap extension
## Bay door operation
#[[Flight Simulators|Simulator]] package
#Outside components visible from inside (i.e. [[W-6 Manx]] canards)

====Other====
#Need to add to the vehicles graph on admin view
#Need to add a small image for the Discord assets [https://discord.com/developers/applications/497844043951374357/rich-presence/assets]

===After Deployment===
====Exteriors====
#Trim colored base maps must be exported as DXT3 even through VP loads as DXT1 to retain alpha layer data
#Need to align the [[ARJ]]s in the cargo bay

==Docks==
#Docking interfaces must be the first module in the ASM file (that is how VP knows which port is where!)
[[Category:Development]]

Special Commands

2026-10-09T13:30:25Z

reskin:

Special Commands

2026-10-09T13:30:02Z

reskin:

Special Commands

2026-10-09T13:29:46Z

reskin: