To begin, I wanted to show my support for your development of Lost Winds and your excellent debut on WiiWare. Fantastic game!
Unfortunately, it seems I've run into one or two small issues in the game.
I encountered my first issue in the Old Village area of the game. In the upper right corner of the map after obtaining the memory chest in the area there was a bridge near some fire. It would appear that any time Toku was standing on the bridge in the process of it being burnt he would float in the air where the bridge previously existed, until I moved him, then once hitting the ground he would lose any ability to move or use his wind powers forcing a game reset. I was able to reproduce this several times and will have a video up of it sometime later today to better demonstrate.
A similar situation happened above Wither Falls for the last chest of the game. I do not recall the exact situation that caused the issue, but it seemed landing on the red vineish enemy while floating caused the same issue to happen as mentioned before.
Edit: While not in the exact location that I encountered, here's a similar instance (not mine) of the issue:
http://www.youtube.com/watch?v=TSsozx-BUsQ
Unfortunately, it seems I've run into one or two small issues in the game.
I encountered my first issue in the Old Village area of the game. In the upper right corner of the map after obtaining the memory chest in the area there was a bridge near some fire. It would appear that any time Toku was standing on the bridge in the process of it being burnt he would float in the air where the bridge previously existed, until I moved him, then once hitting the ground he would lose any ability to move or use his wind powers forcing a game reset. I was able to reproduce this several times and will have a video up of it sometime later today to better demonstrate.
A similar situation happened above Wither Falls for the last chest of the game. I do not recall the exact situation that caused the issue, but it seemed landing on the red vineish enemy while floating caused the same issue to happen as mentioned before.
Edit: While not in the exact location that I encountered, here's a similar instance (not mine) of the issue:
http://www.youtube.com/watch?v=TSsozx-BUsQ
Last edited:
