Performant listen based armour for the Secondlife Military Community.
This repository contains the most up-to-date and lag-free scripts for LBA, as well as the documentation provided by upstream.
The version of LBA that is currently distributed is no longer maintained.
Simply delete your old LBA scripts, and follow the instructions below under "Usage."
The GLBA scripts to use as a replacement for the legacy scripts is as follows:
| Legacy Script Name | GLBA Script |
|---|---|
| LBA-Light-Deployable-vX.XX.lsl | Use GLBA-Slim |
| LBA-Light-vX.XX.lsl | Use GLBA-Slim |
| LBA-Slim-v.X.XX.lsl | Use GLBA-Slim |
| LBA-v.2.32.lsl | Use GLBA-Vehicles |
| LBA-D-v2.32-rc3.lsl | Directional GLBA has not yet been released, continue using legacy |
GLBA is fully compatible with all LBA-compliant weaponry, vehicles, and deployables.
Create a new script in your deployable and copy/paste the LSL code in GLBA-Slim.lsl into it, and hit "Save".
Take the deployable into your inventory and deploy it as needed.
GLBA-Vehicles is meant to be used for vehicles that are meant to be driven, such as tanks, gunships, air ships, boats, cars, golf carts, etc.
Create a new script in your deployable and copy/paste the LSL code in GLBA-Vehicles.lsl into it, and hit "Save".
Take the vehicle into your inventory and rez it where you want.
For those new to git, or the open source GitHub experience, I highly recommend you complete the basic GitHub "Hello World" Tutorial before contributing.
Once or if you understand the essentials of git and/or GitHub, follow this tutorial to fork this repository:
Once you have created a fork, and modified it, you can submit a pull request by going to uncertain-string/SLMCA/pulls and hitting "New pull request."
GitHub has provided this tutorial on How to Collaborate using Pull Requests from a Fork
If you need help, contact frick.teardrop.
If you have any further questions, contact frick.teardrop in Second Life. Frick is always happy to help anybody understand open source projects, and how git (and collaborating within GitHub) works.
The numbers represented in these tables are script time, the average number of seconds (over around a 30 minute window) that each script performs work during a simulator frame.
The results are sorted by the difference between idle and active states. The lowest difference between states wins, as the difference is the actual amount of active script time that the script uses per frame during combat.
Idle state is after rezzing and waiting 10 minutes for script time to settle.
Active state is after being hit with 5,000 collisions & listen events over 5 minutes.
You will notice that homesteads have higher script time. This is because there is 1/4th of the CPU time normally available per frame as they are homesteads. Thanks to optimizations from the mono project, the realized difference in performance is minimal between homesteads and full sims.
You will notice that full sims report a higher script time average, this is because full sims have 4 times the capacity of a homestead, so they schedule far more script executions per frame, and allocate far more CPU time for scripts per frame than homesteads.