devkitPro

Quick question. From the source, it appears that it would be fine, but I just wanted to check. Should oamInit() suffice as a way to just reset the oam for a particular engine after it's already had several spots in memory allocated, etc? I notice there is an undocumented function oamAllocReset() called so I'm wondering if that pretty much does the trick.

Thanks,
Sylus

well, one of the first things oamInit() does is a call to dmaFillWords(), so my guess would be yes. I suggest you try it out and see if anything weard happens.

but why aren't you using oamClear() to clear/reset the oam?

Because it's not just hiding all the sprites that I need to do. I'm also wanting to reset the memory allocation system.

as for hiding sprites: you can make a function yourself(it's not too complicated) for resetting the gfx i don't know, maybe clear the whole vrambank you're using for the sprites?

or by setting the sprites visibility to false, which is what oamClear() does.

also, oamInit() calls oamAllocReset() in the end, so I think it would be ok.