RLVa

*waves*

With my connectivity issues, the failed hard disk and the fact that the end of the month is always the most stressful time at work it seemed like I wouldn’t have much time to actually do anything for another week or so, so I decided to do a “preview release” of RLVa-1.2.0 for those who want to help test and/or want a peek. All one or two of you reading this anyway .

Most of everything should work, notable exceptions are @showloc=n and @shownames=n though… they’ll work in some places but not across the board yet (they’re exceptionally tedious to implement and 2.0 made it a whole lot more complicated and added a great many more places to hide names and/or location from).

For the moment my “still to do” list is along the lines of:

• finish everything up (ie @shownames=n, @showloc=n and probably some random things I’ve forgotten about)
• re-test everything from scratch again
• find some way to make the “composites” feature play nice with inventory links (they’re non-functional at the moment, sowwies)
• when Marine releases re-verify that my idea of what should be blocked by which restriction matches up since we’ve very likely gotten out of sync there

So still quite a bit of work left .

—

I’ll blog about this more (and it’s subject to change until everything’s all done), but some 2.0 vs RLV API clashes to watch out for that I can think of straight away:

• if you use inventory links in your #RLV shared folder then @getpath (and as a result all of the @*this commands) will not return a path (on the plus side I’m not sure if any/many scripts actually use that command)
• if you use inventory links in your #RLV shared folder then @getinvworn will return less useful information (ie since every link is worn if the link target is worn you’ll see a lot of folders that are partially worn which might confuse some existing scripts)
• @detach=n from an attachment on (as an example) “spine” is no longer a synonym for @remattach:spine=n due to the upcoming “multiple attachments per attachment point”. The former “locks” an attachment *object* while the latter “locks” an attachment *point* (you can execute both commands and then look at the RLVa / Debug / Locks… floater to see the difference)
• the tattoo and alpha layer are part of what gets stripped due to @remoutfit=n which may lead to undesirable results (ie an alpha wearable to work in tandem with a prim corset) so use “nostrip” for those if need be

—

Changelog (now even more boring than usual :p): release_notes_RLVa-1.2.txt

I’m keeping the “Catznip viewer” and this blog separated, if only because this one is supposed to be about the “RLVa patch” and not a viewer so (and it keeps this blog free of TPV policy legalese and related hoops)…

While it would certainly help me to have other people test it before it becomes part of Emerald or any other viewer I’m not trying to convince anyone to use it. You either feel comfortable with it, or you don’t .

And now the actual link: Catznip blog

—

(Sorry if this blog seems rushed and inconsistent but it’s 2:20am here now and this little Kitty really hears her bed calling! )