Flickering debug lines
-
@Raphi (View Post)
Does it? I never noticed that one too..
Did you compile/download an older version to check this? -
No, I used the current source...
When PSTN is sparked with other metals than pscn or nscn, it will behave like sparked with nscn.
1240958View Save 1240958Is it supposed to do that?
-
@jward212 (View Post)
I looked at the save, and I can't see any obvious problems. I could try debugging the problem but it's probably just an issue with the orientation.
@Raphi (View Post)
usually when you hit update you will actually update so it isn't a problem. For hitting the 'x' I usually just right click it and it goes away. It isn't really worth it to fix it since most people will just update anyway.
@Raphi (View Post)
Yes, that is intended behavior. -
OoO That is a STUPID atrocious property! *tapity-tap-tap-tapity-tap* "Not anymore." :P
EDIT:
if ((r&0xFF)==PT_SPRK && parts[r>>8].life==3) {
if(parts[r>>8].ctype == PT_PSCN)
state = PISTON_EXTEND;
else if(parts[r>>8].ctype == PT_NSCN && parts[i].temp<=373.15)
state = PISTON_RETRACT;
else if(parts[i].temp>373.15)
state = PISTON_RETRACT;
} -
@cyberdragon (View Post)
how would making it temperature dependent help anything? Also what's the point of checking parts[i].temp<=373.15 when it's going to do PISTON_RETRACT anyway, I think you did that wrong. -
No, I fixed it...see
else if(parts[i].temp>373.15)
state = PISTON_RETRACT;But that property is really anoying with other electronics near the piston, so I made it only work over 100C
-
@Raphi (View Post)
I fixed the first problem by making debug lines not be drawn in persistent mode. They really shouldn't be anyway. I also fixed being able to go too far in the save browser. I didn't make it use the current display mode in the save renderer, since in my tests it didn't look good at all. Having saves (like in the save browser) change depending on your display mode was confusing, you might see all saves rendered in blob mode for example which you probably wouldn't want. I'm going to want to have statmp thumbnails eventually be stored and not re-rendered every time you go in, and so I don't think having deco go on / off is a good idea either. Usually if you have deco in a stamp, you want it there.
But I did see that something broke the fact that stamps and local saves shouldn't be rendered in fire mode. So I fixed that, fire is no longer in the stamp browser and the render a ton faster now.
