[Jonathan_S47]

Wow, I defiantly like what you did to the engines for the Colossus. I am really curious for what you are going to do for the rest of the ship.

[Mongoose]

That's almost a little too detailed.  Nice work, though.  My personal preference would be for something that doesn't deviate too much from the Colossus's original design; I'm one of the few people around here that seems to like the Big C. I'm not sure if making any major modifications to the turret layout would be a good idea, at least in the realm of the beam turrets, since a few of the main campaign missions rely on their placement.  Regardless, that thing is amazing looking; I can't wait to see how the whole thing turns out.

[TopAce]

Originally posted by Mongoose
...I'm one of the few people around here that seems to like the Big C. ....

I am also a Big C*-fan.

*C, not Cube, but Colossus!

[Raptor]

...oh...my...

You've been takening lessons from IPAndrews, haven't you?

With THAT level of detail, I'd be suprised if you can get it ingame without any slowdown.

But good luck.

BTW: I too like the big C.  Though it should have it's full armerment of 84 turrets (it only has 63).

[Nuke]

cool have fun uv-ing that beast.

[MetalDestroyer]

OMFG !! I thougt it was a new spacecraft. And after all, it is THE HTL colossus...

[Slanker_MT]

Tz, there is no need to cut the polies down, just make two versions, one detailed high-poly version for ingame purpose and an uberdetailled extreme-high poly model for use in renders and cutscenes.

[Taristin]

NAh. Make all of the greebling untargettable subsystems and use Bobbaou's new code to make the greebling only show up when you're ~1500 meters from it, or something. :nid:

[TopAce]

Simply drop this amount of greebling. It is not worth it.

[karajorma]

Or you could listen to Bob and Raa who actually know what they are talking about.

[Black Wolf]

Originally posted by karajorma
Or you could listen to Bob and Raa who actually know what they are talking about.

...


...


Nah.

[TopAce]

Originally posted by karajorma
Or you could listen to Bob and Raa who actually know what they are talking about.

I think this post is pointed at me.

[KARMA]

I was out these days so I can reply only now...
about pcount....
when I started I was aiming for 12-15k tris, but I soon realized that I was going well over that limit:p
The actual pcount of the engines is iirc 7300/7500 triangles, so I evaluate that the final pcount will be between 17k and 20k triangles, without turretts.
That's high but not THAT high.
Also, I'll make an high poly lod1 (something like 10k tris) in order to reduce the lod0 range and help those with lower specs machines.
I'll use that new code from bob, but I wasn't aware of it and I don't have an idea of how it works. Anyway, if it just lets you define the visible range of specific subobjects, it'll be useful only for the "pure greebling"; it can't be used, for example, for most of the the pipeworks of the engines, where I'd need more a "subobjects' lod system", I mean the possibility to switch between low poly and high poly versions of a subobject depending by the distance of that subobject and not of the whole ship.
The engines btw are heavily optimized: I cutted more than 1k compared to my first version, with some minimal visual lossess but ****ing up the "cleaneness" of the geometry, I just hope that this will not cause shading or lightning weirdnesses. I also sliced the mesh in many submodels to reduce the pcount, some of them are intersecting and I hope that this won't cause problems.

Side note: the horizontal engine is meant to be blocky, alsthought it turned out smoothy in the render.

[Flipside]

Well, that doesn't sound too killer in the polygons department, and the subobject lodding as you describe it is pretty much what I'm hoping for, since it would allow, for example, with terrains to have a Terrain at Lod0 the whole time whilst to objects on it gain detail as they get closer. As the C practically is a terrain, it kinda makes sense that we are both thinking along the same lines

Anyway, awesome stuff! Looking forward to seeing more

[WMCoolmon]

This is looking very good.

[Ghost]

Heh.. I looked at the first few, and I was like... "What the hell is that?" Then I looked at the rest, and I was like... "OH."

Very nice.

[Grimloq]

Wow... Never heard of 'nidding' before...

Ersh... @_@ Sweet merciful prograsms!!!


(Prograsm: The Greatest Computing Experience )

[Bobboau]

"it can't be used, for example, for most of the the pipeworks of the engines, where I'd need more a "subobjects' lod system", I mean the possibility to switch between low poly and high poly versions of a subobject depending by the distance of that subobject and not of the whole ship."

ummm...



that's exactly what it does, you define a box were a subobjec is or is not visable within, so you make a low poly version that is only visable outside the box and a high poly version that is visable only within, try to make ~1000 poly batches.
the closer you get the more objects should become visable, so you have a rough outline and more and more detail gets added


"some of them are intersecting and I hope that this won't cause problems."

it won't

[Taristin]

Originally posted by Bobboau

that's exactly what it does, you define a box were a subobjec is or is not visable within, so you make a low poly version that is only visable outside the box and a high poly version that is visable only within, try to make ~1000 poly batches.
the closer you get the more objects should become visable, so you have a rough outline and more and more detail gets added

Quoted for good measure!

[KARMA]

that's phantastic, I'm gonna rework a little the model then, using a little less optimized version.
Just a Q: you have to do it in the model (the box is defined during conversion?)? if so, what hierachy should I use?