Yeah those menus are broken, have to edit the file manually.

Or at least I wasn't able to get that menu to work. 

This worked for me:
http://quake_1.republika.pl/q3e_01.jpg

Directory structure: D:\Quake\Quake\qe3\
All the contents of the package are extracted to qe3.

I must say the setup is very unintuitive. How can a first time user know what is meant by remote basepath etc?
And if you set it up wrongly then the program won't even start next time but close with a message about missing palette file.

After getting through the setup problems it starts too look very fine though. Still lack of documentation is a big problem but at least a command list can be found in Help menu.

To get the bsp menu working I have just copied this text at the bottom of quake.qe3 file in the scripts directory.

"bsp_NoVis" "!qbsp $"
"bsp_Entities" "!qbsp -onlyents $"
"bsp_Relight" "!qbsp -onlyents $ && !light $"
"bsp_FullVis (light -maxlt -extra4)" "!qbsp $ && !vis $ && !light -maxlight 1 -extra4 $"
"bsp_FullVis (light -extra4)" "!qbsp $ && !vis $ && !light -extra4"
"bsp_FullVis (no light)" "!qbsp $ && !vis $"
"bsp_FullVis (nowater)" "!qbsp -solid $ && !vis $ && !light $"
"bsp_FullVis" "!qbsp $ && !vis $ && !light $"
"bsp_FastVis (nowater)" "!qbsp -solid $ && !vis -fast $ && !light $"
"bsp_FastVis" "!qbsp $ && !vis -fast $ && !light $"
 

Some editor needs to beat the existing editors in noobster friendliness.

You have every advantage, including that it is the only open source editor made by someone who "gets" mapping.

(Where as Worldcraft isn't open source and will be stuck in 2002 from now 'til doomsday and the other editors seem to not be very learnable).

As a general rule of thumb, you should be able to compile upon startup after loading a map without doing any settings. Default them to something a dumb user can easily comply with (i.e., decide what their Quake directory is .. don't ask them, etc.).

Remember, new users are always "dumb" because they have no experience. If you can satisfy the dumb user, you will as a bonus satisfy the user who is worried that they might discover they fall in the dumb group.

User noobster friendliness makes everyone happy. The advanced user will understand how to customize, and newbster can fumble around and start posting in the mapping help thread when his map won't compile because it doesn't have an info_player_start. 

What I did with ToeTag was to eliminate configuration options. I supply your compiling tools and everything else that you need to make a level. All that I require from you is for you to tell me where your Quake directory is. Once you do that, you're good to go! 

perfect!

Hows the texure lock - during - rotations thingy going?

(or isnt it?) 

Ankh thks i will try tonight!!! 

Ricky

Not so much. I have basic locking on drags (that works most of the time) but nothing for rotations. My math skills are so badly lacking that I haven't the first clue of how to even begin there.

It's on my list but it's probably one of those features that will never actually materialize. 

"Hows the texure lock - during - rotations thingy going?"

My understanding from talking with a Half-Life mapping expert (Scrama) is that the standard .map format can't easily support texture rotation.

That's why in WC3.3/Hammer .map 220 format, they added some extra fields. 

the Worldcraft 1.6/a version was very "temperamental" ..... 

I don't think the user should be limited like that. It might good for beginners not to be swamped with lots of options, but advanced users usually want to tweak the editor to their liking. So basic->advanced options tabs would probably be a better solution. 

The editor does not run on operating systems where people actually make choices themselves. 

I've considered an "Advanced" button on the preferences dialog but since, maybe, 3 people are using the editor it really hasn't gotten near the top of my task list.

There is some validity in wanting to use custom tools for compiling and such but it's never been an issue for me personally so I've been slow to accommodate it.

Spirit

Yes, you are correct. The Mac is not for anal retentive control freaks. 

WTF?! 

 

The editor is great.
I have some questions though.
Is there a possibility of grouping brushes like in Worldcraft?
Also there are no visgroups right? 

Ankh: No visgroups yet. It is definitely planned for the next release. When that will be, I have no idea.


Electro:
"What's a Project Directory?"
"What's a Remote Basepath!?"
Look in the "default.qe3" file for id's short description. The "Remote Basepath" is a legacy left over. It is used for assets that reside on a network server machine. I probably could have removed it but I think I left it in there for a reason, but I don't have the the code with me at the moment to tell you why. For now just set it the same as the "Project Directory"

"...Texture Directory only kept the last 3 characters ..."
This is from using the "Find" button, correct? I have never run into this problem so I don't really know what's happening here. Is the problem consistent?

"...texture move lock toggle via shift+T..."
Whenever I fix a bug that will enable the use of the "Shift" key for shortcuts this can be done. For now, Texture Lock locks for both move and rotate but eventually I'll split the two as unique commands.

"...texture window on my secondary monitor..."
This is not working because the Window Snapping feature doesn't handle anything but the primary display. I'll look into adapting it to handle multiple displays.

"...change the display of the scale of the textures..."
Ctrl+RMB+Drag. Look in the "QE3-mousecmds.txt" file in the "/docs" directory.

"...escape to close dialogs = win..."
Since "Escape" is used to deselect a brush, this can't happen because eventually the "Entity/Texture/Console", "Surface Inspector" and some other windows will be changed to be able to remain "on top" while editing.

"Is there a scroll bar for the texture window..."
RMB+Drag. Again, refer to "QE3-mousecmds.txt".

"...those menus are broken..."
How are they broken? What are they not doing correctly? They work fine for me.


I see now that I should have at least written a description about the Project Settings dialog. It was never my intention to design anything "noob friendly". I'm not trying to make an editor to please the masses or to get people who have never mapped before to start mapping, I just wanted to design an editor that I wanted to use. Hell, it's been almost a year and I still haven't been able to map yet. :). I do recognize my fault in not supplying proper setup documentation (what I wrote in the readme I though would suffice) but the setup will remain the way it is. 

Is development still happening on this project?

I'm looking for a new Q1 editor to try out, as QuArK has been completely buggy shit for me, unfortunately. Constant errors doing the most basic things, and hell with textures. I love QuArK's grouping of map items, that just rocks. So easy to hide various areas of the map, or make them visible but unclickable and so on. But it is just too buggy for me to use.

This after giving up on GtkRadiant learning that it is incapable of doing Q1-style shapred brushes (spheres, cylinders, etc.) as it only handles Q3-style meshes. Lame.

I miss the days of using Qoole in the 90s, as it "just worked" almost always, and was really easy to use. 

thats what I use :) 

i don't think sikkpin is working on this anymore. shame as there are a few minor but annoying bugs, but it's an excellent editor and i recommend it over gtkr. 

@RickyT23:
I don't think I've ever used WorldCraft, as at the time it was popular I was already using Qoole and liking it. I went and looked for WorldCraft a few days ago, and found that it stopped development a few years ago, bought out by Valve. How "complete" is it? I'll go try to find 3.3 to download, thanks.

I also found a Qoole download, and while it has a bug with rotating objects allowing leaks, I can easily work around it. I'll see if it's as good as I remember it being from the 90s! :-P

@necros:
Well, I have downloaded it and will give it a try. Qoole also used the one-2D/one-3D/one-texture layout, and I got really accustomed to it, and prefer it to the three-2D layouts, as I tend to only focus on one of them anyhow. 

Forgot to include my "Samus Aran" nickname in the last posting, oops! I'm surprised this message board lets it post without at least filling in a nickname. 

Its basically Hammer editor, fully developed and stuff. Customizable views, easy to use interface.

It was used for Half-Life levels, and there is a tool which converts Quake .wad files into hlwad format included in the Quakeadapter package, and the TxQBSP tool compiles Quake maps directly from this format. Its a good system, and the Quakeadapter makes it all work with no fuss at all.

http://quakeone.com/qadapter/

A couple of people had troubles getting it to work on ATI cards, but some other people had no problems, I would give it a try ive been using it for years with no hassle. 

Are there any tools good for converting high quality JPEG/Targa textures into the very strange Quake 8bit palette? I run into issues where auto-conversion disregards the special fullbright entries in the palette, making the resulting textures look horrible.

Also, is there any way to use a custom 8bit palette for Quake? I am not using any of the official Quake textures, though the default monster/item skins are still being used. I am currently working on a very bright level (office building taken over by monsters) with 100% custom textures, so it's a pain when they look so awful in-game.

I use the Dark Places engine for actually playing levels, and it has support for 24bit texture overrides in .pk3 files, but I would still like the stock Q1 to look acceptable when distributing the level to people not using Dark Places. 

Log in and it fills in the name automatically.

I use photoshop and TexMex for textures, you'll have to convert textures to indexed colours and load in the Quake palette if you go that route.

If you haven't got a big pile of money lying in the corner then you could try using Paint Shop Pro, which is free and apparantly has automativ palette conversion in the latest version.

TexMex is basically a decent frontend for Quake textures and can do some useful stuff, like extracting from .bsp. 

I use GIMP for pretty much any image editing I do, and it's free so there's no barrier to entry there. The first thing I did was created a copy of the quake palette with all of the fullbrights changed to black. This way when you automatically convert textures, the fullbrights are never mapped, as the program always uses the first colour for black pixels.

In order to get the best texture conversion in GIMP, you need to know about a strange, seemingly undocumented feature: pasting a 24 bit colour image from the clipboard into an index image performs an automatic conversion which matches colours better than any of the "mode->indexed..." conversion methods. It isn't always the ultimate answer though, because it performs no dithering, meaning on subtle gradients you get banding.

My current favoured method is to take the full colour texture, copy it to the clipboard, then apply "positioned" dithering to convert it to the quake palette. I then paste the contents of the clipboard to get the better colour matching version I described before, and convert the pasted layer into a regular layer with an alpha channel.

Then it is a matter of experimenting with portions of the two version by painting on the alpha channel of the top layer. Usually I look for areas which display banding, and expose the lower layer to see if the dithering is an improvement. Sometimes areas on textures which are meant to be noisy end up too uniform without dithering - rusty areas are often examples of this. So paint them out on the alpha channel as well. The nice thing about this is that you don't need to worry about undoing anything; if exposing the lower layer doesn't improve it any, then you can easily paint the top layer back in.

I'll admit that usually when I'm doing this, I am converting textures I've created myself for quake. When I'm doing that, I'll work in full colour to blend/dodge/burn etc, but only paint with base colours from the quake palette. So I'm stacking the deck in my favour there. If you're starting with an texture which was never intended for quake, you may have to perform some colour adjustment to it. Trying to adjust specific channels to nudge an image towards one of the quake palette ranges has never worked well for me, but reducing saturation can help for vibrant images. It's a balancing act though, wash it out too much and you'll be worse off as everything maps to the limited grey ranges.

It is possible to replace the quake palette entirely if you can't get good results
http://www.gamers.org/pub/idgames2/planetquake/chopshop/utilities/quake/wad_utils/newwad14.txt
has the details of what you need to do, using
http://www.gamers.org/pub/idgames2/planetquake/chopshop/utilities/quake/wad_utils/newwad14.zip
You still need everything in one palette though, and there might be a trick to getting glquake to play along. I remember making "noir quake", which just mapped all of the quake palette to sepia tones, and having to mess about to get glquake to forget the standard palette.