Concerninig vehicles, having scripts move into regions is not a problem per se, provided one doesn't mind a reset when they enter the new region. The real problem there is with the predominant physics engine in use (ODE).
It is 'unmanaged' code, and as such it is difficult or impossible (as I am told ;) to serialize physics state and pass it to the next region. Non-physical vehicles *might* be an option, but for the script reset thing. Actually, thinking about it, it would probably not be at all difficult to write a script to work around the reset-on-crossing issue and at least keep the vehicle working, even if it did hitch a bit at borders. On Tue, Jul 26, 2011 at 8:16 PM, Justin Clark-Casey < [email protected]> wrote: > It isn't. > > > On 23/07/11 17:21, Marcus Alexander Link wrote: > >> Is it possible to let scripts only cross regions (out of a region) as >> binaries? >> >> - Marcus >> >> On Sat, Jul 23, 2011 at 3:27 AM, Justin Clark-Casey >> <[email protected]> wrote: >> >>> Fair enough. Let's give it a try and if it causes problems we can always >>> go >>> back. >>> >>> On 22/07/11 09:12, Melanie wrote: >>> >>>> >>>> I'm not opposed, it's just a warning. >>>> >>>> Melanie >>>> >>>> On 22/07/2011 02:00, Justin Clark-Casey wrote: >>>> >>>>> >>>>> On 21/07/11 07:13, Melanie wrote: >>>>> >>>>>> >>>>>> Arguably AllowScriptCrossing could be set to true by default but >>>>>> that would break grids with a non-homogenous script engine >>>>>> landscape, e.g. regions using SCEngine vs. XEngine. false is the >>>>>> safer bet. >>>>>> >>>>> >>>>> I think that other script engines (if any actually exist) would be >>>>> better >>>>> off making use of the defacto state standard >>>>> rather than propogating their own. If they can't load this state >>>>> information then they can just ignore it, which they >>>>> should be doing anyway since the source region could put anything in >>>>> that >>>>> chunk of xml. >>>>> >>>>> ______________________________**_________________ >>>> Opensim-dev mailing list >>>> [email protected] >>>> https://lists.berlios.de/**mailman/listinfo/opensim-dev<https://lists.berlios.de/mailman/listinfo/opensim-dev> >>>> >>>> >>> >>> -- >>> Justin Clark-Casey (justincc) >>> http://justincc.org/blog >>> http://twitter.com/justincc >>> ______________________________**_________________ >>> Opensim-dev mailing list >>> [email protected] >>> https://lists.berlios.de/**mailman/listinfo/opensim-dev<https://lists.berlios.de/mailman/listinfo/opensim-dev> >>> >> ______________________________**_________________ >> Opensim-dev mailing list >> [email protected] >> https://lists.berlios.de/**mailman/listinfo/opensim-dev<https://lists.berlios.de/mailman/listinfo/opensim-dev> >> >> > > -- > Justin Clark-Casey (justincc) > http://justincc.org/blog > http://twitter.com/justincc > ______________________________**_________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/**mailman/listinfo/opensim-dev<https://lists.berlios.de/mailman/listinfo/opensim-dev> > -- =================================== http://simhost.com http://twitter.com/jstallings2 http://www.linkedin.com/pub/5/770/a49
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
