MegaGlest Forum
Archives (read only) => Glest Advanced Engine => Bug reports => Topic started by: ChupaReaper on 3 May 2011, 18:54:11
-
The game wont start at all and the error.txt file produces this:
Glest Advanced Engine: Error log file. 03-May-2011_19-20-12
While loading background style for widget type 'CONSOLE'
loading 'Colours'
gae/shaders/basic.xml: PHYSFS_openRead failed: gae/shaders/basic.xml
Error: The system cannot find the file specified.
XML Error in techs/mrise/factions/hyperion/units/amscrythe/amscrythe.xml:
Node "detector" doesn't have 1 children named "image"
Tree: detector
XML Error in techs/mrise/factions/hyperion/units/amscrythe/amscrythe.xml:
'detector' node doesn't have an attribute named 'type'
XML Error in techs/mrise/factions/hyperion/units/armatel/armatel.xml:
Node "detector" doesn't have 1 children named "image"
Tree: detector
XML Error in techs/mrise/factions/hyperion/units/armatel/armatel.xml:
'detector' node doesn't have an attribute named 'type'
I've made sure that I copied all the latest files and shaders/basic.xml is definitely there. Also what's up with the detectors?
-
Zoythrus had similar troubles loading. I recommended moving addons out of config dir and then logfiles, then when he put addons back it worked (with trying to run after each).
-
Deleting the widget_cfg.txt file from my config dir made it work again but then it stops working until I delete it again.
Edit: Nope this is not a fix, turns out when Glest closes it still has a process running and it wont run again until I task manager -> end process.
Edit: I've narrowed down what's wrong. When the game Crashes (isn't closed through it's menus or with alt+f4) it's process keeps running and the game wont start again until I manually end the process.
-
Edit: I've narrowed down what's wrong. When the game Crashes (isn't closed through it's menus or with alt+f4) it's process keeps running and the game wont start again until I manually end the process.
Hi Chuppa, good to see you got this narrowed down so far, and that it isn't a problem with the engine itself, as such ;)
Try disabling error reporting in windows if you haven't already, it keeps the crashed program open while preparing an error report (dumprep.exe) which is possibly the real problem.