Author Topic: Debug log from OXC - how to obtain ?  (Read 4080 times)

Offline bladum

  • Colonel
  • ****
  • Posts: 213
  • Bladum
    • View Profile
Debug log from OXC - how to obtain ?
« on: December 01, 2014, 12:27:24 pm »
I am looking for debug log from oxc exe file.

Do we need to turn an option on / off ?
Or do we need to have debug build instead of release one ?

I would like to trobleshoot why oxc is closing without error when new mission is about to be create on geoscape. All combinations of missions / alien race are working in battlescape ok but during campaign oxc shots down without error.

EDIT

From what i was able to find when i remove one allien mission from save its working fine. The STR_ALIEN_RETALIATION one.

Code: [Select]
alienMissions:
  - type: STR_ALIEN_RESEARCH
    region: STR_EUROPE
    race: STR_SECTOID
    nextWave: 2
    nextUfoCounter: 1
    spawnCountdown: 10140
    liveUfos: 1
    uniqueID: 1
  - type: STR_ALIEN_TERROR
    region: STR_EUROPE
    race: STR_SECTOID
    nextWave: 2
    nextUfoCounter: 0
    spawnCountdown: 26250
    liveUfos: 1
    uniqueID: 2
  - type: STR_ALIEN_RETALIATION
    region: STR_EUROPE
    race: STR_SECTOID
    nextWave: 0
    nextUfoCounter: 0
    spawnCountdown: 4290
    liveUfos: 0
    uniqueID: 4

Tom
« Last Edit: December 01, 2014, 12:49:48 pm by bladum »

Offline volutar

  • Colonel
  • ****
  • Posts: 351
  • Vanilla digger & Quality assistant
    • View Profile
Re: Debug log from OXC - how to obtain ?
« Reply #1 on: December 01, 2014, 12:54:31 pm »
AFAIK you have to compile the game in debug mode and run with debugging environment to be able to catch crashes.
Currently everything logged is just some AI states (traceai: true), and yaml reader errors (logged by default).

There's no special debugging key which would allow to make any crashreports if they are not caught properly already.

Offline bladum

  • Colonel
  • ****
  • Posts: 213
  • Bladum
    • View Profile
Re: Debug log from OXC - how to obtain ?
« Reply #2 on: December 01, 2014, 02:14:43 pm »
Thanks,

Actually i try to debug src/Savegame/AlienMission.cpp

As based on saved that i have, any data that exist here force OXC to quit. Using latest build.

Save data:

Code: [Select]
  - type: STR_ALIEN_RETALIATION
    region: STR_EUROPE
    race: STR_SECTOID
    nextWave: 0
    nextUfoCounter: 0
    spawnCountdown: 1920
    liveUfos: 0
    uniqueID: 7

Retalation mission rule:

Code: [Select]
  - type: STR_ALIEN_RETALIATION
    points: 0
    raceWeights: {} #Special case, race comes from trigger UFO.
    waves:
      - ufo: STR_SMALL_SCOUT
        count: 1
        trajectory: P8
        timer: 3000
      - ufo: STR_MEDIUM_SCOUT
        count: 2
        trajectory: P8
        timer: 3000
      - ufo: STR_LARGE_SCOUT
        count: 3
        trajectory: P8
        timer: 3000
      - ufo: STR_BATTLESHIP
        count: 2
        trajectory: P8
        timer: 3000

Offline Warboy1982

  • Administrator
  • Commander
  • *****
  • Posts: 2333
  • Developer
    • View Profile
Re: Debug log from OXC - how to obtain ?
« Reply #3 on: December 02, 2014, 08:31:15 am »
make a bug report on the bug tracker, and attach the save.
openxcom.log contains the data that would be output to the log.

bug reports do not belong on the forum

Offline bladum

  • Colonel
  • ****
  • Posts: 213
  • Bladum
    • View Profile
Re: Debug log from OXC - how to obtain ?
« Reply #4 on: December 06, 2014, 03:18:14 pm »
root cause is that STR_BATTLESHIP is hardcoded for retaliation mission