Currently I have run into a little problem which causes the cloning of certain objects if you visit an area multiple times. I am unsure of the cause, however I get the sneakiest of suspicions that it's the draw list doing it as usual.
 |
| That's a lot of wumpa fruit right there. It also rarely clones penguins. |
Ironicly, the objects that get cloned are originals, not the objects that I have added (which you would expect to be more glitchy, but evidently the game thinks otherwise). And as you might have suspected, as more and more objects clone, the game rapidly becomes unplayable.
As such, I need to overcome this problem before I can continue level design. So, may be slow progress for a little while, though I hope I can get this resolved quickly.
When you say "unplayable", do you mean that the object cloning is causing a rapid use of memory?
ReplyDeleteIf so, it's almost reminiscent of when you play in the Sonic debugs and try to add a ton of items - stuff begins to disappear and the game starts having audio stutters/video flickers/etc.
Good luck in fixing this, though.
Yes, that seems to be the case. What happens is the game will first use all available memory it has set aside for rendering objects; failing that it will start using memory assigned to the menus and the HUD display to draw more objects (thus making those appear blank if you call for them), and failing that some objects don't render at all, you can't pause, and trying to do screen transitions freezes the game.
DeleteYou can actually get this effect to occur in Ruination's bonus round on an unmodded Crash 2; break lots of those body slam boxes without picking up the fruit, then try to pause. You'll get one of two things: It either won't let you pause at all, or you'll be able to pause but the menu will look glitchy. Similarly, you can try calling the HUD and it will often be missing its numbers when you do.
What an interesting oversight by developers at that particular area. It'd be interesting to spot other areas like that.
ReplyDelete