pretty much whenever i edit a brush, like playing with the vertices or whatever, it changes color.

one thing i do is right click on a brush and go to properties, click ok and it changes color.

i'm guessing the answer is no then. :( 

I have several flying monsters spawning in close proximity. Although they have some delay between them, occassionally one will spawn on top of the other and I get blood-n-guts all over the place. It seems that trigger_push and trigger_monsterjump do not work with flying monsters. Any ideas on how to avoid this kind of issue without resorting to qc, other than not to do it in the first place? 

to say for sure, need to see this place. trigger_monsterjump does have tested. If the monster is already flying, it does not work. Maybe there is an opportunity to put between the trigger pad covered with textured skip? Then he landed on it and no longer flying 

i don't think that will work as the fl_onground flag (which is what is needed to be on in order for monsterjump to worok) is never changed or explicitly set during teleport so if the monster didn't have it set, then it won't have it set after teleporting. 

Yes, now I've looked at the qc I can see why. I had promised myself no more messing with the devil. I seem to be endlessly 'tweaking' just to get one effect, so I will leave it alone now. If the player gets lucky, so be it.

You never know, I might even finish this map. It's four years and counting: architecture was finished not long after I released the first half of FMB-BDG, lighting about a year later, monsters went in end of last year, play-testing and looking for music this year, and I'm getting older by the minute... 

I was fooling around in Worldcraft today trying to align textures on brushes aligned at 45 degree angles when it occurred to me that someone might have already figured out the correct ratio not only for this, but for most angles in general. Has anyone formulated a table to get proper alignment on textures, scale included? 

so I have a map vising that finished today (this is bsp2 tools), and right after it said left 0:00, 100% as if it was done, it then said *********** ERROR portal not done. I haven't come across this before, uhh... does this mean the entire vis time was wasted and there's some kind of vis-killing problem in the map?

(that would only show up after its 100% done after 333 hours? lol). 

...Ouch :/ 

For 12 sided circles etc I think your angles are often 63.5 degrees (to the nearest half a degree) and 27.5 degrees. Scale for the textures on one of the diagonal sides is 1.06

Stuff I remember :) 

~0.71 is correct

0.75 is sometimes better to make edges align to grid. 

I had figured out the rotations for the 12-sided cylinder, but never the scale. Thanks for both, they're going in my own 'Mapping Tips' document. 

I ran into that error when vising my coag3 map with an older version of WVIS that had a bug with the state save function - interrupting the vis process caused unfinished portals to be left 'open' instead of resetting their progress altogether. BJP then sent me an experimental build of his VIS tool which had a -finish switch that would disregard such conflicting portals and force the vis job to complete.

Now, your problem appears to be different insofar as the WVIS bug was fixed in the final version and the BSP2 tools are based on that source. Or are they - can someone check?
Problem is that, presumably, BJP's new vis won't work here, because of the different BSP version and specifications. Still, you could contact him and see if he's got an idea. 

I doubt I will be able to contact aguirRe these days, though he formerly was one of the best guys to talk to regarding mapping. I'll try him but I'll also try RMQ team / mh who I think (?) is the major tools developer. It could be a very old, rare and gay bug. But I reserve the right to be formally offended to only find out that shit's fucked after 333 hours. It's like a relationship, except even worse (333 hours into a relationship ought to have bought you the notification that you're doomed - long ago!). 

I know the engine uses the serverflags to store information about if the player has the runes or not, what is the rest of the flag used for? Can it be used to store other information that can be used between maps? 

The rest is not used. And if the server does not cut the value of serverflags, I think it can be used 

The scale is the sine of the angle. Like Metlslime said, for 45 degrees this is 0.707. Instead of rotation you often actually need to do negative scaling. Try putting a texture with text (like trigger) or some other obvious left/right or up/down differences and you will see what I mean (also, it needs to be the same size as the texture you will actually use). 

Yes, it's possible. And apparently one can store more than you would expect at first glance if done right. Kinn, and if I'm not mistaken necros and Preach, talked about it not long ago, but I can't remember in which thread. 

Awesome, thanks for the reply, I was not 100% sure and I did search for serverflags in this thread but could not find anything. From my tests it *seems* to work fine. The things I want to remember across map loads affects every client so I am not worried about that. I know about the parm system but I am surprised there is not more use of the serverflag solution. 

yes, we did. :)
http://www.celephais.net/board/view_thread.php?id=4&start=11760&end=11772 

Kind of mixed it up, and still had that one "meta hack" thing in mind, too.... Whatever works, right? 

I had never used the light key _anglesense for the light program (was not in my FGD for hammer).
After a bit of trisouping I found I had dark spots at the corners. _anglesense .1 cleared it up.
Good info thank you
http://necros.slipgateconstruct.com/guides/lighting-basics/

Some info on trisouping
http://www.katsbits.com/tutorials/idtech/trisouping-bsp-brush-based.php 

Glad that was helpful. :) 

Negke, why did you use Netradiant?
Necros, why did you use Sikkpin's variant? 

At this point, i want to use netradiant, but I can't figure out how to load textures in it. :P

I really like Sikkpin's variant, but there is a critical bug somewhere which prevents me from making more complex geometry. Specifically, it is rounding off vertex coordinates when I do not want it to, which tears apart multi-brush objects I've built when trying to rotate them to non-axial angles.

Currently, I'm waiting for Trenchbroom. :) 

the vertex rounding may not actually be a bug, but rather intentional to prevent problems when compiling, but I think off grid vertices are not the cause of compiling problems which is why I don't consider it a good thing in the editor atm.