News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
Clinodes = Clipnodes 
i should use the edit function that isnt there. 
Madfox 
Here are some links about func_detail in the source engine, but I think they pretty much work the same in Quake. (requires tyrutils or rebb's tools)

https://developer.valvesoftware.com/wiki/Func_detail

"Any brush which doesn't significantly block the player's view should probably be detail"

http://rvanhoorn.ruhosting.nl/optimization.php?chapter=func_detail 
Right, Thanks 
The developper mode shows what happens with real vis,
by not drawing all the lines behind the frontview.

Does light.exe effect on func_wall
or do they just stay unaffected? 
Func_wall 
Normally they are lit like regular world brushwork, except don't cast shadows onto the world.
With tyrutils you can set the key/value "_shadow" "1" on a func_wall to make it cast shadows on the world too. 
 
Madfox - Don't get confused. func_wall and func_detail are not the same thing, AFAIK. func_detail is cheaper. 
Yes 
func_detail Are not entities - they become world brushes during the compile process. 
Also 
In quake, unlike in say Q3 and HL2, detail brushes still chop up the rest of the world polys, so bear that in mind when butting random brushes at random orientations into random terrain. 
AH.., 
found the last compilers & beating the maxsurfaces 32768 limb. 
A Path Corner Causing Leak... 
Having a weird issue. I'm using a func_train w/ path_corners to have the ceiling come down to crush the player.

But as it's constructed I need to have the func_corners half-outside the map which the compiler sees as a leak.

Any ideas? Can I alter the pivots of func_trains?

Here's a pic of the corner causing headaches http://imgur.com/2gkM4yj 
 
add a solid brush that fully encapsulates each path corner that is out in the void. 
 
ah, now i looked at the picture.

Just extend the floor and walls so that the area around the path corner is fully solid. 
 
Maybe I've should've tried that :) 
Ok, Another Issue Then, Hopefully Less Stupidity... 
When using the QBSP; TxQBSP found here: https://www.quaddicted.com/tools/map_compilers
My func_details disappear. No collison or visability...

The QBSP found in a pack called TyrUtils render the func_details but I prefered the new one's error messages. 
Func_detail Is A Tyr Feature 
none of the older compilers will support it. 
That Page Is Outdated 
You can get an updated txqbsp with func_detail support at:
http://www.voidspark.net/projects/bjptools_xt/ 
Thanks! 
What's the main difference between tree and tx? 
Their Age 
 
My Don Key 
I'm just using the new bjptools, and if it has on outcome like
CheckFace: ^-- Brush 1030, Line 36552
how do I get so smart to find in the editor that brush?
I can find it in the map with textpath, but that's not the editor. 
Notepad++ ? 
You'll see the brush it belongs to and can coordinate it from there.

What editor are you using? 
Textpad5 
I know where to find a brush in the map,
I just wondered how to find it in Quark orRadiant. 
 
radiant has a 'select brush #' in one of the menus, but no idea about quark. it should though, every editor has that function. 
Bjptools_xt 
The latest one is giving me a report about a virus (win32:evo-gen [Susp]). 
Tried All 
and all give that report. 
Yeah 
I got the same yesterday! 
Which Scanner Are You Guys Using ? 
I have Avira Antivir active, i scan the Archives before uploading with both Avira and Malwarebytes.

I just did so again, as well as uploading the files to Jotti / Virustotal / VirScan.org.

All come up clean.

If you guys are using Avast, theres a few reports about this : https://forum.filezilla-project.org/viewtopic.php?t=33818 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.