Version 1.10.0 was released on July 20, 2014. It includes a few small features and bug fixes. There is no urgency to upgrade to it, as Version 1.9 works just fine, but if any of the changes listed below appeal to you, you may want to do so. We anticipate the next release being a series of Version 2.0 betas.
Version 1.10 seems to have slightly less memory available for programs than 1.9. If your programming runs close to a memory limit, you may want to remove a module or two before upgrading, then see if you can add them back. (Version 2.0, when it is released, will likely have a much greater capacity for storing programming, due to several types of new efficiencies that will be introduced, so if you need to reduce anything now you’ll probably be able to put it back in Version 2.0.)
New features in Version 1.10
- Remote access is now turned off if no program module turns it on. The program modules distributed with recent (and perhaps not-so-recent) CCUs do not do that. To make them do so, you can do any one of the following things:
- If you already have a program module that explicitly sets “remoteok”, such as the “p64 Remote” program module in the Program Exchange, you don’t need to do anything.
- You can edit your p97 Hardware (or any other high-level) program to be sure it has a line in it that says “set remoteok=1”. (This will override any settings you may also make at a lower level.)
- You can install the “p97 RemoteOn” program that is in the Workbench, which only turns on your remote access.
- The upgrader cannot do this for you automatically because it cannot tell if you have set it elsewhere, but it is easy for you to do or your owner to do for you using the Workbench.
- An often-requested feature: Custom controls may now be created that require login access to use. (This does not apply for standard controls like freeze and silence.) To use, just add a number from 1-9 after the widget letter. For example, the following line in a program module will create a control that cannot be changed using an Access Panel or a Remote Control or Workbench logged in lower than level 5. A Remote Control or Workbench logged in at level 5 or higher can set the control. The unit can still change it from its HUD (if selfuse=1), and it can be seen on any device even if it can’t be changed.
mode Shape (Doll=1,<0,1,0>;Robot=2,<0,0,1>) B5
- Internal redesign of power system to support new power source options.
- New program setting “panelkeys” specifies (by UUID) one or more individuals who can automatically open a locked panel door. Separate multiple UUIDs with a comma. The unit will not be asked whether those individuals are allowed to do so.
- You can now always send an “Order” or “Query” from a Remote Control’s “Message” menu, even if you are not logged in. The unit will be informed of the access level of the command (0 if not logged in; higher if logged in) and can decide based on that whether to obey it, return an error message, or respond otherwise.
- Error message when attempting to wake from standby has been clarified. If you are allowed to self-operate, you can try a second time within 30 seconds and it will work. (That’s cheating… but sometimes you need to cheat.)
- Reboot button added to Remote Control and Workbench menus when logged in. This should help with reprogramming.
- When you freeze or shut down while seated, your animation is no longer overridden. (Sometimes this will have inappropriate effects, like continuing to move while frozen and seated, but it is probably going to be better than standing up most of the time.)
- It is no longer possible to set a password for level N in a program module of level lower than N*10. If attempted, the unit will be warned and the password will not work.
Other Changes in Version 1.10
- Access panels with doors should lock when programmed to. (Access panels without doors cannot be locked, and never could.)
- If a remote control is connected to a unit when the unit shuts down or disables remote access, the remote control is disconnected.
- Remote security problem fixed
- Remote accessibility indicated on Cognitive menu
- When avatar’s display name is changed, CCU notices the new name when its power state changes. Going to standby is fine; you don’t (shouldn’t!) need to reboot or relog.
- Bondage Witch Products are now turned off when the CCU goes into standby or shutdown. Clicking a BWP switch when the unit is active puts it in standby; clicking when it is shut down or in standby activates it.
- Emotes do not say “moving slowly” when unit is frozen at low power level.
- When using remote to make unit sit, avatars are not offered as possible seats
- CCU can now generate its own menus without relying on the handle
- Windlight settings are no longer cleared on startup/standby/shutdown unless some effects are actually in use.
- “Close Panel” button now appears on Access Panel main dialog (for panels with a door that can be closed).
- By default, unit no longer says *tick* before each word when it is almost out of power. (You can still set it to do so using setpretickword:*tick*.)
- Speech is no longer slowed immediately after speaking, when using battery.
- When a connection indicator is clicked at the top of the HUD, some information is provided about the connected device.
- “trustedcreators” can now be specified by UUID instead of username. This will help when sim problems prevent the system from finding usernames.
Also see Changes in Version 1.9