So, I went looking for an explanation of the feature. I suppose the assumption is one will attend one of the in-world training secessions.įor instance: Cool new SLurl command line feature! Now that sounds cool… I mean being labeled cool has to indicate someone thought it is. Several of which I have no idea what they do our how they work. There are about a dozen new features listed on the Firestorm site. The Restrained Love Viewer features are updated in this release. The Character Panel works and you can find your lost characters, which seems to be its primary function. You can use the Linkset panel to optimize a region for Pathfinding. So, this feature is more or less just a place holder. It does not show the Navmesh, which is the whole point of the tool. In this release 4.2.2 the panel carries a warning that the feature is incomplete. The View/Test feature is the one that requires the Havok Library. You’ll find this in the top menu in Build->Pathfinding. The viewer’s tools are essentially the same as the tools found in the Linden Development viewer Linksets, Characters, and View/Test. It does prevent Pathfinding Characters from running within the region, which saves Character processing time. Also, ‘disabling’ doesn’t really save any processor time. Of course you have to be the region owner to do that. The page also explains how to enable and disable Pathfinding in a region. Press ctrl-Alt-D to enable the Advanced menu if you don ot already have it enabled. Phoenix: Go to the top menu bar, Advanced → Consoles → Region Debug Console.Press Ctrl-Alt-Q if you do not have the Develop menu enabled. Firestorm: Go to the top menu bar, Develop → Consoles → Region Debug Console.They do provide instructions on how to open the Estate Manager’s Console: This is mostly an index into the SL Wiki pages on Pathfinding. The FS/Ph Team provides their own set of Pathfinding Documentation in their wiki. The big change is the addition of Pathfinding Tools. See: Firestorm Update 4.7(Warning: This link will age out – it is the way the FS blog works) Pathfinding Regardless of where the problems are and who did what Firestorm 4.7 is out. Tonya explains what is happening with this release of Firestorm and why it is out, rolled back, updated, re-un-updated… Some part of that is blamed on Pathfinding and physics updates, which Tonya sort of mixes together, which should be a hint the problems are not at all simple. Tonya does a good job of describing how things are so intertwined that simple sounding problems can be quite involved problems. Fixing the door problem seems like it would be simple. It is in English so you won’t get geek-i-fied. Tonya’s explanation is a good read for anyone that has never done complex software development. So, this is probably not a Firestorm bug but something in the Linden Code. I’ve seen something similar in the Linden Development Viewers for some weeks now. They appear to swing normally, then jump ahead, swinging farther all at once. It turned out that 4.2.1 has a bug in it that makes most swinging doors not look like they act correctly (though they actually do). On August 27 Firestorm 4.2.1 was released followed by an immediate OOPS! There is a problem that Tonya Souther describes as:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |