jacob1
29th Sep 2012
16th Mar 2014
Post any bugs you find here. But there aren't as many bugs that are really bugs and I don't already know about than when this first started, so also use this as a general conversation save, or to ask / tell me anything. #1 most commented save in tpt!
problems
jacob1
bugreport
glitch
fix
960847
tptpp
bugs
tptplusplus
glitches
Comments
-
jacob1: all right, fair enough.
-
so yeah, it would break saves. But he hasn't used PTCT/NTCT for years, nobody really does anymore.
-
"if the spark frequency isn't high enough, an "on" signal could become choppier", "also non-combinatorial and timing circuits would quite certainly be affected"
-
I asked the subframe people more about it to see what they think, they knew more about electronics than me.
-
I accept what you're saying, it's just that "likely" doesn't exactly convince me, you know?
-
A lot of older electronics likely depend on it being slow. You could probably get a few sparks in before it cooled down enough. They very likely use that for something. Older electronics were pretty poorly designed.
-
Just so I'm not spamming that thread, how would changing semiconductor cooling break saves? Would it really be an issue?
-
Security-Drone: I just checked the ISOZ commit history, it never was called that (at least in tpt++). It actually didn't have "isotype z" in the name for years either, I added it in 2013 when I made a bunch of description changes.
-
If it was mentioned elsewhere, I would have immediately forgotten, it's good to have it somewhere I will actually check in a few months
-
Woo, bug posted to github! I just have this overwhelmig dread that it's already been mentioned elsewhere...