:O

Hmm, that q3map2 should be recent enough to work.

Maybe it needs to be "_remap01" and not "_remap". I honestly can't remember.

Add a keyval "_remap" "originalShadername;remappedShadername"

If you need multiple remappings, use _remap01, _remap02, etc. I believe this needs a recent q3map2 to work.

Regarding the head, check that all transforms are frozen/applied/baked in your 3d app. It's common for exporters to ignore transformations and just use simple vertex position data.

The vertex count in max will not be correct for a realtime application. Game engines typically have to split vertices in order to handle different materials, discontinuous uvs (ie, seams) and smoothing group boundaries. There is a good, in depth explanation at http://www.ericchadwick.com/examples/pr...

Whats the use of seperating faces >and< using lightmaps? Lightmap generation uses the same normals as vertex lit surfaces, so separating faces should help prevent smoothing artifacts from messing up your lightmaps. Of course, if you are getting nice lighting already there's nothing to worry about. ...

The vertex lit, split faced model looks the most right to me. There's still some wierd shadowing happening on the panels, but that's one of the downsides of q3's vertex lighting model. The other thing you could do is use split faces and lightmap it with a fairly high lightmapscale. That (should) loo...

One thing you might try is painting/baking multiple versions of a texture with different lighting, and place/blend those to fake surface shading (perhaps with highres lightmaps to take care of the tricky spots?). Of course, that would be technically difficult and a crapload of work, and lightmap sha...

Nice texture, but the in game shot shows smoothing artifacts on the model (the lopsided dark triangle on the top beam, for instance). If you are exporting models from Blender you'll have to split some faces in order to get even vertex lighting, since smoothing information isn't exported correctly.

Model import doesn't work like that in q3 or d3. Texturing needs to be done by assigning materials and editing uvs in the 3d app. That data is then exported part of the model file and can't be edited from within radiant.

Models will be vertex lit by default. You lightmap them by compiling with -meta and adding the keyval "spawnflags n" (n=2, lightmapped; n=6, lightmapped and autoclipped) to your model entity.

I'm serious. They look fake and bad, totally lack in style, and apart from one or two trivial examples fail at looking much like any kind of real surface. This is exactly the kind of cheap bullshit that can makes CG and games look so crap.

:icon13:

I'm sorry, but those textures are terrible. Ugh.

Select your fog light, add keyval shaderparm3 [maxFogDistance].

It's age. And cigarettes.

EDIT:

obscure red nut

Betelnut?

That has got to be wrong - you can see the vertexes moving on a deform flare quad.

Changing tangents aren't a problem anywhere in d3 that I know of. Anyway, check out http://www.iddevnet.com/doom3/materials.php - there is a section there which lists the deform functions and their syntax.

But you can export and import them back in should you need to do any manual lightmap editing. I've done this a few times, and as you clearly know it's not useful for increasing lightmap size. Otherwise, if you use lightstyles, external lightmaps are generated. You know, I didn't think of that. I mi...

I had to change the settings on my logitech to get mouse3 to work for everything. I can't remember from what to what, though.

Er, worth a try.

If Q3Map2, you can use external lightmaps

Er, how exactly? You can certainly export external lightmaps, but I can't figure out how to actually use one in q3 (iirc these are useful for rtcw/wolf:et but not vq3).

Q3 lightmaps are limited to 128*128, which means that a large or densely lightmapped level is going to have quite a few. That leads to the sort of problems you are having, as well as being bad for performance. There's not all that much you can do other than to minimise texture variety and lightmap u...

I get exactly what he means, and I think in that shot it's all down to lighting. I don't mean the surface interaction stuff, but the actual large scale lighting of the scene. Almost everything in that shot is either fully sunlit or fully ambient, with no pleasant transitions between the two values. ...

That's not necessary. -patchmeta alone will "bake" patch geometry into the bsp, and it won't be affected by lod.

Yeah, no lighting? It's not finished without highlights, shadows, etc. Seems slightly grainy for plastic, too - maybe a bit less "dirt overlay" and a few careful bumps and scrapes in the right spots would help that.

Proportion, colour choice etc seems good though.