The Autonomy Control Systems Remote Control allows a user to operate an android featuring the ACS Central Control Unit (CCU) from anywhere in the same region. It can connect to any unit configured to allow remote access. Only one unit may be controlled at a time.? The Remote Control is sold with modify and transfer permissions, so you can buy one to give another person.
The Remote Controller Chip performs the same function in a compact chip that may be installed in any construct operated by an ACS CCU, a Nekobot controller, or a Cinis Power Core.? It is sold with modify and copy permissions, but NOT transfer.
Important: The Remote Controller Chip is NOT designed for installation in organic beings and will not function there. It will also NOT recognize constructs with unsupported operating systems, and will not function there. Refunds will not be offered if you purchase one and cannot use it for these reasons.
See below for a list of changes in the latest Remote Control upgrade.
By default, every CCU allows any remote control created by ACS to connect to it and operate its basic functions (shutdown/activate, freeze, silence, stay, and changing modes).
Remote access may be disabled by setting remoteok=0 in the unit’s programming. For example, one might add the line
to the unit’s “p99 Unit” notecard. This will not disconnect any remote controls that may already be connected, but it will prevent any new ones from connecting. (It also will not prevent the workbench from connecting, when the unit is lying on it.)
While examining this notecard, note the line “set hackable=1”. This is an OUT-OF-CHARACTER setting that will in the future cause some things to happen which may assist a knowledgeable operator who wishes to, in character, gain unauthorized access to a unit. The methods for doing this are not documented and will not be. Neither are methods for combatting hacking in character, though this too will be possible. If you do not want to allow in-character hacking, change the “1” to a “0”.
A unit is usually aware when a remote control connects to it ((a “REM” indicator will appear on your HUD)), but cannot tell who is operating it.
When so directed, a unit’s thoughts may be reported to any remote devices connected to it, including remote controls and the workbench. ((Click on your HUD, then “Think.”)) The unit is not necessarily aware that its thought is being so reported.
Using the Remote Control
A handheld Remote Control is typically held in the left hand for operation, although it may also be rezzed unattached. A Remote Controller Chip is attached as a HUD (next to the CCU, for units with one). You may operate a remote control by clicking on it if:
- You are within 5 meters of it, AND
- It is not being used by anyone else, AND any one of the following:
- You own it, OR
- It is not held by anyone, OR
- It is held by an android that is immobilized.
You may operate a remote control you are holding (or have installed) by typing “/36remote”, which may be easier than clicking on it. When you do this, or click on it, the remote will scan the sim for ACS units with active remote interfaces, and (assuming any are found) offer a list of them. Click the name of a unit to connect to it.
You can also specify the first few letters of the unit’s name (username or display name) in the chat box, e.g. “/36juli”.
Connecting to the unit in this way is sufficient to allow access to some of the unit’s functions – mostly, the same ones you could access from the unit’s Access Panel, if it has one, plus remote direction (see below). To gain additional access, click “Log In,” and enter the unit’s password in the text box. (If you do not have a password for the unit, perhaps you are not supposed to have greater access to it.)
Logging in to the unit using one of its passwords allows the operator additional control of the unit, which may include:
- Message menu:
- Think – Sends the unit a thought
- Query – Sends the unit’s CCU a query to which it will respond. The unit will not be aware of the query or its own reply.
- Order – Sends the unit an order it must obey. The unit will not be aware of the order, but may realize it is not acting on its own initiative.
- Message – Sends the unit a message it will be aware of. It may reply if it so chooses.
- Say, Whisper – Causes the unit to speak words of your choosing
- Emote – Causes the unit to act as you direct
- Software menu:
- Programs: Lists the unit’s program modules so you can download or delete one, or upload a new one. (To upload a new program, first write the notecard, then put it into the remote control. Right-click the remote, click “Edit”. Go to the “Content” tab. Drag the notecard from your inventory into the contents. You can then close the edit window. BE CAREFUL NOT TO DELETE ANYTHING YOU DIDN’T PUT THERE YOURSELF.)
- Animations: Lists the unit’s loaded pose animations so you can delete one or upload a new one.
- Defrag – Causes the unit to reload its program memory, which may resolve certain problems
- Disconnect: When you are finished controlling the unit, disconnecting will allow you to connect to another. The remote control will also disconnect automatically in a short time if the unit logs out, moves to a different region, or detaches its CCU.
Automatic Login: New in Version 1.8! To cause your Remote Control or Remote Controller Chip to automatically log into a unit once you have connected to it, place a notecard in it whose name is the unit’s username (e.g. “brattle” or “kaori.gray”) and whose only content is the unit’s password. You may add notecards for as many units as you like.
If you attempt to use a feature for which you do not have sufficient access, you will be notified.
Future CCU versions may offer slightly different commands.
The Remote Control and Remote Controller Chip are modifyable, even if they say they aren’t when in your inventory. You can change the color of the larger prim while holding it. If you want to change its name, you will need to rez it on the ground, edit its name, then pick it up again.
New in Version 1.9 of the ACS Remote Control and ACS CCU, you can gain direct control of a unit’s motor functions to move it in any direction you choose. Click the “Direct…” button. In a moment, you will receive a dialog box asking you to allow the Directing HUD to be attached. Click Yes, and it will appear at the top of your screen.
The controls have the following functions:
- Arrows: Cause the unit to walk forward, walk backward, turn left, or turn right. Hold down the keys to keep the unit moving. The unit cannot override your remote commands, but once you release they key, it will regain control of itself in a few seconds. (The Motion indicator on the unit’s HUD and Access Panel turns purple to indicate the unit is being remotely controlled.)
- +/- above the arrows: Increase or decrease the speed of remotely controlled movement.
- Dialog: Brings up the usual Remote Control dialog.
- Call: Calls the unit to approach the remote control. (Be careful when using this, as the unit will attempt to move directly toward you. It will not steer to avoid obstacles. It may be better to simply send the unit an order to come to you.)
- Tether: Allows you to select an object near the unit which it will then be forced to stay near. The +/- keys below the Tether button change how far from the object the unit may travel before being forced to return.
- Release: Releases the unit from any Tethering.
- Chair icon: Allows you to direct the unit to sit on a nearby object.
- Power icon: Puts the unit in standby, or reactivates it.
- Snowflake icon: Freezes or unfreezes the unit.
- Chat icon: Mutes or unmutes the unit.
- Thought bubble: Allows you to type a message which the unit will experience as a thought. (For example, “Mr. Chelton sure is a nice guy.”) Usually requires login.
- <-? Sends the unit a query to which it must respond. (“How do you feel towards Mr. Chelton now?”) Some or all queries may require login to be effective (for CCUs older than v1.10, all queries usually require login.)
- <-!? Sends the unit a message. (“Hello there. We are going to have fun today.”) Usually requires login.
- <-X Sends the unit a command it must obey. (“Change into a sexy outfit.”) Some or all commands may require login to be effective (for CCUs older than v1.10, all commands usually require login.)
- Large speech box: Sends the unit a message it will say aloud. Usually requires login.
- Small speech box: Sends the unit a message it will whisper. Usually requires login.
- Happy face: Sends the unit a message it will emote. Usually requires login.
The Directing HUD will automatically detach from your HUD when you disconnect from the unit. At present it will also disconnect if you attach or detach other items from yourself; this behavior is probably a Second Life bug and hopefully will not continue. You may also detach it manually. It will not enter your inventory.
More on the Remote Controller Chip
- Compatibility with other systems may be added in the future, if appropriate information is available from the device’s maker
- As the chip draws its power from the unit in which it is installed, it will not function when the unit is shut down or in standby
- A unit experiencing cognitive interference will most likely be unable to operate the chip.
- For ACS Unit Owners: To allow a control to enable or disable your unit’s Remote Control chip at the operator’s desire, simply have the unit put the chip inside a folder in its Behaviors (or Shapes) folder, inside #RLV. Then program the mode to attachover: that folder to enable the remote control, and detach: that folder to disable it. (You could also lockfolder: that folder to ensure the unit cannot reattach it when it is disabled.)
Changes in Version 1.11
- The Remote Control should work properly when connecting to, or in the presence of, avatars with long display names.
- If you bought the Copyable version of the Remote Control, it is now actually copyable.
Changes in Version 1.10
- Login is no longer automatically required for Orders and Queries. The unit will be notified of the login level (0 if not logged in) and will determine whether the specific order or query requires a higher login level to be effective. (Generally speaking, simple orders like “Come to the Hub” or queries like “What are you doing?” should not require a login, or at least not a high level login. More invasive orders like “Love John Avatar” or queries like “How do you feel about John Avatar?”may require a login. Each unit may have its own criteria for determining this.
Changes in Version 1.9
- New Directing HUD allows you to direct a unit’s movement using the Remote Control
- New and improved animations for using the Remote Control
- Animation added for holding the Remote Control to keep it out of skirts and hips
- Remote Control no longer animates its owner when unattached
Changes in Version 1.8
- Ability to automatically log in to a unit upon connection
- Detach option on menu (handheld Remote Control only)
- Units available to connect to are now listed in alphabetical order
- Texture updated to use new ACS logo
Changes in Version 1.3
- Ability to use chat command to connect to a specific unit (e.g. “/36jul”)
- When connecting to an upgrader, indicate it as such, not as yourself
- When someone else uses a Remote Control you are holding, you are notified. (This can happen if you are frozen with it in your hand, for example.)
- Fixed problem causing Remote Control to sometimes become nonresponsive when attached
- Uploading software to another unit works more consistently
- No more script error produced if there is a unit in the region with too long a display name
- Animation times out if menu is ignored