[Reloaded]

When I had Win xp 32 bits and played this game with all its campaigns including BP and WiH everything was fine but now that I try to play it in Win 7 Ultimate 64 bits it keeps sending me this error and kicks itself out.

Any ideas on where shall I start?

By the way, I already have everything on FS2 directory

Attached you'll find the screenshot I have:

Reloaded

[attachment deleted by an evil time traveler]

[MatthTheGeek]

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

For info, I also have a 7ulti x64 and it works more than fine, so that's not your issue.

[Reloaded]

Thanks!
I'll post it tomorrow morning.
Gotta hit the sack

[-Norbert-]

I have the same OS and my FS2 runs fine, so the chances are good that the tech-experts will be able to help you out.

[Reloaded]

Ok, I managed to start the game. One of these errors was that I forgot to use a single pilot per campaign. Having said that I've been granted access to the game. Now, When the game loads the first mission on BP1, right before the briefing starts it gives me this error:

Code: [Select]

Could not load in 2_CommandBrief-mb!
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
USER32.dll! PeekMessageA + 360 bytes
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
fs2_open_3_7_1_SSE2_BP.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes


[niffiwan]

About that log?

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

[Reloaded]

Ok. Here's my fs2_open.log file.

By the way, I'ts getting kind of strange because, apparently, now I'm able to play missions as normal, but every time the game loads the next one It sends me some errors, I click ok and I return to the game. Now this is the first part. The second part of the mistery is when I close the program and start it again. That's when I realize that my mission records are not being kept by the game forcing me to start from the very beginning of BP1.
Sorry, I'm absolutely not  an expert on this. 

[attachment deleted by an evil time traveler]

[Yarn]

Did you actually install the MediaVPs? If you did, then make sure that they're in a folder called mediavps_3612 (and it must be called "mediavps_3612"). You absolutely must have the MediaVPs installed there to play Blue Planet (as well as many other mods).

Code: [Select]

Found root pack 'D:\Games\FreeSpace2\data\music\MV_Music.vp' with a checksum of 0xb3e21469
Delete this.

Code: [Select]

Initializing OpenGL graphics device at 1280x720 with 16-bit color...
I strongly recommend playing with 32-bit color.

[niffiwan]

Just one addition to everything that Yarn said, if you have a CD in F:, you should probably remove it.

[Reloaded]

I JUST CAN'T BELIEVE IT!! *hides face behind both hands and then laughs painfully*
THAT was the error all the time! (mediavps missing)
Now all errors are gone since I've placed the .vp files in that folder, not a single error nor warning pops up and all the beauty of BP has been restored to what it was supposed to be.
My gosh, I can't believe this was so simple to solve 

Sorry for all this, guys. But thank you VERY much for all your help. Now everything is fine.

[AdmiralRalwood]

One of these errors was that I forgot to use a single pilot per campaign.

You don't have to use a single pilot per campaign since 3.7.0. FSO will complain that the currently-selected campaign isn't present if you switch mods, but it still remembers your progress for them all separately.

[MachManX]

You don't have to use a single pilot per campaign since 3.7.0. FSO will complain that the currently-selected campaign isn't present if you switch mods, but it still remembers your progress for them all separately.

PRAISE the coders for this feature!