But i found so many websites contradicting each other (some say like that one that it is a false positive, others that it is a virus that slowdown your computer and some others even tell you how to delete it) that i preferred to play it safe and report it.

But if Hrimfaxi uses Avast too, i suppose it can be an only-Avast issue. 

Avast it is! 8-) 

case solved 

is it possible? 

Use func_walls with skip texture. 

Since that will block projectiles and break the monsters' line of sight. 

I thought Tyrann's tools handled brush models made with clip brushes? 

one way to improve it is to make a func_wall where the main body is a clip brush, but that has small skip brushes at 2 opposite corners.

This works around a bug in qbsp where clip brushes don't contribute to the physics bounding box of the model, which means you can pass through them if you don't contact the too-small bounding box.

By adding the skip brushes at opposite corners, those brushes ensure the bounding box is correct. And the middle clip brush will work then. 

This works around a bug in qbsp where clip brushes don't contribute to the physics bounding box of the model

Fixed in TyrUtils apparently. 

but now they show up ingame with the skip texture, how do i prevent that? 

What compiler are you using? 

ne_q1sp with txqbsp 

I have no idea if that supports skip brushes. Try Tyrann's tools first. They are the most up-to-date, and most fully-featured. 

you can also run newskip.exe after running any version of qbsp, to hide the skip brushes. But there are qbsp versions that do it automatically. 

that did the job 

M.S.E.



. 

Tyranns tools are pretty old compared to he newest tx_qbspxt versions.
Not to mention they are some dimensions slower. 

What are you talking about?
Both are fast, as to say they both take only seconds even on a map with 12000 brushes. 

Just wanted to do a back to back test on bbin1. XT takes about two minutes iirc; tyrqbsp crashes... 

Yeah, The Hell That's Coming was a few minutes worth of QBSP time ... all those portal errors add up. :) 

8m30s for tyr vs 1m14s for txqbsp_xt.exe in wine. 

and tyr's used more of everything in the WriteBSP table. Up to 30% more clipnodes and 10% more vertices, marksurfaces. 

Same here, the splitting txqbsp_xt does seems to be more efficient than i thought.

And its faster, yes. 

Hello, very quick question - what's the latest/best Radiant-derived editor to use for Quake (1) these days? 

I'm a fan of netradiant. It's not perfect, and I'm not even sure anyone is still working on it, but it feels very solid. I did have to remap all the hotkeys in the latest version though to get it how I like it.