bug 1.7 stuck while entering Angolwen

Where bugs go to lie down and rest

Moderator: Moderator

Post Reply
Message
Author
mooncatz
Wayist
Posts: 22
Joined: Sun Jun 09, 2013 8:09 pm

bug 1.7 stuck while entering Angolwen

#1 Post by mooncatz »

I played archmage as usual and got endless loading screen while I was trying to enter Angolwen for second time. Chat stopped scrolling, I couldn't do anything, so I killed the game.
If I load the save, I get black screen and lua error en masse.
After that I asked the mod to teleport me out to worldmap. It worked but I still get the same endless loading screen if I try to enter the city.
Savefile is here https://hdd.tomsk.ru/file/mmetrolf
linux x64

Updated: it's interesting to note that I've made another archmage and the situation repeats. I entered Angolwen successfully first time and can't enter the second time.
Loading screen: https://hdd.tomsk.ru/file/vdvshbwh
Lua error: https://hdd.tomsk.ru/file/pdudhwgz

Update2 : Way to reproduce: make lvl 1 archmage, skip abashed expanse and return to Angolwen immediately. The game goes to endless loading with DLCs and works flawlessly w/o them.

Pisastrish
Thalore
Posts: 157
Joined: Wed Sep 28, 2016 8:07 pm

Re: bug 1.7 stuck while entering Angolwen

#2 Post by Pisastrish »

I've had this happen with a a number of different levels, all different zones, classes, races. It seems like any time you revisit a level this has a chance of happening

cundel
Yeek
Posts: 12
Joined: Thu Mar 26, 2020 12:58 pm

Re: bug 1.7 stuck while entering Angolwen

#3 Post by cundel »

Same here. Some version of this error message appears for me when this bug occurs:

Code: Select all

Loading savefile 	/save/faehi/
Lua Error: [string "d={}..."]:18: attempt to perform arithmetic on global 'inf' (a nil value)
	At [C]:-1 __unm
	At [string "d={}..."]:18 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:6575 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:8 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:2024 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:720 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:162 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:42 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:10174 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:446 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:287 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadObject
	At [string "d={}..."]:104 deserialize
	At /engine/class.lua:501 load
	At /engine/Savefile.lua:477 loadReal
	At /engine/Savefile.lua:559 loadGame
	At /engine/Module.lua:1081 instanciate
	At /engine/utils.lua:2881 showMainMenu
	At /engine/init.lua:207 
	At [C]:-1 dofile
	At /loader/init.lua:217 
This specific error message appeared when loading a file that is in Dreadfell. A similar message occurred for me when visiting Angolwen for the 2nd time. Deleting the respective zone in the save file fixes the issue and regenerates the zone as expected.

UPDATE: did some digging (in an effort to recover my save file) and here's the specific object in the save file that caused the error: https://pastebin.com/YZp51V4y
It's a forge giant that has the attribute "high_value" set to -inf on line 18.

darkgod
Master of Eyal
Posts: 10750
Joined: Wed Jul 24, 2002 9:26 pm
Location: Angolwen
Contact:

Re: bug 1.7 stuck while entering Angolwen

#4 Post by darkgod »

should both be fixed; retest when I release 1.7b2 please
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning ;)

Post Reply