[Nico]

another maping update.

[mikhael]

I think you MIGHT have gone a bit over the top witht he detail in the wing maps there, Venom.

[Ryx]

[Taristin]

Originally posted by mikhael
I think you MIGHT have gone a bit over the top witht he detail in the wing maps there, Venom.

Nah, it's just right.

[Woolie Wool]

Originally posted by Nico
Started mapping the fighter version.

Also set up a designation system:
the very original version is the Ezechiel A ( demonstrator version, that's what it was in OTT actually, a ship performing test on real battleground, availabilibity was limited to one squadron in the whole campaign ).
The version above is the standard, series version, designated Ezechiel C
The biplace version is designated Ezechiel B.
Dunno, maybe I'll make more versions, why not.

Okay, NOW I like it again. If you release it, I might put out a slightly modified version with a pointed nose called the Ezechiel D, which would be an atmospheric variant. Then we'll all be happy.

[Woolie Wool]

Originally posted by mikhael
I think you MIGHT have gone a bit over the top witht he detail in the wing maps there, Venom.

No.

[Nico]

Originally posted by mikhael
I think you MIGHT have gone a bit over the top witht he detail in the wing maps there, Venom.

Well, it does come from OTT, so that's fine
WW: well, good luck modifying it.

[Deepblue]

Originally posted by Nico

another maping update.

Ugh, not the wings. Please dont kill the wings. Have less stuff on the white wing sections and you will be good.

[StratComm]

Woolie, as this isn't a model dump ship, it's usually protocol to consult the author before modifying the mesh.  Its something that modders can take offense to if you aren't careful.  Not that you have it yet, but don't you ever jeopardize a release by saying how you will modify it.

And wow.  Maybe a tad more contrast on the wing mapping (main color sections, not detail), but that's a relatively minor thing.  This one really needs a

[Bobboau]

I figured out a way to code in outlines for cell shadeing effectively, don't worry

[Nico]

Originally posted by StratComm
Maybe a tad more contrast on the wing mapping (main color sections, not detail)

It's the white decal that's eating the contrasts ( in fact, the ship is all grey, there's a decal layer in toshop.

Bob: cool, wanna see that
One more update:

I know the bottom needs more work, but that's all for today.

[Liberator]

Venico, it looks nice, but it's entirely too light compared to the pretextured version.  I think it would look nice with portions of the texture darkened way down, not 0,0,0(RGB), but something like 75,75,75(RGB).

[Nico]

I know, tried already. See the fact that there's about no contrast on the white part? well, on the dark parts I tried, it did the exact opposite, and it looked vasudan
So for now, I'm keeping it like that, I'll worry about colour schemes later. But I do intend to have it about the same colour as it was in OTT.

[Woolie Wool]

Originally posted by Nico
WW: well, good luck modifying it.

Heh, it probably won't be THAT hard, although from my experiences, your ships' mapping and textures have been quite tricky to do things with (as evident in my failed attempt to shinemap the Ezechiel), so it might actually be uite a challenge, I dunno.

[aldo_14]

Texture count / res?

[Nico]

one map for the cockpit/pilot, one map for the glass parts of the canopy ( transparency map, will save a giant useless alpha channel and a huge TGA file as well ) and one 2048*2048 map for the ship itself. Then a 256*256, 128*128 and 64*64 maps for the lods. I thought about using a custom map for the debris, but that would be pushing it.
The cockpit and glass maps would be reused for any ships using those parts, so that's one map that would be loaded for a lot of ships, don't think it's a memory waste that way.

[Nico]

Originally posted by Woolie Wool


Heh, it probably won't be THAT hard, although from my experiences, your ships' mapping and textures have been quite tricky to do things with (as evident in my failed attempt to shinemap the Ezechiel), so it might actually be uite a challenge, I dunno.

Don't bother planning it, you won't have my permission to modify the mesh anyway.

[aldo_14]

Originally posted by Nico
one map for the cockpit/pilot, one map for the glass parts of the canopy ( transparency map, will save a giant useless alpha channel and a huge TGA file as well ) and one 2048*2048 map for the ship itself. Then a 256*256, 128*128 and 64*64 maps for the lods. I thought about using a custom map for the debris, but that would be pushing it.
The cockpit and glass maps would be reused for any ships using those parts, so that's one map that would be loaded for a lot of ships, don't think it's a memory waste that way.

2048 * 2048?  Seems a bit...big.

IMo.

I've just started going back to 1024*1024 for fighters.... honestly don;t see how much difference a larger map would make, given the distance you tend to see the models at.  i'd have went for 512*512, but i'm using the base mesh for renders.

EDIT:  As an aside, I just found a really good way to do corroded / damaged textures (i.e. grain)... my new ******** engines look **** hot!  Yay!

[Col. Fishguts]

 wow...this thing could become the new SCP flagship to show of the game to not-yet-believers....

[Nico]

Originally posted by aldo_14


2048 * 2048?  Seems a bit...big.

IMo.

I've just started going back to 1024*1024 for fighters.... honestly don;t see how much difference a larger map would make, given the distance you tend to see the models at.  i'd have went for 512*512, but i'm using the base mesh for renders.

Woomeister told me that one 2048*2048 map runs better than two or three smaller maps. Anyway, nothing prevents the map to be scaled down if there's a performance hit.