Posts for Tavados

Posted: 12/22/2015 4:37 PM
Quote
Tavados
Experienced Forum User
Joined: 12/21/2015
Posts: 5
Believe it or not, but I already looked to the EWRAM. Yea, 005040 contains x and 005044 contains y, but only of the center of rotation. There doesn't seem to be x and y for all parts, which I definately need. With another variable telling the rotation of the block it would technically be possible aswell, although I really hope to straightup get four x and y coordinates.
Posted: 12/21/2015 1:37 PM
Quote
Tavados
Experienced Forum User
Joined: 12/21/2015
Posts: 5
I said twice that I did that already, maybe I'm formulating it wrong. I tested 4Bytes, I tested 2Bytes, I tested 1Byte. In each case the memory jumps around to values that don't make sense.
Posted: 12/21/2015 1:03 PM
Quote
Tavados
Experienced Forum User
Joined: 12/21/2015
Posts: 5
x goes from 0 to 9 and y goes from -1 to 19 (-1 is for when e.g. the square spawns at the very top, only showing the lower half). As I said I also looked at the values Byte by Byte and it doesn't make sense either. For example the x-coordinate of part0 (of the 4 part object) is at 0x7750, then the actual position is in 7750 itself, not in 7751,7752,7753. Also that value jumps from e.g. 7 to 0 then to 24 etc. Is the IWRAM the only legit domain to find those values?
Posted: 12/21/2015 10:52 AM
Quote
Tavados
Experienced Forum User
Joined: 12/21/2015
Posts: 5
When I change to 1Byte, I look at each quarter of the 4Byte address. So when 7754@4Byte flickers, then I will look at 7754,7755,7756,7757@1Byte! Edit: Either way, the important information seems to be only in the first Byte (for 7754 [0,18] would be in sane range) but it "flickers" to several hundreds when looking at 1ByteUnsigned.
Posted: 12/21/2015 10:22 AM
(Edited: 12/21/2015 10:49 AM)
Post subject: Ram "flickers" at Tetris World
Quote
Tavados
Experienced Forum User
Joined: 12/21/2015
Posts: 5
Hi there, hopefully I chose the correct category. So, I want to implement some machine learning and I chose Tetris World for the GBA as platform to do so. By now I got several ram addresses that contain the x and y of the current blocks vertices. Unfortunately the values "flicker" a lot. For example x is 32(goes in steps of 8 when moving left or right) and y is 10(decrements whenever the block goes down) and in the next tick they suddenly are at seemingly arbitrary values and then go back to normal. If I go for 4Byte unsigned they jump to several millions, if I go for signed, then obviously also to negative millions and even if i set the size to 2 or 1 Byte, the values jump around a lot and don't stay at the values that would make sense. Has anybody got an idea, why that happens and how I could fix that? It would suck if I had to make a sanity check for each value every time. Edit: I made a gif, so you can see what i mean. here