- Joined
- Jan 7, 2008
- Messages
- 5,789
- Reaction score
- 778
- Points
- 203
- Location
- Earth
- Website
- orbides.org
- Preferred Pronouns
- she/her
As i mentioned before, odds are i won't be around to finish or improve my add-ons, even the good ones.
But there is one add-on that is both good and open-source friendly, being made in C++ and with extendability in mind.
UAP, the Universal Autopilots.
Previous threads:
http://www.orbiter-forum.com/showthread.php?t=22753
http://www.orbiter-forum.com/showthread.php?t=14704
http://www.orbiter-forum.com/showthread.php?t=14650
So...
Here are the sources for it:
http://www.thespaceway.org/files/uap-0.3.1-sources.zip
EDIT 201224: And Github version: https://github.com/artlav/uap
I tweaked them to compile with recent Orbiter, and checked that they still work, but other than that it's as-is.
I don't know what the consensus was on the GPL vs LGPL vs Whatever, so it's released under the "Don't be a dickhead" license (if i missed some development to the effect of "no open source addons are allowed now", please tell me).
I've also included some of the reference materials used.
The most impressive part, transorbit module, is based on OrbiterPEG by Chris Jeppesen, the rest of it is mine as far as i remember.
The system was designed under assumption that other people would write modules for it.
There is an extensive base class that you derive from to make an actual autopilot.
The base class handles the scheduling and housekeeping, as well as abstracting the vessel, providing an intuitive interface at the level of "accelerate this way at this many m/s^2 with this engine set", or "point north".
Since there never was any interest in it, the interface didn't get cleaned up, completed or documented.
The rest of the system are:
-SAL, Simulation Abstraction Layer. This abstracts the simulator (Orbiter, Spaceway) into an API used by the autopilots.
-UAPSYS, the system itself, that handles task scheduling, vessel tracking, state saving and so on.
-UAP MFD, the user interface that shows the UAP info for the vessel you are sitting in.
Basically, the system is designed to run in the background, with the MFD being a terminal into it.
So, that's about it.
I figured it's better to leave it here with small odds that someone will pick up the work and give it future, rather than not leaving it here with exactly zero odds of it having a future.
If you have any questions, i'm here to answer them.
But there is one add-on that is both good and open-source friendly, being made in C++ and with extendability in mind.
UAP, the Universal Autopilots.
Previous threads:
http://www.orbiter-forum.com/showthread.php?t=22753
http://www.orbiter-forum.com/showthread.php?t=14704
http://www.orbiter-forum.com/showthread.php?t=14650
So...
Here are the sources for it:
http://www.thespaceway.org/files/uap-0.3.1-sources.zip
EDIT 201224: And Github version: https://github.com/artlav/uap
I tweaked them to compile with recent Orbiter, and checked that they still work, but other than that it's as-is.
I don't know what the consensus was on the GPL vs LGPL vs Whatever, so it's released under the "Don't be a dickhead" license (if i missed some development to the effect of "no open source addons are allowed now", please tell me).
I've also included some of the reference materials used.
The most impressive part, transorbit module, is based on OrbiterPEG by Chris Jeppesen, the rest of it is mine as far as i remember.
The system was designed under assumption that other people would write modules for it.
There is an extensive base class that you derive from to make an actual autopilot.
The base class handles the scheduling and housekeeping, as well as abstracting the vessel, providing an intuitive interface at the level of "accelerate this way at this many m/s^2 with this engine set", or "point north".
Since there never was any interest in it, the interface didn't get cleaned up, completed or documented.
The rest of the system are:
-SAL, Simulation Abstraction Layer. This abstracts the simulator (Orbiter, Spaceway) into an API used by the autopilots.
-UAPSYS, the system itself, that handles task scheduling, vessel tracking, state saving and so on.
-UAP MFD, the user interface that shows the UAP info for the vessel you are sitting in.
Basically, the system is designed to run in the background, with the MFD being a terminal into it.
So, that's about it.
I figured it's better to leave it here with small odds that someone will pick up the work and give it future, rather than not leaving it here with exactly zero odds of it having a future.
If you have any questions, i'm here to answer them.
Last edited: