[dkharrat]

Hello,

I was planning on working for the demo project tonight, so I downloaded fs2_open from CVS, and it complied perfectly well (with a few warnings), but when running the game, it crashes the moment I put the mouse on the door (for entering the campaign). Here is the callstack result:

Assert: bm_bitmaps[n].handle == bitmap_id
File: e:\other projects\fs2\fs2_open3.4\code\bmpman\bmpman.cpp
Line: 2273

Call stack:
------------------------------------------------------------------
    fs2_open_debug.exe 0054e76a()
    fs2_open_debug.exe 00628df9()
    fs2_open_debug.exe 00628fa1()
    fs2_open_debug.exe 0062f156()
    fs2_open_debug.exe 006319ab()
    fs2_open_debug.exe 00419b39()
    fs2_open_debug.exe 0058522f()
    fs2_open_debug.exe 0040bffb()
    fs2_open_debug.exe 004fb373()
    fs2_open_debug.exe 0040d254()
    fs2_open_debug.exe 0040d32e()
    fs2_open_debug.exe 006a4bc4()
    kernel32.dll 77e814c7()
------------------------------------------------------------------

It also crashes at the same point (the assert line) when creating new pilots.

I tried running the compiled debug version available at the FS2_OPEN 3.4 Thread and it worked fine with no problems. I wonder why my compiled version doesn't work. Any clues?

[WMCoolmon]

1) What are you compiling with?

2) Could you post the warnings you got while compiling it?

[dkharrat]

I'm compling using Visual Studio .NET 7.0

I don't think the warnings are an issue. There's one like: "inreferenced variable".

[dkharrat]

I just tried an old version of fs2_open I had (v3.1) and it compiled perfectly fine (with the same warnings as in v3.4). Above that, it didn't crash at all and worked smoothly.

So there's probably something wrong with v3.4  Could it probably be the decals causing it?????

[WMCoolmon]

It sounds like something was added to the CVS that wasn't in the 3.4 release...I think it's tagged somehow, but I don't know how. I'll try firing up WinCVS and see if I can figure out how.

[WMCoolmon]

Update: It appears version 3.4 wasn't tagged (Or perhaps I'm missing something?). Your best bet would probably be figuring out which files have changed since the 3.4 build date.

[Goober5000]

:doh: that would be my fault.  I don't know how to tag versions.

dkharrat, did you try running the 3.4 that was posted, as opposed to compiling it yourself?

The debug version was built a week after the release version, so it's not identical.  If you get errors in the posted release as opposed to the debug, it might have been an error that got fixed.

It might also be something with .NET that's different from VC++ 6.

Stuff to double-check:
that you made a new fs2_open pilot
that you have the warp.pof file in your models directory

[Inquisitor]

CRAP.

That's actually my fault.

I know when the last chanegs went in, I'll tag a 3.4 this afternoon if I can sneak away from my desk.

[dkharrat]

dkharrat, did you try running the 3.4 that was posted, as opposed to compiling it yourself?

Goober5000: Yes in fact, I tried both versions, and both of them work perfectly fine. I don't think it's VS.NET because I've compiled a previous version of fs2_open (v3.1) and it worked fine.

One thing I'd like to know, what's that tagged business? How do I figure out which ones are tagged and which are not? Once they get tagged, what do I do to get the compilation to work?

And also, yes, I've tried making a new pilot, but the moment it completes, it crashes at the same line (as the one in the first post).

warp.pof is also copied into my models directoy.

[Goober5000]

Well, let's see if I understand correctly...

both the 3.4 release and the 3.4 debug EXEs that were posted in the thread work nicely

3.1 compiles on your machine and runs
3.4 compiles on your machine and does not run

So it sounds like your machine doesn't like compiling something that was added between 3.1 and 3.4.  That's a lot of possibilities...

I don't suppose you have access to a VC++ compiler?

[dkharrat]

Were there any changes to the code after the release of the compiled versions in the post? Probably, something changed that is causing it not to work.

[Inquisitor]

Yeah, there have been a few committs, this should get to bugzilla at some point if it hasn't already...

[Goober5000]

Yes - a bunch of changes, mostly by me.  Possibly what might be causing the error is the wing insignia mod.  I only added that within the last day or two, though - try doing a build of files earlier than Monday, and see if that makes any difference.

[dkharrat]

Is there a specific command in CVS to get certain files (e.g according to date modified) ? It would be annoying to get files individually

[Goober5000]

I'm not sure.  Inquisitor prolly knows.

On a side note, Inquisitor, I just noticed that freespace.cpp has a <<<<<< CVS thing in the comments left from a conflict way back from version 2.9 and 2.5.  I did a search, and that's the only file that currently has a CVS conflict.  Can you get someone to check it out and see if it's okay?  It looked like it had something to do with the DX8 branch.

[Inquisitor]

yeha, in wincvs, there is a tab for tag/version, it's like "get version before date xxX" I'll have to look and see exactly.

You have to be careful with that and "clear" the date flags before you try to update or sommitt those files, it's another option on that checkout dialog, I think it's in another thread here about CVS.

DX stuff, eh? shouldn't be any unless you grabbed the DX branch... I'll look at it.