Aces High Bulletin Board

Help and Support Forums => Aces High Bug Reports => Topic started by: Roscoroo on June 30, 2006, 03:16:09 PM

Title: the Mystery CTD bug
Post by: Roscoroo on June 30, 2006, 03:16:09 PM

I think ive found it (or the cause of one)

1st instance of ctd  is while in god mode ...
If I am putting input on my joystick and i hit esc key to toggle the board up or down ... thats an instant ctd

2nd instance was while flying a 262 ,,, I had destroy objects up on the board and i hit the esc key while i had joystick input at the same time ,,was another ctd

now if i didnt put any joystick input in I could hit the esc key just fine to toggle the board up or down ...

Note; I was in the SEA on the new japan1 terrain at the time .

Title: the Mystery CTD bug
Post by: rogerdee on July 03, 2006, 09:18:06 AM

same thing happend to m  hit escapebutton to bring up map while turing with oystick. instat ctd

Title: the Mystery CTD bug
Post by: Kev367th on July 04, 2006, 06:36:48 PM

Since last patch getting A LOT of CTD's .

Message is -

The instruction at 0x0044c3ea (varies) referenced memory at 0x00000000 (constant), The memory could not be read.

Title: the Mystery CTD bug
Post by: Roscoroo on July 09, 2006, 12:00:09 PM

Theres a nice no warning ctd in the MA still ... seams to happen when working the views and stick heavy in a furball. :(

Title: Aces High Crash 10.09.2006
Post by: aqhawasi on October 09, 2006, 08:54:55 AM

Crashed three times today:

Application popup: Aces High II: aceshigh.exe - Application Error : The instruction at "0x004b82b0" referenced memory at "0x00000000". The memory could not be "read".

Apparently, I am not alone on this one.  Any ideas?

Title: the Mystery CTD bug
Post by: 1epic1 on October 10, 2006, 03:46:40 AM

Title: the Mystery CTD bug
Post by: straffo on October 10, 2006, 04:27:17 AM

mppppfff the deadly null pointer :D

Title: the Mystery CTD bug
Post by: Krusty on October 10, 2006, 10:03:56 AM

perk the null pointer!

Title: not crashed for a day
Post by: aqhawasi on October 10, 2006, 06:24:35 PM

Deleted the settings folder (had to copy my joystick jsm files back though), and changed my video settings to pre-load objects in system memory.  Also hit "Restore Defaults", which set my video buffer size (or something like that) to 1024.  Also updated my video card drivers to the latest nVidia release.  Game hasn't crashed after long hours of playing.  We'll see.  Thanks for the null pointer.  I also definitely need to spend less time on this game... its starting to feel like a second job, but one I like.