Not much to say, just look at these pictures
Jump to content
Posted 23 October 2018 - 02:34 PM
You may want to say a bit more. What (is/is not) happening that you (think/don't think) should happen?
Posted 23 October 2018 - 03:34 PM
It looked totally black when I saw it at work. At home I can at least make out that it's stairs.
Posted 23 October 2018 - 04:56 PM
This appears to be common with 2.06. I have 4 places in my current WIP where this happens. There used to be 6, but 2 have worked themselves out over the past week w/o me doing anything specific to overcome them.
My best advice short of someone fixing the problem in TDM is to live with it until you're about to enter beta test. If the problem is still around, or has moved elsewhere, you can convert the offending area to a model, or cover it with a separate patch.
Posted 23 October 2018 - 09:33 PM
My first idea is that messy brushwork flubs the render so you get black like that along a seam usually from the bad brushwork. That typically means building off of the grid, like a tiny sliver of brush sticks out, there's a tiny overlap of two brushes, or a tiny gap between two brushes, or two brushes meet at a tiny angle, or any combination. The solution is to rebuild the thing on the grid with cleaner brushwork. Or like grayman said, convert it to a func_stat as it doesn't look like it has to be sealing anyway.
Posted 23 October 2018 - 10:03 PM
Posted 24 October 2018 - 12:46 AM
I'd be curious to see a wireframe of what that section looks like with r_showtris.
During compilation the engine is looking for ways to simplify and optimize brushwork. It's culling away surfaces that won't be seen. It's merging bits with the same material, texture alignment, and normal. Then it's trying to figure out how to triangulate what is left. Sometimes the compiler gets it wrong. There's no real way to avoid that short of constructing the bulk of your map out of models where you can explicitly specify how the resulting mesh should be constructed.
You might however be able to coerce the compiler into doing a better job by building the staircase, or even just the problematic portion, in a different way. Here's a few examples with a mock-up of the original on the left...
Posted 24 October 2018 - 02:25 AM
The other work around for this os to make step tops FS,
So in this instance I would use the third method show in Rich's image above, where the small step-caps and triangular parts are made FS. Then because Ai and the player tend to trip over the little bits of the cap that jut out, you make the whole FS non-solid and then place simple nodrawsolid brushes of the matching material, (stone, wood, etc) where the triangular parts of the steps are.
I can make a little video for you if you like.
Posted 24 October 2018 - 06:49 AM
That looks to me like dmap causing a bad cut in the geometry at compile time, perhaps if you manually cut the last big steep at the top level of the smaller one touching it?
| | |
| | |
| | |
Posted 24 October 2018 - 10:16 AM
To convert to a func_static, simply select all of the brushes that you want to become one func_static, right click, then scroll down until you see convert to func_static in the drop down menu. It looks like you can convert that entire staircase into one func_static, because as grayman said, it doesn't look like its a sealing brush
Edited by Amadeus, 24 October 2018 - 10:17 AM.
Posted 24 October 2018 - 12:43 PM
That last pic shows that dmap created a n-gon (geometry with more than 3 edges). Everything should be triangles (geometry with 3 sides) showing that you need to cut that stairs manually until that doesn't happen (or someone on the engine team finds why dmap breaks down on that).
Not saying that it doesn't but why converting to a func_static would solve bad dmap triangulation?
Posted 24 October 2018 - 11:51 PM
@Zen3001, could you share the map? (question for others: should he share both the .map and .darkradiant, or is just one of them enough?)
Could you maybe also share your dmap log for comparison?
(to get the dmap log in a text file use the console command clear first (to get rid of unnecessary garbage), then dmap your map, then do condump dmaplog.txt. Then share the content of dmaplog.txt -- dmaplog.txt is an arbitrary name, you can call it whatever you want. You can check the condump command here, near the bottom.)
Edited by Skaruts, 25 October 2018 - 12:09 AM.
Posted 25 October 2018 - 10:01 AM
something in dmap is causing triangles to be recorded in the proc file the wrong way round, usually corners in triangles are recorded as 0,1,2 but where the triangle seems to be missing its being recorded as 2,1,0.
If you go inside the box with the missing triangle you can see it drawn on the wrong side of the box, eg the inside of the box, and not the outside.
Posted 25 October 2018 - 10:25 AM
Not just that, it's not cutting triangles below the step (the wooden board), as it does below all the others. That empty triangle should be 3 triangles.
I just forgot to change the texture of two boards from caulk to the wooden texture, nothing wrong with that.
0 members, 0 guests, 0 anonymous users