Here's a brush from the map file
( 193.373 -320.665 600 ) ( 192.665 -321.373 600 ) ( 216 -343.293 600 ) COP1_2 [ 0.707093 -0.707121 0 -11.127 ] [ -0.707107 -0.707107 -0 -59.0101 ] 0 1.00098 0.999997
( 215.293 -344 632 ) ( 192.665 -321.373 632 ) ( 216 -343.293 632 ) COP1_2 [ 0.707114 -0.707099 0 -11.4788 ] [ -0.707107 -0.707107 -0 -59.01 ] 0 1 0.999997
( 216 -343.293 632 ) ( 216 -343.293 600 ) ( 215.293 -344 632 ) COP1_2 [ 0.707099 0.707114 -0 59.0142 ] [ -0 -0 -1 56 ] 0 0.999997 1
( 192.665 -321.373 632 ) ( 192.665 -321.373 600 ) ( 193.373 -320.665 632 ) COP1_2 [ 0.707099 0.707114 0 59.0139 ] [ 0 0 -1 56 ] 0 0.999997 1
( 215.293 -344 632 ) ( 215.293 -344 600 ) ( 192.665 -321.373 632 ) COP1_2 [ 0.707107 -0.707107 -0 -11.4797 ] [ -0 -0 -1 56 ] 0 1 1
( 193.373 -320.665 632 ) ( 193.373 -320.665 600 ) ( 216 -343.293 632 ) RUNE_A [ 0.707107 -0.707107 0 -11.4801 ] [ 0 -0 -1 24 ] 0 0.999999 1

Horray for guinea pigging new level editors 

In JACK you can free rotate a selection of vertices in vertex edit mode around a pivot point under your mouse cursor by right click -> dragging in the 2d view. Even if you go back and move the rotated verts back onto grid after the operation they will be off by a tiny amount, resulting in the crazy decimal points.

So : PSA - Don't use vertex free rotate mode! 

http://i.imgur.com/2qIIzYV.png

So, I recently converted my map from standard to valve 220 format, thanks to ericw's recent tool update. As nice as textures not "shearing" all of the time when you do weird and kinky things to your brushes is though, I find myself missing the nicer way that standard format seems to handle textures wrapped around curved brushes.

The image linked at the top of the post is an example of this - both are valve 220 brushes, but the left one has texturing from before I converted the map, and the other has had its textures freshly "reset" to no offset/rotation/scaling.

Does anyone have any tips for getting the sort of look that the brush on the left has for "new" brushes? I imagine it must be possible in the format still, but it obviously does not come naturally... 

Getting this error in Quakespazm. Solutions I've tried is using the find/replace feature in notepad to remove all water/sky textures from map, and also tied "-subdivide 256" on the Txqbsp command line. (without fully understanding what it does.) It still fails to load.

I'm beginning to think that the issue is architectural. i.e. too much visible to player or something. Could that be the case? The map on a fastvis was in the ballpark of 30+ megs which is something I've never seen before. And if thats the case, is there anything I can do to salvage the map?

in editor screenshot:
http://i.imgur.com/4b0xReO.png 

It's definitely not too much architectural detail, most likely bad texture alignment on a face.

My light tool used to print an error for this with the texture name and coordinates of the face to aid fixing it, but it looks like that message was broken at some point. I can take a look at the bsp if you want. 

I'm trying download DaZ's .fgd from post #18307, but I get the 404 error.
Where I get JACK-compatible .fgd for vanilla Quake and Ericw compilers? 

I had this error recently, you may have a brush somewhere with a texture that is either squished waaaaay to small or stretched waaaay to high.

I ended up pasting the map file into excel, using spaces to delimit the rows, then sorting by the last row to see the highest and lowest values.

I don't know what the exact limits are, but I would get rid of any texture that is scaled smaller than 0.1 or larger than 5. 

if you notice in the SS, that none of the textures are aligned, that is because I selected all and reset textures in an effort to solve a problem with texture scale that was causing BSP to fail.. It worked but loading the map would still crash the engine. "Bad Surface Extants." it says.

I managed to compile a "working" version of the map by placing a giant brush in the middle of it, effectively blocking view to the other side. It runs fine apparently in Quakespasm no problem but the map was targeted for quakeworld and in QW its a disaster.

QS SS: http://i.imgur.com/22j6yh3.png
QW SS: http://i.imgur.com/4QWcwXM.png

I thought that running a full vis overnight might solve the QW issues but when I woke up it still had 33 hrs to go. Also in QW it takes some time for it to load and you need the -mem 128 command line too.

It was a lot of fun putting this map together but find that working within the the perimeters of QBSP and engine (somewhat restrictive) capabilities to be an unforeseen challenge. I'm still compelled to work on it, but a lot of my focus will be on scaling it back, or salvaging the more clever brushwork (by my standards) for more sensible application.

I loved mapping for Quake back in the day and find that modern editors are so fluid and responsive that it's very easy to become drunk with power. 

Which compilers did you use - does this occur with bjptools_xt or tyrutils_ericw? 

TxQBSP 1.13 I want to experiment more with the existing compilers though. 

Make sure that your faces are all set to 'world' alignment, not 'face'. (P.S. world/face terms used by Worldcraft/JACK/Hammer and may not match terminology for your editor) 

is so similar to a map I was working on over a year ago it's crazy... it took me a second to realise it wasnt the same map. 

This link should work for the fgd https://www.dropbox.com/s/lv4r7tmcspcz2gt/quake4ericwTools.fgd?dl=0 

Big thanks for this. 

how to create transparent glass? 

Introduce manganese dioxide into the manufacturing process. 

... is your friend ... (but I didn;t have link in mind where you could find it)

OK, others, please correct me if I do not remember properly:

1/ Create a brush using a "plain" water texture (i.e using only one color) and name it *<watername>: this wil be your glass

2/ Create a func_wall of the exact same size, and use a skip texture there

3/ Add skip tool in your list of compilation tool, after bsp process (bsp/skip/vis/light). So ultimately the func_wall will have its texture removed but remains solid (you can't pass through it), but the "water" texture remains gicing the glass texture visual.

4/ Load the map, and adjust r_water_alpha value in the console to a value that is below 1.. the closer to 0, the more transparent the glass.

Enjoy ! 

An alternative way is to use a solid color texture (such as grey) and make it a func_wall.

Add an alpha key with value of however transparent you want the glass (So .65 for example). 

... but I am not sure this is supported by all engines... not even sure the other techniques is working with all engines either.. though... 

https://www.quaddicted.com/reviews/mfxsp17.html

This map has an example of glass. It comes with a .map that you can look at to see how it was done. 

Neither technique would work with the original engines as far as I know, but I'm pretty sure that the alpha key has been a thing for a while... someone correct me if I'm wrong of course. 

alpha key doesn't always work as intented. I usually make teleporters' liquid a func_wall with alpha 1, but it often looks transparent anyway (I noticed that in videos/streams) 

Quakespasm supports seperate alpha for water/slime/lava/telefluid set in worldspawn just fyi :) 

What are the potential problems if exceeding the vertexes limit? I'm pretty much right at it now. However, only just noticed that I had exceeded it by roughly 4000 in MCE with no apparent downsides that I'm aware of?! 

Quakespasm supports seperate alpha for water/slime/lava/telefluid set in worldspawn just fyi :)

I must have missed it.