Re: func_detail issue
Posted by Static88 on
Sun Jan 9th 2005 at 10:48am
Posted
2005-01-09 10:48am
122 posts
52 snarkmarks
Registered:
Dec 31st 2004
Occupation: USMC
Location: USA
Is it adviseable/possible to make all/some of my models in HL2DM func_details? Also, Should I make the brush faces that cannot be seen by the player into nodraw or hint brushes? I have lots of building facades in my map that were made from brushes.
I also have things like building models and fuel pump models in my map. The gas pumps are prop_statics right now. Just trying to reduce compile time and increase in-game performance.
I've read lots of threads on these issues but it seems that people have different opinions and I just need it clarified before I scour my level and change tons of brush faces. on a side note, my current map .bsp size is almost 10 mb. Thanks in advance.
Re: func_detail issue
Posted by Leperous on
Sun Jan 9th 2005 at 12:06pm
Posted
2005-01-09 12:06pm
Leperous
Creator of SnarkPit!
member
3382 posts
1635 snarkmarks
Registered:
Aug 21st 2001
Occupation: Lazy student
Location: UK
Er, func_detail is a brush entity, you can't turn models into it. If you're talking about a prop_detail, these entities don't somehow speed up game performance and are useless unless you're building some sort of 'entity gallery'. However, turning small pieces of complicated looking architecture or things which will horribly split faces into a func_detail or func_brush is a good idea. (Yak- I've noticed some of my func_details don't cause any splitting!) Check out the dm_lockdown source map supplied with the SDK to see what sort of thing to do, and use the console command mat_wireframe 1 in game.
Faces you can't see in the world, such as rooftops, should be textured with nodraw. There's no point in texturing faces that won't ever get rendered (e.g. those touching the void or in between two brushes).
And HINT brushes and areaportals are your friend for increasing in-game performance, there are various tutorials on how to use these here and around the internet. If I get some time one day then I'll write a tutorial on in-game performance enhancing tips :smile:
Re: func_detail issue
Posted by Static88 on
Sun Jan 9th 2005 at 5:37pm
122 posts
52 snarkmarks
Registered:
Dec 31st 2004
Occupation: USMC
Location: USA
Thanks for the info, Lep. I appreciate it.
Re: func_detail issue
Posted by uberDingo on
Sun Jan 9th 2005 at 5:41pm
72 posts
17 snarkmarks
Registered:
Dec 21st 2004
awe nutts... Ive turned some things In my map into func_detail because I thought it increased performance. For example I have a roller coaster type car that Ive built that runs along a track (func_traintank) and then I took that same roller coaster and moved it to a section in the map that's basically a spare parts warehouse. The roller coaster car I put in the parts warehouse I turned into a func_detail because it's made up of a number of brushes. Im now led to believe that making it a func_detail is making things worse then better and I should turn it into a prop_static or just leave it as a bunch of brushes.
Re: func_detail issue
Posted by Livett on
Sun Jan 9th 2005 at 5:42pm
164 posts
46 snarkmarks
Registered:
Dec 24th 2004
Occupation: Student
Location: England
No... making it a func_detail is a good idea. They help improve performance.
Re: func_detail issue
Posted by Vassago5kft on
Sun Jan 9th 2005 at 6:49pm
39 posts
14 snarkmarks
Registered:
Nov 24th 2004
Occupation: 3D Artist, 5000ft Inc
Location: Reno, NV, USA
Yes. If you make them func_detail, then they won't cause any splitting
during the VIS calculation. That in turn, means cleaner polys and fewer
polys.
As far as the nodraw texture, you don't have to worry about putting in
some areas. Places like underneath the street for example, and outside
of the skybox. Those faces will be automatically culled.
Re: func_detail issue
Posted by Yak_Fighter on
Mon Jan 10th 2005 at 2:37am
1832 posts
742 snarkmarks
Registered:
Dec 30th 2001
Occupation: College Student/Slacker
Location: Indianapolis, IN
Well I noticed it while working on my map. I had two types of doorways, a regular and a combine one. The regular one fit perfectly into the wall so nothing was sticking out while the combine one was slightly slanted so that one of the two edges was sticking out over a big floor brush. The regular one cut up the nearby floor on both edges while the combine one cut it up only where the one edge was aligned. The one sticking out did nothing. Then with my knowledge of the old engine and some experimentation I pretty much figured it out. When I get the time I'm going to write up a tutorial about proper func_detail usage and suggestions on how to avoid the face splitting.