Hero Ships

posted on March 3rd, 2017, 12:30 am

Hey all,

I have a question. I'm trying to replace the hero ship, USS Enterprise-E, in the STA 2 Classic mod for Fleet Ops. I've downloaded and installed a version of the Enterprise-E that I like, and followed the instructions to the letter, yet, when I go ingame, the stock ship, with stock textures, keeps popping up.

I've always had this problem when it came to replacing the Enterprise-E, and at this point, I'm kinda wondering how to fix it. As I understand modding, if I replace the model file, in this case the .SOD, with a brand new one (ie - overwrite the original file), should the new model and textures get pulled up by the game? Or am I missing something?

- ChiefBrex

posted on March 4th, 2017, 8:23 am

it's hard to say without seeing your exact files.

Did you replace the texture file as well? If the ship doesn't replace properly, you may be able to get it working by giving your SOD and textures a new name and using the "basename = " command in your ship odfs. This command lets you specify the SOD it will use.

posted on March 4th, 2017, 3:48 pm

The SOD file name is:
Fente.SOD

The ODF file name is:
Fente.odf

Both of these names *are* the names for the stock ships (so far as I know).

Now the textures do not replace the stock textures. But, as far as I understand modding, this shouldn't be an issue. So long as the SOD is replaced, the new textures should load.

I did test to make sure the new model and textures imported properly by using the Storm3D Viewer, and in the viewer, the new model and textures *do* load. Hence my confusion. If the new model and textures work in the viewer, they *should* work ingame.

I'll double check the ODF file just to be on the safe side. And I can take screenshots if needed to get help. Just let me know what you need to assist.

posted on March 14th, 2017, 8:33 pm

So, no one has any suggestions or ideas on why I can't get the USS Enterprise-E to switch out in Armada II?

posted on March 15th, 2017, 2:32 am

This may not help, but....

Fbattle and Fente are the stock sods

Fbattle, Fbattle_1 and Fbattle_2 are the stock textures for the Sovereign and FEnte, FEnte_1 and FEnte_2 are the stock Enterprise-E textures.

What's the name of your new Enterprise-E textures? You've already stated they are not named the same as stock so it shouldn't cause the issue you are having, but just curious.

If you delete the stock textures that have the _1, _2, etc after them does that help in game?

Next, if you remove the Fbattle and FEnte textures from your folder does that fix the problem with your new textures?

And just to be sure, you've made the Enterprise-E buildable from a shipyard or are otherwise using it in the single player missions?

posted on March 15th, 2017, 7:11 am

I believe the problem you have is that you're starting the first mission of the federation campaign "Invasion" and in the intro sequence you see the stock Sovereign flying at you, and then around that planet, right? Actually when you see the small fleet leaving the starbase with the voiceover by Patrick Stewart, you should see the SOD you put into the game ...

Anyway, in the first 3 sequences of "Invasion" the game doesn't use the" fente.sod", but the standard Sovereign "fbattle.sod" that you see flying at you. You will have to replace both SODs if you want to see your new Sovereign in the intro.

However, if you mean you put in your SOD, named it "fente.sod" and when the game starts after showing the mission objectives and you still see the stock one, then I was mistaken and apologise.

posted on March 19th, 2017, 5:29 am

It's been some years since I edited the campaigns, but I am fairly sure it uses the Enterprise 3d model rather than the generic Sovereign for those flybys. I remember replacing the Enterprise-E with the Enterprise-A, and "fbattle" with the Missouri, and I saw the Enterprise-A whizzing past the planet, not a Missouri Class.

I may have edited both the ODFs AND the campaign though, so apologies if I am mistaken.