foogs, kinn is right. If you're using ericw's fork of the compiling tools you can add -dirt to the command line. Or add it to the worldspawn. Either way it will add some extra depth to your scene by faking ambient occlusion. 

Yeah and you'll want to goon around with the various dirt settings. Here's a handy visual guide!

http://ericwa.github.io/tyrutils-ericw/ 

Moved a few items around and added an extra room after getting rid of the big ramp.

http://www.mediafire.com/download/94w8mbq7alssjy6/spz1dm1_14Oct15.rar

After this I vote I'll need some help lighting spz1dm2 

I like the addition of coloured lighting, looks nice. Map looks a lot better now. Still a few things I would clean up, some of the trims near the lava need to go all the way to the end of the platform edge for example.

But my quibbles would be minor at this point. 

i just realized i was doing lighting with gamma 0.5. no wonder why everything is so bright :(, But it's what I play with though :( So I guess I should do lighting with default gamma in quake? 

gamma should be 1 when mapping because that's the default. 

disagree, gamma should be used to make the stock ID levels look correct on your monitor, then you should make your levels similar to the brightness of the stock ID levels. 

 

Just had a look at the map and no idea how I missed that. Thanks for the heads up. 

The last time I asked for help with Screenies I was told to put it in the screenshot thread instead of Mapping Problems so here goes:

I have two different compilers on the PC: Txqbsp and Tyr_qbsp(renamed so that I could differentiate).
Both of them are giving me texture alignment issues (IE they don't match what I see in TB)

With Txqbsp this happens:
http://www.quaketastic.com/files/screen_shots/spz1dm1_txqbsp.jpg

and with Tyr_qbsp this happens:
http://www.quaketastic.com/files/screen_shots/spz1dm1_tyr_qbsp1.jpg

and generates 5 warnings:
"*** WARNING 12: New portal was clipped away in CutNodePortals_r
*** WARNING 12: New portal was clipped away in CutNodePortals_r
*** WARNING 10: Reached occupant at (-720 -688 294), no filling performed.
Leak file written to spz1dm1.pts
*** WARNING 22: Healing degenerate edge (0.000000) at (208.000 -1264.000 512.000
*** WARNING 22: Healing degenerate edge (0.000000) at (224.000 -1248.000 480.000"

leak being here (my teleport entity might be extending outside map, I'll check)
http://www.quaketastic.com/files/screen_shots/spz1dm1_tyr_qbsp2.jpg

1) Why? and...
2) What do? 

I forgot to add that after some Trigonometry calculations the angle to get the textures to line up correctly in spz1dm1_txqbsp.jpg is 26.6� 

You can likely fix the second one by passing in "-oldaxis" or whatever the flag for that compiler is. It flips the 45 degree determination logic... 

check the coords given, there is a hole in your map.
You can put the .pts file into your /maps folder, load the map in engine and via "pointfile" command check where the leak is located. 

i read only the half of it.

Note that liquid brushes (*prefix) dont seal your map, so it looks like that teleporting brush could be the cause of the leak. 

The strange thing is with txqbsp the leak doesn't happen. There's a solid wall behind that teleporter brush. I just checked the entity after my post earlier and that's also not outside the map. Possibly due to the supposed leak it does not vis with tyr_qbsp either.

-oldaxis worked by the way thanks. 

You can also load the pointfile in TrenchBroom if it's in the same directory as your map file. 

It's under the File menu. After that, you can ride on the point file trace, look in the View > Camera menu to find the shortcut keys to advance / retreat the camera. 

Loaded up the pointfile in TB but it seems to go straight through the middle of a solid brush, not the joins of any. It seems placing a teleporter entity at a 45� angle is a bad idea =P

Would it be too forward to ask somebody to have a look at it? 

first try to delete and remake that brush, if you haven't already. 

After various cases of "Is it this one? Delete, recompile, No!" etc I just deleted the whole lot and started again.

Good news: No leaks
Bad news: wtf...
http://www.quaketastic.com/files/spz1dm1_wtf.jpg
(could have sworn i was in the screenshots directory, oops...) 

Yep, thats a missing face, check for floating point inaccuracies.

Or even duplicate brushes at that spot. Or or or.

Try to keep the brushes on grid and their texture alignments too. 

Snap the verticies of all nearby brushes. I think it's under edit? Or Tools maybe. 

Okay, figured something out. No matter what the brush looks like, as soon as I add it inside this area, that wall to the in the WTF screenshot gets the missing face. Even these 2 pillars I have in now cause the same issue.

http://www.quaketastic.com/files/screen_shots/spz1dm1_TB.jpg 

Just ran a test. Compiling the exact same .map with txqbsp instead of tyr's and that brush works fine. 

In my experience those sort of differences between tyrutils and txqbsp are usually due to the different default epsilon values the compilers have.

For research purposes: try passing the flag "-epsilon 0.0001" to txqbsp, it should bring back the flickering face. The next version of my tyrutils-ericw will support that "-epsilon" flag so you can tweak it.

However, as ijed says there are probably some off-grid brushes / small misalignments that are the root cause.