[mjn.mixael]

How can I use these with a custom campaign?
You will need to open that campaign's mod.ini, look for the mediavps or mediavps_3612 entry, and change it to mediavps_2014_beta.

BTW is there a reason you started to rename your mediaVP folder with every major release?

The last time I was here (2007-2008), it was only called "mediavps". Then at some point you decided to add a version number after it. And now there's a year number??

Not that this would prevent me from playing, but I find it exceedingly irritating to manually edit every mod.ini file of my 30+ mods

Too much hard work ;D

The reason is because the FSU decided that it is about upgrading Freespace 2 and as a bonus that generally works with mods as an upgrade pack. However, we  (FSU) simply cannot guarantee that the newer mediavps packs will work with every mod ever. So, you are free to edit your mod.ini's if you want. However, the system is designed so that mods built on MediaVPs 3.6.10 will -always- work when loaded with MediaVPs 3.6.10. They may work with 3.6.12, but we can't ensure that. It's up to the mod creators to update their mods for the newer mediavps packs if they want to support them.

NOTE: FSU will attempt to assist mods that want to update their mods with compatibility issues.

[Lykurgos88]

The reason is because the FSU decided that it is about upgrading Freespace 2 and as a bonus that generally works with mods as an upgrade pack. However, we  (FSU) simply cannot guarantee that the newer mediavps packs will work with every mod ever. So, you are free to edit your mod.ini's if you want. However, the system is designed so that mods built on MediaVPs 3.6.10 will -always- work when loaded with MediaVPs 3.6.10. They may work with 3.6.12, but we can't ensure that. It's up to the mod creators to update their mods for the newer mediavps packs if they want to support them.

This would make sense if the FSO installation instruction page also contained links for legacy mediavps files. Now it seems they are nowhere to be found, or at least it's very difficult to find old mediavps.

I haven't really encountered any problems with upgrading mod.ini from "mediavps" to "mediavps_3612" with any mods, but here's the thing: IF there was an unfortunate incident, and a mission refuses to work because of too fresh mediavp files, the only possible solution for playing that mission would be to use retail FS models and textures.

IF this kind of thing were to happen, I believe everyone would prefer using legacy mediavp mod directory as a substitute. It's always a better option than plain retail FS2.

EDIT: I say this because I recognize that most of the mod makers really can't upgrade their mods with every new MediaVP update.

[Luis Dias]

So you're basically saying that someone somewhere might be having an obscure problem that no one has yet complained about?

Ok.

[Lykurgos88]

So you're basically saying that someone somewhere might be having an obscure problem that no one has yet complained about?

Ok.

You are missing the point. It seems that FSU team is afraid of compatibility issues. If there was no compatibility issues whatsoever, the most logical thing would be to keep mediavp -directory's name SAME with every update and only upgrade single files.

This way no one would ever have to update mod.ini files.

[mjn.mixael]

A: this is not the thread to debate that issue.

B: it's not going to change.

[The E]

You are missing the point. It seems that FSU team is afraid of compatibility issues. If there was no compatibility issues whatsoever, the most logical thing would be to keep mediavp -directory's name SAME with every update and only upgrade single files.

This way no one would ever have to update mod.ini files.

Look, we've been thinking about this issue a long time. The way we've chosen to implement this is the best available to us given the way FS modding works.

[Lykurgos88]

So, no links for old mediavps (pre 3.6.12)? That's disappointing.

[Grizzly]

Is the FSU team actually aiming for yearly release's now (with a "code freeze" at the 31st of december or something like that), or is it just called 2014 because it is no longer geared towards a certain build?

[mjn.mixael]

or is it just called 2014 because it is no longer geared towards a certain build?

This.

So, no links for old mediavps (pre 3.6.12)? That's disappointing.

Hey look, I used the forum search!

[Lykurgos88]

No, I meant that this page should have additional links:

http://www.hard-light.net/wiki/index.php/Installing_FreeSpace_2_Open

Sorry, i've been very confusing today. I'll go to sleep...

[mjn.mixael]

It's the Wiki.. add them.

[niffiwan]

For those that have encountered the Ptah insignia problem, I've just committed a change to the code to increase the allowed faces/vertexes for insignia.  I've loaded all the models in the techroom without any issues, but more testing would be good, just grab the next nightly build (in probably nearly 24 hours as I think I just missed the scheduled windows nightly build time)

Also, if any modellers could weigh in on the best value for max vertexes given a new faces limit of 80 that would also be appreciated. Or in other words, what's the max number vertexes there could to for an 80 faces insignia?

[Oddgrim]

Okey, I have done some more thinking on the matter and a new 72 triangle limit would form a perfect square with 49 vertexes. (If anyone don't know , the retail limit is 8 triangles with 9 vertexes, highly impractical for any curved surface.)

edit: Perhaps 128 triangles would be even better?

[Luis Dias]

...a new 72 triangle limit would form a perfect square with 49 vertexes.

[Grizzly]

Thanks Mjn,

Just curious, what actually is the MediaVP roadmap/release schedule/whatsever?

[Hellzed]

Any chance we get a beta 2 once most of the LOD issues are fixed ?

[Yarn]

So, no links for old mediavps (pre 3.6.12)? That's disappointing.

The 3.6.12 MediaVP release thread does have a link to the 3.6.10 MediaVPs--just look near the very top of that post.

[JCDNWarrior]

Edit: Disregard original post, forgot to adjust the mod.ini file.

BP2 does throw out a bunch of glowpoint errors now though.

[mjn.mixael]

Mod creators have been privately reached out to and asked to check for such compatibility issues. FSU only tests against retail FS. There are too many mods for us to test against each of them.

That is to say, I have no doubt BP2 throws errors, but I'm not going to look into why. I'll wait until I hear back from someone on the BP team if it's something FSU needs to deal with or a simple change for their modpack.

[JCDNWarrior]

Perfectly understandable, I already assumed that, as well. I was just considering if it would somehow be of help, though. I'll look forward to see compatibilities from other mods come about.