project-navigation
Personal tools

Author Topic: ufoai-2.3-dev-win32-24629 CTD  (Read 2164 times)

Offline crazydog

  • Rookie
  • ***
  • Posts: 21
    • View Profile
ufoai-2.3-dev-win32-24629 CTD
« on: June 09, 2009, 12:13:05 pm »
Version is ufoai-2.3-dev-win32-24629
Windows xp pro sp3
directx mar2009
gforce 8800 gts 512
3gb ram
quad 6600
latest updates and drivers

new game
map is ufo crash
CTD
ufoconsole attached

[attachment deleted by admin]

Offline vedrit

  • Sergeant
  • *****
  • Posts: 438
    • View Profile
Re: ufoai-2.3-dev-win32-24629 CTD
« Reply #1 on: June 09, 2009, 10:15:32 pm »
Did this cause the game to crash?

Offline crazydog

  • Rookie
  • ***
  • Posts: 21
    • View Profile
Re: ufoai-2.3-dev-win32-24629 CTD
« Reply #2 on: June 09, 2009, 10:57:02 pm »
CTD=Crash to desktop.........

Offline vedrit

  • Sergeant
  • *****
  • Posts: 438
    • View Profile
Re: ufoai-2.3-dev-win32-24629 CTD
« Reply #3 on: June 09, 2009, 11:01:24 pm »
people and their acronyms.
I find it hard to believe that an invalid target would cause the game to crash

Offline geever

  • Project Coder
  • PHALANX Commander
  • ***
  • Posts: 2560
    • View Profile
Re: ufoai-2.3-dev-win32-24629 CTD
« Reply #4 on: June 09, 2009, 11:20:37 pm »
No if it's segfaulted for example, the ufoconsole.log is useless (it's truncated).

A problem is - for me - that CTD really means nothing, it can be a segfault (general protection failure), an assert, a Sys_Error(), or so...

Backtrace would be needed but for that people should be able to use debugger. We have an article about Debugging if you wanna try.

-geever