Originally posted by dirbaio
Oh...
Here's why I changed it:
In a level file, the object number is stored in a byte (8 bits). The max number in a byte is 255. So we (well, Treeki) thought that the object limit was 256.
BUT then I saw that making a tileset bigger than 128 objects crashed the game. Always.
So for some reason the game likes max 128 objects, so I changed it in the editor...
I am not getting crashes in the higher object numbers. Is it possible to re-add the 256 limit? I think it is a cumulative 128 objects that will crash it. Again, I was getting corruption below 100. What would happen was that some tiles would look right in the editor. But, in a real DS they were different tiles altogether. The fix at that time for me was to assign them to higher numbers than what the original tileset objects had.
I really want to use the new editor, as its additional content is very useful. But I have built a lot of my game based on the above mentioned. So, I would basically have to start all over to use the new editor revisions. I am surprised there haven't been many others with the corruption issue. SKJmin had the same corruption problem as well in his NSMB3 build. I had talked to him a while back about the corruption problem, and that is how I came to fix it.
|