Dynaverse.net

Taldrenites => Starfleet Command Models => Topic started by: Bernard Guignard on January 01, 2007, 02:45:44 pm

Title: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Bernard Guignard on January 01, 2007, 02:45:44 pm

Hello all
     I'm just wondering if some one is going to port over some of those ships from legacy that is currently not on the roster
example the battle ship, and the Enterprise era Cruiser or light cruiser I'm not sure I saw some of the screen captures and thought it would be nice to port them over to SFC OP.  ;D

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Starforce2 on January 01, 2007, 03:38:16 pm

could start by rebuildign some. For example, someone bashed a crude tmp battleship. Some of the klingons ect could prboably be amde from exsisting parts IE vorcha variant.

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Terradyhne on January 02, 2007, 08:49:18 am

you could rename A2 models fileformat SOD to M3D (or whatever the Legacy fileformat ending is) and dirctly use them in Legacy, maybe i or someone other could rename the Legacy modelfile ending to SOD and import it into Milkshape or using the CV Tool to convert into SFC MOD fileformat and reimport them with Milkshape !!

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: intermech on January 02, 2007, 10:52:28 am

Does that work???!!!! or is it a shot it the dark?? Could be the key if it works!!!!

first edit

Here is some news about it:

http://legacy.filefront.com/news/Mod_Conversion_Success;31090I

second edit

Ok, second edit, yeah, it works, change the *.m3d to *.sod and use CV to import the model or convert it to *.mod like Tarradyhne said!

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Starforce2 on January 03, 2007, 06:33:46 am

as for exporting models form legacy (stock models) it would require the proprietary plugin for max8. M3d was created by maddoc (or perhaps a special plugin written just for them) and the devs tell me it's unlikely to be released.

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: intermech on January 03, 2007, 07:31:35 am

Yeah, Fallen Warrior and I tried the *.sod import trick on stock models yesterday; the first effort was a failure. However, do not give up hope.

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Reverend on January 07, 2007, 04:02:18 pm

Guys, I'm fairly certain all those ships are already at Battleclinic or through BC Files... don't they all look familiar to anyone else?

Title: Re: Porting over Legacy Class Ships that Are not in our current SFC Roster
Post by: Smiley on January 09, 2007, 05:13:04 pm

Quote from: Reverend on January 07, 2007, 04:02:18 pm

Guys, I'm fairly certain all those ships are already at Battleclinic or through BC Files... don't they all look familiar to anyone else?

Lol, Star Trek ships look familiar? PSML

It's possible to export to .sod format and then rename to .m3d to get ships INTO Legacy, but not vice versa. M3D (on looking at the files with a hex editor looks similar to the SOD format, but it is different). It's only because Legacy is Armada 3 in disguise that it can use .sod models at all!