Error logs

Tech support for HISTORY™ Great Battles Medieval

Moderator: Slitherine Core

Post Reply
comradep
Staff Sergeant - StuG IIIF
Staff Sergeant - StuG IIIF
Posts: 253
Joined: Wed Oct 18, 2006 7:47 pm

Error logs

Post by comradep » Fri Oct 16, 2009 4:07 pm

My error log thus far:

UNKNOWN TAGS IN: Config\system.txt
Unknown Tag: TURNTICKS
Unknown Tag: HITBONUS
END: Config\system.txt
Creating Device.....
MonkeyInitStart
MIS: Found DD
MIS: IsHW
MIS: SetCoop
MIS: Setting Disp Mode
MIS: Done Init 3D Device
MIS: SDRS
MIS: Tex Enum
MIS: Init Decal Render
WARNING: FAILED to load sample data\sounds\Clang.wav (4)
WARNING: FAILED to load sample data\sounds\empty.wav (59)
INITIAL LOAD 12516
Time to Load: 26046
QUEST WARNINGS:
QUEST: Variable (EscortLoot) is a Result without being tested
QUEST: Variable (Tourney) is a Prereq without being altered
QUEST: Variable ($$ENDED_CAMPAIGN) is unused
QUEST: Variable (ORDERSTAR) is unused

CHAIN: ENGLISHCAMPAIGN_0 length = 16
QUEST WARNINGS:
QUEST: Variable (EscortLoot) is a Result without being tested
QUEST: Variable (Tourney) is a Prereq without being altered
QUEST: Variable ($$ENDED_CAMPAIGN) is unused
QUEST: Variable (ORDERSTAR) is unused

CHAIN: ENGLISHCAMPAIGN_0 length = 16
QUEST WARNINGS:
QUEST: Variable (EscortLoot) is a Result without being tested
QUEST: Variable (Tourney) is a Prereq without being altered
QUEST: Variable ($$ENDED_CAMPAIGN) is unused
QUEST: Variable (ORDERSTAR) is unused

CHAIN: ENGLISHCAMPAIGN_0 length = 16
QUEST WARNINGS:
QUEST: Variable (EscortLoot) is a Result without being tested
QUEST: Variable (Tourney) is a Prereq without being altered
QUEST: Variable ($$ENDED_CAMPAIGN) is unused
QUEST: Variable (ORDERSTAR) is unused

CHAIN: ENGLISHCAMPAIGN_0 length = 16
Still elements in Fonts
KERNEL MEMORY CHECKING IS **OFF**


The game crashed as I was scrolling the map to the east, possibly due to something on the background, I can't think of any good reason as I wasn't using the mouse or abilities.

pipfromslitherine
Site Admin
Site Admin
Posts: 9106
Joined: Wed Mar 23, 2005 10:35 pm

Post by pipfromslitherine » Fri Oct 16, 2009 4:29 pm

That error log shows a clean shutdown, so perhaps you ran the game again after the crash?

Cheers

Pip

comradep
Staff Sergeant - StuG IIIF
Staff Sergeant - StuG IIIF
Posts: 253
Joined: Wed Oct 18, 2006 7:47 pm

Post by comradep » Fri Oct 16, 2009 4:57 pm

Even if the game shuts down normally, the error log is updated?

Wouldn't it make more sense if the error log would...well...log errors?

As I have only that error log in the folder indicated by Iain, I'm afraid I can't give you the error log from the crash.

IainMcNeil
Site Admin
Site Admin
Posts: 13524
Joined: Fri Apr 01, 2005 10:19 am

Post by IainMcNeil » Fri Oct 16, 2009 5:13 pm

The problem is the log doesnt know if there will an error in advance so it has to log it as it goes :)

comradep
Staff Sergeant - StuG IIIF
Staff Sergeant - StuG IIIF
Posts: 253
Joined: Wed Oct 18, 2006 7:47 pm

Post by comradep » Fri Oct 16, 2009 6:00 pm

I understand that much, but why does the error log update itself even if there's no error?

In most games with such a feature, an error log is created when an error occurs and it will sit in some folder until I do something with it, it won't be automatically overwritten when no error occurs. It does kind of remove the usefulness of the utility if it's constantly updated whenever I shut down the program.

IainMcNeil
Site Admin
Site Admin
Posts: 13524
Joined: Fri Apr 01, 2005 10:19 am

Post by IainMcNeil » Fri Oct 16, 2009 9:26 pm

The error log is output before the error occurs. The point is the code has crashed by the time the error happens and it is too late to do anything as the code has stopped working. The log reports everything except the actual error so you see the last thing reported before it crashed. If we could log the error we would already know what it was and fix it :)

pipfromslitherine
Site Admin
Site Admin
Posts: 9106
Joined: Wed Mar 23, 2005 10:35 pm

Post by pipfromslitherine » Fri Oct 16, 2009 10:58 pm

What you're talking about are usually crash dumps, which is something that is useful, but somewhat different to the error log, which logs pretty much everything of interest, as it might be useful later.

The log is flushed as it is written because a crash could easily kill off the C runtime or the other elements of the process needed to write out the file.

If you do see another crash, please grab the error log and let us take a look and we can hopefully work out why.

Cheers

Pip

Post Reply

Return to “HISTORY™ Great Battles Medieval : Tech Support”