[NJSP 3002]

I played blue planet its awsome but all of the sudden i get this each time i run this.

Warning: Weapon explosion 'MS_Impact' does not have an LOD0 anim!
File: Weapons.cpp
Line: 1241


Call stack:
------------------------------------------------------------------
    parse_weapon()    parse_weaponstbl()    parse_modular_table()    weapon_init()    game_init()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 770d3677()
    ntdll.dll 777a9d72()
    ntdll.dll 777a9d45()
------------------------------------------------------------------
Could not load in main hall mask 'MainScreen-M'!

(This error most likely means that you are missing required 640x480 interface art.)
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12r_INF_SSE2.exe! <no symbol>
fs2_open_3_6_12r_INF_SSE2.exe! <no symbol>

[Dilmah G]

What the? The E'll come by and hopefully sort this out better than I can, but that bracketed sentence. Dude, are you playing in 640x480?

[NJSP 3002]

no im not  running 640 x 480 it says iam but dont know why

[General Battuta]

Debug log please. We'll have this fixed in an instant if you can post one for us.

[Jeff Vader]

no im not  running 640 x 480 it says iam but dont know why

What says you are? The Launcher? If so, perchance you'd like to change it to something that is at least 1024x768.

And yes, your fs2_open.log could not hurt in any way.

[TopAce]

Is that resolution even supported? I can't run FSO in 640x480 anymore. It's still selectable from the Launcher, but it runs the game in 1024x768 nevertheless.

[Dragon]

To clarify: display resolution doesn't equal resolution FSO is running on.
You have to set the resolution in launcher.

[-Norbert-]

I guess it can't hurt to go through the basic stuff just in case.
Use a 3.6.10 Infernobuild or newer (3.6.12 RC2 is recommended).
Make sure you don't have the (old) blueplanet.vp file in your mod folder.
Make sure the MediaVP folder is called "MediaVPs" (or alternatively change the mod.ini to point to the correct folder).
If you enabled post-processing in the launcher, make sure you also have the neccesary files for pp (one table and two effect files).

Btw.: Were did the troubleshoot sticky go?

[Aardwolf]

@JeffVader:

(This error most likely means that you are missing required 640x480 interface art.)

And FFS, it says "Warning". That's not the same as an error. Why don't you just click the ignore button? Actually, it looks like there's two unrelated issues there... First is says "Warning: Weapon explosion 'MS_Impact' does not have an LOD0 anim!" and then it says "Could not load in main hall mask 'MainScreen-M'!"... I'm confused now.

[FreeSpaceFreak]

NJSP 3002: Look here and follow exactly the steps listed there.

[Jeff Vader]

Actually, it looks like there's two unrelated issues there... First is says "Warning: Weapon explosion 'MS_Impact' does not have an LOD0 anim!" and then it says "Could not load in main hall mask 'MainScreen-M'!"... I'm confused now.

Yes. Two entirely separate issues. The "Could not load in main hall mask..." is an error, caused by using a low resolution when there is no 640x480 interface art to be found. The "Weapon explosion..." bit is a warning and could be skipped. Though I thought Blue Planet should not be spilling out warnings just like that. Perchance a faulty setup?

[Fury]

Actually MS_Impact is mediavps effect, hence the error is also caused by mediavps. He doesn't have his mediavps set up correctly or they're outdated. Or he's otherwise managed to mess up mods.

The error about main hall mask is the only valid error in there, which is indeed caused by BP:AoA DC not having properly set up low-res interface masks. Mind you. tihis has been fixed months ago but we're waiting for final pieces to release both update to BP: AoA as well as BP2: WiH R1.

[Aardwolf]

So why did it display both the warning and the error in the same thing? Or did he just mispost it?

[The E]

No, it's probably just a setup issue. His mediavps are either not installed correctly, or corrupted.