Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: Hippo on July 12, 2010, 06:05:41 pm

Title: issues with movies
Post by: Hippo on July 12, 2010, 06:05:41 pm
Used Turey's installer, running Port 3.1.1 w/mediavp's, all ogg cutscenes present.

When I launch the game, I get the FS2 intro, and if i rename/remove that, the FS1 into does not play, nor do any of the normal FS1 cutscene .ogg's as you progress through the campaign.
Title: Re: issues with movies
Post by: Goober5000 on July 12, 2010, 06:09:57 pm
Can you post your fs2_open.log, as well as screenshots of your root folder and your fsport mod folder?
Title: Re: issues with movies
Post by: Galemp on July 12, 2010, 06:21:06 pm
What version of FSO are you using? You should be on 3.6.12 RC3 (it's on the front page.) It might be that you're using an older version that doesn't support OGG, and it's playing the FS2 intro because it's MVE.
Title: Re: issues with movies
Post by: Hippo on July 12, 2010, 07:05:34 pm
(http://ahtw.org/tmp/directories.png)
Working directory, mod directory, and then a search for all intro.ogg files, respectively.

3.1.1, 3.6.12 RC3 (inf)

no .mve files

[attachment deleted by ninja]
Title: Re: issues with movies
Post by: The E on July 12, 2010, 07:11:18 pm
If your fsport movies are in fsport\movies, they need to be in fsport\data\movies
Title: Re: issues with movies
Post by: Hippo on July 12, 2010, 07:21:18 pm
that fixed it, thanks
Title: Re: issues with movies
Post by: Cobra on July 12, 2010, 08:51:02 pm
Derp!

How come you're using Turey's installer? Ain't it broken and corrupted and whatnot?
Title: Re: issues with movies
Post by: The E on July 12, 2010, 08:59:55 pm
Turey's is not broken and corrupted anymore.

That said, it really should have put the movies in the correct directory.
Title: Re: issues with movies
Post by: Goober5000 on July 12, 2010, 10:17:58 pm
Quote from: The E on July 12, 2010, 08:59:55 pm
That said, it really should have put the movies in the correct directory.
That seems to have been a problem with the FSPort's install config, not the Installer itself.  I've fixed it.