Seige911 Jul 7, 2013 @ 10:46pm
Crash Issue
The game was working for me previously (Approx a year ago). Decided to give it another spin and was greeted by a traceback right after I get to viewing the logs. I get an identical traceback no matter which log I click. I have currently tried validating the game (had to reaquire 72 files), and removing local contents and reinstalling. If the errors were not in .rpy I could probably fix them myself, since it appears to be a trivial python array issue. Any ideas on how to fix this?

Error:

I'm sorry, but an uncaught exception occurred.

While running game code:
File "game/script.rpy", line 1816, in script
File "game/script.rpy", line 1816, in python
File "game/screens.rpy", line 415, in python
IndexError: list index out of range

-- Full Traceback ------------------------------------------------------------

Full traceback:
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\execution.py", line 265, in run
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\ast.py", line 632, in execute
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\python.py", line 972, in py_exec_bytecode
File "game/script.rpy", line 1816, in <module>
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\exports.py", line 789, in pause
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\ui.py", line 237, in interact
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 1799, in interact
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 2037, in interact_core
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 246, in visit_all
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 246, in visit_all
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 246, in visit_all
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 248, in visit_all
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\core.py", line 2037, in <lambda>
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\screen.py", line 155, in per_interact
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\display\screen.py", line 247, in update
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\screenlang.py", line 1166, in __call__
File "C:\Program Files (x86)\Steam\steamapps\common\Analogue A Hate Story\renpy\python.py", line 972, in py_exec_bytecode
File "game/screens.rpy", line 415, in <module>
IndexError: list index out of range

Windows-post2008Server-6.1.7601-SP1
Ren'Py 6.13.11.1715
Analogue 0.0
Showing 1-5 of 5 comments
< >
Seige911 Jul 7, 2013 @ 10:52pm 
More info: Looks like it is only when accessing block 4. If I access any other block first everything looks to work. Interesting.
echo_20 Jul 10, 2013 @ 2:00pm 
Some files are missing. Check game cache
♪ᴹeᴸoᴰy♪ Jul 12, 2013 @ 8:56am 
I'm having the same issue, but with all of the blocks. I validate the cache, and it says I'm missing 72 files. It proceeds to download 512kbs worth. Game continues to crash. I've done this 4 times now and it still won't work. I've even tried validating twice in a row, but it never finds anything wrong the second time.
Scout  [developer] Jul 12, 2013 @ 9:49am 
See this thread: http://steamcommunity.com/app/209370/discussions/0/864949483115743007/

Basically, I'm really sorry—if you made a save with that version of the game that was briefly broken, that save will be rendered unplayable. You'll have to start a new game.

Let me know if that doesn't help!
Seige911 Jul 12, 2013 @ 11:26am 
Thanks for the response,

I bought this game on a whim, and I am glad I did. If nothiing else than to support a developer who continues to try to improve already existing software and who is willing to help those who are caught by things that slipped through the QA process. That and the manner which the game crashed is actually nice as well, most just crash with no error and no way to attempt to recover (though I do smell liberal use of the traceback module, but there is nothing wrong with that).

If your still trying to patch the issue one thing to suggest to others as a temp work around is to open some block other than 4, that seems to bypass the issue, at least for me. Happy "import pdb; pdb.set_trace()" or alternatively "python -m pdb Analogue.py"
Showing 1-5 of 5 comments
< >
Per page: 15 30 50