Vehicle Move System V2 is now available

z1225_VehicleMoveSystem2_512The movement of prims within a virtual world is appropriate in many situations such as for show (i.e. parades) or as a form of transportation (i.e. trains) as well as entertaining avatars (i.e. amusement rides). Vehicle-Move System from Kerhop’s Innovations allows you to specify a starting location, smooth travel along a path, and the ending location of a prim with minimal editing of a notecard all without causing sim lag due to physics. Working examples of a parade, train, and amusement ride are all included for your review in preparation for your own creations. Now, with version two you can also create and sell your own attractions! All scripts are no-modify, but they are yes-copy/yes-trans (with restrictions).

What’s New in Version 2.0
1)  Create and Sell your own parades, transportation systems, or amusement rides.  2) Improved optimization of scripts means there is now minimal delay in between segments.  3) Enforces via script that creator of vehicle must be same avatar as movement programmer.  4) Removed implementation of showstartcircuit(), showfactorvars(), and showcurrentposrot()

SL Marketplace


Why it is So Important to Functionality Test Objects

functionalityFunctionality testing a new product or service before general release to the public is generally performed in two stages, alpha testing performed by the creator of the product and then beta testing by individuals most likely to use the product in the field. The primary reasons for functionality testing is to ensure that it satisfies the requirements of end users and also to come up with suggestions for future improvements.

Scripted objects are more likely to be functionality tested than non-scripted objects. Such testing requires that the product be utilized over and over again starting with individual testing of minor components (i.e. when odd symbols and excessive characters are submitted into the script does it respond appropriately or result in parsing and memory errors?) working up to the overall major characteristics of the solution such as generating the correct output when provided multiple variations of inputs. If a significant issue is discovered at the early stages these are usually resolved first before proceeding onto a later and larger stage. The testing process can very monotonous, yet is an important requirement.

The platform and viewer used to interact with and view the object is a circumstance that needs to be considered too as many still insist on using older viewers that may not be capable of rezzing sculpt and mesh objects nor respond appropriately to the latest and greatest scripting commands. Textures may not load as quickly as desired on computers with minimum hardware specifications and/or slow internet bandwidth speeds. Such limitations may either be addressed by the creator through either modification of the object or a mention in the notecard instructions that the viewer, hardware, and bandwidth must be meet certain requirements. In the latter case any identified glitches are indicated as “not a bug” and disregarded.

In the absence of external testers the creator can simulate much of the above by having multiple clients installed on multiple computers (i.e. desktop and laptop/netbook) as well as connections both hard-wired as well as wireless to vary the internet connection speeds. Alternate accounts can not only test for correct functionality, but can also be used to ensure the permission of objects and their contents (i.e. textures, notecards, scripts, animations, etc) appropriately protect the creator against theft while also allowing the user to customize or configure as required.