I've taken your advice and kinda fixed the mirror glass, replaced the geometry with a texture of broken glass.
Looks a bit better than before. Bench is in there just to test it and see how it looks like ingame.

obsidian wrote:Glass/mirrors tends to break radially and spiderweb or crack laterally.

Yeah it looks kinda bullshitty, gotta fix it. Thanks
It's for urban terror, this is actually the updated fstech1 engine, so it supports VBO and normal mapping.

Why don't i embarrass myself a little with a couple of screenshots of my WiP.

Would you be so kind and send me that model so i can run a few tests with it.
I give you my word i will not use it in mt work or redistribute it.

That is with 3dsmax yes, I've had more problems with vertex lighting breaking on long thin triangles and looking bad with skybox lighting rather than smoothing group issues. But it might be cause i make models for Urban Terror and not Q3? Not sure if that engine was changed in some way so the smooth...

I got models with over 10 000 polygons and smoothing groups work OK.
But if polygons are tiny even vertex lighting looks bad.
If i were you I'd shadow bake the model and lose the mirror, you got a model with a lot of polygons and that mirror is duplicating them.

I wanted to create like a fake skybox. Something i can put on the outer side of a window and make the image look far like it has some actual depth.
But without using surfaceparm sky for it.

obsidian wrote:http://q3map2.robotrenegade.com/docs/shader_manual/general-directives.html#sort

I knew it's going to be something i saw a hundred times and never payed attention to it.
Thanks Obsidian.

Is it possible to write a shader that will make a surface appear infinitely far. Like skies look infinitely far.

Surfacelights can be just as "hard" depending on the shader script directives you set. Glad you found the solution. I read the shader manual but i can't seem to find those directives that will affect light attenuation or hardness, mind pointing me in the right direction? Or am i missing s...

I managed to find a solution to my problem. It was right there in front of me the whole time. -filter switch i was using to smooth out the shadows was blurring the lightmap, so when it was blurring a part of the lightmap on the model that was already pretty feathered it blurred it to the point where...

try phong shader? or do this thing with patches ) actually I have quite shitty lightmaps lighting on my models as well, much worse than what you get, I think it cant be helped Phong shader doesn't changes anything. And i made it a model so i can unwrap it and apply a texture properly. Yeah it can't...

Yes i can make them vertex lit and the shadow will look just fine. But like the title of the thread says and you pointed out in your earlier post, vertex lighting and bump maps don't go together. As you can see on those screenshots if the model is larger the lightmap is smoother. Larger polygons don...

I think bad lightmaps are caused by triangle merging. Several triangles are merged into one and then the lightmap looks wrong.
Is there a way to prevent merging?

Nope, no way around it. The normalmap functionality with Q3Map2 isn't true bump/normalmaps as in other modern games. Normalmaps are rendered by the GPU as per-pixel shadows in realtime, where lightmaps are pre-rendered and the relative size of a luxel is comparatively low resolution. You're looking...

the bumpmaps is not realtime in q3 it actually gets baked down on the lightmaps and thats why they dont show with only vertex llightning. So there's no way around it huh. Oddly enough I've just noticed the surface actually is showing some vague sings of a bump map being applied, but for some reason...

Hi all, i got a problem I'm hoping someone can help me solve. I made a simple model that is giving me some problems. When vertex lit bump maps don't show, like they're not being used at all. When lightmapped, they're visible but then shadows look very bad, as though smoothing groups aren't being int...