Despite our best efforts, at times bugs do appear in our products. Since putting out an updated version is sometimes a time-consuming process, this page will list any significant issues we’re aware of and explain how to work around them. If you have a problem not mentioned here, or the suggested fix doesn’t work for you, please notify JulieDoll.
- If a component isn’t working, DO NOT buy a new copy of the component. That almost never helps. Clearing your cache will definitely not help. (There are very few problems for which that is a good idea nowadays; it is more likely to make things worse.)
- Resetting scripts is a good general-purpose strategy when you don’t know what else to try and no staff member is online to ask. Your CCU must be unbolted for you to do this. If the problem seems to be with an Access Panel or Battery, reset that component first. If that doesn’t solve the problem, try resetting the HUD. (You will need to boot yourself after doing so.) This is rarely the best solution, but it does tend to fix most problems.
- Relogging doesn’t usually help, but it costs nothing to try.
- If you’re having problems recharging a battery, or people cannot use the Workbench to upgrade you or Remote Controls to control you, you may have deleted the “set trustedcreators=brattle” line in your p99 Unitonly program module. This line tells the CCU to allow devices I created to connect to it; remove it, and they can’t. (Version 2 will do this better and give you better feedback when it fails.)
- Random program lines fail. The program parser is very sensitive to capitalization and spacing. Make sure all key words are in lowercase, and there are no spaces before or after colons, equal signs, or commas required by the command.
- If you’re seeing a bunch of text that begins with “** mc” and makes no sense, some debugging has gotten turned on that shouldn’t be. Edit whichever device is producing the messages, and carefully delete the script called “-MessageMonitor.” Don’t delete anything else.
- CCU allows normal (non-green, non-object) speech. This is (and always has been) normal behavior for the CCU. Intercepting speech creates lag – not a lot, but some – and so the CCU does not do it unless there is a reason for it to. Reasons include using the speechname: command to change your name in chat to something other than your display name, altering your speech to when power is low or it is being interfered with, and speaking for you when your programming requires it. Otherwise, the CCU reduces server load by letting it handle your speech normally.
- CCU renames you when you don’t want it to. Look for a “speechname:<some name here>” line in your programming, and remove it. Whether you found one or not, add a line “action (power=1) speechname:”. Then reboot.
- The “blur” setting for effectshutdown and effectstandby does not always work. This is a viewer issue. For me, using Firestorm 4.5.1, it works sometimes and fails others. It may be that some graphics settings work while others don’t. If this setting doesn’t work for you, use others instead. “Dim” works well on all viewers as far as I know. (I think Firestorm 4.6.5 has corrected this problem.)
- Access Panel colors can’t be changed. The colors of the standard indicators cannot be changed.??It would be pretty confusing if they could, since everyone’s indicators would indicate things differently, meaning they wouldn’t indicate anything at all. The color of the metal or plastic frame that the indicators are embedded in can be changed, allowing you to match the color of the panel’s skirt to your skin, and make the rest of it steel, copper, white plastic, or any other material you choose.
- Head moves around while frozen, even with no AO active. In Firestorm, try going to Preferences -> Firestorm -> Avatar, and reducing the top two sliders to 0.
Known issues with Version 1.10:
- Repeated run-time errors of the form “[script:-ProgramReader] Script run-time error… Stack-Heap Collision]”. Rebooting your CCU corrects this issue temporarily. Upgrading to Version 1.11 should correct it permanently.
- Batteries sometimes do not connect properly on initial installation. Reset scripts on the battery to correct this. It is usually only required once.
Known issues with Version 1.9:
- If you use a battery, several actions (such as speaking, emoting, and teleporting) cause a bit of extra power drain, as you can see by watching the drain indicator on the left side of your CCU. This is intended behavior. While the drain is occurring, your system may behave as if power is low (e.g. not allow teleporting, slow your speech) even if it is full. This is not intended behavior, and is fixed in Version 1.10.
Known issues with Version 1.8:
- Sometimes the HUD appears all squished together, or you may get a Stack/Heap Collision error from -CCU-HUD. These errors can both be corrrected by resetting scripts on your HUD. Once corrected, this problem does not recur. (Fixed in Version 1.9.)
- Units using Batteries or Doll Keys may experience a brief period of muteness or difficulty touching things after teleporting. This is normal – teleporting takes a lot of energy, and it takes a few seconds to recover. However, sometimes with Version 1.8 the restrictions do not go away as they should. Defragging or resetting scripts should fix this. This problem can recur. Version 1.9 fixes this problem.
- If you receive an error saying that your Handle is not attached, (1) make sure it is attached, and (2) if it is, detach it and reattach it. That usually solves the problem. If it does not, resetting scripts on your HUD is worth a try. If you find this happening frequently, inform JulieDoll.