Who's started converting products to Mono?

Just wondering if anyone's made the switch 'for real', i.e. not on a test project or something like that. It should be on all sims by now, right. Are there any changes or bug fixes planned for the near future that would be worth waiting for?

The products I'm thinking about do some math, so I'm hoping for a little performance boost / sim load reduction.

state changes are totally screwed as in 5 minutes for a state exit. I've read about a couple more here and there. Personally I would suggest waiting a couple of weeks and give time for QA to knock out a couple of the showstoppers first.

I too am enormously interested in a real world test. My initial results (discussed elsewhere) have stopped me from attempting a bulk convert, and in particular I'll be awaiting the outcome of the following unresolved Jira's: SVC-2958, SVC-2967, SVC-2973, SVC-2972.

If someone *does* do a full sim convert, I'd be fascinated to know the difference in script time (ctrl-shift-1) on a sim where the only difference was all scripts compiled to LSL/all scripts compiled to Mono. Also any perceived lag differences.

My initial results (discussed elsewhere) all point to the strong possiblity that the "mono sim" would lag more by a factor of between 20% to 100%. Of course, I am equally strongly hoping that this is wrong - but I've never seen the comparison.

Additionally even this comparison may be moot, since the LSL that's on the 1.24 version *is not the same* as the LSL that's on the 1.23 version and earlier.

/esc

Thanks. I've been following some of the other threads, and I know I should be doing my homework, but I also know that some of you are keeping track of this much better than I am, so sometimes it's just easier to drop in and ask people

I have had products tried and tested in Beta for a while, but as Jesse said, I am holding off a few weeks before releasing them. I have recompiled a few of my older scripts with good success, but they were scripts that a) I knew would benefit as they had no state changes and were already small footprint and b) do not require the new viewer.
I have started testing other products in MONO, but certainly will not be releasing them until I know what unforseen bugs are running wild, It can be hard enough debugging my own code without having an unpredictable environment to work in

i did a tryout on my "jelly prim" (look at splo)

since its doing a crapton of math per loop

didnt help much, if at all