press releases news

companion 8.4.4

This service release for Companion 8.4 fixes a security bug caused by incorrect implementation of the 'trigger' command. It also fixes 'charge' for large values and improves display of port connectivity on NS-226 units. Updating is strongly recommended for all 8.4.x users.

Full documentation for 8.4 is available at support.nanite-systems.com.

Battery recall: If your batteries were purchased before February 11, 2017, they need to be replaced to be used with Companion 8.4.2 or later. To get replacement batteries, send your current power cells to Takura Thielt (any time), Kuro Umino (any time) or rhet0rica (weekends only). See the batteries page for more information.

installation instructions for Companion 8.4.4

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on! Keep in mind you will still need an updated battery, as mentioned above.
  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance. You can also use the command @about to get the same information.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select install. If you are running 8.3.0 or later, select connect.
    1. Select the sim's primary update server. If you are in Eisa, this is xcentral:0. If you are in one of the other supported updating sims, see the list here.
    2. If you are running a version of 8.4 already, select update. (Otherwise, select install.)
    3. Select the Companion_8.4.4 package and upgrade or install it.
    4. If you do not see the update package, see alternative instructions for updating via the command line.
    5. Accept the notecard _System_8.4.4_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    6. Installation will take up to 2 minutes. You will receive a message saying Done. Installed 56 files total. when the process is finished.
    7. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console. If you already use the HUD, you should have been offered an updated one during the install process.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.
  7. Important note for returning customers: A battery recall was issued on February 11, 2017. Older power cells will not work with the new release. See above for instructions on replacing your battery. If you purchased your battery on or after February 11, 2017, this does not affect you.

changes in 8.4.4

  • Fixed environmental charges being ignored if over 20 kJ (a prompt would be generated, but the result discarded); this should fix the pulse beacon, taser, and large @zap jumps.
  • Fixed the 'trigger' public bus command to work as intended; it was producing system commands with no arguments instead of activating the Arabesque trigger system. You can now use Arabesque notecards called 'e_charge-start' and 'e_charge-stop' to execute instructions when starting/stopping charging.
  • Fixed a slight cosmetic issue with the NS-226 Hephaestus controller not using the visible ports on its case when cables were connected without a Nanoconnectivity adapter installed.

changes in 8.4.3

  • Support for shielded uRTG batteries
  • Removed spurious debug messages in the SCM damage effect code

changes in 8.4.2

  • Resolved inconsistent format in QUERY_SUBSYSTEM and response messages, creating difficulty for app creators who needed to check subsystem states.
  • Battery swap-outs were still causing explosive overheating in ATOS/E. This should be resolved now. An update to ATOS/E is not required.
  • Fixed devices menu reporting devices as not found or not installed.
  • Added version checking for batteries. Please also ensure that you get an updated battery.
  • Fixed a bug where '@color company' would cause the unit's lights to go black.
  • Restored the hinge script in the XSU.

dax/3 goes mini

DAX/3m

It's hard to believe it's been almost eleven months since the DAX/3 first hit the store shelves—our fastest-ever selling controller design, with millions of preorders shipped to eager robot owners across the galaxy just on its first day. But today that bit of history just might be old news, because the DAX/3 mini is a thing of true beauty.

Featuring a matte black ceramic exterior, the DAX/3m is designed to fit in perfectly with our popular Metalloplastic Nova epidermal coating system. Tint its numerous exterior faces however you like, and in whatever patterns you like. It can even be scaled down to just two thirds of its default size if you have a very small avatar. And if you want to change what parts of the hardware light up, no problem—the modern autoconf flicker is more than happy to read new settings out of part descriptions with just a quick reset, and also provides controllable !lamp support.

The DAX/3m features Companion 8.4.3.1, a special version of 8.4.3 that includes support for the DAX/3m's battery socket and sound scheme defaults. Support will also be available in the upcoming 8.5m2 pre-alpha release. ATOS/E is not included by default, but can easily be installed by following the instructions at support.nanite-systems.com.

Available now online or at one of our store locations for just L$900. Become more!

And as always, information on our other controller systems is available at the feature comparison page.


Regarding recent events

Over the past week, you may have heard about our decision to cooperate with federal regulators in the United States pertaining to the improper procurement of biological samples for use in our recreational android and gynoid products. There have been a lot of rumors circulating as to the exact nature of the sampling process, so I'd like to take a moment to clarify some key facts about what happened and what you can expect going forward.

Sampling is a means of sourcing biological and neurological information from an organic template in order to enrich the human-like qualities of our robots. With only a few exceptions, units manufactured and sold by NSCP are designed to have unique appearances and personalities, so that they can better simulate the real experience of talking to a human being. In some cases, we use in-place sampling, also known as 'conversion,' 'robotification,' 'cyberization,' or 'nanite refabrication' to extract the relevant details from a person. Normally, this is done voluntarily, which is legal under Federal law and in several states.

Nanite Systems regularly employs promising students in a wide variety of internships to help foster the talent that our company is built on. As of this writing, we have over fifty thousand interns with the company on dozens of planets, moons, and satellite colonies. As a conglomerate with interests in robotics research, military logistics, and industrial supply, it is inevitable that our employees, as well as interns, are sometimes in risky or hazardous situations, including dangers inherent in the military research and development process, battlefield resupply, and deep space cargo hauling. We take every step available to safeguard the lives of our current and future employees, but in the event that loss of life does occur, next of kin are notified immediately, per standard industry practice and in accordance with the laws of most countries.

Recently, it was discovered that some of our sales staff used our sampling equipment to salvage some of the physical and mental characteristics from interns, both living and recently deceased, exploiting these tragedies that affect everyone in the company in order to obtain bonuses intended for conversion candidate recruitment. In a number of cases it has been confirmed that the living interns involved in these forced conversions were unwilling or had been misled as to the procedure and its consequences. While the resulting product may appear to emulate the attitudes and outlooks of their organic predecessors, they are not to be confused with full-body cyborgs and are only shallow imitations.

After consulting with a number of families of the victims, we've decided to institute a company-wide ban on conversion and to screen against any units that contain detectable traces of human personality or experience, except where an audit can confirm that the unit was voluntarily converted. It is of utmost importance to us that customers can be confident their machines are safe and behave within expected parameters. I and the company as a whole cannot express enough how sorry we are that grieving families have had to grapple with questions of whether or not their daughters, sisters, sons, and brothers have been properly laid to rest. Hopefully, this will set us on the road to making amends.


Tamara Peluso
CEO, Nanite Systems Consumer Products
Acting Chair of the Board of Directors of Nanite Systems Corporation

If you're concerned one of your family members may have been improperly subject to sampling, we want to hear from you. Contact us by email.


ATOS/H combat meter





L$ 300
marketplace link

customer motivation survey

What makes a robot a robot? The purpose of this survey is to better understand why our customers buy our products. The data from it will be used to identify opportunities to satisfy and supplement under-served segments of our userbase. All questions are optional. A summary of overall survey results may be made public, but your individual answers will be kept confidential and anonymous. Everyone is invited to answer, including owners and users who are not robots themselves.

Take the survey here.


customer survey for male-bodied avatars

Nanite Systems is exploring opportunities to create more products targeted specifically at customers who use bodies that are non-feminine. We are interested in collecting data on market size and composition, usage rates of various popular mesh bodies, and where our customers feel our existing offerings are deficient.

The questionnaire includes 13 questions and should take 10-15 minutes to complete. Click here to take the survey.


companion 8.4.3

This service release for Companion 8.4 addresses a HUD issue and adds support for the new uRTG battery that will be released later today. Other bugfixes and improvements are still scheduled for Companion 8.5 and are not included in this patch.

Full documentation for 8.4 is available at support.nanite-systems.com.

Battery recall: If your batteries were purchased before February 11, 2017, they need to be replaced to be used with Companion 8.4.2 or 8.4.3. To get replacement batteries, send your current power cells to Takura Thielt (any time), Kuro Umino (any time) or rhet0rica (weekends only). See the batteries page for more information.

installation instructions for Companion 8.4.3

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on! Keep in mind you will still need an updated battery.
  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance. You can also use the command @about to get the same information.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select install. If you are running 8.3.0 or later, select connect.
    1. Select the sim's primary update server. If you are in Eisa, this is xcentral:0. If you are in one of the other supported updating sims, see the list here.
    2. If you are running a version of 8.4 already, select update. (Otherwise, select install.)
    3. Select the Companion_8.4.3 package and upgrade or install it.
    4. If you do not see the update package, see alternative instructions for updating via the command line.
    5. Accept the notecard _System_8.4.2_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    6. Installation will take up to 2 minutes. You will receive a message saying Done. Installed 56 files total. when the process is finished.
    7. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console. If you already use the HUD, you should have been offered an updated one during the install process.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.
  7. Important note for this version only: A battery recall was issued on February 11, 2017. Older power cells will not work with the new release. See above for instructions on replacing your battery.

changes in 8.4.3

  • Support for shielded uRTG batteries
  • Removed spurious debug messages in the SCM damage effect code

changes in 8.4.2

  • Resolved inconsistent format in QUERY_SUBSYSTEM and response messages, creating difficulty for app creators who needed to check subsystem states.
  • Battery swap-outs were still causing explosive overheating in ATOS/E. This should be resolved now. An update to ATOS/E is not required.
  • Fixed devices menu reporting devices as not found or not installed.
  • Added version checking for batteries. Please also ensure that you get an updated battery.
  • Fixed a bug where '@color company' would cause the unit's lights to go black.
  • Restored the hinge script in the XSU.

announcing the project incubator

Eagerly awaiting a product release? Wish we'd get something out the door sooner? Help shape the company's future! Today we're announcing the availability of our project incubator website. Vote to tell us what you want to see, and we'll prioritize the most popular ideas. You can upvote as many projects as you want, but only once. Click here to get started.

Have an idea for something you think we should really, really offer? Check the support site to make sure we don't already have it, and then contact our support email with your suggestions, or send a notecard in-world to rhet0rica or Tamara. Be certain that you don't mind sharing, though—when offering ideas, you must be willing to waive all rights to them, and allow us to use them without expectation of giving you any credit, control, or monetary compensation for the contributions.


companion 8.4.2 + battery recall

This service release for Companion 8.4 addresses a few minor issues. It also comes with an absolutely necessary battery recall.

Updating is mandatory and should not be delayed.

Note: Full documentation for 8.4 is a work in progress. Check the support site, at support.nanite-systems.com often.

Battery recall: For several reasons, all batteries currently in service must be replaced. Old batteries (purchased prior to 1 PM SLT on February 11, 2017) will not function with this version of Companion or any subsequent OS release. Your controller will simply fail to turn on. We have done this to force users to update. To get replacement batteries, see the batteries information page.

New batteries end in -X, -C, or -G. Nightfall users who have decided to stick with the one-hour fuel cell can simply get a redelivery, as these batteries are copy-mod. OC Alkaline Batteries are now 0093-24, replacing the old 0093-23+ version. If your battery does not include a part number in its name, it is obsolete.

ProductOld part numberNew part number
Fuel Cell (62 minutes)13-6022-F/CM13-0622-G/CM62
Alkaline (2 hours)0093-23+0093-24
Lithium-Ion Polymer (4 hours)13-0536-B13-0536-C
Metabolic Reactor (8 hours)13-0001-B13-0001-C
Sonofusion Reactor (24 hours)13-7026-T13-7026-X

Changes in the new batteries include non-degrading behavior for more expensive cells (and degrading for cheaper cells), auto-positioning for all cells, new sound effects, new animations, improved insertion angle, and more. These new batteries will work in controllers running older versions of Companion.

Auto-positioning: All new batteries are designed to automatically position themselves in the controller's battery socket. To adjust this behavior, edit your battery and change the number in the description field. (If the description field is blank or says "(No description)", replace it with "-0.334", without the quotes.) This is dependent on the depth of your torso and must be configured individually for each unit. If for some reason auto-positioning doesn't work for you (e.g. your controller is not centered on your back), then you can disable it by attaching the battery to your chest and the controller to your spine, instead. Some manual adjustments will still be required.

installation instructions for Companion 8.4.2

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on! DAX/3 users are strongly encouraged to get a redelivery, as it has been updated to address some issues with the lighting script and is now easier to resize. Keep in mind you will still need an updated battery.

  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance. You can also use the command @about to get the same information.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select install. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running a version of 8.4 already, select update. (Otherwise, select install.)
    3. Select the Companion_8.4.2 package and upgrade or install it.
    4. If you do not see the update package, see alternative instructions for updating via the command line.
    5. Accept the notecard _System_8.4.2_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    6. Installation will take up to 2 minutes. You will receive a message saying Done. Installed 56 files total. when the process is finished.
    7. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console. If you already use the HUD, you should have been offered an updated one during the install process.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.
  7. Important note for this version only: A battery recall was issued on February 11, 2017. Older power cells will not work with the new release. See above for instructions on replacing your battery.

changes in 8.4.2

  • Resolved inconsistent format in QUERY_SUBSYSTEM and response messages, creating difficulty for app creators who needed to check subsystem states.
  • Battery swap-outs were still causing explosive overheating in ATOS/E. This should be resolved now. An update to ATOS/E is not required.
  • Fixed devices menu reporting devices as not found or not installed.
  • Added version checking for batteries. Please also ensure that you get an updated battery.
  • Fixed a bug where '@color company' would cause the unit's lights to go black.
  • Restored the hinge script in the XSU.

companion 8.4.1

This service release for Companion 8.4 addresses a number of minor issues.

All users are strongly encouraged to update.

Note: Full documentation for 8.4 is a work in progress. Check the support site, at support.nanite-systems.com often.

installation instructions

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on! DAX/3 users are strongly encouraged to get a redelivery, as it has been updated to address some issues with the lighting script and is now easier to resize.

  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select install. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running a version of 8.4 already, select update. (Otherwise, select install.)
    3. Select the Companion_8.4.1 package and upgrade or install it.
    4. Accept the notecard _System_8.4.1_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    5. Installation will take up to 2 minutes. You will receive a message saying Done. Installed 57 files total. when the process is finished.
    6. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.

changes in 8.4.1

  • Improved overcharging protection: inverse square law past 20 m, consent required. This means that any @zap command usage or other charging device will need consent to send more than 20 kJ of power to you.
  • Re-examine animation permissions errors.
  • Fixed message 170 ignoring 'method' parameter.
  • Model tamper warning, automatic OEM chip reload.
  • fixed @verbosity being renamed to @VERBOSITY_LEVEL.
  • Fixed issues in startFollowingName() affecting two-part legacy names when using _devotion collars.
  • Code modernization in user manager.
  • Fixed: @access displays local access setting in place of remote access setting.
  • Various fixes affecting @autolock.
  • Check permissions properly for @bolts, @gender and @commands.
  • Guard against more math errors (checking battery level immediately after 5% shutoff while drawing 0 W).
  • Automatically blank-out unused faces of touchscreen prims (specular issue; affects mostly XSU users).

companion 8.4

It's taken close to a year, but Companion 8.4 is finally available for regular use. This is an immense update, almost doubling the size of the firmware code base.

release highlights

  • RLV relay
  • Tutorial mode
  • Smarter HUD delivery
  • Auxiliary power, giving more flexibility in what subsystems are available when powered down
  • Distress beacon
  • Domain membership, including downloading settings and users from a central domain server
  • Guest access control
  • Path navigation (see previous announcement)
  • Improved following mechanics
  • Improved ATOS/E support
  • Foreign device connection
  • System policies
  • And more!

Companion 8.4.0 is required for two new systems that were released during its development cycle, the XSU and DAX/3. All other users are strongly encouraged to update, as well.

Note: Full documentation for 8.4 is a work in progress. Check the support site, at support.nanite-systems.com often.

installation instructions

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on!

Redelivery is not yet available for this version. We're working on updating the controller hardware to incorporate minor improvements that have been made since they were released. Follow the instructions below.

  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select update. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running a pre-release version of 8.4 already, select update.
    3. Select the Companion_8.4.0 package and upgrade it.
    4. Accept the notecard _System_8.4.0_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    5. Installation will take up to 2 minutes. You will receive a message saying Done. Installed 54 files total. when the process is finished.
    6. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.

changes in 8.4

8.3.11.1

  • NS-409 Nightfall support

8.4 milestone 1

  • moved @follow from _bonds to _compliance
  • @follow priority management should be better now
  • @navigate in _compliance (support for automated navigation)
  • an attempt at fixing repeated autolock
  • message 42 (INTERFERENCE_STATE) allowing system modules to react to interference. Proof of concept: _ambiance will now shut off audio output
  • entirely when type S interference is present.
  • support for 'weapon' bus messages to _sentinel
  • removed 'light' message (old OSL will no longer work fully)
  • 'power' message now sends every 10 seconds to all devices; format changed from percentage to float
  • 'rate' and 'power' now send to any newly-attached device
  • converted arabesque 'sound' and 'preload' verbs into actual system commands
  • arabesque 'vox' command now '@sound vox ...'
  • interference now in _coil (introduced bug? interference not applied if shield fails)
  • blocked _coil from emitting multiple 'charge cycle complete' audio notifications
  • port protocol
  • @persona now lists active RLV folder
  • new probe strategy for finding batteries on attach: system probes 6 times at a normal interval until it finds a battery; this may solve every issue
  • forever?
  • refactor _console-screen::_manager into _core and _interface (expect bugs)

8.4 milestone 1.1

  • finished incomplete optimization of _power that was causing charging issues

8.4 milestone 1.2

  • implemented '@navigate auto'
  • cleaned up '@zap'
  • fixed BaCdrive charge bug

8.4 milestone 1.3

  • fixed issues with manual starting of node navigation
  • added exception to battery probe strategy for BaCdrive
  • added beta-version tagging (displays in @about and on main menu)
  • restored persona and carrier display to HUD
  • progress on fixing exhibition-tty listener overflow
  • fixed HUD removing section -1 for devices that did not have a section
  • simple @off, @halt and @reboot commands
  • @send - range is 0 (regionsayto self), 10 (whisper), 20 (say), 100 (shout), region (regionsay), UUID (regionsayto)
  • fixed HUD not responding to @probe—no more need to reboot to make the HUD show up!
  • public bus 'trigger' verb for event handling (_arabesque should hook for event-driven e_ action notecards; provide linked message API for other
  • programs to respond, too)—this could be used for adding on extra custom environmental reactions to things like sitting on a charger or leaving a
  • display booth; similar to 'navigate'; consider adding e_attach?
  • renamed '_init' script to 'e_boot'
  • added 'e_charge-start', 'e_charge-stop', 'e_shutdown' events
  • arabesque now issues commands with id of script activator, not unit; added $user and $username evars for object that activated the script
  • added 'H^ ' for deleting spaces before variables in arabesque.
  • restructured menus into putative 8.4.0 format
  • @commands reindex

8.4 milestone 2

  • full RLV relay (new External Restriction Interface (ERR) module named _restraint, not to be confused with old CSB module name)
  • ERR multiple restraint source integration
  • ERR restraint removal
  • ERR block system chat when in effect
  • ERR @clear command implemented
  • @charge command for interfacing with chargers directly
  • attempt to fix animation permissions errors in _bonds
  • attempt to eliminate remaining issues with local HUD not showing up when it should
  • power profiles should now update menu text correctly
  • moved vox filter interface from _obedience into _compliance to cope with enlarged command vocabulary overloading the index
  • ERR send !release,ok in response to @safeword
  • integrated HUD for akashic icon

8.4.0 milestone 2.1

  • gender-q and gender lightbus messages; 610 (EFFECT_VOCAL) and 611 (SEND_GENDER) messages
  • fixed missing menu graphics in manage > policy
  • commands will automatically re-index rather than reporting 'command not found' if no commands are known
  • HUD should now accept messages from non-controller peripherals; should make @rainbow work correctly
  • menu states for _restraint options
  • _foundation will now auto-boot after reset once _oem is done loading—let's find out if this is a bad idea!
  • basic captive audio (audience); no point in using it yet, though; has the awkward habit of punching through intended deafness
  • work on fixing xanadu 8.3 bug that prevents available updates from being displayed
  • improved HUD efficiency; cleaned up possible sources of misbehavior e.g. stuck hovertext
  • expanded 601 (QUERY_BATTERY) into DEVICE_QUERY so _sentinel can re-poll for HUD key

8.4.0 preview A (milestone 3)

  • revalued jump to be 403 J/sec instead of 203 J/sec
  • fixed a bug where rejected devices would install anyway
  • removed 'keychain migrate' command: rarely used and upgrades from earlier than 8.2 can just install 8.3 temporarily if they really need it
  • automatically add accepttp exceptions for owners provided the unit can teleport
  • UPM CLI: @guest
  • UPM consent
  • UPM menu interface (included under manage > users)
  • fixed 'previous' and 'next' buttons on user browser
  • UPM integration for _restraint and _compliance::navigate
  • UPM-authorized adding for light bus devices not owned by unit
  • Renamed 'System' package to 'Companion' henceforth; added 'ATOS/E' package to list of updatables.
  • UPM: owner-vs-object distinction (still has some bugs)
  • ATOS real death (messages 905 and 906)
  • Cleaned up bootstyle and boot sequence slightly

8.4 build 2016-06-01

  • Added additional exceptions to guest access for controller and self access (when unit is own guest)
  • Added default action selection: either accept (temporary whitelist) or deny (ignore access request.) Deny is the default. Asymmetric options are to minimize hassle required to fix the issue if the unit is AFK.
  • require basic local access to control the dwm session - no more menu prompts for rejectees
  • RLV relay should default to off!
  • fixed guest access prompt for registered users; caused by keychain changes—cached permission bit now cleared before all keychain operations
  • fixed "details" button not working on guest access dialogs for users (should have been "details...")
  • fixed guest access prompts appearing for NULL_KEY and blank key
  • added "!lamp on" and "!lamp off" for upcoming flicker script improvements
  • fixed owners list not being cleaned after object transfer
  • fixed badge clicks not working on _console-screen

8.4 build 2016-07-16

  • re-fixed guest access prompts appearing for NULL_KEY and blank key
  • resolved enormous and redundant lists of secure commands in the @commands index
  • @audience; audience will now respect subsystem status and interference for hearing (still needs ERR integration)
  • no execution of e_boot? issue seemed to go away when poked
  • started implementation of chassis spec; _foundation and _power on stack-heap watch
  • relocated whole remote control interface to _bonds because of running out of space in _puppet
  • _puppet should no longer generate foreign device prompts for attachments

8.4 build 2016-07-24

  • fixed faulty management of temporary whitelist and temporary blacklist causing stride corruption
  • @range command for follow control; also @leash now aliases to @follow
  • new order for subsystems: video, audio, move, teleport, rapid, voice, mind, preamp, power amp, radio in, radio out, GPS, identify. This will affect t3z's old power profile scripts for Arabesque. (They have been updated. Some may have changed a little.)
  • switch to using list facilities for summing elements in _power
  • chassis specification support: _foundation, _power, and _sentinel (ATOS/E 12.0.1) now all recognize a number of chassis options using messages 993 and 994 from _puppet (updated chassis controller module will be released soon)

8.4 build 2016-07-31

  • resolved totally useless shutdown behavior
  • fixed abnormal windlight changes during charging
  • @policy command implemented; doesn't actually affect the system yet, though
  • empty fields now hidden in @about; serial prefix is now "NS" for non-DAX and non-SXD units (otherwise still "SXD").
  • @unleash to mirror @leash

8.4 build 2016-08-13

  • '@persona probe' to force refresh of personas list
  • XSU support

8.4 build 2016-09-10

  • waypoint following should not set the device manager's follow target
  • added xanadu 'cleanup' message to destroy dead package installers
  • fixed '@navigate stop'
  • added 100 kJ cap to @zap when _sentinel is installed (not foolproof; can cause disasters if multizap is used)
  • fixed redundant dialog menus opening when touch screen is used (caused by conflicts in local guest access code)
  • added optional header file for coilDDT so messages can be named
  • menu controls for basic policy features
  • local command input on /1, like OC commands (see '@commands local' and '@commands prefix')
  • serial numbers not of length 9 will now be displayed without hyphens in the boot sequence and @about
  • subsystem blocking by devices (proof-of-concept device: cortex)
  • IRR policy control of subsystems, vox, apparel, and persona settings.
  • beginning support for arousal model (not yet available)

8.4 milestone 5

  • /1 command prefixes now forced to lower case
  • curfew policy
  • block follow and navigate while motors disabled
  • restrict access to @restraint/@rlv (managers only)
  • curfew time entry
  • fixed a case where guest authorization was removing the wrong listeners
  • fixed a case causing corruption of temporary white/black lists (numbers appearing in lists)
  • require basic remote access to create a tty session - no more menu prompts for rejectees; unfortunately this means that old remote consoles (before 1.5) no longer work
  • fixed a long-standing bug where changing @access settings would not clear cached permissions for last accessor
  • don't ask for permission to respond to ! commands in RLV (??? seems to already be fixed)
  • default to verbosity = 1
  • IRR implementation: radio limitations (implementation restriction: clearing the user list can cause exceptions to linger until reattach)

8.4 milestone 6

  • fixed HUD "0/-1" problems
  • NRS: removed 'arrived at waypoint name' messages
  • added subtle sound effects during _oem parsing to make it easier to diagnose hung updates
  • Remote script execution
  • Sync users

8.4 milestone 7

  • Reapply restraints on relog
  • Add semifreeze to bonds/power/coil
  • Adjustable speed during navigation
  • Tutorial
  • beacon test mode
  • beacon frequency
  • capacitor charging
  • permission exemptions
  • timeouts
  • control menu
  • management commands
  • block safeword with _oem switch
  • Tutorial widget (HUD)
  • Feedback menu
  • Raise PONG_TIMEOUT to 45 sec
  • Console attach in response to power off?

8.4 alpha 1

  • Set @beacon and @aux to manager/owner only commands
  • llList2List issues in local /1 commands
  • '@optics apply' (for ATOS/E)
  • Preserve manually-set !broken through teleports
  • Fix inverted freeze/unfreeze light bus messages

8.4 alpha 2

  • All subsystems blocked after removing a subsystem-blocking device
  • no llSetTimerEvent() at all
  • @navigate start <node name>
  • Added menu chime schemes 6 through 9
  • smarter #RLV management for consoles
  • Support for chat power cost adjustments via the chassis controller
  • Singularity detection (!!llTextBox!!)
  • Add '@authority none' and '@name none'
  • '@navigate start' should wait until arrival to trigger node
  • Use '@navigate auto' even for nodes belonging to authorized users
  • block send emotes
  • block send whisper only
  • Confirm ERR correctly detects user permissions when using @restraint command
  • improve projector screen persistence
  • fix 'commands' browser
  • PIN locking should limit available /1 commands to unlock only
  • Fix default position for segments to be less hostile to manual re-positioning
  • Fix beta version display on menus

8.4 alpha 3

  • Solve issues with inconsistent states in session creation queue
  • Check cases of '@bolts auto' failure
  • Proof of concept for foreign device consent interface: electrosense-powered door
  • Switched to fartouch:2.5 for motor locks
  • feedback for single-shot power loads (let devices ask for a pulse of power and get feedback)
  • CB sends real-port instead of port-real
  • performance overhaul to layout function
  • 'allowed/forbidden' messages inverted for policies
  • Fix behavior of missing buttons
  • Mute 'session destroyed' messages
  • Could not find notecard 'e_charge-start'.

8.4 release candidate 1

  • domain functionality shakedown
  • _restraint shakedown
  • reimplement HUD integration API
  • Add domain to @about
  • Raised cached display name limit to 23 bytes
  • Add CSU parameter teleport-recharge-time
  • chatshout overrides chatnormal
  • Fixed interference support for power-free (BaCdrive) models
  • cortex strips persona folder on shutdown
  • Protection against missing button labels
  • Code modernization
  • Encoding issues causing vanishing/imploding menu items
  • Add blank items to devices list menu for spacing
  • Code modernization

8.4 release candidate 2

  • Audience respect for pertinent RLV restraints
  • Added (( as an alias for ooc (note that this is usually intercepted by RLV)
  • 'add' and 'remove' instructions in 501 EDIT_MENU
  • Support 711 and 712 for system module removal
  • ifexists for Arabesque
  • Added @open command for triggering applications
  • Added SET_SELF_ACCESS, removed SEC_SELF
  • Ignore blank RLV commands

dax/3

Get ready to fall in love with a machine—again.

Today marks the release of our newest control system, the Class 3 Digital Articulated Escort. Powered by Companion 8.4, the DAX/3 presents one of the most powerful and completely immersive experiences available on the grid to date.

Auxiliary power.

Say goodbye to fumbling around in the dark for your battery. When your Companion 8.4-powered DAX/3 unit shuts down, it switches to auxiliary power, giving you a few precious minutes to swap out your power source, observe your surroundings, and keep in touch with your friends.

Intimate design.

The purpose of the DAX series has always been clear: to bring robotics into the personal domain. Tamara Peluso's finest work to date, the organically-sculpted outer shell captures that perfectly, creating a shape that both celebrates the curves of the human body and defies them, challenging the eye to remember you're something more than human.

Real restraint.

Get ready to leave your other toys behind. Companion 8.4 includes a full RLV relay capable of handling restraint sources from up to 64 users simultaneously. With the new Consent model, equipment belonging to your authorized users can be automatically granted permission to apply restrictions without any intervention.

Price: L$1000

(Battery sold separately.)


introducing navigation

After nearly a year of research and development, the Navigation Routing System is now available for general use. Bring your home or business to life with real automation, permitting units to carry out tasks you program. Implement greeters, tours, touchless software updating, housekeeping services, and more with ease using the new Navigation Route Designer HUD.

To place a node using the HUD, simply click the corresponding icon, and it will be spawned at your feet. If applicable, a prompt will then guide you through the process of setting up your new node.

  • move: The simplest node type, these instruct the unit to proceed to the next node in the chain when reached. A series of move nodes is ideal for guiding a unit down a corridor or long path, or simply turning a sharp corner.
  • teleport: Like a move node, the unit will continue onward to the next step in the sequence when reaching this node. However, it will do so by teleporting. This makes it easy to create teleportation hubs that can send units anywhere in the sim!
  • speak: Speak nodes instruct the unit to say a pre-set message that you choose. (Even with their mind subsystems disabled.) These are great for tours, greetings, and more. Afterward, the unit will continue to the next node if one is specified.
  • wait: The unit will wait at this node for a specified number of seconds before moving on.
  • animate: Like a wait node, but with one extra twist: drop an animation into the node to make the unit play it while waiting. To replace the animation, simply drop in a new one.
  • script: These are the most versatile node type, and can execute any commands that a normal user would be allowed to perform on the unit with a remote console. Toggle subsystems, trigger RLV commands, or turn the unit off entirely! As with other node types, the unit will continue to the next node in the chain after the script is finished.
  • halt: Unlike all the others, the unit will not continue pathing past this point.

Automatic forward chaining: by default, the HUD will connect the nodes in the order you place them down. This can be toggled by clicking the corresponding text in the bottom-right corner of the HUD. To manually re-connect a node, simply click on it and select 'set next' from its main menu.

Undo functionality: click 'delete last node' on the HUD to remove nodes one at a time, from most recent to earliest.

Version requirements: A controller running Companion 8.4a or later is required to experience the navigation system. See Updating to the latest firmware for more information.

Price and availability: the Navigation Route Designer HUD is available now from our Main Campus in Eisa for L$600. Drop by our Main Campus Sales Area and try out the demo route!


Buy all our playsets and toys

Nanite Systems is pleased to announce the following product releases:


ATOS/E 12.0.0e and Companion 8.4a

Read the full announcement here.

solid-state security

Representing the culmination of almost five years of work by NanoSec Chiyoda office in partnership with the Eisa Consumer Products Division, Nanite Systems is proud to present the Nightfall urban security controller. At home equally on the beat and in the office, the Nightfall is the perfect foundation for building an incorruptible, always-on police force capable of responding to any threat with the same precision and efficiency as a well-trained soldier and resolving disputes with robust, tactful ethical reasoning.

The Nightfall brings a much-needed refresh to the look and feel of our standard Companion-based platforms, with updated sounds, a clearer voice, and an improved hinge mechanism. It includes ATOS/E pre-installed, as well as a starter battery, so there's no delay whatsoever between installation and entry into service.

Available now online or at one of our store locations for just L$800. For bulk orders, please contact sales directly.


companion 8.3.11

A month ago we said we expected Companion 8.3.6 to be the last release of the 8.3 series. That didn't pan out—in that interval, not one, but six patches have been released, addressing topics as diverse as support for the new Barthes Asset Control cranial disc drive, the death of the "night light" bug, and underpinning for our new ATOS/E combat extensions module.

introducing Companion

In preparation for the release of the Advanced Tactical Operating System (ATOS) later this year, we've decided to rebrand the existing SXD System Firmware as "Companion" instead of just "System." Installation and update media will continue to be distributed as 'System' until 8.4.

introducing ATOS/E

Currently in open beta, ATOS Elements is a set of combat-oriented features that can be used by any Nanite Systems unit. When finished, it will enable weapons connectivity, real heat management and automatic cooling control, a system damage model with automatic nanite repair and repair stations, representation of injuries through RLV folder management, and on-screen identification of friend-or-foe status (IFF) with health bars for targets.

Although they sound the same, ATOS/E should not be confused with ATOS Cortex (or ATOS/CX) which will be only available for Aegis, Aide, Scout, and other military-grade controllers. ATOS/CX is very similar in featureset to Companion with the ATOS/E add-on, but removes civilian-centric features such as personas and the speech pipeline for a more streamlined, battlefield-ready experience behind a brand new, first-person-shooter-like HUD, the Shield Command Environment, or SCE.

major release highlights

  • New command for controlling lights: @optics
  • Teleporting short distances no longer completely discharges the FTL capacitor.
  • New teleport sounds (model-dependent.)
  • New on-board manual system, @help (not yet fully complete.)
  • Error messages when unsupported commands are used
  • Support for custom boot/shutdown and menu sound effects
  • Numerous bugfixes; see below

As of 8.3.0, the Tai Yong Labs DAX/T (part number SXD-02-0800-T) is officially deprecated following the closure of Tai Yong Medical. Existing DAX/T users are encouraged to look at the controller comparison page and consider a replacement. DAX/T controllers will continue to function and be updatable as long as 8.x DAX/2 controllers are supported (i.e., until the release of version 9.0), but controllers retrieved using (Redeliver) monads will be stuck on 8.2.1, and not updated to the present or future versions.

installation instructions

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on!
  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select update. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running 8.3.0 or later, select update.
    3. Select the System_8.3.11 package and upgrade it.
    4. Accept the notecard _System_8.3.11_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    5. Installation will take up to 2 minutes. You will receive a message saying If this is the first reset after a system update, you may now boot the OS. when the process is finished.
    6. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.

changes in 8.3.6 - 8.3.11

What's new in System 8.3.11?

  • Persona RLV folders will now automatically be reapplied when the controller is attached.
  • Fixed a bug where "Still loading OEM information. Please wait." message would lead to lines in the _oem table being skipped. It should no longer ever be necessary to run an extra @reset foundation after updating.
  • Local access denied from devices will now send a message to the responsible person; this was broken in 8.3.0 or shortly afterward.
  • Light bus message "auth-compare" to test if someone has permissions to override another user when using a device.
  • Callback for charging with negative amounts: if successful, power drain is rewarded with a 'charge' message equal to the number of kJ that were stolen. (Only applies if drainprotect is disabled.)

What's new in System 8.3.10?

  • Better handling for rezzing the controller on ground? Spurious restraint applications should be less likely.
  • Fixed names for interfered subsystems.
  • Added %% and $$ to arabesque, like @@
  • _power now always emits message 4 (POWER_RATE) even when system isn't charging; required for _sentinel heat support
  • _foundation now waits until _power is finished shutting down to initiate reboot; should solve problems with hinge and other devices acting as though the system is powered down after a reboot
  • Removed command browser from _console-screen.
  • New icons for _console-screen (manage, sign, shield, fan).
  • add-button light bus command for _console-screen.
  • !fan is disabled if _sentinel is installed.
  • Changed linked message passing model: messages over 1000 will now be passed to memory card without modification, except 2001 and 2002.
  • Implemented support for RCA (spectrum + 1) charging.
  • Persona button on HUD did not work correctly.
  • Added multiple|item|packing for messages 71, 182, 183, and 184
  • this majorly reduces buffer overflow problems during boot and fixes a new bug where the persona list request (message 70) was not being seen by _songbird.
  • Slightly lowered teleport cost.

What's new in System 8.3.9?

  • Fixed _cortex emitting "persona default" on reset.
  • Fixed adjustheight ownersay spam on attach / failure to restore height offsets on attach.
  • Added BaCdrive controller support.

What's new in System 8.3.8?

  • Fixed suspend-follow not clearing on BaCdrive after persona change.
  • Added BaCdrive peripheral support.

What's new in System 8.3.7?

  • Refactored hover height stuff into _bonds to free up memory in _power; fixes stack-heap in 8.3.6.
  • Added power-on hover height adjustment and changed syntax of @hover to support.

What's new in System 8.3.6?

  • FTL/teleport subsystem can now be turned on while capacitor is full.
  • Lights-on after shutdown fixed: moved actual 'off' lightbus message into _power.
  • 'cancel' did not work in filter configuration menus.
  • Devices menu no longer echoes its actions to the owner
  • HUD button for devices was using wrong session if unit was last user of session 0 (now eliminated all uses of -1 hackery)
  • Fixed: system failed to disconnect from chargers properly on relog or forced TP.
  • Added @setup console, @hover, and @verbosity to the index of commands

system 8.3.5

It's that time again. After two iterations of the beta process, we're confident we've got a release that's stable enough for general use. This update mostly contains bugfixes, but there are some new features as well. The last scheduled version of the 8.3 series will be 8.3.6, which will add a convenient auto-update command and little else.

introducing Companion

In preparation for the release of the Advanced Tactical Operating System (ATOS) later this year, we've decided to rebrand the existing SXD System Firmware as "Companion" instead of just "System." Installation and update media will continue to be distributed as 'System' until 8.4.

major release highlights

  • New command for controlling lights: @optics
  • Teleporting short distances no longer completely discharges the FTL capacitor.
  • New teleport sounds (model-dependent.)
  • New on-board manual system, @help (not yet fully complete.)
  • Error messages when unsupported commands are used
  • Support for custom boot/shutdown and menu sound effects
  • Numerous bugfixes; see below

As of 8.3.0, the Tai Yong Labs DAX/T (part number SXD-02-0800-T) is officially deprecated following the closure of Tai Yong Medical. Existing DAX/T users are encouraged to look at the controller comparison page and consider a replacement. DAX/T controllers will continue to function and be updatable as long as 8.x DAX/2 controllers are supported (i.e., until the release of version 9.0), but controllers retrieved using (Redeliver) monads will be stuck on 8.2.1, and not updated to the present or future versions.

installation instructions

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on!
  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select update. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running 8.3.0 or later, select update.
    3. Select the System_8.3.5 package and upgrade it.
    4. Accept the notecard _System_8.3.5_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    5. Installation will take up to 2 minutes. You will receive a message saying If this is the first reset after a system update, you may now boot the OS. when the process is finished.
    6. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.

changes in 8.3.3 - 8.3.5

What's new in System 8.3.5?

  • Possible solution for post-teleport blackout; inconclusive.
  • Short-distance teleports (less than 5000m) no longer completely discharge the FTL capacitor.
  • New command for controlling windlight: @optics <windlight preset>
  • Another fix for exhibition-tty overflows; should no longer be possible to create too many listeners unless there are genuinely 64 sessions or more—stale listeners weren't being removed if a new dialog was requested before the last one was clicked.
  • Moved @follow from _arabesque to _bonds for pragmatics.
  • Moved @puppet ddt into _coil; needed more room in _puppet.
  • DWM input on empty menu cells is reported during dynamic/audio prompts; generates 'button not found' errors.
  • RLV chat redirect not restored after updating: automatically rebind if user channel changes.

What's new in System 8.3.4?

  • RE-FIXED: fixed a bug preventing setting of menu sound schemes
  • RE-FIXED: adding and removing boot and menu schemes with 'scheme add' and 'scheme remove'
  • add 182 for @puppet ddt
  • light bus must power down when system halts

What's new in System 8.3.3?

  • HUD now plays sound effect (using info from new interference-state light bus verb) when sensory input is disabled/enabled due to interference
  • output pipe and release should now display on/off status in ex4 menus properly
  • fixed bug in _oem command handling; should be more elegant now.
  • attempted fix for 'too many listeners in exhibition-tty': users now cannot be added to the session creation queue multiple times
  • started rebranding as 'Companion'; main menu and boot screen will now always display correct version
  • @puppet ddt
  • manual system for command reference
  • unregistered commands and/or non-existent commands now emit error messages when used
  • moved the sittp restraint back to the teleport subsystem; it's just too much power!
  • make FTL core a recharging load (like the shield)
  • fixed a bug preventing setting of menu sound schemes
  • adding and removing boot and menu schemes with 'scheme add' and 'scheme remove'
  • autolock should no longer continue to trigger while controller is locked
  • menu should time out and return home when not in use
  • speech marker suppression token: "#@!" embedded in a speech message will be removed, and the message will not produce a speech marker.
  • (experimental titler now built into superbit)
  • _power now reports subsystem state changes (using the @power command) to the unit if verbosity is 0 or 1 and the unit would not otherwise be notified

system 8.3.2

After many beta versions and unstable early releases, the next major release of our civilian firmware, 8.3, is finally available. 8.3.2 addresses a number of common bugs encountered by testers of the 8.3.0 and 8.3.1 versions which were newly introduced in those patches.

major release highlights

  • complete rewrite of menu and display code allowing support for more types of displays and simultaneous accesses by multiple control devices (8.3.0)
  • command-line interfaces for package management and gender settings (8.3.0)
  • support for configuration file for the local console HUD (8.3.0)
  • speech filtering pipeline should now remain robust after rebooting (8.3.0)
  • OEM table file can now contain system commands in addition to hardcoded parameters; unrecognized lines will be interpreted as system commands (8.3.2)
  • preliminary support for the Mynt Kinetics MynK-i controller prototype's planar holographic display (8.3.2)
  • new way of getting back into the chat redirect: /1capture (8.3.2)

As of 8.3.0, the Tai Yong Labs DAX/T (part number SXD-02-0800-T) is officially deprecated following the closure of Tai Yong Medical. Existing DAX/T users are encouraged to look at the controller comparison page and consider a replacement. DAX/T controllers will continue to function and be updatable as long as 8.x DAX/2 controllers are supported (i.e., until the release of version 9.0), but controllers retrieved using (Redeliver) monads will be stuck on 8.2.1, and not updated to the present or future versions.

installation instructions

Express route: everything below can be skipped if you received a (Redeliver) object with your controller. Simply wear it and you will automatically be given a clean copy of the newest version. If you have made changes that you'd like to keep, though, read on!
  1. Check your current software version by selecting 'about' from the main menu. If it's 8.0.0 or later, you're good to go. If it's older, or you can't even find the 'about' item, contact technical support directly for further assistance.
  2. Come to a region with Xanadu support.
  3. Getting ready. Type the following to back up your current list of users: @keychain save
    This is optional if you do not wish to preserve your current users.
  4. Installation. Go to the following menu: manage > software. If you are running 8.2.1 or earlier, select update. If you are running 8.3.0 or later, select connect.
    1. Select xcentral:0.
    2. If you are running 8.3.0 or later, select update.
    3. Select the System_8.3.2 package and upgrade it.
    4. Accept the notecard _System_8.3.2_info when it is offered. If you are running an Aegis that was previously running 8.2.0, there are additional instructions inside that are very important.
    5. Installation will take up to 2 minutes. You will receive a message saying If this is the first reset after a system update, you may now boot the OS. when the process is finished.
    6. Turn the controller back on.
  5. If you do not currently have a HUD at the bottom of your screen, type @setup console.
  6. Finalizing. Reboot once to apply the applicable changes from the last step.

changes in 8.3.0 - 8.3.2

What's new in System 8.3.0?

  • All systems have the ability to auto-position their batteries now, provided the model signature has not been changed
  • Fixed Scout readout support (broken in 8.2.1)
  • Fixed Aegis HUD support (broken in 8.2.9)
  • PIN locking fixed
  • vox no longer messes up on reboot
  • All menus except PIN management converted to use ex4 internally
  • Finished converting Xanadu and Users management
  • @xanadu
  • Ongoing work to translate more dialog-based menus into the new ex4-compliant format.
  • ORIX controller identification protocol. For now, the type field is limited to 'NS' for standard controllers or 'SXD' for SXD and DAX/2 controllers, but this will change eventually to support reporting of e.g. cyborgs.
  • light bus will no longer be left in 'on' state following foundation reset
  • @gender
  • System will now check for "s_recover" animation instead of using default AO "standup" if available; must last less than 2.40 sec
  • renamed _restraint to _bonds
  • _foundation now forces waiting until OEM file has fully loaded, eliminating many awkward inconsistencies
  • power gauges for slice-based controllers (SXD, DAX, and 112) should no longer be the wrong size following script resets (related to OEM model identifier loading)
  • properly fixed sendchannel_sec restraints that were blocking /channel chat even when the output pipe was disabled.
  • HUD configuration file
  • 'Stargate telemetry received' message only when unit is focus of TP.
  • experimentally moved sittp to be part of the rapid subsystem instead of teleport; this is one of the most common customer complaints
  • _power is now responsible for managing RLV on boot/shutdown/attach, both alleviating overloads in _foundation caused by too many registered commands and substantially improving the efficiency of these processes
  • Make 500 edit the menu directly instead of relying on the main display function.
  • Exhibition 4 (ex4) new graphical manager based on a Model–ViewController architecture, supporting multiple concurrent sessions
    • Exhibition/DWM: support for primary display
    • exhibition-core menu and session management
    • text labels for menu items (for better display over TTY)
    • Exhibition/TTY: support for multiple dialog-based terminal interactions

What's new in System 8.3.1?

  • Personas menu no longer messes up after a persona is activated
  • Xanadu couldn't get info notecards properly
  • Commands menu should cycle pages properly

What's new in System 8.3.2?

  • _oem file can now contain system commands, just like an arabesque script with no parameter substitution—any unrecognized verb will be passed on as a normal 1 (COMMAND) message. Rejoice; you can now use this to hardcode things like gender and access settings. Keep in mind that _oem files already support color, so be sure to use floating-point format and omit 'save', e.g. 'color 1 0 1' for cyan
  • fixed @gender voice changes producing null chat sound warning still
  • _power shouldn't emit level threshold notices more than once per 10 seconds
  • Added new cortex rebinding command: /1capture
  • @adjustheight:0=force on detach; no more weird vertical offset issues
  • "set PIN" and "locked" menus should now reprompt properly
  • changed remote access default to all users rather than owner only
  • ! remote control no longer works due to changes in access context code
  • merged preliminary MynK-i support branch into trunk (support for planar holographic displays with project/stop_project light bus messages)
  • HUD menu buttons and remote console menu button should work as intended now

notice of region name change

Our home sector, Latexopolis, has been officially redesignated Eisa by the Galactic Standards Authority. Please ensure all mail is correctly addressed.


1 2 3
Next