|
|
|
Maggie Darwin made changes - 01/Jan/09 09:04 AM
Maggie Darwin made changes - 01/Jan/09 09:04 AM
Maggie Darwin made changes - 01/Jan/09 09:04 AM
Maggie Darwin made changes - 01/Jan/09 09:04 AM
[
Permlink
| « Hide
]
rade bailey added a comment - 27/Jan/09 09:11 PM
Not only is this an excellent idea, it would go a long way towards streamlining the 'feel' of the grid. Virtually all intersim TPs work by sitting on them, adding this ability to a cross-sim 'port is just a logical extension.
I think this would be a kick-ass feature and I've already voted in support of it.
That said, while we wait for implementation, we should bear in mind that latency between regions (especiall pre-LLNet) and object and avatar marshalling, serialization and demartialling performance are already the source of significant failure modes causing lost attachments, expired_region_handoff and separation of riders from vehicles (leaving their cameras behind in many cases). So refactorings involving some performance wins in this area (OMFG...you use XML for this?) may be necessary before implementing this makes sense. I dont think it will be any more unreliable that trying to drive a car over a region border, which has a 10% chance of unsitting you and deleting the car.
As it is a specialized function, LL can use the new protocalls to do the region crossing/teleport rather than using the old legacy code. I would imagen a dialog box should popup that says "teleport to <name> region" with a yes/no responce that gets returned via dataserver event. The alternative is for a permissions request to be send and returned in the permissions event. Whateer permissions are applied it is important that the script is not delayed in a way that would spoil any cool teleporting effects. While still letting the script know if the teleport offer was accepted or not. Darling Brody Addition to security will be needed for when the destination land does not permit BUILD.
If the destination land does not permit BUILD then the function should return an error when it is called. At this point the script will have to call the function again with the teleport prim set to FALSE. New function format would return a true/false integer (with th ability to turns other errors if needed) :- integer llTeleportAgent(key agent, string region, vector pos, rotation rot, integer prim) _______________________ A less desirable, but easier implementation would be to teleport the avatar and just not rez the object if the destination land has BUILD disabled. This would remove the need for llTeleportAgent to remotly check parcel settings in the destination region. _______________________ I would image the same system that is used for moving objects over regions could be used to insert an avatar sitting on an object into another region using teleport. If it cant be done this way then rez the oject and auto sit the avtar on it as part of the teleport process. Darling Brody.
darling brody made changes - 09/Apr/09 04:18 AM
Dude Latzo made changes - 12/Apr/09 08:12 AM
Dude Latzo seems to be vandalizing PJIRA by closing issues reported by Darling Brody
Maggie Darwin made changes - 12/Apr/09 09:09 AM
Harleen Gretzky made changes - 12/Apr/09 10:13 AM
Um....Harleen? is this really a JIRA you meant to set a fix version for?
Dude Latzo set the fix version, I removed it.
It shouldn't need to ask the avatar IF the script is owned by the landowner of the parcel the avatar is in, but there should be a "time out" after any teleport in which the call is ignored. See SVC-212 for why.
Ezian Ecksol made changes - 07/Aug/09 02:06 AM
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||