[1.5.3] Crash when starting new game

Where bugs go to lie down and rest

Moderator: Moderator

Post Reply
Message
Author
Dozebom
Wayist
Posts: 16
Joined: Thu Mar 09, 2017 6:37 pm

[1.5.3] Crash when starting new game

#1 Post by Dozebom »

Lua Error: attempt to call a nil value
At [C]:-1
At /engine/Module.lua:339 parse
At /engine/Module.lua:358 listBackgrounds
At /engine/Module.lua:717
At [C]:-1 enable
At /engine/Module.lua:713 loadScreen
At /engine/Module.lua:947 instanciate
At /engine/utils.lua:2243 showMainMenu
At /engine/init.lua:172
At [C]:-1 dofile
At /loader/init.lua:217

This only started after I added some addons, but it doesn't look like there's any errors related to them...

Dozebom
Wayist
Posts: 16
Joined: Thu Mar 09, 2017 6:37 pm

Re: [1.5.3] Crash when starting new game

#2 Post by Dozebom »

It's not the addons! Huh...

Dozebom
Wayist
Posts: 16
Joined: Thu Mar 09, 2017 6:37 pm

Re: [1.5.3] Crash when starting new game

#3 Post by Dozebom »

My previous error (Safe Mode when starting game) went away after I deleted the T-Engine and the t-engine4 folders, but then *this* problem happened. Maybe I should disable shaders.

Dozebom
Wayist
Posts: 16
Joined: Thu Mar 09, 2017 6:37 pm

Re: [1.5.3] Crash when starting new game

#4 Post by Dozebom »

Nope. That didn't work.

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

Re: [1.5.3] Crash when starting new game

#5 Post by darkgod »

Try to move away the whole of C:/users/FOO/t-engine/ 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 ;)

Dozebom
Wayist
Posts: 16
Joined: Thu Mar 09, 2017 6:37 pm

Re: [1.5.3] Crash when starting new game

#6 Post by Dozebom »

You mean backing it up and then deleting it? I've already done that; that's what caused this bug. Before I did that, I got the "Safe Mode bug" described in my other thread. If I move the backed-up folder back, I get the "Safe Mode bug" again.

Post Reply