That's what I thought they meant.But why not just use the cordon tool to make a big box of 2D sky around the map instead?
Last edited:
That's what I thought they meant.But why not just use the cordon tool to make a big box of 2D sky around the map instead?
I actualy still do this while the map is in alpha state (realy, if this extra processor cost would already be a problem in alpha, there are much bigger problems in the map). So for timesaving i actualy think that during alpha its a good thing to do that. Although when doing that a normal compile on vvis should still be done since the small tricks a fast compile can normaly do, these no longer work with such poor skybox. It shouldnt be any problem to render almost the entire skybox around it because in the later versions of the map, the detail is going to be way heavier.
Kinda, but it causes weird problems with lighting and seeing through roofs. That's why its on a list of stupid mistakes.waitwaitwait... nodraw can be used for clipping?
Its just a habit, i do those temp skyboxes in a visgroup so i can always turn them on when needed. Which is a good thing during test compiles in a beta. You can quickly turn on the group to see if the detailing you did ended out the correct way. Where you can keep the cordon to just limit hammer in its visibility which on larger maps can prevent a cluster of lines in the top, side etc views.But in that case, why not just use cordon?
Its how they clip the tank above the hatch in mvm maps.would you tell me that nodraw works?
You'll never cut my visleaves!![]()
I have become death, destroyer of worlds.
I really hate that section not resetting back to Block after switching to Arch or Sphere, but I'd probably be more annoyed if it did.![]()
I have become death, destroyer of worlds.
That's why modern software's philosophy is the more stuff has settings and is flexible, the betterI really hate that section not resetting back to Block after switching to Arch or Sphere, but I'd probably be more annoyed if it did.