[b43] Game stuck on load screen for entering Caldera.

[Crim, The Red Thunder]

Been stuck at 100% on loading zone when entering the caldera (second time) and sitting here for over 5 minutes now. Music continues to loop, and mouse cursor 'flickers' in the tome window (typically solid when loading or processing things heavily), as if the computer wasn't trying to do anything. How do I get OUT of this mess (without losing the character), so I can at least close tome? (Without screwing the character) And how do I get back INTO the caldera, so I can try for my unlock?

[SageAcrin]

Forcequitting is usually safe enough when presented with a big nasty bug.

You'll lose everything until your last save, of course, but it's better than losing the character forever.

[Crim, The Red Thunder]

That got me out (thanks), but on attempting to reload the character, things got much worse. After loading, world map music is playing, game appears to treat me as if I am on the world map (can't use items, etc.) but the only elements visible are the HUD displays. Everything else is black. Even my character doesn't show up. Lua errors generated on attempting to use the < or > commands (I knew I was standing on caldera entrance, but apparently the game doesn't), Different lua error generated on attempting to use the look command. Can't do anything, don't appear able to solve the problem. Attempting to save and reload (which was what ingame chat recommended), did NOT solve the problem, I remain in my formless black void. I update this here, hoping someone can tell me what needs to be done to fix my character.

Edit: (Or should I start a new bug topic for this?)

[supermini]

Turn on lua console. You can see how it is done here: http://te4.org/wiki/t4modules-debugging

When in game, bring up the console and type
game.changeLevel(1, "trollmire")

If that doesn't work, save the game again (while in limbo), then load and try again.

[wildwolfofdark]

This is the error at 82-84% loading the area that I got.

[SHADER] Loading from /data/gfx/shaders/funky_bubbles.lua
Lua Error: /engine/Shader.lua:123: attempt to index local 'shad' (a nil value)
At [C]:-1 __index
At /engine/Shader.lua:123 createProgram
At /engine/Shader.lua:139 loaded
At /engine/class.lua:325 load
At /engine/Savefile.lua:387 loadObject
At [string "d={}..."]:328 deserialize
At /engine/class.lua:316 load
At /engine/Savefile.lua:387 loadObject
At [string "d={}..."]:585 deserialize
At /engine/class.lua:316 load
At /engine/Savefile.lua:387 loadReal
At /engine/Savefile.lua:455 loadGame
At /engine/Module.lua:643 instanciate
At /engine/utils.lua:1871 showMainMenu
At /engine/init.lua:124
At [C]:-1 dofile
At /loader/init.lua:183
[PROFILE THREAD] batching CSETs

[jenx]

ah - I had this and solved it. It happens when Open GL shaders is disabled. Try enabling it, and restarting. If this doesn't work, I know it is one of the video options.

Still a bug, but this is a workaround.

[Crim, The Red Thunder]

My shaders were ON. I didn't know what, but I knew there was a bug related to them being off in the caldera. Not sure about his bug (if that's what you were talking about) but I double checked mine. Unless the crash somehow forced them off...

[darkgod]

The ycan be on and still your video card not support them correctly

[Crim, The Red Thunder]

The ycan be on and still your video card not support them correctly

How can I confirm that THIS is the problem? I entered the caldera (once) successfully, after dying to a worm that walks, I respawned elsewhere (world map) ad tried to head back in. At that point it hung. If it was a shader issue, wouldn't it have happened the first time I tried to go in? (Plus, I thought the shader issue was with one of the dreams) If this IS the problem, how can I go about getting around it on future runs?

[darkgod]

You cant, but I'm sure.
ANd you're best bet is to avoid the caldera util next beta, which is soon anyway