[Roanoke]

This is actually gonna be a static prop, hopefully going into a custom System Shock 2 map. Cos' the Shock "Dark" engine is older than FS it's a low poly (<800) mesh but I fancy a cross over to FS, allbeit beefed up or a Vanilla model.

[TrashMan]

Me likes!   

[Taristin]

I like. REminds me a bit of my huntercraft, but with big engine pods on the sides.

[BlackDove]

Very good.

[Raptor]

Vaguely similar to a C&C Orca (the original one...)

Not too sure about those spars attaching the engines though...

[Mefustae]

Vaguely similar to a C&C Orca (the original one...)

Exactly what I thought, I would even go so far as to say it could be a direct predecessor to the good ol' Orca we all know and love.

[NGTM-1R]

No, a successor seems more likely, since the drives look more advanced then the Orca's tilt-fans.

[Roanoke]

I actually started playing C&C Tiberium Sun recently (again), though the resembelence wasn't intended. It just kinda happened. I've been building generic sci-fi stuff, such as vehicles, guns, props etc for possible cross over game content ie, porting models into different games.

On that thought, building within strict poly limits is fun. More fun than mega-high-poly rendering, IMO.

[CaptJosh]

It reminds me of the Orca fighter from the Command & Conquer games

[Unknown Target]

Looks neat, I like it

[Nuke]

i did something very similar a long time ago for descent 2. i was inspired by those terminator 2 flying robot things. i like the way you did the tail, looks ww2ish.

[IPAndrews]

They all end up very similar looking these ships don't they. Other forum members have already pointed out that it looks like X ship or Y ship, it also looks like the Valkyrie gunship. One of my favourite ships from B5. Which I guess means that it looks pretty cool

[Roanoke]

Gone through a major rebuild (took it back to a symmetry modifier stage) which kinda torpedo'd the mapping process. Piccys to follow when I can decide what to do with the cockpit nose area. Still shooting for <1K polys. You wouldn't believe how untidy the mesh was. must have unwrapped it about 5 times now, for various reasons. 

[Roanoke]

more confident in my unwrapping hence more polys. 1200 approx, with plenty of room for manouvre.

[Trivial Psychic]

The tail configuration also reminds me of the V-22 Osprey, except that the V-22 uses rotors rather than full-on jets.

[Roanoke]

I'm still not happy with what the unwrap modifier is producing. This is the mesh prior to unwrapping:



So am I right in thinking all those verts 'n' edges which are located out of the mapping box are problems ? I tried rebuilding the ares with little success, unlike last time. I still don't understand why there's a problem as the mesh is 100%.

[Taristin]

Umm. You have to select faces, uv map it, and then unwrap...

[Nuke]

you should break it up into sections first, you can add a bunch of selection modifiers to set up groups and thin uv map each one individually. in truespace i accomplish the same thing my giving each section a different color, which can be selecte with ctrl + the polygot selection tool. makes them easyer to select and project.

[Roanoke]

No, what I mean is the errors I'm getting appear to correspond with the verts and edges that are all skew whiff prior to unwrapping. Ie, if all the verts 'n' faces are all within the mapping box prior to any adjustment then the mesh is sound, atleast that's how it appears to be.

[Nuke]

what you need to to is move everything out of the box on the uvw editor. and then select a group of pollies, apply a projection to them, and then adjust them in the uvw editor so they dont take up all the space. that mess of pollies you have there is normal on a model with no uv space.