User Tools

Site Tools


Corrade-based SL Control Architecture

Running an SL/Corrade system is complicated - in fact it being a couple of years since I last did it I've forgotten how it works. So here's what I've rediscovered.

I think there are two ways of controlling using Corrade:

  • Writing server-side (ie your PC) side code to talk via API to the Corrade code - not tried that yet, may not even be there!
  • Writing an LSL script in-world that sends commands via web service which the Corrade code then:
    • - a) sends to the bot, eg to perform an action
    • - b) sends back response data to the LSL script (e.g. to report the results of an action)

This latter is what I've done.

The Corrade code also picks up any in-world alerts/notifications that the bot receives and sends them down to the LSL script.

The real “gotcha” in all this is that in Corrade Configuration you need to set a password for the Group that the bot and controller are sharing (this password does not exist in SL, it is only for Corrade), and you need to enter this password into your Corrade control script.

Since LSL processing is obviously limited (and even my simple/developed test script had blown the stack/heap) you want to keep this bit to the bare minimum and use ANOTHER web service to link out to your main code running on your own server elsewhere.

So the overall architecture is as below:

corrade-based_sl_control_architecture.txt · Last modified: 2020/01/21 13:58 by admin