Elevator Update 2.6.2 Available

March 24, 2018

Replaced update system in shipping crates with CasperUpdate due to the closure of HippoTech. This also means that if you’ve purchased your elevator (or many other Union Micro products) in-world before March 24, 2018, you will not be able to automatically check for and receive updates as your current crates are trying to check HippoUpdate for updates which is now offline. You’ll have to contact Stylez Gomez to arrange for a manual update. I’ll post more info on Twitter (@UnionMicro) or UnionMicro.net when I have an update path for manual updates.

No elevator functionality was changed. I don’t foresee any more gen2 updates coming but I want to be ready in-case a change in SL breaks something and I have to push out an update.

February 2, 2014

  • Updated script package to 2.6.2:
    • Added a new disk to the package that contains a set of experimental scripts (2.6.2e).
      • These scripts should be considered EXPERIMENTAL and although they have been tested it’s impossible for us to test under all possible scenarios. It’s suggested that you rez a fresh elevator system and test it yourself before using it on a production system.
      • Our mesh testing was limited but successful. If you’d like to create a mesh elevator you will have to use the panel and buttons from an existing non-mesh default elevator. Gen2 is designed for use with buttons being separate prims (although you can make each button a mesh if you want). Gen3 will be more efficient with the call panel.
      • Converted the movement engine of elevator car to the engine that will be used in our Gen3 elevators.
        • Movement is now animation based and not physics based.
        • Allows for the usage of mesh objects.
        • No gaps required around the elevator car anymore.
        • Smoother and more reliable movement.
      • Removed much code from _car_main used for keeping the physics engine in check.
      • Added notecard options to allow the end-user to control the physics shape of the root and child prims (see below). Most users should not need to use these options.
  • “Vanilla” scripts updated to facilitate going back and forth from experimental to vanilla scripts.
    • Vanilla scripts are considered to be the normal scripts which use the older physics based movement (the engine which all of our elevators used up until this point).
    • Scripts will set all prims in the object to PRIM_PHYSICS_SHAPE_PRIM. If you somehow have a mesh working with 2.6.1 then don’t update to vanilla 2.6.2 (use experimental scripts instead).