Sprite Bug

Try to make sure, the Sprite-Position is inside the lookable area of the screen and the Sprite itself is not hide or behind a other Sprite. But without the Code or a Key it is impossible to realy help you debuging.

Well, the only other thing on screen is just text saying "_____'s trip to anciet egypt" at the top of the screen. and I used

SPSET 0,464,48,16,16 

(the numbers go with my sprite set i created) and after wards used

SPOFS 0, 90, 0, 1000

and After That I i used

SPSCALE 0,1,1

so? it may be me, but?

I'm this annoyed!

Spoiler

Yes it's a joke.

Youre code should work. So there are possible Bugs later in Code: - The Sprite will be hide (try

SPSHOW 0

to fix) - The Area of picture you are using is empty - The code is not Execute - The Main loop create the Bug: - move/hide/delete/colored the Sprite or don't refresh the display or don't use the code or ... ( Edit: if you have execute Samples before you are using yore Code it is possible that the Sprite was hide this way. )

Yea thanks, I'll try these Methods as soon as my 3DS dies and then gets recharged. it kinda froze while watching youtube. but anyways thanks.

It might also be that the sprite is behind something, because SPOFS id, x, y, 1000 will set your sprite behind almost everything.

It might also be that the sprite is behind something, because SPOFS id, x, y, 1000 will set your sprite behind almost everything.

yea I said the screen was clear except text at the top. so it shouldn't be the problem

Update: If you are using

SPSET ...
'and then
XSCREEN
'or
ACLS

all sprite will be reseted and the sprite isn't set anymore.

Update: If you are using

SPSET ...
'and then
XSCREEN
'or
ACLS

all sprite will be reseted and the sprite isn't set anymore.

Well. Oh. OH. OOOHHH. Thank you. ;-) so THAT was the problem. Wow, how stupid could I be. I was so focused on getting the bottom screen to work that no didn't realize it would reset the top screen. Thanks alot. I'm so dumb.

Update: If you are using

SPSET ...
'and then
XSCREEN
'or
ACLS

all sprite will be reseted and the sprite isn't set anymore.

Well. Oh. OH. OOOHHH. Thank you. ;-) so THAT was the problem. Wow, how stupid could I be. I was so focused on getting the bottom screen to work that no didn't realize it would reset the top screen. Thanks alot. I'm so dumb.

Not as dumb as when I wondered why an IF statement caused a syntax error, and it was because I forgot to add THEN I will never make that mistake again ^_hopefully

Hey cause I'm la oof when it comes to coding, and I'm too lazy to search up anwser for like 10 minutes, i want to know, why can't I load more than one sprite on screen? I can't continue (just like the other problem) until i get an anwser so i can fix it. And im lazy so yea. #LAZY

Hey cause I'm la oof when it comes to coding, and I'm too lazy to search up anwser for like 10 minutes, i want to know, why can't I load more than one sprite on screen? I can't continue (just like the other problem) until i get an anwser so i can fix it. And im lazy so yea. #LAZY

Well you need to change the management number for the sprite, because using SPSET 0,SPRITE DEFINITION twice just makes the same sprite twice. The first number is which sprite you want to add/modify, while the second number is what the sprite looks like. So, to make a new sprite that doesn't replace one, you can just change the first number. Using SPSET 0,0 twice will replace the first use. So using a different management number, you can avoid that with something like SPSET 1,0 or SPSET 263,0, or whatever management number. It may be a good idea to organize these, though, based on what your program needs, like 0-199 projectiles, 200-299 UI stuff, etc. But any organisation style works as long as it fits what your program needs.

Hey cause I'm la oof when it comes to coding, and I'm too lazy to search up anwser for like 10 minutes, i want to know, why can't I load more than one sprite on screen? I can't continue (just like the other problem) until i get an anwser so i can fix it. And im lazy so yea. #LAZY

Well you need to change the management number for the sprite, because using SPSET 0,SPRITE DEFINITION twice just makes the same sprite twice. The first number is which sprite you want to add/modify, while the second number is what the sprite looks like. So, to make a new sprite that doesn't replace one, you can just change the first number. Using SPSET 0,0 twice will replace the first use. So using a different management number, you can avoid that with something like SPSET 1,0 or SPSET 263,0, or whatever management number. It may be a good idea to organize these, though, based on what your program needs, like 0-199 projectiles, 200-299 UI stuff, etc. But any organisation style works as long as it fits what your program needs.

thanks like ALOT. (an idiot, I'm am)