Hehe, TBH, I wasn't a 100% positive that hint brush in my pic would work, being flush with the non-axial corridor brush face (been a long time). Sweet relief when pjw affirmed things :) I'd rather stretch those non-axial corridor parts a good 64 units for good messure too, though, and have the hint ...

ahh nice. (I also see I made my floor is wrong as well :D ) So angles like that don't need to be made into detail? Well, from your pic I gather that this corridor borders directly on The Void, so the brushes would *need* to be structural. If you plan to add a caulk hull later on, though, then, yes,...

Hipshot wrote:Can a curve like that really be VISed any good?

Depends on how long the corridor is.

In my pic, hinting *could* be achieved, but it's a close call =>

When brush faces connect on a 45 degree angle, use a clipping ratio of 2:1 on the brushes =>

When there's a shortage on trolling pansies, you'll be the first to be called upon.

But for the time being: GTFO :icon10:

Looks amazing.

Really like how you blended together the organic and the non-organic there.

What are you no-clipping into in that pic?
Seems to end so abruptly.
Or is it a region compile?

Hr.O wrote:ps. sorry for the delay, it took me a while to stumble over this thread again.

Hehe, np, I don't frequent here as much as I used to, either.

Stills seems a strange and 'hacky' solution, though...oh well.

Judging by your first pic (05-31), I can't understand how you would expect *not* to run into sparklie-problems. You've got patches run into and overlapping other patches and brushes. No offence, but that's a real slop-fest, right there. First off, have vertices of patches and brushes join in a neat ...

obsidian wrote:I don't know about making the ends of patches... I've never had to do that...

Never heard of this method, either.

Care to elucidate, Hr. O?

I'm just waiting for you to upload them nifty textures you been working on so I can fuck around with them.

(Or did I miss something?)

In C:\Program Files\Quake III Arena\baseq3\scripts\... there's a file called 'shaderlist.txt'.

This is where all shader files are 'called'.

In order for shaders to work they must be mentioned here.

Dis you remove the double slash "//" in front of "models" in your shaderlist file?

Been a long time but I seem to remember something about having to remove them in order to make custom model shaders work.

Looking VERY interesting there, sumatra.

I keep being amazed at what the Q3A engine can achieve when used by skillful people.

Yup =>