Blender seems like a great tool to create terrains and other "advanced" brushwork. Here is a long but easy way to get a Quake 1 map from the Q3 .map export.

-First a dirty hack. Edit the export_map.py. A bit below "# Split mesh into connected regions" change "write_face2brush(file, f)" to "write_cube2brush(file, face_group)". I suggest saving under a new name (top of the file) to avoid confusion.

-Create your stuff from single brushes. You can use the first brush as base.

-Move vertices around happily (with snapping I suggest) and don't forget triangulation on faces that need it (if you get gaps and "wrong" brushes exported, this will be the reason). Ctrl-T and Ctrl-Shift-T (for the other diagonale) do this. You will need to do it on faces that create a new edge.

-When you are done, export: File -> Export -> your q3 script. If you use 64 for scale, the first brush will equal a 128� brush, 32 will get you 64� and so on. I think the Grid Snap is a good idea, haven't played with it yet.

-Open the .map in QuArK (Quake 3). Copy the brushes into a Quake 1 .map. Save that .map.

-Open the Q1 .map in a texteditor and replace ".00000" with "" if you feel like it. You must replace all " 0 1 1 0 0 0" with " 0 1 1". (If there are 0.xxxxx values, well those too. I haven't really figured out where those sometimes sneak in yet.)

Done! 

Before exporting, make sure to select all brushes (a). 

First I had to convert the brushes in the sprite upside down, as I only got an upside down sprite in game.

This is actually a bug; sprites are drawn upside-down in glquake and a lot of engines that are based on glquake. 

i didn't really explain properly:

$frame 1 2 3

void() can_stand1 =[ $1, can_stand2 ] {ai_stand();};
void() can_stand2 =[ $2, can_stand3 ] {ai_stand();};
void() can_stand3 =[ $3, can_stand1 ] {ai_stand();};

should be



void() can_stand1 =[ 0, can_stand2 ] {ai_stand();};
void() can_stand2 =[ 1, can_stand3 ] {ai_stand();};
void() can_stand3 =[ 2, can_stand1 ] {ai_stand();};

all those $frame1 $frame2 crap does is start counting up from 0 and assign a number, so when you do like

$walk1 $walk2
$run1 $run

$walk1 = 0
$walk2 = 1
$run1 = 2
$run2 = 3

and your model would have the two walk frames as the first two frames, and the two run frames as the last two. (they have to be in that order) 

and as far as i can tell,

$cd /raid/quake/id1/models/can
$origin 16 16 24
$base base
$skin base
is completely useless and doesn't do anything.
it was only there when id compiled the old models using their old tools. now with qme and such, that isn't necessary. 

Thanks for your answers, it was really a mystery to me how to get sprites inside Quake.

metlslime - I already thought I did something wrong. FimG shows all the other sprites right, but it is something to remind.

preach - that works great. I have already your tutorial on my disk, but reading it again won't do me harm. It gives more insight in the statements.

necros - thanks, that makes the script shorter and reasonable to use.

For now the sprite runs good, but I can't place it on buttom. If I use:

setsize (self, '0 0 0', '12 12 24');

the can appears excact on the half. 

found it. placing them better in Quark. 

Someone could do a cheatsheet image (or webpage) showcasing a multitude of settings and setting combinations from aguiRre's Light.exe.

RE:Blender:
It sure is fun (especially if you are used to a crippling editor like QuArK) but the need for manual triangulation ruins half of it. Maybe there is an automatic way, I haven't found it yet. It would be great if concave brushes would automatically split into smaller convex ones, heh. Also if there was a way to split meshes into cubes, woohoo. There are some nifty generators, maybe there is a way. r_speeds be damned!
Using a pure 3D "interface" surely feels different and to me it also inspires.

http://www.quaketastic.com/upload/files/screen_shots/spirit_blender1.jpg
http://www.quaketastic.com/upload/files/screen_shots/spirit_blender2.jpg 

"It would be great if concave brushes would automatically split into smaller convex ones, heh."

I tried to add that feature to ToeTag for ages - it's not as easy as it sounds. Would be hella nice though. 

H� Willem, I was surprised to see that screenshot on quaketastic.
I'm already a long time mapping on the Doom's Hangar.
So I was quiet surprised seeing someone who had actually done it. 

Where is the 15 character texture name limit set in Quake? Is it the WAD format, the compiler tools, the engine(s)? How hard would it be to get rid of it? 

The WAD format is a huge part of it. Because of that, to change it, you'd have to change all of the engine and tool code that references WAD files. 

Damn, that is one restriction I just cannot comprehend. 

You should look into how MDL files are stored and de-coded sometimes. Now THAT'S a mind bending nightmare. 

a lot of quake tech was sufficient for what id wanted to do, so they never bothered to worry about it. 

Stores vector min, max; as floats, then the vectors for everything else are stored as unsigned bytes, with 0 being the minimum possible value for the axis and 255 being the maximum possible.

Did I miss anything? 

"Did I miss anything?"

That's the overall concept, yes. Have you written code to actually parse that out of a PAK file? It's a nightmare. 

My "Blender fix" will leave you with many many MANY duplicate brushes. I obviously did not know what I was doing. Well, I don't think anyone except me uses it but still, just be aware so far. 

Someone could do a cheatsheet image (or webpage) showcasing a multitude of settings and setting combinations from aguiRre's Light.exe.

AguirRe?

And don't forget to take the screenies in software AND GL, because especially minlight using areas look vastly better in software (as do torches, candles etc). This goes as far as walls appearing to be a different color.

:-P 

But all that depends on which monitor you'll be looking at the pictures on, and what it's settings are. 

1) I have a complex door (in terms of brushwork) and I want to duplicate it as a set of brushes. How can I change an entity into brushwork?

2) I have a map that is on the limits (marksurfaces, clipnodes etc) and one of my complex doors does not appear in-game. Common problem? 

call the .map file up into a text file:

{
"spawnflags" "2048"
"classname" "func_door"
"targetname" "t34"
"angle" "-2"
"wait" "-1"
"speed" "50"
"sounds" "4"
"message" "These bars are opened elsewhere..."
{
( -304 904 -192 ) ( -304 880 -192 ) ( -304 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -272 904 -192 ) ( -304 904 -192 ) ( -304 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -272 880 -192 ) ( -272 904 -192 ) ( -272 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -304 888 -192 ) ( -272 888 -192 ) ( -272 888 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -304 880 -128 ) ( -304 904 -128 ) ( -272 904 -128 ) MET5_1 0 0 0 1.000000 1.000000
( -272 904 -256 ) ( -304 904 -256 ) ( -304 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
}
{
( -368 904 -192 ) ( -368 880 -192 ) ( -368 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -336 904 -192 ) ( -368 904 -192 ) ( -368 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -336 880 -192 ) ( -336 904 -192 ) ( -336 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -376 888 -192 ) ( -344 888 -192 ) ( -344 888 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -368 880 -128 ) ( -368 904 -128 ) ( -336 904 -128 ) MET5_1 0 0 0 1.000000 1.000000
( -336 904 -256 ) ( -368 904 -256 ) ( -368 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
}
}

eliminate this part first:

{
"spawnflags" "2048"
"classname" "func_door"
"targetname" "t34"
"angle" "-2"
"wait" "-1"
"speed" "50"
"sounds" "4"
"message" "These bars are opened elsewhere..."

go to the bottom of the entity and eliminate the last curvy bracket:
....
( -336 904 -256 ) ( -368 904 -256 ) ( -368 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
}
}

so it looks like this:

{
( -304 904 -192 ) ( -304 880 -192 ) ( -304 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -272 904 -192 ) ( -304 904 -192 ) ( -304 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -272 880 -192 ) ( -272 904 -192 ) ( -272 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -304 888 -192 ) ( -272 888 -192 ) ( -272 888 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -304 880 -128 ) ( -304 904 -128 ) ( -272 904 -128 ) MET5_1 0 0 0 1.000000 1.000000
( -272 904 -256 ) ( -304 904 -256 ) ( -304 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
}
{
( -368 904 -192 ) ( -368 880 -192 ) ( -368 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -336 904 -192 ) ( -368 904 -192 ) ( -368 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -336 880 -192 ) ( -336 904 -192 ) ( -336 904 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -376 888 -192 ) ( -344 888 -192 ) ( -344 888 -256 ) MET5_1 0 0 0 1.000000 1.000000
( -368 880 -128 ) ( -368 904 -128 ) ( -336 904 -128 ) MET5_1 0 0 0 1.000000 1.000000
( -336 904 -256 ) ( -368 904 -256 ) ( -368 880 -256 ) MET5_1 0 0 0 1.000000 1.000000
} 

1) Move the door entity somewhere, copy its brushes, and move it back in position. :P

2) Is any part of it visblocked? Or wrong spawnflags/fields? 

I'm curious how Worldcraft and BSP handle it. If you take a brush (or brushes) in Radiant and eliminate the entity portion, you create an object not recognized as either a brush or entity, and the .map file will do crazy things, like what happened to me years ago, it created each single brush as a world_spawn entity. So, that is one thing I recommend editing by hand in a text file, or like Neg!ke said, recreate the brushes manually in the editor. 

it created each single brush as a world_spawn entity.

each single brush as a separate world_spawn entity, thousands of them.