Here's a nasty one. I don't know what's causing it but it's ruining this save. The lamps stayed glowing on unpause even after reloading. But I reopened it and unpaused and they died. Do I have to save unpaused or is there something wrong?

The system itself is faulty. I opened a save that did not use to cause much lag and noticed it lagging badly. Not even starting the save, just unpausing, it went down to about 40 fps. So, I decided to check something. I opened the same save in my mod and it ran about 10 frames faster. Something is wrong.

Note: I'll try erasing each element and wall indevidualy till it stops lagging to see if it's a certain element(s) causing the problem.

EDIT: My God! I left it sitting unpaused (still not doing much) and was dropping below 30 fps. This is BAD!

EDIT: The simulator has major errors, people are going to start noticing. I erased a tiny bit of water and it got WORSE! And yes, I'm sure this is in the official version.

No, this is frequent, and major slowdown with nothing much going on in the save. And my mod runs faster when I've added to the engine. Something is slowing it down, either a stray variable (floating) or an out of control function running when it's not supposed to. I think I found one problem...glass is causing some of the lag.

Note: I immediately found it before I finished this post, this: parts[i].pavg[1] = sim->pv[y/CELL][x/CELL];

is double defined here:

int Element_GLAS::update(UPDATE_FUNC_ARGS)
{
parts[i].pavg[0] = parts[i].pavg[1];
parts[i].pavg[1] = sim->pv[y/CELL][x/CELL];

(blah...blah...blah)

}

And here too:

if (t == PT_GLAS || t == PT_QRTZ || t == PT_TUNG)
{
parts[i].pavg[0] = 0.0f;
parts[i].pavg[1] = pv[y/CELL][x/CELL];
}

BUT WAIT...THERE'S MORE!

Notice...that parts[i].pavg[0] is also double defined this way

parts[i].pavg[0] = 0.0f;

and this way too:

parts[i].pavg[0] = parts[i].pavg[1];

EDIT: I FIXED IT! :D :P

if (t == PT_QRTZ || t == PT_TUNG)
{
parts[i].pavg[0] = 0.0f;
parts[i].pavg[1] = pv[y/CELL][x/CELL];
}

I can see exactly what it does, it's crap stuck on there for that "else" statement to prevent the simulator from stopping some elements from breaking. WEEELLL....

Merry Christmas

/*if (t == PT_GLAS || t == PT_QRTZ || t == PT_TUNG)
{
parts[i].pavg[0] = 0.0f;
parts[i].pavg[1] = pv[y/CELL][x/CELL];
}
else
{
parts[i].pavg[0] = 0.0f;
parts[i].pavg[1] = 0.0f;
}*/

And a Happy New Year too...

if(t != PT_GLAS || t != PT_QRTZ || t != PT_TUNG)
{
parts[i].pavg[0] = 0.0f;
parts[i].pavg[1] = 0.0f;
}

Everthing works fine with less lag.

Err YES

You already defined that reset in the elements themselves.

2) glass SHOULD break immediately in high pressure, it's glass AND IT DOES IN THE OFFICIAL VERSION ANYWAY, and I tested pausing and putting it in high pressure than turning air off, it stayed intact

3)no, you are totally and absolutely wrong, it won't "keep it's pressure values", they will be reset by that definition in the element loop. 

And the final nail in your particularly ugly coffin...when glass melts, it's no longer glass, it's Molten GLAS, which is actually LAVA(GLAS) SOOOO...any values it had are gone. :P:P:P:P:P:P:P:P:P:P:P:P:P :  P

If this goes on any longer...I might spontaniously turn into Pheonix Wright.

EDIT: TAKE THAT Edgeworth!