The problem mentioned in my "Linden Lab wants to break C:SI…" post was included in the just-announced V1.20 Release Candidate Viewer.
Please take the time to vote for JIRA VWR-6232, we may still have time to change this!
Reminder: Release Candidate viewers are optional updates that contain the latest round of bug fixes and/or soon-to-be-released new features. Please try the RC viewers only if you want to participate in the bug reporting process and identify issues before they become the default viewer. You can have both a Release Candidate and the primary viewer installed side by side on your computer, so if issues are encountered when testing the RC viewer you can switch back to the production viewer.
Popularity: 41% [?]






Well… I got the “mandatory upgrade” notice, installed the new viewer, and actually feel just a little bit better…
It doesn’t completely break dash, I can still dash, and CTRL-R still works, but it’s going to cause immense confusion among people coming into Second Life who are told “double-tap W to run” and then try using a product that uses double-tap for it’s own purposes.
There’s also some solace in the fact that 1.19 was a required viewer update, so theoretically it will be a while before there is another.
Colin’s latest blog post is : SVC-1862 Fixed
No, this one is required if you use Dazzle
And it sucks ass… Keeps crashing
The only reason I was still using Dazzle was because it didn’t crash as much
I just created VWR-6256 Meta-issue: Bugs that effect C:SI Combat Samurai Island http://jira.secondlife.com/browse/VWR-6256 to keep track of all bugs that effect C:SI. If you know of any other bugs please start linking as related! Go go go! xD
Aimee Congrejo’s latest blog post is : VWR-6256 Meta-issue: Bugs that effect C:SI Combat Samurai Island
So, this particular bug doesn’t seem to actually *break* anything, at least not while CTRL-R still works.
What it will do, though, is cause confusion in the future from people newly come to SL and C:SI, who try to run by double-tapping and end up dashing. My guess is that they’ll blame C:SI for trying to override client functionality, not realizing that dash came before double-tap run.
So, it’s still a problem, and should still be voted on in order to get LL to engage in a conversation about how to properly implement such things.
They really should learn to discuss changes like this *before* implementing them
“Tofu Linden - 10/Apr/08 02:03 AM
Please cite non-theoretically-broken landmarks and items (i.e. where vended from) and I’ll have a look. ”
Ehhh? WTF someone wanna clear what what he/she is talking about for me?
Zero Gee: Tofu is looking for examples of objects that are known to be broken through actual testing in-world, and the location of where he can get them from so he can look. (He wants to know where the vendors for the objects are.)
That really sounds like a brush-off, and kind of snide, but I’m willing to give him the benefit of the doubt and attribute it to the problem of using a comment system to communicate.
So here’s how I replied to him :
Well I made my point clear I think in one of my last comments.
“Tofu Linden - 11/Apr/08 01:53 AM I’ll talk to some folks here about what to do with tap-tap-hold, based on the feedback.”
You know, I felt so damn compelled to say something in response to that but I had to hold back. I mean its like “Oh really? Well thats awful bold of you.” gah!
Tofu Linden: Omniphaze and emDash seem to function fine in our tests. What problems are being seen?
And again I just want to say something not so nice … I mean com’on…”what problems are being seen?” Oh, you mean other than it just being a craptastic idea ?!
They need to get over the whole “this makes something crash?” mentality and read the f’ing reports. It’s been explained quite clearly and re-iterated in a number of ways.
RTFC, Linden Lab, RTFC!!!
My sentiments EXACTLY robby… GAW.
Tofu Linden - 16/Apr/08 07:26 AM
We’ve come to this plan of action (probably for RC2) based on feedback and discussion:
* This will default to ‘On’
* A persistent ‘advanced’ option will be added to allow it to be disabled.
Shit like that makes me sick and pisses me off. Does anyone know the number of a good slap’a'fool service?
Yeah… So much for the idea that they might actually listen to the community, huh?
Dude you have no idea how pissed off I am right now.
I just really hope that it wont interfere with the CSI weapons. Is there any possibility that it might screw with new combo ideas you guys had?
It might, yeah… I guess we’ll just work around it :\
What I don’t get is how, after over 160 votes, its still not officially assigned to any of the lindens.
Anyway tofu said that there will be an option to completely turn it off so i’m curious how complete that turning it off will really be.
=^.^= How *dare* we use common sense to vote on a bug we *know* is gonna fook us *before* actually seeing the bug in action. LOL
Aimee Congrejo’s latest blog post is : C:SI TFS 3vs3 March 2008 Tendai-shu vs. Yakuza Samurai
Basically this is “Lab-speak” for : “Disingenuous bullshit blah blah blah I can’t hear you blah blah blah gonna do whatever we want blah blah blah ain’t fixin’ nuthin.”
Yeah well, like I said in game to Aimee, Tofu can suck a giant tree limb I’m still kind of pissed right now.
So I just noticed that there is indeed an option to toggle this new feature: Advanced->Character->Tap-Tap-Hold to Run.
Colin’s latest blog post is : MySql 5.1
Yes… There is an option to turn it OFF.