Apparently today’s The Final Stand 3v3 tournament was marred by a few cases of warrior’s weapons breaking. Very early this morning Ayame received a report of a similar issue. In both cases, from what information I’ve been able to gather, the telltale symptom is a script error and a math error. Thereafter, it seems that the weapons are no longer usable and some people have had to get a new one from the product box.
So far it seems to only happen in Havok™ 4 sims since the last update (and we hope that the new update will fix it, but it doesn’t seem likely based on what I see from the fix list), and may in fact be limited to Edo for all I know.
I’m asking for anyone who experiences this issue to please notify any of the C:SI developers. Feel free to drop any of us a notecard, IM, or you may also comment here on this blog or create a post on the Official C:SI Bug Report forum.
We’d most like to see a copy-and-paste of the actual error, the time it occurred, which sim it was, and as much as you can remember of what you were doing at that time. For example, if you had just blocked a slash we’d like to know, if you had just kicked someone, etc. If you want a device that can record the entire duel and save it for us to review, just let me know and I’ll drop you one.
At this point we have some guesses as to possible causes, but nothing concrete enough to report to Linden Lab®.
I’ll make an additional offer of $5000L to the first person who can give us a 100% repro case (meaning that you can reproduce it 100% of the time using the exact same steps) that I can give to the LL Havok™ 4 team so that we can enlist their help in solving this problem.
Please help us gather as much useful information as possible, it will help us all in the long run!
14 Comments
Well, in point of fact, it only seems to be happening since this morning as far as I’ve heard. I don’t think the new Havok4 code has been deployed on Edo, I think it’s Beta-grid only now, so I have no idea what could possibly have changed yesterday to start this problem.
The C:SI code has certainly not changed recently, so… It would seem extremely likely that it’s broken on Linden Lab’s side.
I have been on the beta grid and on all four sims there regular movement is ok and even the fight ao work. Till you pull out your sword… one ..two key press in a kick or any attack and immediate crash for me. This happend six times one in each sim. and two in the lower sim on the left. It is absolutly unplayable and will crash instantly every time.
I think the word needs to be put out heavily and anybody with a CSI sword needs to vote on the ticket here. Cause you will be screaming WTF! if they don’t hear us and implement Havoc 4
*Coco waves at C:SI land
Ciao!
Oh, wow
That’s lame! I was hoping things would be getting better, not worse, with Havok 4. Well poopy!
I will make some time first thing tomorrow morning to go to Beta and test this myself. If there’s no relevant JIRA issue, I will create one. Either way, I will post a link here so everyone can vote on it!
Saw a sword break at Meiji yesterday (believe it was when I was sparring Rayno). Math error. Never seen that before.
Even if you can’t get a 100% repro, the *exact* wording of the error would be useful. I really doubt that any of the Havok4 changes could cause a new math error – we simply didn’t touch that code. So that is a weird case.
For the crash: If you have a weapon that reliably crashes a havok4 region on the beta grid please drop a copy on me or Sidewinder Linden, and send me (or him) an IM as to what it is about. If you could file a jira that helps a whole lot.
I had not heard of this problem before (and it does not sound related to others we have seen lately)… Even if you have a partial repro case, or a hunch as to what is happening, I would appreciate hearing about the details you’ve figured out so far. It would also be useful to know if several weapons break at the same time, or is it just “one here and there”. If you could either a) send me a sample of each weapon that had this problem or b) IM me so that we can arrange a time so that I can see each weapon that is misbehaving and pick up it’s ID that would be very helpful.
Thanks in advance,
Sidewinder
Sidewinder, thanks for taking the time to look at this post. I will do my best to get you as much good information as possible, as soon and as often as I am able to.
As for sending samples of the weapons, I will try to find out specifically which ones have experienced the issue and will send a sample as soon as possible.
@Kelly Linden – I agree, it is a very weird case, and a relatively new one at that. It has never happened before, and so far as I know there hasn’t been a Havok4 update on the MG that fits the time frame.
I’m stumped, but we’ll get you all of the information we are able to.
Thanks for taking the time to read about the issue!
WOW!!! I just logged in to the Beta grid to test the weapons, and was greeted with this:
This happened in Sandbox Cordova MONO.
Perhaps not relevant to the post at hand, but it was sure alarming
After this point, none of my HUD or weapons worked
Well, I’m posting this via my profile web tab on the Beta grid…
I tried, I really, really did. Beta grid is not usable right now, the map doesn’t work, the search doesn’t work, I cannot get to any Havok 4 sims in order to test the weapons, even by attempting to sign in at the location of the only Havok4 sim I’ve been able to find so far (Havok4 Sandbox NoDmg).
I signed in initially on a Mono sim, and that broke my C:SI HUD as well as my sword, and now I’m stuck at a Welcome Area literally unable to get to any island because I cannot map there.
I will try again tomorrow, maybe the Beta grid will be working then.
Robby I think the beta grid was most definitely full of epic fail.
I know I have seen some very stable scripted items start having troubles timed the day LL rolled out the latest server version with some unspecified changes to string operations. Since then, I have been having sporadic script crashes on items that never had issues before. Change to string operations referenced here:
http://blog.secondlife.com/2008/03/06/rolling-restart-thursday-march-6th-5pm-10pm-pst/
“We’ve investigated the issue and have identified the cause. In the 1.19.1 server code we tightened up some bounds checking for string copies within the LSL string operations. After identifying this as the source of the performance degradation, we identified a fix – which maintains the bounds checking, but also surpasses the performance of 1.19.0 by approximately 10%.”
This somehow created a script crashing issue. But as the details of what changed were not made public, it’s impossible to to find the cause, especially when you don’t have access to the source code of the scripted item in question. But perhaps this will put someone on the right track.
The first I saw this happen was *months* ago in Meiji and Tokugawa with an Ashes Cursed Spirit. I told the owner (freebsdd Allen) to IM Esprite but it looks like he never did cuz you guys haven’t heard of this before. ^_^ So it’s not new…but it’s pretty rare.
I’ve also seen a few blade breaks with the same error in Samurai Edo and Cold Steel.
Here are the times and logs from the TFS tourney (Samurai Edo):
As far as this happening before I haven’t had had any math error issues recently but I have had them. But only with my Ashes Jin.
2 Trackbacks
[...] Life scripter and content creator. This may provide a bit of a clue to the problem I posted about before : I know I have seen some very stable scripted items start having troubles timed the day LL rolled [...]
[...] to take this opportunity to point out for the benefit of those not following the comments to the C:SI Weapons Breaking thread that Darien Caldwell had some insights that, if correct, could mean that the issue is not [...]