I always come back to this: to heck with the numbers, make it fun. 

I cannot caveat enough that such measurements are of little exact use. It's good for ballparking it and discovering "oh shit I'm way off" and don't trust it more than that. 

Hello! Does anybody know if there is a special utillity for converting .obj to quake 3 patch? Also, where can I find any documentation about q3 patches? 

Or use a model! 

Hi!
Have a problem with my map that I don't know how to fix.
After finnishing all and testing, in the first room, a black rectangle appears on the floor with the sound of a teleport. I can't remember that I made one and even can't find it in the editor.
Is there a way to search for things in trenchbroom or other ways? 

I would go to the spot in the map in TB and "drill down" to see if there's a brush embedded in that spot in the map. IIRC you hold control + mouse scroll wheel to drill down your brush selections. Of you can hide the floor brush to see if anything is below it. 

I haqve deleted the floor and theres nothing. I've also been going downward if theres something below. Also nothing. I have no clue? A bug? I've posted the map on screenshots and betas. 

in game:

"r_showbboxes" will draw white outlines around all entities, this will confirm there is an entity there. (NOTE: i don't think this shows static entities)

(alternate: set "r_drawentities" to 0 which will stop drawing all entities, including static entities -- another way to confirm this is an entity)

"edicts" command will list all entities in the console, problem with this is that brush entities all have the origin of 0,0,0 so you need to look at absmin/absmax or something to figure out which one is the one you are looking for. (hint: condump this to a file since it's easier to read in a text editor.) 

THANKS!

With r_shobboxes 1 I found a brush that moved somewhere and made me trobles ago. Deleted it and that was it. Bohh! Thank you so much!!!
Hope you're doing fine and find some time to play my map.

Best wishes!

GunSgtHighway 

:) 

Haha! :D Thanks for assistence! :D 

Is there any documentation on these two AD entities? I can't find them in the ad_v1_70P1_documentation.txt, and I can't get the func_insidevolume to detect the pushable and send an output to a func_door, even though I have the "pushable" flag checked. 

These were added/modified very close to release. Probably why no information.

Did you open the "test_pushable" map to see how to set it up? 

1)Create a brush then --> tie to entity > func_pushable, no other parameters needed.

2)Create second brush then --> tie to entity > func_door, then give the door a name Ex: "PushableOpens".

3)Create your last brush and --> tie to entity > func_insidevolume, give it a Target(fully inside) of: "PushableOpens". Uncheck all flags but Pushable.

Tada!

Now I don't remember the specific conversation with sock but there was concern for this: "Name of target(s) to trigger when something is FULLY INSIDE the volume (fires every 0.1s)."

Namely, the constant firing. I think that's why there's more complex setups for these. But you could select "Only ONCE" for "wait", for the func_insidevolume if that will work for you?

hth's 

Or if it does do constant firing, just target a trigger_relay set to once. Only have the trigger_relay target the actual door.

My guess is it has to do with needing the pushable fully inside rather than just touching like a trigger. 

Thanks! You hit the nail right on the head - I did not know the pushable had to be completely inside for it to work. Did a few more tests and it worked exactly as it should.
I'm a bit annoyed that pushables, that doesn't move, don't block gasshooters but this allows me to do a workaround for that. 

You could use Target2 also, which is when a pushable is "partially inside" the volume ;)

Also, I'm a bit confused on the pushables that "don't move" comment? Maybe you mean when you are not pushing them? 

I tested it. Yeah, pushables are not solid to the gasshooter at all.

Seems an isolated case, versus the other trap types I tested('nades, spikes etc). Prolly not that hard to "fix". 

Hi. Do someone know if there's a way to create longer messages than one line? and maybe change its colour? 

Yes, you can just move to another line by adding \n.
Just like this. “Hello, this is my message \n how do you like it?”
In game it will be seemed like this:
Hello, this is my message
how do you like it? 

Thank you very mutch! 

Color is possible in Darkplaces but you only use normal white or orange (bold) in all other engines like this:
\bImportant Message!\b\nNotice, thank you for noticing\n this notice.

For Darkplaces or QuakeLive engines:
The color codes are as follows:
^1 = Red
^2 = Green
^3 = Yellow
^4 = Blue
^5 = Light Blue
^6 = Magenta
^7 = White

E.g:

^4BLUE TEXTBOOK\n^7Normal white message.