Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: -Norbert- on July 02, 2009, 11:28:36 am

Title: Apollo and Vaklyrie problems
Post by: -Norbert- on July 02, 2009, 11:28:36 am
I have the following problem.
In FS_Port with MediaVPs everything is showing up fine in the latest version, only the Apollo and the Valkyrie aren't.

Now the strange thing is, if I play Silent Threat Reborn with MediaVPs I get shiny new models for both fighters.
Is there something wrong with my install?

And if not, which files do I have to get out of the STR VPs and over into my FS_Port data-folder to get the new models and textures there too?

I attached a picture made of two screenshots out of the techroom. Left is the FS_Port+MediaVP Valk and to the right the Silent Threat Reborn+MediaVP one.

[attachment deleted by MSC
Title: Re: Apollo and Vaklyrie problems
Post by: General Battuta on July 02, 2009, 11:30:19 am
Are you using the FSPort MediaVPs and are they mentioned in your FSPort mod.ini?

That's probably the issue.
Title: Re: Apollo and Vaklyrie problems
Post by: Jeff Vader on July 02, 2009, 11:41:02 am
I'd do it like this:
- select fsport-mediavps as mod
- make sure that \fsport-mediavps\ has a mod.ini, which has the "secondarylist" line pointing to "fsport,mediavps".
- ????
- PROFIT
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 02, 2009, 12:54:39 pm
Perhaps it helps: I have it as following on my harddrive:
All the vp files with exception of the mv_fsport.vp are in the FS_Port folder.
I also have a 2nd folder called FS_Port_Mediavp which contains the mv_fsport and a mod.ini in which FS_Port is in primarylist and MediaVP secondarylist.
That 2nd folder is the one I select as Mod in the Launcher.

When I do it like Jeff Vader suggested, with both FS_Port and MediaVPs in secondarylist, I get the new model for Valkyrie and Apollo, but without glowmaps and cockpits.
And all the other ships look like vanilla FS2 models.
Title: Re: Apollo and Vaklyrie problems
Post by: Cobra on July 02, 2009, 03:56:39 pm
Make sure that your folders are named as they are in your mod.ini. ;)
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 03, 2009, 04:30:35 am
They are. To make sure I even copy/pasted the names from the folders to the mod.ini
Title: Re: Apollo and Vaklyrie problems
Post by: Jeff Vader on July 03, 2009, 04:40:10 am
fs2_open.log?
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 03, 2009, 08:02:57 am
Untill recently I played with the Nightly Build 4989, but I just tried it with 3610 RC 3, without any change.
The Log is from the 3610 RC3 debug exe.

[attachment deleted by MSC
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 03, 2009, 08:05:48 am
Lightspeed's nebula pack is included in the mvps, and not needed anymore.
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 03, 2009, 08:29:10 am
I just found a way to make the two fighters work right.... guess it's kind of a workaround.

I created a new folder that only has the following mod.ini in it:

Code: [Select]
[launcher]
modname      = FS Port + Media VP Experiment;
image255x112 = ;
infotext     = ;
website      = ;
forum        = ;

[multimod]
primarylist = FS_Port_Mediavp;
secondarylist = FS_Port,MediaVP3610;

I have no idea why this works (or why it didn't work before), but at least I get the shiny new versions now....
Title: Re: Apollo and Vaklyrie problems
Post by: Jeff Vader on July 03, 2009, 09:26:59 am
You'll notice, that
Code: [Select]
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\FS1OGGcutscenepack.vp' with a checksum of 0x6b9172f7
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\fsport-missions.vp' with a checksum of 0x0ae28029
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\fsport3_1_1.vp' with a checksum of 0x1d2c40f2
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\sparky_hi_fs1.vp' with a checksum of 0x367ba125
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\stu_fs1.vp' with a checksum of 0xf74f0afe
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\tango_fs1.vp' with a checksum of 0x98f0f4cd
Found root pack 'D:\Spiele\FreeSpace2\FS_Port\warble_fs1.vp' with a checksum of 0x49c6c98d
Found root pack 'D:\Spiele\FreeSpace2\FS_Port_Mediavp\mv_fsport.vp' with a checksum of 0xdc8abbde
Found root pack 'D:\Spiele\FreeSpace2\MediaVP3610\MV_Complete.vp' with a checksum of 0x31df7754
Found root pack 'D:\Spiele\FreeSpace2\MediaVP3610\mv_music.vp' with a checksum of 0xbbd92e16
according to the log, your mod folders were loaded in the wrong order: the correct order still is FSPort MediaVPs, FSPort, MediaVPs. Yours was FSPort, FSPort MediaVPs, MediaVPs. What you've done now with the new folder achieves this and apparently works, but it is still... wrong.

As The E mentioned, you don't need LightspeedFS2.vp anymore. And even if you did, it wouldn't belong in the \freespace2\ folder; the correct place would be \freespace2\mediavps\.

Code: [Select]
Searching root pack 'D:\Spiele\FreeSpace2\stu_fs2.vp' ... 1777 filesYour stu_fs2.vp is broken; it should contain 2355 files.

Also, your mod folder names are rather complicated and unconventional. Most people have their MediaVPs in a folder called "mediavps", FSPort in "fsport" and FSPort MediaVPs in "fsport_mediavps". Not that the names matter much, but you'll just have to configure your own mod.inis, because the majority of mods assume that the folder names are what I mentioned and the mod.inis supplied with them have been made accordingly.
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 03, 2009, 10:05:59 am
I called the 3610 folder that way because I still have another folder with the 368 mediavps in case some older mod has problems with the new MediaVPs (for that case I also kept a 3.6.9 build on my drive).

And the stu_fs2.vp isn't broken. I have the german verison of the game. In that only the ingame lines and the command briefings have voice. The normal briefings and the debriefings don't, which accounts for the lower number of files in it.

You say they are loaded in the wrong order, but how can I change that?
When I tried to put both the FS_Port and the MediaVPs into secondary, the game only loaded the new models of the Apollo and Valk (without glowmaps and cockpits) but all the other models were plain vanilla FS2 ones, as I mentioned before.
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 03, 2009, 10:17:18 am
I called the 3610 folder that way because I still have another folder with the 368 mediavps in case some older mod has problems with the new MediaVPs (for that case I also kept a 3.6.9 build on my drive).

NOT a good idea. There have been very few issues with the new mvps, and none at all in recent weeks. Keeping the 368s around is just going to confuse things. Plus, campaign/mod designers do rely on the standard folder/mod names for their mod.inis, as well as our attempts to troubleshoot borked installs. We really do prefer people to have a uniform folder layout.

To fix your problem, you need to edit your FSPort mod.ini by adding the following line after [multimod]
primarylist = FS_Port_Mediavp;

and deleting the FS_Port_Mediavp entry from the secondarylist.

Please note that all of this could have been avoided if you had stuck to the normal folder names, and just selected the fsport-mediavps as a mod....
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 03, 2009, 11:42:11 am
Quote
Keeping the 368s around is just going to confuse things.
Why? I keep them in a seperate folder. Unless I put that folder into a mod.ini, it won't ever be looked at right?

OMG *facepalm*
I just found out from were all my trouble came from....
Little cause, big problem. I had it like this "secondarylist = FS_Port, MediaVP3610" and that stupid little blank space between the comma and the mediavp srewed everything up.
Once the blank space after the comma is gone, everything works perfectly.

Thanks for the help to you all and sorry for wasting your time just because of a single blank space...
Title: Re: Apollo and Vaklyrie problems
Post by: Jeff Vader on July 03, 2009, 12:22:23 pm
sorry for wasting your time just because of a single blank space...
Is it such a waste of time if you learnt something in the process?
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 04, 2009, 01:26:14 pm
I guess not, but it's still annoying go through all this just because of a single blank space :nod:
Title: Re: Apollo and Vaklyrie problems
Post by: Galemp on July 05, 2009, 11:42:07 pm
dey shud fix dat.
Title: Re: Apollo and Vaklyrie problems
Post by: Three_Leaf_Ivy on July 21, 2009, 12:00:55 pm
Alright, I finally give up after a  :mad: and :hopping: -inclusive rage session. I apologize for bumping a near-month old topic but I'm having the opposite problem that the original topic poster had: when I'm playing Silent Threat: Reborn, the Apollo, Valkyrie, Angel, Athena, Dragon, and Karnak models aren't upgraded but when I'm playing the FSPort (via selecting the MediaVPs folder as the mod) they work fine (other than the Angel which I cannot test because it's not in the FSPort tech room).

I'm using FSOpen 3.6.10 with the 3.6.10 MediaVPs. FSPort 3.1.1 with MediaVPs 3.1.1.

My folder setup's like this, pretty self-explanatory:
fsport
fsport-mediavps
fsport-str

And the mod.ini multimods's go like this

fsport:
[multimod]
primarylist  = fsport_mediavps;
secondarylist = ,mediavps;

fsport-mediavps:
secondarylist = fsport,mediavps;

fsport-str:
secondarylist = fsport,mediavps;

I've tried a loooooooooooootta different changes to the fsport-str mod.ini that I can't remember exactly, but I just know I'm missing something exceedingly simple because when I switch to the fsport-mediavps folder as the mod the above mentioned models show up perfectly shiny and upgraded. Now that I've calmed down it's pure :confused: . Someone help? =(
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 21, 2009, 12:04:32 pm
if all that info is correct, you need to rename the fsport-mediavps folder to fsport_mediavps.

The secondarylist for str should read:
secondarylist = fsport_mediavps,fsport,mediavps;
Title: Re: Apollo and Vaklyrie problems
Post by: Jeff Vader on July 21, 2009, 12:09:13 pm
Uh, actually
Code: [Select]
primarylist = fsport_mediavps;
secondarylist = fsport,mediavps;
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 21, 2009, 12:10:45 pm
Yeah, like that. *headdesk*
Title: Re: Apollo and Vaklyrie problems
Post by: Three_Leaf_Ivy on July 21, 2009, 12:18:54 pm
Strangely enough both solutions work perfectly. (I saw and tested E's solution before making Jeff Vader's correction.) Ahh, I knew it was something simple like that. :o Thank you both for an surprisingly extremely rapid response!
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 21, 2009, 12:26:02 pm
Witness the remarkable power of the HLP support team.
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 27, 2009, 06:42:37 pm
I have the same problem with the Apollo and Valkyrie, i must start with the fs_mediavps right?

the mod.ini is:
[launcher]
modname      = FS Port + Media VPs
image255x112 = ;
infotext     = ;
website      = ;
forum        = ;

[multimod]
primarylist = fsport_mediavps;
secondarylist = fsport,mediavps;

also i have when i start ST:Reborn:
Warning: Unable to find WEAPON_LIST_TYPE string "Prometheus" in stuff_int_list

Many possible sources for this error.  Get a programmer!

File: PARSELO.CPP
Line: 2527


Call stack:
------------------------------------------------------------------
    parse_common_object_data()    parse_object()    parse_objects()    parse_mission()    parse_main()    mission_load()    game_start_mission()    game_enter_state()    gameseq_set_state()    game_process_event()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c817067()
------------------------------------------------------------------

and a Hall error i dont know why
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 27, 2009, 06:48:01 pm
The mod.ini should work. Are the folder names correct?
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 27, 2009, 07:00:40 pm
The mod.ini should work. Are the folder names correct?

yes all folders are correct
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 27, 2009, 07:04:31 pm
Please select a debug build in the Launcher, run it until it crashes, then post the fs2_open.log (found in the data folder inside your FreeSpace 2 directory) here, please.
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 27, 2009, 07:13:06 pm
here is it

[attachment deleted by Tolwyn]
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 27, 2009, 07:18:41 pm
You have not followed the mod installation instructions correctly.
Code: [Select]
Found root pack 'D:\Spiele\FreeSpace2\stu_fs1.vp' with a checksum of 0xf74f0afe
That one belongs in the fsport directory.

Code: [Select]
Found root pack 'D:\Spiele\FreeSpace2\mediavps\data\MV_Advanced.vp' with a checksum of 0x08a62d20
Found root pack 'D:\Spiele\FreeSpace2\mediavps\data\MV_Assets.vp' with a checksum of 0xb8c5d655
Found root pack 'D:\Spiele\FreeSpace2\mediavps\data\MV_Core.vp' with a checksum of 0x0a0213e0
Found root pack 'D:\Spiele\FreeSpace2\mediavps\data\MV_Effects.vp' with a checksum of 0xb2296226
Found root pack 'D:\Spiele\FreeSpace2\mediavps\data\mv_music.vp' with a checksum of 0xbbd92e16

These are superfluous and should be deleted.

Code: [Select]
Found root pack 'f:\tango2_fs2.vp' with a checksum of 0x799e46a1
Found root pack 'f:\tango3_fs2.vp' with a checksum of 0x825f5ee0
Found root pack 'f:\warble_fs2.vp' with a checksum of 0xa7037300

You don't need to have the FreeSpace disc in the drive.

You should also select the mod you have problems with, run the debug build, then post the log.
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 27, 2009, 07:46:36 pm
ok it works, but the Valkyrie and Apollo have the old (very ugly) model
Title: Re: Apollo and Vaklyrie problems
Post by: The E on July 27, 2009, 07:56:43 pm
Do you have problems similar to the ones mentioned in the first post of this thread? I.e. if you select ST:R as the active mod, you get the shiny models, if you select the fsport, you don't?

For reference, these are the mod.ini's I use:
ST:R
Code: [Select]
[launcher]
modname      = Silent Threat: Reborn v1.0;
image255x112 = fsport-str.bmp;
infotext     = As the Great War rages on, you've been commissioned by Galactic Terran Intelligence for special intelligence operations.  Your objectives are to contain the Shivan onslaught and preserve the fragile Terran-Vasudan alliance.  But a series of suspicious events cloud the GTI's spotless record.  Is the GTI setting you up or are the Shivans spreading their evil rage?;
website      = http://fsport.hard-light.net/website/str/;
forum        = http://www.hard-light.net/forums/index.php/board,140.0.html;

[multimod]
secondarylist = fsport_mediavps,fsport,mediavps;

FSPort:
Code: [Select]
[launcher]
modname      = FSPort v3.1.1;
image255x112 = fsport.bmp;
infotext     = A fourteen-year war between the Terran and Vasudan species leads into something far more sinister.  This is the story of the Great War.;
website      = http://fsport.hard-light.net/;
forum        = http://www.hard-light.net/forums/index.php/board,39.0.html;

FSPort mediavps:
Code: [Select]
[launcher]
modname      = FSPort MediaVPs v3.1.1;
image255x112 = fsport-mediavps.bmp;
infotext     = Freespace Port Media VPs.  Requires FSPort 3.1.1 and standard Media VPs 3.6.10.;
website      = http://fsport.hard-light.net/;
forum        = http://www.hard-light.net/forums/index.php/board,170.0.html;

[multimod]
secondarylist = fsport,mediavps;
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 28, 2009, 02:59:46 am
maybe i have a old sparky_fs1 version? my version is from december
Title: Re: Apollo and Vaklyrie problems
Post by: -Norbert- on July 28, 2009, 09:47:36 am
Make sure you don't have any blank spaces between two entries in the same line.
Code: [Select]
secondarylist = fsport,mediavps;   This will work.

Code: [Select]
secondarylist = fsport, mediavps;  This caused me to have the same problem you described.
Title: Re: Apollo and Vaklyrie problems
Post by: Lyk on July 28, 2009, 09:56:17 am
the .ini are correctly