what's mean "Too many t-junctions to fix up!" ?

  • Site Migration: See bugs? Report them here. Want something changed or have an idea? Suggest it here.

pasta masta

L1: Registered
Nov 9, 2017
i tried compile my map many times but no renewal, can't find diffrent point before

Too many t-junctions to fix up! (2842 prims, max 32768 :: 65556 indices, max 65536)

this thing is my problem how to fix "t-junctions"?


(*single chuckle*)
Apr 10, 2014
so how to before trigged? (func_detail -> none)

What you should do instead of removing all of your func_details, is to convert some of them in to world brushes. Since too many caused the problem, you should only need to get rid of some.


Mar 1, 2010
Okay so the more complex answer is that tjuncts are anywhere a func detail brush touches a world brush, or another func detail brush. Too many of these tjuncts and you get the error you have.

One of the most common places a lot of these are caused are where stairs meet their trim or the wall. An easy fix if you have trim is to make the trim itself func_lod or func_brush, which would stop a tjunct from being made for each step.

Another common place is where a bunch of support beams all meet, like say a central beam. Turning that beam into one of the above mentioned entities can help reduce them.

Mind you with the above fix, your are adding to the entity/ edict count, which is another limitation you have to keep in mind.

Another way to fix a lot is turning some of your more detailed brushwork into models.

After that, reducing detailing certainly doesn't hurt.

You can monitor your tjuncts with the waterindices section of your compile log.

Tjuncts are a big pain in the ass and often pop up with late stage very detailed maps. So congrats if that's where you got!