@onetruepuple - Very useful, thanks!

@Preach - That is very good to know. 

I tryed enter:

/Users/usuario/Desktop/QuakeFolder/MapID/maps./"qbsp" Qf1m1.map

/Users/usuario/Desktop/Quakefolder/Quake/MapID/maps./"qbsp" Qf1m1.map

cd ~/Users/usuario/Desktop/Quakefolder/Quake/MapID/maps./qbsp Qf1m1.map

cd ~/Users/usuario/Desktop/Quakefolder/Quake/MapID/maps/qbsp Qf1m1.map

and more.

I can`t qbsp, vis, light with tyran utils in mac, the binnaries are recognized as unix file... 

Where is the file "Qf1m1.map", and where is the qbsp executable? Are they both in
/Users/usuario/Desktop/Quakefolder/Quake/MapID/maps? Are you sure this is the correct path? If so, what you need to do is open a Terminal and type:

cd ~/Desktop/Quakefolder/Quake/MapID/maps

Press the "enter" key, and then type

./qbsp Qf1m1.map

and press the "enter" key again. 

I have qbsp in maps folder, but this action too I was done 

Do doors not block light? 

all func_* (b_models) do not block lights.
you can set a key on them, shadow 1. with this they will cast shadows, but no dynamic shadows.
So a door that is closed will have a shadow, but opening it wont remove the shadow drawn.
Can look strange and all. 

I downloaded ericw/tyrutils and now it works perfectly ;D 

@mfx That's also good to no. Fortunately I didn't need to implement shadow 1 after messing with the troublesome lighting. Lighting is hard! 

I added the "centroid" to quake.fgd, next I put scor.mdl and h_scourge.mdl to directory(obviously tested), next I added it to TB map, but when I test the bsp of this, the centroid not exists...

I need some other file? 

you're missing the centroid code my friend. I'm not sure if Scourge of Armagon's source has been released for you to compile a new progs.dat.

The next best bet is to map for a mod with it included. I think the Drake mod has it but I'm not sure any others do. 

Ok, when release my game obligated to make a .pak. 

 

 

func_plat starts in up floor, I want to stop it when be down, but I also want the plat up when player leaves it... 

Not sure I understand what you want to do, but keep in mind that you can use a func_door (or even func_door_secret) to create a lift in a map.

A func_plat always starts at the bottom and moves up, but with a func_door you can create a lift that starts at the top and moves downwards (which sounds like what you are trying to do).

This might help a little:

http://www.quakewiki.net/archives/worldcraft/entity/standard/std2.shtm#9

http://www.quakewiki.net/archives/worldcraft/entity/standard/std2.shtm#5

http://www.quakewiki.net/archives/worldcraft/entity/standard/std2.shtm#6 

I forget that I watched it in the map source 

I've been trying to make a first test for my map but vis can't get compiled because of lots of func_wall that I used on a group of brushes so I could select them easier (TB1).
Is there a way to turn them back to worldspawn brushes? Just putting "worldspawn in their classname doesn't seem to do anything. 

Or something similar.

I think that is what you are looking for? 

 

In vis appears "couldn't read Qf1m1.prt" and is not there in "maps". Also when I test my map some boxes are not existing in the place I put and when I put "noclip" I look the same box in back floor or simply was not reached in game, with the most of the items it happens.

I want to know if is problem of the .prt file or another thing I don't considered.
Thanks✩ 

Actually I never hit such issue, so, maybe it is just a path declaration problem when runing the tool (I would look for the prt file and try to figure out whether it exists... and if yes, where it is located first)

Also, is it happening with fast vis or full vis ? 

Fast & full? (?)
http://prntscr.com/behjj0
I have vis in "Quake/MapID/maps" for a custom mod, but when is time to vis the Qf1m1.bsp "couldn't read Qf1m1.prt"

I don't know if the .prt file is generated by qbsp or light, and also I don't know if .prt file has an important rol 

Your map probably has a leak. The PRT is generated by QBSP, but only if the map is sealed.

TrenchBroom has a "Load Point file" command that usually shows where the leak is.