Someone lemme know if something like this is also happening to you as well. The only thing I can think of that is having this lockup occur, is the music is trying to calculate when & where to loop, but the game is looking for a song that doesn't exist/isn't where it's supposed to be in the translation, so it kills itself as a result. The TF5 Opponent one is left untouched, but the player one plays nothing when selected, so I can see where I believe the maker got it from. The UMD Recognition TF5 bgm unlocks seem to be tampered with as well. The TF5 DD bgm is basically inserted directly on top of the spot the TF6 DD bgm is supposed to be, with the opponent's DD theme untouched. I went to the music player on both games, and weirdly enough, the translation and untouched have the music in different spots under different names. I then loaded a fresh, untouched TF6 game, loaded my save as they share the same game ID, followed the exact same steps, and no crash occurred. if after a minute or so, it didn't hard-lock the game and require a reset. It's the Tag Force 5 DD bgm, rather than the usual TF6 bgm. *(inhales)* So when I duel on the translation with Destiny Draw *(DD)* active, different music is loaded. I've been playing one of the translations as well, but I seem to have encountered a weird hiccup.
0 Comments
Leave a Reply. |