3 ms·
This style of coop multi-tasking was in Crash Team Racing on PS1 for a while. Unfortunately on a machine with only 2meg of ram it turned out to take too much me
by greggman3 6y ago
This style of coop multi-tasking was in Crash Team Racing on PS1 for a while. Unfortunately on a machine with only 2meg of ram it turned out to take too much memory and be too fragile. The stacks had to be small, add one printf for debugging and you'd overflow the stack. Eventually it was torn out.
- anonymoushn 6y agoI'm surprised you didn't pile on by making a printf which switches to the main stack, does the actual printf, and switches back.
- deleted 6y ago[deleted]
- greggman3 6y agoprintf was just an obvious example. Any function had this problem. You run, things work, and then under some condition the function you called called something else and crash. Or you try to add some functionality to a function in the system and suddenly the tasks crash because your edit used more stack. The point isn't to dis this method. It's just to say it was frustrating with tiny stacks.
- anonymoushn 6y agoI see, that does sound tough.
- aktau 6y agoWhat was it replaced with?
- greggman3 6y agoThe typical for g of gameobject g.update()