Re: Error: Could not load in 2_CommandBrief-mb!

-mod bpcomplete,MediaVPs_2014,bpcomplete,MediaVPs_2014Get the 0.12 RC2 version of wxLauncher here, which will work better with 3.8 (this specific bug has been fixed in recent Nightly Builds, but a newer wxLauncher will work better anyway).

Now, for the actual error you got: your installation of the 2014 MediaVPs is incomplete.

Found root pack 'C:\STEAM\steamapps\common\Freespace 2\MediaVPs_2014\MV_Assets.vp' with a checksum of 0x23b7997eFound root pack 'C:\STEAM\steamapps\common\Freespace 2\MediaVPs_2014\MV_Effects.vp' with a checksum of 0x6fbd3357At the very minimum, you need MV_Root.vp (which contains the interface file that the error is referring to). As you're using a 64-bit build of FSO and a GTX 950, you may also want MV_Advanced.vp and MV_A-Glows.vp, which contain larger textures (and complement the BP advanced texture VPs you already have installed). MV_CB_ANI_1.vp and MV_CB_ANI_2.vp contain higher-resolution versions of the original command briefing animations, which might come in handy if you ever want to play FreeSpace Blue. MV_Music.vp contains higher-quality versions of the original FS2 audio tracks; I can't remember if any of them are used in BP anywhere, but again, they'll come in handy in FreeSpace Blue.

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".(the very next day)<MageKing17> this ****ing code did it to me again<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."<MageKing17> **** ME<MageKing17> THE REASON IS PEOPLE ARE STUPID<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"(...)<MageKing17> so<MageKing17> more than two hours<MageKing17> but once again we have reached the inevitable conclusion<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

Re: Error: Could not load in 2_CommandBrief-mb!

Thanks for the quick reply. I remember having some errors during my first attempt at fs open installation. It seems that the missing files you are referring to are the files that I did not download when I decided to go for a minimal install to avoid the errors.

I will re-download and report back.

Thanks.

Edit: I can't find the file : MV_Root.vp in the fs open custom install menu.

Re: Error: Could not load in 2_CommandBrief-mb!

FreeSpace Open 3.7.4 Windows Standard: The hash value for 'scptrackir.dll' did not agree with the expected value. This could indicate a corrupted download or a problem with the mod. If this problem persists over multiple attempts, contact the mod author for assistance. The file has been deleted.2014 FSU MediaVPs: The file 'MV_Root.7z' could not be downloaded.MV_Assets: Skipped because parent mod was not installed.MV_Effects: Skipped because parent mod was not installed.MV_Music: Skipped because parent mod was not installed.MV_Advanced: Skipped because parent mod was not installed.MV_A-Glows: Skipped because parent mod was not installed.MV_RadarIcons: Skipped because parent mod was not installed.MV_CB_ANI_1: Skipped because parent mod was not installed.MV_CB_ANI_2: Skipped because parent mod was not installed.FreeSpace Open 3.7.4 Windows SSE: The hash value for 'scptrackir.dll' did not agree with the expected value. This could indicate a corrupted download or a problem with the mod. If this problem persists over multiple attempts, contact the mod author for assistance. The file has been deleted.

Re: Error: Could not load in 2_CommandBrief-mb!

Does this link work for you? It's the exact same URL the installer tries to download from, so if it works, then either the installer's problem was a temporary failure, or something else is going horribly wrong.

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".(the very next day)<MageKing17> this ****ing code did it to me again<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."<MageKing17> **** ME<MageKing17> THE REASON IS PEOPLE ARE STUPID<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"(...)<MageKing17> so<MageKing17> more than two hours<MageKing17> but once again we have reached the inevitable conclusion<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".(the very next day)<MageKing17> this ****ing code did it to me again<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."<MageKing17> **** ME<MageKing17> THE REASON IS PEOPLE ARE STUPID<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"(...)<MageKing17> so<MageKing17> more than two hours<MageKing17> but once again we have reached the inevitable conclusion<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

Re: Error: Could not load in 2_CommandBrief-mb!

But unless you manually copied that MV_Root.vp over to the 2014 MediaVPs' folder (which you absolutely should not do), there's no way for FSO to find it, because BP's mod.ini doesn't reference the 3.6.12 MediaVPs, so wxLauncher won't put them into the -mod command-line option, so the same interface file should still be missing... so how is it working?

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. <MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".(the very next day)<MageKing17> this ****ing code did it to me again<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."<MageKing17> **** ME<MageKing17> THE REASON IS PEOPLE ARE STUPID<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"(...)<MageKing17> so<MageKing17> more than two hours<MageKing17> but once again we have reached the inevitable conclusion<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.