I’ve complained about the symptoms, but now we may know the cause. Thanks to some sleuthing by Makkiavelli Toland and my own experiences in trying to create a halfway decent workaround, it seems extremely likely that the cause is in the state_exit event being delayed.
Tip of the samurai helmet to Escort DeFarge, who notified me that there is a JIRA issue already on file for this: SVC-2958. Please go vote, and make your voices heard! We need Linden Lab to address this issue.
If history is any indication, it will take Linden Lab some time to acknowledge, research, and distribute a fix for this, so I will continue working on a workaround, and will distribute it as soon as testing is complete. I’d rather have them do it right than distribute another batch of bugs 
Also, remember that Archanox is working on a long-term plan to move the C:SI scripts to Mono, and will almost certainly do a better job of getting things working than my hackish workarounds, and I’ll share anything I discover with him.
I am relieved. Time for a nap
[UPDATE]
Periapse Linden commented on SVC-2958:
Babbage has checked in a fix for this. Vektor is testing the new version now. We intend to complete a rolling restart this week with this fix and fixes for several other serious issues.
Popularity: 54% [?]
Zai says “Maybe there’s a market for a turn-based C:SI system”
Jackass
I also have to add : I’ve NEVER experienced worse performance than I have with the new 1.21 RC0 viewer. Well, maybe one time about a year ago when I was being griefed with a texture bomb. Actually no, I think this is worse.
Been tracking the JIRA issue. This issue is in the top 20 most popular thanks to great voting, and is the only confirmed “showstopper” (ie most crucial) issue in that high on the list. It’s been assigned to Soft Linden as of last night. Hopefully work will begin on it soon on the LL side.
Hopefully this means I’m on the right track for finding a workaround?
Okay… So far as I can tell, this Beta is looking fairly usable. I think I’m going to try to get a bunch of people to really hammer on it before pushing out an update, though.
Maybe instead of an update I will do a public beta? That’s something to think about, anyways.
But I’m anxious to get a working weapon into the hands of everyone who’s purchased one of my weapons and currently can’t use them.
What is the timeout for the beta swords? Mine would not work yesterday. Also I think it may be a good idea to get as many Beta users on a sim as we can and do an FFA just to see what kind of stuff might turn up under that stress.
The timeout is in two weeks from today, actually. I don’t know of any reason the sword would not have worked yesterday that would be related to the trial period.
One thing to keep in mind is that if you wear the sword to any sim that is not running Mono, it will break.
An FFA sounds like fun and I’d like to see how the sword handles it, though I wouldn’t expect any kind of detailed information. But basically, it might at least demonstrate whether there’s any obvious big problems.
Unfortunately, there’s just no way I’d be able to witness it. Ever since I installed the Second Life 1.21 RC0 viewer, I cannot go to any public places. The more avatars there are, the worse it is. Even with two or three avatars present, I cannot type, and the viewer starts suffering so bad that it’s completely useless.
To make matters worse, when I try to go back to using the primary Release viewer, I can’t stay online for more than 60 seconds or so.
I’d love to see what such an FFA would be like, but I’m afraid I couldn’t be there to see for myself
I thinks I need a new copy. Mine broke and my copies mysteriously disappeared from my inv.
Yes, mine is broken too. It seems that if you take an attachment that contains Mono compiled scripts into a sim running 1.23.4, the scripts will break and not work again until they are recompiled (or maybe just reset). Either way, this isn’t something you can do if you don’t have modify permissions. Maybe this is a bug that should be reported? I understand them not working in sims running the old server, but they probably shouldn’t need to be reset or recompiled before they work again anywhere. Although theoretically all the sims should be upgraded soon, so it won’t matter.
I think if you made a vendor with just the mono beta sword (no sheath) That could work yeah? idk Couldn’t they just grab the sword and use the sheath like we do sometimes for Betas?
A FFA sounds awesome. I think one this friday will be sweet. I’ll make it as publis as possible. Muahahahahaha!
“Status: Fix Pending (was: Open)”
Yay!!!
“I think if you made a vendor with just the mono beta sword (no sheath) That could work yeah? idk Couldn’t they just grab the sword and use the sheath like we do sometimes for Betas?”
Hmmm..could you do this Robby? Almost everyone I know has accidentally broken their betas.
I have a new plan. I will not be releasing a Mono version in the very near future, as we want to wait until Mono is more stable and all C:SI developers can switch to Mono at the same time.
I did spend some time this morning working on getting a workaround for the Mono issue done using ‘old’ non-Mono scripts, and I think I’ve actually managed to come up with something that works. I will be passing out beta versions today as soon as I am able, and if all goes well I will release a non-Mono version that can work around the state_exit problem
By the way… Anyone who received a Taketori Katana RC1 version this morning… Just delete it. It’s horribly, horribly broken, and had a major bug that I didn’t notice before giving it out.
Wait for the RC2, which I will have ready today.
lol.
“It’s horribly, horribly broken” That sounds like my first post-Labor Day work day in general.
Here’s an idea! Make a Daikon Forge group. Then make a beta vendor in one spot. The vendor would contain the sword only. That way only people that have the sword can do anything with it. Put it in “sheathed mode.” That would make the sword useless to anyone else cause you wouldn’t be able to see it. Then instead of sending a sword everyone sperately, you just send a group notice and set the vendor down somewhere. BAM! Less work and more time with the fam! :3
I already have a Daikon Forge group
There’s a beta vendor at my main store Asian Inspiration (first item in my Profile Picks). It will give anyone who clicks on it and already has at least 100 C:SI duels a copy of the latest Beta version.
This beta version WILL NOT update automatically like a release weapon, and will completely STOP FUNCTIONING on September 15.
The beta comes in a product box just like a normal Taketori, so you can get as many copies as you like from that.
It also does NOT use Mono. This is just a fix of the existing scripts to get around the state_exit bug, so it should run pretty much anywhere and won’t break if you happen to find a non-Mono region somewhere on the grid.
Yay again. Thanks Robby!
You already have a group?! And I’m not in it! OMGosh! /nuuuuu! Say it isn’t so! Do you wish for me to give you my pinky? O.o?!
Yay for beta vendor! *kicks LL in da junk* Oooo shiny thing! *scampers off*
let’s cross our fingers that the restart does the trick without new borkifications…except for Shindo who may have given all of his finger to Robby by that time.
Word is that it doesn’t resolve the issue. I don’t know this first-hand, but that’s what I am reading in JIRA.
In any case, you should be able to use the latest Beta, since it’s not Mono
It does look like they are getting a fix for this soon, which means probably several more days of waiting for it at the very least. Unfortunately I am having a different problem with the RC. Every time I try to open any new window too quickly after opening a different window—be it a script, my inventory, search, or even Help->About to get the version info—I crash to desktop. It’s very, very frustrating. I was hoping to get a couple of my scripts to Mono, considering that it supposedly handles list interactions much faster. Most especially I wanted to try out my chain lightning staff to see if it improves at all.
The problem I’m having is reported on the public jira by a couple of other people as well, but it doesn’t seem like a large number of people have similar crashes.
Eyana Yohkoh’s latest blog post is : Galaxy Generator Released
I’ve had all kinds of stability and performance issues with the RC, but I haven’t experienced quite the same things you have. I actually haven’t had many crashes, though performance is so excruciatingly bad that a crash might at times be less stressful. At least then I’d have a reason to take a break and calm down, lol.
My HoD feels great on the preview grid in sims running v1.24.4. I’m going back in with a test partner for sparring. Looks good so far.
kk, Silver Csak and I just had about 5 spars on the preview grid. HoD vs Wave. Swords are functional. Some timing wonkiness but that could be some weird lag issue in the beta grid. But MUCH improved. Hopefully it’s enough for the devs to fine tune if needed.
IT’S NOT MONO!!!!!
This beta that I put up in my store is not Mono. If any of you reading this are one of the people telling others that this beta is using Mono, please stop.
There was a Mono beta that a few people got to try out. That one is now officially dead and won’t be revisited until the entire C:SI team is officially working on Mono. The beta that I made available in my store is a refactoring of the standard LSL scripts to get around the bug mentioned above, and that is all.
holy jesus.. either something went wrong at LL or they told “Lightning Linden” to take care of this state_exit thingy..
Looks like they already started updating servers, since our Dreamgate-Sim (a void sim!!) is running 1.24.4 now.. and yes, the swords are working there.
and no, its not a sparring sim
You are at 194373.4, 308615.9, 22.5 in Dreamgate […]
Second Life Server 1.24.4.95600
Yeah, that’s pretty speedy work, alright!
Where can I find out about how quickly this will get deployed grid-wide? I haven’t seen that information yet.
Ah… Okay, so they went from putting it on the preview grid to deploying it this week? Wow.
I think that perhaps several aspects garnered the state_exit issue immediate attention. One, it a major kink in the much touted Mono. Two, we got 200+ votes on it over a weekend in JIRA, placing it within the top 15 most popular items. Three, i think 3 independent confirmations appeared in JIRA on the same day, cementing the issue as a Showstopper, or top priority. Else…we just got lucky.
Well, I’m glad they are on top of it. Honestly, it’s incidents like this that make me think about quitting Second Life altogether sometimes.
Robby leaving = major suckage. Me no like major suckage.