A list of Tower 11 glitch workarounds:

#1Hawke0Posted 5/5/2013 6:49:39 AM
kylemcauliffe15 posted...
So last night the glitch reared its ugly head. I got to the 11th tower, explored some, left, and tried to go back. Freeze. So I attempted the glitch bypass trick with some flesh I got in the tower. Followed it to a T and the game still froze. I went and got some flesh from a different tower, game still froze.

Now I didn't just give it to Elena, I did so and slept afterwards till she was awake. The game would play the same cutscene about flowers outside each time before I could enter the tower. It would freeze no matter if I chose 11 or 12. I repeated the process at least 4 times and nothing worked.

I saw someone mention copying the savedata to another slot. So I tried that. Well this time after giving Elena some flesh and sleeping, she was NOT outside. She was inside. I talked to her like usual except I did NOT give her anything else. Went outside to tower 11 and it let me in!

Went through it some then went back. Tried the process again, just no copying. It did not work. So I did it again, but chose tower 12. IT WORKED! Then on my way back once more I did something a bit different: I gave Elena gifts along with the flesh and followed the usual procedure. This time I got the flower cutscene to play outside. IT FROZE EVEN THOUGH I CHOSE 12. I did everything exactly the same once more but chose tower 11. IT FROZE. I chose 12 again. Same thing.

So I decided to give Elena nothing but the monster flesh this time. She did not go outside after waking up, and none of the cutscenes played that did before a freeze. I chose 11. IT FROZE. Once more, but with tower 12. SUCCESS!

So basically I could only enter the final two towers by picking 12 each time after giving Elena FLESH AND NOTHING ELSE, then sleeping until she woke-up. If I gave her anything else and triggered other scenes outside it froze no matter which tower I picked. But what I don't get is why it let me in to tower 11 once after the glitch started. I cannot figure it out!

_______________________________________________________________
Yang_Shu posted...
2. After I came back from towers 11/12 to give Elena beast flesh, I can't go back into either tower. WTF??

SOLUTION - Try talking to Elena first and even trigger a cutscene by giving her a gift or sleeping until morning (7:00), this way you have breakfast with her which triggers an event scene. Then try entering one of the towers. Make sure to save first.

_______________________________________________________________
Dentenshi posted...
After many freezes and mastering the tower dusk and dawn towers layout. I found that if you beat the last two towers without going back home to feed Elana the game didn't freeze.

_______________________________________________________________
OmegaBlades posted...
Others who are experiencing this issue seem to have found a workaround, though. Basically, trigger a full-on cutscene with Elena, then try going into the tower again and it shouldn't freeze. The easiest way to do this is to feed her some monster meat, then sleep until morning so it triggers a breakfast scene with her. Then immediately after breakfast, head back out and enter the tower, and it should let you in.

Don't post yet!
---
Armstrong/Monsoon 2016
#2Hawke0(Topic Creator)Posted 5/5/2013 6:55:35 AM(edited)
In short, to avoid getting the glitch, clear the towers in one go. For this you'd be best off watching a walkthrough, but if you don't want to do that you can get around it by sleeping until morning, then having breakfast with Elena, which should allow you to enter the towers. Also, giving Elena flesh, then sleeping until she wakes up. However, this only seems to work for tower 12.
How many other workarounds did I miss? If you have one, please post it here.
---
Armstrong/Monsoon 2016
#3Thanatos2kPosted 5/5/2013 3:29:22 PM
Hard reset your system after the freeze, then enter tower 12.

Worked for me every time.
---
-Thanatos2k-
#4EvenSpoonierPosted 5/5/2013 6:11:50 PM(edited)
OK, I've been doing a lot of testing on my glitched save file. I don't have a cause, but I may have a reliable prophylaxis: as long as you're carrying meat that will spoil when you enter the Dawn or Dusk Towers, the game will not crash. This means that you have to enter from the Observatory while carrying meat (it won't spoil if you go directly from one tower to another, and so it can't protect you). It also means that you can't do this with meat that has already spoiled: it can't spoil again.

I ask other gamers to test this on their save files. Grab a piece of Beast Flesh from an early tower (I recommend Treetop), return to the Observatory, and then without giving it to Elena, go straight to either Dusk or Dawn. If this crashes your game, please let me know.

Since writing this, I found a way to make it fail. Get two pieces instead of one, feed one piece to Elena, and then carry the other piece into the tower. The meat should indeed spoil, but the game will still crash.
---
"Playing a game for its graphics is like watching pornography for the story." - Kadiroth
#5k69DegreesPosted 5/6/2013 8:42:53 AM
saving, resetting, loading, and heading straight for tower 11 worked for me
#6EvenSpoonierPosted 5/8/2013 3:19:05 PM
k69Degrees posted...
saving, resetting, loading, and heading straight for tower 11 worked for me

That worked for me once, but only once. I'm still not completely sure why.

One thing about this glitch is that its nature seems to change over time. I've gotten it to points where the workarounds don't work but you can just walk into the towers without doing anything special. This leads me to wonder if many people who think they don't have the glitch actually do, but they happen to go to the towers during a point when the glitch conditions don't include Just Going In, so they had no reason to notice.
---
"Playing a game for its graphics is like watching pornography for the story." - Kadiroth
#7RPGNinja123Posted 5/9/2013 1:28:20 AM
EvenSpoonier posted...
k69Degrees posted...
saving, resetting, loading, and heading straight for tower 11 worked for me

That worked for me once, but only once. I'm still not completely sure why.

One thing about this glitch is that its nature seems to change over time. I've gotten it to points where the workarounds don't work but you can just walk into the towers without doing anything special. This leads me to wonder if many people who think they don't have the glitch actually do, but they happen to go to the towers during a point when the glitch conditions don't include Just Going In, so they had no reason to notice.


I have said from the beginning beginning (including to that XSEED guy) that all the copies of the game contain the glitch and you would be silly not to think otherwise.

This isn't a case of that "1 in 5" people have in in their copy. It is a case of that everyone has the glitch in the NA version of the game but since most people probably only did 1 playthrough and didn't encounter the glitch they think they are somehow glitch free which is absurd.
---
It's a beautiful time to be a 3DS owner.
3DS Friend Code = 0232-8140-1787 (send a PM if you add me)
#8EvenSpoonierPosted 5/9/2013 2:28:15 AM
RPGNinja123 posted...
EvenSpoonier posted...
k69Degrees posted...
saving, resetting, loading, and heading straight for tower 11 worked for me

That worked for me once, but only once. I'm still not completely sure why.

One thing about this glitch is that its nature seems to change over time. I've gotten it to points where the workarounds don't work but you can just walk into the towers without doing anything special. This leads me to wonder if many people who think they don't have the glitch actually do, but they happen to go to the towers during a point when the glitch conditions don't include Just Going In, so they had no reason to notice.


I have said from the beginning beginning (including to that XSEED guy) that all the copies of the game contain the glitch and you would be silly not to think otherwise.

This isn't a case of that "1 in 5" people have in in their copy. It is a case of that everyone has the glitch in the NA version of the game but since most people probably only did 1 playthrough and didn't encounter the glitch they think they are somehow glitch free which is absurd.

Obviously the code that triggers the glitch must be present in all copies. There has only been one print run, and no opportunity to change things. But just as obvious is that not everybody has experienced the glitch: even in the US, it is possible (perhaps even likely) that the majority of people do not. The real question is why that happens.

Some could argue that there are situations, including some common ones, in which the glitch code simply cannot run. Obviously I cannot see the code -none of us can- but it's certainly not outside the realm of possibility for that to happen. When it happens reliably, we in the industry call it dead code, and although that's generally considered something to be excised, every once in a while something gets missed. This could be such a case: a bit of dead code from early in development that wasn't caught, and now a second glitch has appeared that makes a call into it. The reverse is also possible: dead code that was excised, but it turns out that the code wasn't as dead as everyone thought, and now the game is trying to call something that's not there. Both scenarios are extremely common cases for console freezing glitches.

But my new theory is that it's not actually about dead (or not-so-dead) code. Rather, the "changing" nature of the glitch -in quotes because it doesn't actually change; we just don't understand it well enough to see the common pattern yet- happens to be such that for a lot of people who get to that point in the game, the conditions for a crash are things they would not try anyway. On my own save file, I've seen conditions where trying to work around the glitch actually triggers it, while doing nothing special works just fine. Perhaps this is how most people experience the game. Such a situation would be indistinguishable from being glitch-free.
---
"Playing a game for its graphics is like watching pornography for the story." - Kadiroth
#9RPGNinja123Posted 5/9/2013 8:10:56 AM
EvenSpoonier posted...
RPGNinja123 posted...
EvenSpoonier posted...
k69Degrees posted...
saving, resetting, loading, and heading straight for tower 11 worked for me

That worked for me once, but only once. I'm still not completely sure why.

One thing about this glitch is that its nature seems to change over time. I've gotten it to points where the workarounds don't work but you can just walk into the towers without doing anything special. This leads me to wonder if many people who think they don't have the glitch actually do, but they happen to go to the towers during a point when the glitch conditions don't include Just Going In, so they had no reason to notice.


I have said from the beginning beginning (including to that XSEED guy) that all the copies of the game contain the glitch and you would be silly not to think otherwise.

This isn't a case of that "1 in 5" people have in in their copy. It is a case of that everyone has the glitch in the NA version of the game but since most people probably only did 1 playthrough and didn't encounter the glitch they think they are somehow glitch free which is absurd.

Obviously the code that triggers the glitch must be present in all copies. There has only been one print run, and no opportunity to change things. But just as obvious is that not everybody has experienced the glitch: even in the US, it is possible (perhaps even likely) that the majority of people do not. The real question is why that happens.

Some could argue that there are situations, including some common ones, in which the glitch code simply cannot run. Obviously I cannot see the code -none of us can- but it's certainly not outside the realm of possibility for that to happen. When it happens reliably, we in the industry call it dead code, and although that's generally considered something to be excised, every once in a while something gets missed. This could be such a case: a bit of dead code from early in development that wasn't caught, and now a second glitch has appeared that makes a call into it. The reverse is also possible: dead code that was excised, but it turns out that the code wasn't as dead as everyone thought, and now the game is trying to call something that's not there. Both scenarios are extremely common cases for console freezing glitches.

But my new theory is that it's not actually about dead (or not-so-dead) code. Rather, the "changing" nature of the glitch -in quotes because it doesn't actually change; we just don't understand it well enough to see the common pattern yet- happens to be such that for a lot of people who get to that point in the game, the conditions for a crash are things they would not try anyway. On my own save file, I've seen conditions where trying to work around the glitch actually triggers it, while doing nothing special works just fine. Perhaps this is how most people experience the game. Such a situation would be indistinguishable from being glitch-free.


Thanks for continuing the research, it would be neat to finally see a definitive workaround for a glitch that works 100% of the time. We both know they aren't releasing a patch and the XSEED guy has mysteriously disappeared as of late after declaring that "the glitch doesn't happen to that many people".
---
It's a beautiful time to be a 3DS owner.
3DS Friend Code = 0232-8140-1787 (send a PM if you add me)
#10Thanatos2kPosted 5/9/2013 8:37:39 AM
My theory is it has something to do with Elena's affinity.

I didn't get any freezes UNTIL I got Elena to max affinity after my second incursion into tower 11.

Has anyone else gotten a freeze when Elena wasn't at max affinity?
---
-Thanatos2k-