I got an interesting IM this morning :
[07:00] Silver Csak: Dear Robby, The wave and the taketory dont work right in the Shadow sim,,,,,, starting in block position then to kick, then back to block,, takes about 7 seconds if it works at all,,,, pretty serious problem on this sim,,,, but it works fine everywhere else. Would you tell some one about this please,,,,,, thanks Robby..
Now, I’ve never heard of anything like this before, so I logged in for a bit to check it out. Turns out, Silver’s right : It is absolutely painful to go into and out of block. It seemed as if all script state transitions were spotty, and the weapons controlled like mud when going from block->attack, ready->attack, ready->block, etc, etc. Many times, it simply didn’t work at all.
But it’s not just the Taketori and Wave that were affected. I even had trouble when using the Cursed Spirit. The account I used didn’t have all of the weapons, so I wasn’t able to test more than those three, but what I encountered was absolutely abysmal. The Taketori was worst of all, and the Cursed was best, but none of the three had anything even remotely resembling good performance.
So I went back to my home sim to test. Same results, I’m sorry to say. I was flabbergasted. Surely this couldn’t be a general problem, right? I mean… I’d expect hundreds of people to be raising hell over such poor performance, but I’ve not really heard anything that would indicate such widespread problems.
I still had a bit of time to test before I had to return to work, so I headed to Samurai Island and Edo to check things out. While performance was still relatively lousy compared to what I was experiencing before my recent break from SL, it was at least an order of magnitude better than the last two sims I’d been in. I started to feel a little better, thinking that I wouldn’t be too surprised if a couple simulators were having problems. That is, until I teleported to another sim.
So far, three out of four sims were so bad that it was simply not even worth trying. I can’t state that strongly enough : I would absolutely not try to have a fight in those sims. You couldn’t pay me to waste my time, even, because there’s absolutely no question that it would be nothing but an exercise in frustration.
Just to be sure, I tried yet another sim. Same thing, the performance (and by the way I noted that the ’sim stats’ display for all of the sims showed near-perfect numbers) was so bad that I gave up within thirty seconds. This is exceptionally discouraging, because just a couple of days ago I was having absolutely no problems whatsoever, and the difference was as noticeable as hitting a brick wall at 50mph.
The only anomaly I noticed was that the Samurai Island estate simulators were running a difference version of the sim software (as indicated by a popup notice), but everything else appeared fine.
So, anyone know what this is, and when it started? Did I just miss out on knowing this because I’ve been out of touch? Is this a known issue?
What the hell is going on here?
Popularity: 31% [?]
I just tested this. It’s horrible. Horrible! :O
I just logged after fighting at Italia State, which was perfect.
I hope that Judo’s experience is the norm, and that what I saw was a temporary and localized thing!
it must have to do with the new server version they are deploying at the moment. i went to a few places to compare and whereever 1.24.3 was already running i experienced the same problems mentioned above. here are the results:
1.24.3 - penghu - not working
1.24.3 - shadow - not working
1.24.3 - ravkom - not working
1.24.3 - simulacron shrouded - not working
1.24.3 - hengill - not working
1.23.4 - italia state - working
1.23.4 - dragon claw - working
1.23.4 - edo japan - working
1.23.4 - heisei - working
1.23.4 - emei - working
1.23.4 - night shadows - working
once again they break content by changing something, i just hope it will also break a lot of other stuff so there will be enough people posting and voting for it on jira. in a few hours the new version will be deployed to the whole grid and it will be impossible for anybody to have a proper spar until it gets fixed so it should be posted as showstopper. any volunteers? lol
Nooooooooooooooooooooo! WTFig Newton?! Lynkis and I experinced that yesterday butt thought it was just a lag thing. fjfhjfdhjfdhjffd!
BTW Seven Samurai?! Woot! lol :3
I now see the problem at Shadow. There is a delay going from block to slash or kick to will make countering virtually impossible.
Theo’s right. v1.24.3 has broken the C:SI content. The weapons are wholescale poorly responsive. Italia State still runs v1.23.4 and the weapons work fine there. Nice detective work.
I had this issue today and two days ago..It seems to be spotty. I can have the issue on one sim and leave and come back a short time later and have no issues. This has happened to me with the Ring as well as the Wave and Take. It surely sucks.
I have to agree with Shindo on the pic! Whooot! Seven Samurai! I’m going to go watch that again right now!
BTW..nice to know I’m not going nuts and that there is a problem.
Dragon Claw Island is also on the new server version since few hours, same as Heisei. Same issues with our weapons, fighting impossible and I noted double high script activity as normal on our sim.
That is a desaster !!
So I am curious, what is the game plan now given that C:SI is effectively broken? Are the developers going to work on mono, and will we have to wait until the scripts have been rewritten for mono to fight again, and if so, any estimate of how long that might take? Or will there be any attempt to deal with the block latency problem using the existing script? Without C:SI, sl is a bust for me!
Thanks
Judo -
We are working on Mono, but that is not a satisfactory solution because at this point there’s no telling how long that could take.
In the meantime, I will try to narrow down as much as possible exactly what part of the scripts is having the problem, and then make Linden Lab aware of the issue in the most loud and persistent way possible.
Not that Linden Lab has a good record of responding to issues, but I do think it’s necessary for us to let them know that they have once again broken content in a major and unacceptable way.
Without C:SI, Second Life is pretty much a bust for me as well
Maybe Hamlet Au of New World Notes would be interested in writing an article about the effects of mono on c:si and possibly other widely used content that’s been broken if you got in touch with him. If not, maybe the referrals he gets from the link in my comment will be enough to get his attention.
Hamlet pretty much sticks to the positive and uplifting aspects of Second Life. I doubt he’d be interested in an article about how over nineteen thousand people now have broken content due to a poor server rollout
The only issue I know if which affects scripts running on the original scripting engine in 1.24.3 is that state changes are incorrectly restricted to 1 per frame. We have a fix for this issue which will be likely rolled out next week. If the problem is due to something else, please file a bug on the public JIRA here https://jira.secondlife.com/browse/SVC-1276
Babbage Linden’s latest blog post is : Mono Launch
Babbage, thank you for taking the time to leave a comment.
Despite being highly emotional and upset by this, I’m trying to find a workaround, and I think I’ve discovered something interesting about the cause.
When I have a repro case with minimal distracting code, I’ll file a JIRA issue. I don’t think this problem is directly related to the one you’ve mentioned, but I’ll attach the code when I can for you to see.