[Mongoose]

Thinking about it more, it seems like it'd make sense to be able to point to the MediaVPs as the repository of every single upgrade of canon FS content. Then the FSPort VPs could be reserved for the additional models and variants that Port campaigns rely on. Everyone's able to more conveniently use FS1 assets, and modders don't need to reinvent the wheel and add a bunch of duplicate content. 

[General Battuta]

Yes but also...maybe? Would this involve adding a bunch of ships that could push mods dependent on the MVPs over the ship limit? It seems great, I’m just trying to do due diligence, dude.

[General Battuta]

Doot doot doo doot doot

[mjn.mixael]

Well I guess that depends. My plan was to "table" these using +nocreate which would mean that...

--mods can activate these assets by simply including $name: apollo (at least I think that'll work...)
--FSO wouldn't actually create a ship.

So if that works like I expect, then that does not add to the ship count. Alternatively, this could be strictly assets only. Models, textures. Mods could activate the asset by writing an entire table entry and just reference the asset files. In this case I'd include a text file that has table entries for each asset is included but not activated by FSU.

[Zarax]

How would you deal with models that are different between FS1 and FS2?

[Goober5000]

Name a model (not a table file) where something that was present in FS1 is not present in FS2.

[Zarax]

I assumed a few (Lucifer, Typhon, Hades) did receive some change between FS1 and FS2, guess I was mistaken.

[Goober5000]

It's not a rhetorical question.  If there are any conflicting model changes, I really would like to know.  But I don't think there are.

[Nightmare]

Well, in theory FS1 and 2 models should have different turret models where lasers have been replaced by flak/beam weapons. But that's probably not going to happen.

[Nightmare]

I assumed a few (Lucifer, Typhon, Hades) did receive some change between FS1 and FS2, guess I was mistaken.

In case of Lucy and Hades, their HP was changed, but that doesn't have anything to do with the models. Also, they didn't show up in FS2 plot anyway.

[0rph3u5]

I assumed a few (Lucifer, Typhon, Hades) did receive some change between FS1 and FS2, guess I was mistaken.

There are some changes in the stats of some ships, e.g. the SD Demon recieved a substatial HP boost, but those are table side changes which fall outside what the MVPs do (as they use modular tables to modify an existing ships.tbl)

[mjn.mixael]

Alright, the votes make it pretty clear. I'm going to make this happen.

[Zarax]

That's a great news!

[Nightmare]

 

[Galemp]

I am in full support of canon models and weapons (Apollo, ML-16) being folded into the FSU and non-canon (Karnak, Serkr) being relegated to FSPort.

I also agree that everything not strictly related to 3D assets, such as interface art, remain with FSPort.

[fightermedic]

I am absolutely in support of this

[mjn.mixael]

I've basically got this done. I ran into a complication with how I wanted it to work, though, because of $pbanks and $sbanks. There's no good way to set those to work with mods and including these ships in the tbm with +nocreate can easily override mods who would then need to override the override. Oh well.

Tables setups are still going to be include, but they are 100% opt-in. mv_assets_fs1-shp.disabled and mv_assets_fs1-wep.disabled.

The assets, however, are included and ready to use.

[Galemp]

You have the new and improved Apollo model?

[Nyctaeus]

Apollo is broken. PBR Maps produce very strange results. I actually tried to fix it, but failed to find the cause so I produced pimped non-PBR variant. I may publish it one day.

[mjn.mixael]

Apollo is broken. PBR Maps produce very strange results. I actually tried to fix it, but failed to find the cause so I produced pimped non-PBR variant. I may publish it one day.

Seems fine to me. Care to be more specific?