(semi-resolved) Crash when ejecting ammo, and trying to rejoin - floating ammo icon crashes game?

sono · Post by **sono** » Wed Aug 12, 2009 2:17 pm

Setup

Relatively fresh Allegiance Beta install. No settings have changed.

Description

Game causes an access violation when ejecting cargo. The ejection sound is being played, then the game crashes to desktop.

Reproduced how

Launched Giga Heavy Scout, immediately after launch ejected 1 rack of ammo by pressing ctrl-s.

Log

8/12/2009 2:11:29 PM: Mission Initialize id=0 this=d26a008 now=11302878

8/12/2009 2:11:34 PM: 7927012:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:34 PM: MAX IMBALANCE VALUE =
8/12/2009 2:11:34 PM: 220552480:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:34 PM: 32767
8/12/2009 2:11:34 PM: 7880556:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:34 PM:

8/12/2009 2:11:37 PM: 1237712:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:37 PM: Station initialize 0

8/12/2009 2:11:37 PM: 1237712:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:37 PM: Station initialize 7

8/12/2009 2:11:37 PM: 1237712:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:37 PM: Station initialize 6

8/12/2009 2:11:37 PM: 403513528:OUTPUT_DEBUG_STRING_EVENT
8/12/2009 2:11:37 PM: assertion failed: '!(bError && !pfile->IsValid() && m_psite)' (..\src\engine\modeler.cpp:2469)

8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXCEPTION_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXCEPTION_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_THREAD_DEBUG_EVENT
8/12/2009 2:11:37 PM: EXCEPTION_ACCESS_VIOLATION:EXIT_PROCESS_DEBUG_EVENT
8/12/2009 2:11:37 PM: Allegiance exited with code: EXCEPTION_ACCESS_VIOLATION
8/12/2009 2:11:37 PM: Creating Crashfile

sono · Post by **sono** » Wed Aug 12, 2009 2:37 pm

Cause:

Missing ammo_iconbmp.mdl, fuel_iconbmp.mdl

My theory, lol:

Those files are missing after downloading R4 release Allegiance and updating into beta mode if you have never run autoupdate on the release download.

Workaround: I copied the files from R4, which stopped the crashes. But no icons are displayed ingame now.

Post by **pkk** » Wed Aug 12, 2009 3:55 pm

sono wrote:QUOTE (sono @ Aug 12 2009, 04:37 PM) Cause:

Missing ammo_iconbmp.mdl, fuel_iconbmp.mdl

Wrong, the files were broken. R4 can handle such broken files (doesn't display them), while R5 crashs.

sono · Post by **sono** » Wed Aug 12, 2009 4:17 pm

That might be true for you, for me they were just missing.

RONG U!

Anyway, as i said, the R4 files don't crash, but no icons are displayed.

Cortex · Post by **Cortex** » Wed Aug 12, 2009 4:47 pm

pkk wrote:QUOTE (pkk @ Aug 12 2009, 05:55 PM) Wrong, the files were broken. R4 can handle such broken files (doesn't display them), while R5 crashs.

<untested assumption>To avoid confusion: it's probably not R4 vs. R5 that's causing the issues here but rather debug vs. retail builds. Retail builds ignore the broken files, while debug builds don't.

However, you never get to run R4 debug builds. You need ASGS to connect to the lobby hosting the R4 servers, and ASGS doesn't let you through with debug builds (or rather: any build that isn't the official build -- and the official build is a retail build).

R5 is sometimes tested with debug builds (the dev lobby isn't ASGS restricted).

-- Cort

Adam4 · Post by **Adam4** » Wed Aug 12, 2009 4:53 pm

QUOTE !(bError && !pfile->IsValid() && m_psite)[/quote]

Should have told you everything you needed to know. Invalid/non-existing file.

Cortex · Post by **Cortex** » Wed Aug 12, 2009 6:08 pm

Adam4 wrote:QUOTE (Adam4 @ Aug 12 2009, 06:53 PM) QUOTE !(bError && !pfile->IsValid() && m_psite)

Should have told you everything you needed to know. Invalid/non-existing file.
[/quote]
ROFL, I think that's asking a bit too much from a simple user. It took me three minutes myself to decode that (particularly because it's negated once again in the assertion method) and I'm fairly used to reading complex boolean expressions.

Plus, I think he reported it to get it fixed, not just to ask what causes it.

-- Cort

sono · Post by **sono** » Wed Aug 12, 2009 11:23 pm

Adam4 wrote:QUOTE (Adam4 @ Aug 12 2009, 09:53 AM) Should have told you everything you needed to know. Invalid/non-existing file.

Adam,

code much?

To elaborate on this, because i am growing a bit tired of the attitude around here

That's one line of code out of several thousand. It tells me this: If a couple of values that seem to be related to files (an error flag, possibly related to a previous fopen, a validation flag, possibly related to some.. validation, and an undescript modifier) are set in a certain way, the program will stop.

Which files, you ask? Was it not found, or was it invalid? What am i supposed to do about it? Is this an issue, or is something wrong on my end?

The important tip came from madp in the beta server: to look for those files, for they are the relevant ones for ammo/fuel icons.

Your post, on the contrary, tells us only one thing: Adam is a jerk! Woot. ~yt

Adam4 · Post by **Adam4** » Thu Aug 13, 2009 12:24 am

In response to your question, no. I have the coding experience of the average Joe. I would have thought it logical that a user could go through the log, spot the "file" and "valid". Then, combine this with either filemon (for the experienced user) or calculated guesses based on the situation (crash after an ammo ejection), and you have a logical conclusion.

I'll refrain from lowering myself to the level of throwing insults around, but would recommend that you don't insult anyone who just happens to post, when you don't know the circumstances.

FYI, I spent a good 15 minutes going through the problem with Cortex (as a result of this thread I might add), whereby we established that it was limited to Debug builds, and that the appropriate (fixed) files, need pushing via AU.

Since this problem has now been confirmed as a core issue, the appropriate place for discussions regarding fixing it belong in the Core Development Zone. Therefore I'm now going to lock this thread.