#47814 - wbochar - Wed Jul 13, 2005 9:08 pm
I have a prog that uses BG0, BG1, BG2 with OBJ and OBJ1D with Mode 0
I was using just one BG and mode 0 with the sprites and it worked fine, but after some modifications and addintions of other tilesets and BG's my sprite seems to have gotten corrupted along the way.
I checked in vba and the sprite is successfully loaded in oam in the first slot. when I check the actual display there is a big black square on the screen. This feels like a wrong memory spot or somehting isnt being copied correctly etc. The code to hande the sprites has been the same through all my tests, so the addition of the extra backgrounds and tilesets seems to be my culprit..
Has this happened to anyone else? I have had 10 sprites bouncing around the screen before and I am using the same code that worked previously for other projects... I just cant seem to figure out whats going on. Any initial thoughts?
I am at work on break right now, so maybe when I get home I'll up the source. But TIA for anyone who might have any thoughts sans le code.
wolfgang
I was using just one BG and mode 0 with the sprites and it worked fine, but after some modifications and addintions of other tilesets and BG's my sprite seems to have gotten corrupted along the way.
I checked in vba and the sprite is successfully loaded in oam in the first slot. when I check the actual display there is a big black square on the screen. This feels like a wrong memory spot or somehting isnt being copied correctly etc. The code to hande the sprites has been the same through all my tests, so the addition of the extra backgrounds and tilesets seems to be my culprit..
Has this happened to anyone else? I have had 10 sprites bouncing around the screen before and I am using the same code that worked previously for other projects... I just cant seem to figure out whats going on. Any initial thoughts?
I am at work on break right now, so maybe when I get home I'll up the source. But TIA for anyone who might have any thoughts sans le code.
wolfgang