[Mobius]

Shinryu is the coolest Japanese name.

[maxim4o]

As for name how does Chaos sound?
Or Cerberus?

[Mobius]

Chaos? It'd fit for a Shivan ship...

Cerberus? It's already used...

[Grimper]

You could name it the Raijin, seeing as how lightning and such can easily be translated as beams.

I vote for Raijin. It sounds good and its not to hard to pronounce like some other names that were suggested. As for the texturing on the ship, the engines at the back look a little over-detailed.  It looks sorta like the engines are covered with pebbles.

[Stormkeeper]

Esarai already named it the Amaterasu, iirc.

[esarai]

Amaterasu is currently leading as my personal favorite, and is as such the name I use to refer to it now, but in the tradition of DICE studios and their Battlefront games, it may be a development codename. In other words I'm still open to suggestions and input.

[ssmit132]

Use any name you want . Although if third-parties want to rename it if they download it, they can.

[Water]

There's a problem.... the ship only reads 84 of the guns. There are four designations of turret: turretXXa, turretXXb, turretXXc, turretXXd. If two turrets have the same XX value but are different, say class a and c, then it chooses only one of them and leaves the other out. I can't manually assemble the turrets because my install of pcs hates my guts. Any suggestions to solve this?

I'm loading the model in as all the original subobjects, not having been thrown together in TrueSpace. Would assembling subobjects that could be only one subobject help allow for more turrets?

turretXXa is lod0 - multipart will rotate and barrels will aim
turretXXb is lod1 - multipart will rotate only
turretXXc is lod2 - no movement of parts.

If you haven't solved the firing point problem, just pm the file and I can have a quick look at it. With that many turrets, you really need them to import automatically into PCS2.

[Mobius]

You could name it the Raijin, seeing as how lightning and such can easily be translated as beams.

I vote for Raijin. It sounds good and its not to hard to pronounce like some other names that were suggested. As for the texturing on the ship, the engines at the back look a little over-detailed.  It looks sorta like the engines are covered with pebbles.

Wouldn't that be easily confused with Ryujin?

[esarai]

There's a problem.... the ship only reads 84 of the guns. There are four designations of turret: turretXXa, turretXXb, turretXXc, turretXXd. If two turrets have the same XX value but are different, say class a and c, then it chooses only one of them and leaves the other out. I can't manually assemble the turrets because my install of pcs hates my guts. Any suggestions to solve this?

I'm loading the model in as all the original subobjects, not having been thrown together in TrueSpace. Would assembling subobjects that could be only one subobject help allow for more turrets?

turretXXa is lod0 - multipart will rotate and barrels will aim
turretXXb is lod1 - multipart will rotate only
turretXXc is lod2 - no movement of parts.

If you haven't solved the firing point problem, just pm the file and I can have a quick look at it. With that many turrets, you really need them to import automatically into PCS2.

...crap. That means they all need their own value for XX, doesn't it? Will altering the name to be something like "bigturretXX" still let PCS auto-assemble the guns, or do they have to be named "turretXX" specifically? If that's the case, then will naming a turret "turret169" break anything?

[Droid803]

You could name it the Raijin, seeing as how lightning and such can easily be translated as beams.

I vote for Raijin. It sounds good and its not to hard to pronounce like some other names that were suggested. As for the texturing on the ship, the engines at the back look a little over-detailed.  It looks sorta like the engines are covered with pebbles.

Wouldn't that be easily confused with Ryujin?

Yes, and with Raiden...
Heck, its a fusion of the two names XD

Shinryu FTW!

[Water]

...crap. That means they all need their own value for XX, doesn't it? Will altering the name to be something like "bigturretXX" still let PCS auto-assemble the guns, or do they have to be named "turretXX" specifically? If that's the case, then will naming a turret "turret169" break anything?

Own value for XX - yes
BigturretXX - no
turret169 - not good. PCS2 will auto generate turrets between whatever was the last turret you had and 169.

turret28
or turret28a-base and turret28-arms
fire point turret28-fp01

If you get the heirarchy and fire points correct, then in PCS2 you never have to touch the turrets.

[Droid803]

But he has 169 turrets.
So it'll go turret01, turret02, ... turret168, turret169

[esarai]

What droid said. The issue is not the hierarchy. I can get that down just fine. The issue is the sheer number of guns this thing has and how well PCS2 can handle names dealing with XX values over 99. But it sounds like that shouldn't mess anything up... if it can successfully name a turret "turret169" and do everything else in between, that means I just need to undo the current naming scheme and give each turret its own XX value.

[ShadowGorrath]

Maybe name it 'Capella', in memory and honour of the fallen system? Unless it's not GTVA.

Btw, esarai, check your message inbox here on HLP.

[Grimper]

What about the pebbly engines?

[esarai]

... I kinda wanted it that way. I figure the engines would be the most complex part of the ship. The texture I used is a hue-shifted contrast-increased captial3.dds, so it will seem more pebbly. I could try a different texture, though...

[esarai]

update: the model has over 30 different pieces of debris. And the debris isn't finished. Sorry for not rendering this, but at this stage giving the ship's subobjects the textures for that would be a pain.

[Hellstryker]

Alright, this isn't going to make sense at all but, I don't think it looks freespacey at all. Yet it somehow fits.

[Jadehawk]

Looks perfectly fine to me Just hope to texture this someday soon as my 21st Battle Group can use it.