Our website is made possible by displaying online advertisements to our visitors.
Please consider supporting us by disabling your ad blocker.
Please consider supporting us by disabling your ad blocker.
OpenSimWorld is the directory of 3D Virtual Worlds based on OpenSimulator and connected through the HyperGrid. Learn More
New Members
NinaMoya, ZamaniMoya, JustQLBQT, Beach, Niekginder, Charles Leclerc, Ainfick, Founderbil, Autumnhazelbee, UrbancityGrid, SillyRedwood, MelaniePouch, ThornBlackbird, DunceFrog, Carin4s, Glue_Bubbles_24, 4589698, SoniaLilou, Daniel2097, HudsonWyldLikes
Active NPC's Question
I have set out a bunch of waypoints and linked them and everything works as it should. I can tell the NPC to go to various places. Its pretty cool. Whats not so cool is the huge wait time at each waypoint.
The NPC will say " If you want to go there, follow me." and will start walking. I start following, but it stops for a good 10-15 seconds at each waypoint along the way. How would I make this delay shorter or go away altogether?
The NPC will say " If you want to go there, follow me." and will start walking. I start following, but it stops for a good 10-15 seconds at each waypoint along the way. How would I make this delay shorter or go away altogether?
Comments
I think that isnt to be altered in the script, but one of the multiple note cards in them. I found this part in "documentation" nc: waitvar foo 13 : wait (and do nothing) until the variable foo becomes 13 Maybe this is something for waiting.. or.. a recorded pause somewhere in waypoints? I use a diffrent system. But here its more a NCs problem. not one of the scripts
like(0)
I think that Foo thing is related to the note cards you can make to issue a list of instructions to carry out. I think they can handle if statements and other stuff that can be modified on the fly depending on how the NPC is interacting with other things. I have not messed with them yet, as all I really need is some foot traffic wandering about. I will have another read of that section to make sure I understood the feature properly though.
The way points are rezed from a HUD to form a web of pathways. You have to touch the newest waypoint maker, then a previous marker to link them so that the script can work out a route from any point to any other in the web of way points. once done it saves two note cards in the controller. One has the way point positions and names and the other has the list of links. There is no wait time linked to each point. You just say the NPC's name and go to "name of waypoint" and it will navigate there (waiting for way to long at each point) or you can say "name leave" and it will wander about randomly.
There are a few llGetUnixTime functions in the script, but its so complex that I can't figure out what its doing. Its above my scripting ability.
I wouldn't be surprised if the script just has so much going on that its processing the way points between doing other things.
I do have another system that can make a predefined path, but it can't cope with junctions in the path. It does have the advantage of not having a huge pause at each way point unless you specify a wait time at a certain point.
Its a shame this system has this issue as its really cool that it can work out the best path to take to get around.
like(0)
The way points are rezed from a HUD to form a web of pathways. You have to touch the newest waypoint maker, then a previous marker to link them so that the script can work out a route from any point to any other in the web of way points. once done it saves two note cards in the controller. One has the way point positions and names and the other has the list of links. There is no wait time linked to each point. You just say the NPC's name and go to "name of waypoint" and it will navigate there (waiting for way to long at each point) or you can say "name leave" and it will wander about randomly.
There are a few llGetUnixTime functions in the script, but its so complex that I can't figure out what its doing. Its above my scripting ability.
I wouldn't be surprised if the script just has so much going on that its processing the way points between doing other things.
I do have another system that can make a predefined path, but it can't cope with junctions in the path. It does have the advantage of not having a huge pause at each way point unless you specify a wait time at a certain point.
Its a shame this system has this issue as its really cool that it can work out the best path to take to get around.
Yes...you repeated things from the documentation nc :-) But maybe here under the article wait commands: https://opensimworld.com/library?view=4
like(0)
Hey there, @MrSnoodle! If you could kindly provide the script you're using for the NPC animator, I'll be happy to take a look at it and see if I can help remedy the slowdown. Since inventory transfers are a pain when HGing, feel free to paste your script on a service like https://pastebin.com and then share the link here and I'll take a look.
like(0)
Thanks for the reply, here is the entire script https://pastebin.com/Y14r97h0
its the Active NPC system found on the opensimworld sim in osgrid.
hg.osgrid.org:80:OpenSimWorld
The script is massively complex and I have looked through it to find the part that deals with navigating the waypoints, but there is so much stuff that is interacting with that section that there was no obvious thing to adjust.
its acting like it has a set time to get to the next waypoint regardless of how long it will actually take to get there. Instead of adjusting the time to suit the distance. I assume the script has no way of detecting when the NPC actually gets to the waypoint in order to request the next one, so it just waits an arbitrary amount of time and hopes for the best before proceeding to the next point.
If you have a few points close together to navigate a bend then it takes forever for the NPC to make any progress.
Many thanks
like(0)
its the Active NPC system found on the opensimworld sim in osgrid.
hg.osgrid.org:80:OpenSimWorld
The script is massively complex and I have looked through it to find the part that deals with navigating the waypoints, but there is so much stuff that is interacting with that section that there was no obvious thing to adjust.
its acting like it has a set time to get to the next waypoint regardless of how long it will actually take to get there. Instead of adjusting the time to suit the distance. I assume the script has no way of detecting when the NPC actually gets to the waypoint in order to request the next one, so it just waits an arbitrary amount of time and hopes for the best before proceeding to the next point.
If you have a few points close together to navigate a bend then it takes forever for the NPC to make any progress.
Many thanks
You may try to hit up the creator of the script. He's also the admin of OSW, but I've read that it's easier to get into contact with him by IMing him in-world or sending him a notecard.
like(0)