C:SI Broken Again!

Hey the new upgrade broke CI. Lets all get on here and let LL know.
The issue as we all know is that it takes forever to change back an forth between blocks and attacks. LL promised that the code would be portable and it is not. Additionally they seem to have forgot to tell our developers this had changed.

So, personally, what I'd like to see is LL roll back the upgrade on our sims until they help our developers fix this issue. There is at least one sim that still hasn't been upgraded at this point. Seems to me we should be able to get all our sims back on the old code as well.

So, please check in here and say your piece. Let's let them know we are here and we are not happy.

I'm not too happy about this either. One of the CombatI developers has spoken about it a bit on their blog.

http://www.daikonforge.com/webtab/2008/08/30/mono-is-teh-suxxors/

You can also see live stats about the number of combati users on the side of that blog, as I post this it says:

"So far 19,069 unique Second Life® account holders have fought a total of 1,962,894 duels using CI weapons in 6,833 different regions."

I think I've found the root of the problem. I've got several people testing a workaround now. It's not a full workaround in the sense that it will provide the same performance characteristics we had before this server rollout, but it should allow us to at least use the products (instead of it being a complete and utter waste of time to try), and I may yet come up with an even better workaround.

Once I get some more hard facts and a good repro case with minimal distracting code I'll file a JIRA issue on it, and we can all go there and be squeaky wheels, lol.

P.S.: I think the root of the problem lies in code that's remained unchanged for at least a year now. It's certainly not something that *we've* changed, and could have something to do with how Linden implemented Mono compatibility. That is, I think they integrated Mono in such a way that some of the 'hooks' that even the old scripting engine use were modified, and a bug crept in. That's just an assumption, though. As I said, I'll file a JIRA and we'll see what the LL devs have to say.