Hello

Many time without posts of mine, right? lol

here my HLVIS results:

Func_walls don't split your leafs into more pieces so it might help. It will make server performance worse if you have too many entities but it's worth it in many cases. Func_walls don't split up walls in many pieces either(use gl_wireframe 1 and let a pipe touch a flat wall and another one func_wall and you'll see the mess it makes), this would be good for client performance.

I have a room that causes leaf errors, cagey's talked about it so i won't go into it, but making func_walls didn't help me with my errors, but they can help. What can also help is changing geometry or the like.

I get these to if I go over the detail limit the engine can handle I think and they are somehow easy to fix, or at least I think so
Let me explain how I find them and then fix them.

I'm always doing -Full VIS
to prevent these errors...

Here is a screenshot from the area that is affected...
Don't know what's wrong there

I've already removed 2 "45 degrees rotated crates"from there, but the problem continue, don't know really whats wrong in there...

tips?

EDIT: The Screenshot is from a Top-Down View

are you able to get undeneath the boxes trough that passage towards the lower floor? (assuming its co)

Still it wouldn't hurt to put a hint brush at the bottom witht the hint textured face facing towards the shaft which goes to the level with the boxes

This maybe even fix your problem.

try the following:

- Create a Cilyndric solid brush that, when you look straight down to it, has the same shape as your problematic (too complex) brush. (imagine your brush has been flatened, and then stretched to a cylinder)
- Cover this cylinder with the HINT texture and place it over the problematic brush. The brush should fit perfectly into the cylinder. HINT brushes wont be visible after compiling. It just changes the leaf portals.
- Do not let this cylinder touch the ground or ceeling, keep it small, cut it short, keep it out off eye-height if possible, if not performance goes down, but not as much as func_walls.

(it does not need to be a cylinder, a simple cube might be enough. But a cylinder of the same z-shape has a better chance for fixing the leaf portal saw into leaf.)

----

To just "see" the leaf portal saw into leaf" ingame do this:

A leaf portal is an invisible face in your map, that blocks your sight when you cant see it from your location.
thoose are given x-y-z coordinates of your leaf portal
(-24.000 -2569.760 -860.000)
(-67.500 -2528.000 -860.000)
(-67.500 -2528.000 -888.000)
(-65.001 -2530.399 -888.000)
(-24.000 -2569.760 -886.794)
its the 5 corner points of an invisible 5 sided face somewere in your map that will show a hall of mirrors.
So the "face" is somewere at (-60 -2500 -870)
walk around in your compiled map looking at (or better THROUGHT) this location untill you see a hall of mirror there. It might only be visible from one tiny spot (somewere in the air), but thats rare. It might be really small itself, you wont even notice, onos sized leaf portals saw into leafes are damn rare.
If you cant fint it, propably noone else will, and its damage to the map is minimal. almost every NS map has tons of halls of mirrors.
If you can find it you can proudly say "hah there it is" but it ont help you much fixing it.
There is a developer command to show your xyz position ingame, but i forgot.

Fixed it =)

I used some retangles, to divide the lower level and those 3 boxes in the image...

The unique problem is: the HINT texture is touching the ground.. do this decrease too much the performance ?

btw, if you remember the command, please, post it here =D

Thanks

In developer mode try "gl_wireframe 2" (or "gl_wireframe 1") (in opengl mode only) and you see lines all over your textures.
Thoose lines are borders of leaf portals (visible were they hit a wall, but they are invisible all over the room).
With the HINT texture you can force thoose "lines" were ever you want.

Thoose lines split up all the textures into smaller pieces (= W-poly`s).
This affects the flashlight in bad ways most times, you see it breaking up along thoose lines.
In general it makes your r-speeds higher in big rooms, since each texture piece you see is one W-poly.

Around corners it can make your r_speeds lower because you can not see around corners soo far then.
Thats why intelligent usage of HINT brushes around corners increases R-Speed by lowering W-polys.

Ok, I've fixed the Leaf Portals problem on my map..

usually, when I got leaf portals, there was a wall that was "transpassable" by players..

now, I got rid of these Leaft Portals, but the wall seems to be transpassable by Fades, Onos and Marines...

Someone got this problem too?
don't have any idea how to fix that...

got xpcageys compile tools and tried "-cliptype precise" or other "-cliptype"
read for that in xp-cageys webbed thread.

The ns engine uses 4 "hulls", one shows whats visible and 3 "clipping hulls" set were 3 different sized players can move; (crouching, human, onos).
By creating the clipping hulls sometimes errors happen with that old engine.
xp-cageys compile tools are way more intelligent in creating clipping hulls.

when xp-tools do not help, report it to him as a bug.
In 1.04 (before everyone used xp-tools) every second official map had well known places were clipping went wrong and you could move out of the map.
To be on the save side use CLIP brushes. Thoose will create invisible walls, you can just shoot trough, build and walk on, but not in.
They wont affect anything else in the map but blocking movement.

Already using "precise" cliptype...

What I need to do ?

create a retangle, with 1 side as clip and every other side as skip, and put there this problem is happening?

btw, any problem using this as "Coincident" ? Like, placing *exacly* in the same place as the brush that is having those problems?

EDIT: Discovered that I need to put CLIP on all sides of the brush
but, any problem If I put them "Coincident" ?