RSDuck / craftus_reloaded

A second attempt at a homebrew Minecraft clone for 3DS
Other
53 stars 9 forks source link

Crash while playing the game #2

Closed jj20466 closed 7 years ago

jj20466 commented 7 years ago

crash_dump_00000016.dmp.zip I was playing the game yesterday when it crashed all of a sudden mid build and this came up 20170827_160421 Then i went to the location and found the dump file so you can look at and is there a way for you to turn auto jump off or fix it cause when ever i bump into a wall it makes me jump.

RSDuck commented 7 years ago

I looked into the crash and I think it's related to file I/O but I'm still not sure. Can you reproduce the crash, or did it happen only once? And if you don't mind, can you please send me the save folder of the world? You're probably playing on a n3ds. I always forget about them. I have to disable the auto jumping on nd3ses and improve so that it is more like MC PE.

jj20466 commented 7 years ago

I would love to recreate the error but it deleted most of my build and i dont know how i did it,i was making a castle and i had the outside walls with towers on each corner then i started outlining the main building/house on the inside and as i was making the second floor the game crashed then the error popped up. ffg.zip

.

RSDuck commented 7 years ago

this issue seems to be one of these where it's hard to find the orgin, because they can't really be reproduced.

I really hope I fixed this issue, but I let the issue open, it might happen once again

jj20466 commented 7 years ago

Game crashed again,only thing i did before it crashed was jump by pressing the button then landing on a block in front of me i think about a block or two away. crash data.zip

jj20466 commented 7 years ago

I took a screenshot of what i was doing this time after the game crashed. 20170830_122845 All i was doing was looking down while holding the place block button and slowly moving forward to build the wall crash data new.zip

RSDuck commented 7 years ago

I think, I fixed this issue, but if someone experiences a similar error again, please reopen this issue