[DahBlount]

When I attempted to play the second mission, I CTDed, switched to debug build and got the following.

Code: [Select]

For ship 'TC-TRI', detail level
mismatch. Table has 4,
POF has 3.
ntdll.dll! ZwWaitForSingleObject + 12 bytes
KERNELBASE.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
fs2_open_3_7_1_SSE-DEBUG-20131105_r10010.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 14 bytes
ntdll.dll! RtlInitializeExceptionChain + 133 bytes
ntdll.dll! RtlInitializeExceptionChain + 88 bytes

Log is included.

[attachment deleted by an evil time traveler]

[MatthTheGeek]

This is not a CTD. Press Cancel.

This is a warning coming from the MVPs that is raised with recent builds, and should be fixed with the next version of the MVPs. It has nothing to do with BP.

[DahBlount]

Okay. I'll just wait on that then.

[MatthTheGeek]

On the MVPs ? I'd suggest against that, we have no indication as to when this next release will happen. Just ignore the warning.

[Kolgena]

That's a cargo container that never appears in all of BP. You should be fine to play without any "fixes" if you just press cancel and alt tab back in.

[MatthTheGeek]

That's a cargo container that never appears in all of BP.

Wrong.

Her Finest Hour and Everything is Permitted have a bunch of those. Might or might not have easter egg contents, too 

[DahBlount]

Wait, now I'm confused. I was able to load the mission and get to the briefing screen, but when I click on commit to mission, I crash. What's up with that?
Tested with r10010 and r10014.

[niffiwan]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

[DahBlount]

Here you go.

[attachment deleted by an evil time traveler]

[niffiwan]

hmmm... so it crashes with both release and debug executables?

Also, you do seem to have a lot of loose files in your FSO directories.

Code: [Select]

Searching root 'C:\Games\Freespace2\blueplanet2\' ... 6 files
...
Searching root 'C:\Games\Freespace2\blueplanet\' ... 2 files
...
Searching root 'C:\Games\Freespace2\mediavps_3612\' ... 77 files
...
Searching root 'C:\Games\Freespace2\' ... 3581 files

Especially in 'C:\Games\Freespace2\data\', I've only got 14 loose files there.  Maybe have a look through those 3581 files and move them out of your FSO dirs if you don't know what they're for?

[DahBlount]

Yeah, lots of loose files. Managed to reduce the number of files in the data folder to around 700, around 680 of them are cache files. Removed files from the MVP folder, leaving 18 files. The files in the BP folders are cache files.
After removal, attempted to play with both release and debug builds or r10010 and r10014 but the game still crashed.

[niffiwan]

well, that's annoying. 

hmm.

What about grabbing another stack trace?

[DahBlount]

I will attempt to, for some reason it keeps on saying "Build failed" in the bottom left corner and pressing F5 does not work.
I already rechecked SVN and I am stuck as to what the problem is.\

Edit: Okay I got a successful build to work finally.
Edit2: Was able to get a stack trace but my internet crapped out on me. Posting from my phone, will have the stack trace to you tomorrow.

[DahBlount]

Here you go. http://pastebin.com/yZ9PQTQV

[MachManX]

I too have the same crash.  Previously my game crashed on the first mission but the new build fixed the issue.  Now I'm crashing on this second mission using the same, new build.  I'll post a crash log later.

[attachment deleted by an evil time traveler]

[The E]

Will be fixed in the next build.

[DahBlount]

Thanks!

[Lykurgos88]

I am getting CTD in the exact same mission. Here is the log file.

I am using the latest BP.patch file and Yarn's Adaptable HUD (BP version) build. Because I really wanted my HUD elements to scale correctly.

[attachment deleted by an evil time traveler]

[The E]

Whatever you are using, you are using a build based on a revision that does not have the fixes in the latest BP builds.

Let me be absolutely clear about this: The only builds I support for BP are the normal nightlies (with compatibility pack), and the ones I make myself. You are on your own when using anything else.

[Yarn]

I am using the latest BP.patch file and Yarn's Adaptable HUD (BP version) build. Because I really wanted my HUD elements to scale correctly.

There's little reason to use my builds to play Blue Planet 2 because BP2 includes its own HUD, including a widescreen one, and it's not made with my builds in mind (not that it should be). Could you try the latest BP build here?

BP.patch is useful only for making your own builds; just having it in your FS2 folder or anywhere else has absolutely no effect on how the game runs.