------------------------------------------------------------
Satori Starships Nuvu & Pulsar
----------------------------------------------------------------
| . . . . . . . . . . . . . Main Menu . . . . . . . . . . . . . . . |
|
| . .. Settings . . . . . . Menu . . . . . .Landmarks . . |
| . . Fire Panel . . . Goto Menu . . . Local Sim . . . |
| . .. Trackers . . . . Dockings . . . . . AutoPilot . . . |
| . . . Portals . . .. Chat Comm . . . . AutoData . . . |
----------------------------------------------------------------
----------------------------------------
Set of Nuvu-A, Nuvu-B, Pulsar-A and Pulsar-B. Two starship styles with 'B' larger than
the 'A' version.
Starships Pulsar and Nuvu are physical 40m length motherships that rezz a set of warbirds
and civilian transports which auto-dock to designated mothership lander pads/pods.
The starship crew consists of pilot and two gunners, with additonal seating for 4.
Landers and Warbirds are a mix of single and multi-passenger crews.
Inworld touch panels for basic ship functions.
Hud has full access to all ship functions.
The pilot flies without use of MouseLook mode.
SL Landmarks (or notecards) may be use to create additional tour bot or
teleport destinations.
--------------------------------------------
TAO OS - Linux (like) OS on a Prim
--------------------------------------------
Full TOS Library Files (Google Drive)
TOS 5.2 -- https://drive.google.com/drive/folders/1-GA0aPt-VzGmwyt6bmvmC-ZlRoEKw2_8?usp=drive_link
Library of TOS builds :
Maker Build Paks -- https://drive.google.com/drive/folders/1pPMpIAEYDSbMD9ilf3BhE-5mlpvAP1E_?usp=drive_link
----------------------------------
Tao Operating System ... a Linux Like system on a prim
- the TOS is composed of scripts that act as a Linux on a Prim system,
with CLI, Multi-Task Macro Interpeters, Cron, Shared Memory, Hud GUI,
XMem Explorer, Network and APIs for motion, prim and sim functions.
- the Macro Interpeter loads a notecard, parsed as op-code cpu commands,
stored internally and executed. Each vcpu can hold multiple macros and
allow them to act as internal subroutines or act with other vcpu units.
- the vpus are multi-tasking, such that any or all may run at any time
and running macros are interruptable by outside events.
- scripts are sparsely placed in multiple prims, since each script
can access each other directly thru router functions, this reduces
sim overhead since all scripts in the object are not triggered.
- Notecards are treaded as runtime data files and as macro files to be
loaded by the byte-code macro interpeters (vcpus).
- files are placed into three catagories:
/user - files specific to the user build (cli prim)
/bin - system files that make up the basic os (vpu.a prim)
/app - applications and addons (vpu.b prim)
there are 'paks' that comprise the os and app packages.
- Generally, user notecards are located in the CLI / Filecache prim, which acts
as the system manager, macro loader and data reader for the Tos system.
Otherwise, all system and parameter files are located on the prims with the
vpu scripts, as their monitor registers the files for access by readers.
- all Tos Systems are self rebooting capable, where the Hud GUI allows you
to reload all memory, all macros from internal files and restart the system.
Also you can recover from a crashed 'vcpu' script by resetting and reloading it.
The PBMonitor API allows oversight and control of vpu scripts in it's prim.
There's also a BIOS Hud Menu fall back, in case of a total cold restart.
----------------
-- Superuser / Developer notes --
- the real purpose of the vpus, is to act as the glue between the various APIs.
the macros let you reformat the data flow between the APIs, as well as set
up conditions that affect the states of the APIs.
note that vpu performance is around 1150 lines/sec, which is rather slow for a
computer but most api macros are less than 10 lines long. And the APIS perform
most of the cpu activities internally, leaving vpus to act as a traffic cops.
- there are two types of Macro Interpeters, the difference is that the developer
one has a macro 'remove' command to erase the macro from it's memory.
the default is treaded as ROM, where it must be entirely erased before reuse.
the default is the production version, as it holds more macro memory,
----------------
- 40m ship has auto-pilot capabilities, with landmarks or sim map usage
- Custom physical/non-physical engine (both have precise and 'sloppy' movements)
- Pilot and two gunners with access to a variety of ship-damage weapons
- Hud Menus for all ship functions and touch panels for commonly used commands.
- TOS 5.2 : a linux-like in-world micro-controller
