Page 1 of 1

Loading error?

Posted: Sun May 30, 2010 2:45 am
by Frumple
A number of my savefiles are now putting the following out in the stdout file:

Code: Select all

Lua Error: /engine/Savefile.lua:185: attempt to index local 'f' (a nil value)
	At [C]:-1 
	At /engine/Savefile.lua:185 loadReal
	At /engine/Savefile.lua:234 loadGame
	At /special/mainmenu/class/Game.lua:216 fct
	At /engine/ButtonList.lua:119 click
	At /engine/ButtonList.lua:57 fct
	At /engine/Mouse.lua:42 
They are refusing to load, unfortunately. The little loading box will pop up, CPU cycles will be consumed, then after a little bit it'll just more or less hang. Pressing a button will cause the loading box to disappear, but nothing else to occur. Extracting T4 to a different folder, just in case, produced the same effect.

Whatever this is just ate the first fighter I've actually gotten off the ground :(

Re: Loading error?

Posted: Sun May 30, 2010 7:53 am
by darkgod
Send it to me please

Re: Loading error?

Posted: Sun May 30, 2010 9:24 am
by Frumple
How much do you want? Just one of the saves, or all of the non-functioning ones? The savegame lua file? Whole shebang? And, uh, where do I send it*? Do you have a preferred compression format (.zip, .rar, .7z, etc.) for the folder?

*Is the little contact button on the older tome page alright? Want to confirm before I throw a ~4 meg file at someone's inbox, heh.

Re: Loading error?

Posted: Sun May 30, 2010 9:39 am
by darkgod
the whole savefile directory, zip is fine.

Send it at darkgod@[thenewtomedomain]

Re: Loading error?

Posted: Sun May 30, 2010 9:46 am
by Frumple
Sent, I think. Should be from a gmail sakkaku.kami account.

Re: Loading error?

Posted: Sun May 30, 2010 9:54 am
by darkgod
Got it, it seems the main savefile is truncated ! hum
Do you remember any errors in the log when you saved ?

Re: Loading error?

Posted: Sun May 30, 2010 2:09 pm
by Frumple
None that I can remember, but I wasn't looking, either. The save process was interrupted in that case, though I've got a few it wasn't (and is displaying the same behavior), that I can remember. It's been doing it regularly to my files, so I'll start keeping an eye out for it, get back to you.