You guys didn't buy Worldcraft when it came out? I still have my original version 1.1 disk with the paper receipt from ACD Systems. 

The full 1.6 version on another thread. Not sure about the legality of that, but it's not for sale anymore and I'm not hosting, so...

The only difference AFAIK is being able to use the prefabs system.

1.6 doesn't have the advanced texture snap that 3.3 and later provide, and there are a few glitches in there that can be annoying. 

One thing I always liked about the old Worldcraft was that it allowed you to move individual vertexes anywhere you wanted to, even if it would be an invalid brush. NetRadiant infuriates me sometimes because of the automatic checking and rearranging of other vertexes just to keep the brush valid. Sometimes to get from point A to point B you need to pass through invalid shapes. 

It's fine! Tried Trenchbroom but it's too different, I don't feel like I get the control and precision I want with it as easily as with 2D editors.

As for 'the compilers requiring .wad to work', not true, there have been compilers that support hlwad for ages now. Haven't there? 

Trenchbroom is the greatest editor of all time! 

Nope, you still need the normal wads afaik. 

It crashes when I add Quake.Wad to map properties. Maybe I'm using the wrong wad? I'd like somebody to post me a working link here. 

https://www.quaddicted.com/files/wads/ 

Vertex mode. Trying to enable it crashes the tool and gives a shithole of errors. I wonder what's the creator's mail so I could send the log here. 

I didn't notice your nickname, Sleepwalk. Do you need the log anyways? 

http://pastebin.com/achrjSMd 

And set Instancing Mode to Force Off. 

I just did it.

I opened my .map file in np++, checked the texture location in the header. It says "blah.hlwad". So I'm like 'heh - thought so!'.

So then I went into my texture's directory and renamed my .wad files to whatever_meh.wad. (adding '_meh' obv.)

Compiled again, worked! Loaded into the engine, textures intact.

WC3.3 + TxQbsp std. 

 

It's right here, near the top....

http://user.tninet.se/~xir870k/readmetx.txt

'Support for Valve WAD3 format.' 

(sometimes) 

i've wait for 5hours with the classic converter, but with wally i made it in 5min 

I want make map for Quoth2. How I can use self palette.lmp and conchars.lmp with this mod? 

but I am excited about you making a Quoth map. 

All you need is the entity definition to make it and the mod to test it. 

Most compilers don't support HLWAD (Tyrbsp doesn't anyway). That's why I said that and it's probably why the docs for TqBSP specifically mention that is does support it, it's not a normal behavior for Quake BSP. I found that out when I moved the .wad files before compiling and ended up with a level that was all pink checkerboard textures. 

Digs: I think what you're asking is how you'd use custom graphics like console characters in the Quoth mod. I'm not clear if this is something you want to do personally or it's something that you're planning to go with your map (replicating the trick zerst�rer pulled to get the � character in quake is a potentially valid reason to need this).

What makes it difficult is that Quoth already has a custom character set in order to display e.g. the flashlight meter graphics. From a creative point of view it means you need to preserve the quoth characters in your custom set. There's a practical side too: Quoth has the custom characters in its pak files, which gives them highest priority.

So the ways of overriding that pak file priority are:
1) Opening the pak file and deleting the file, then placing your custom file in the directory.
2) Opening the pak file and replacing the conchars with your custom set directly.
3) Adding a pak file with a higher number (pak3.pak) having the custom conchars file within it.
4) Create a new mod directory, then run that mod using an engine that supports the "-quoth" command line command to import files from both your mod and Quoth.

Options 1 to 3 would be fine for personal use. 3 has the downside that sometime in 2016 Quoth 3.1 will come out and overwrite your pak3.pak file. 1 and 2 would need to be performed manually if you reinstalled Quoth. If you're planning this feature for the map release then 4 is probably the right approach, but bear in mind this still makes it a bit more effort for people to play your map, so you need to weigh that against the value of the custom conchars. 

Yes, the fourth option a little more difficult for the users. But he is the best in my opinion. I will use it. Thank you! 

Just because you're driving around in a mini-cooper doesn't mean that cars cannot travel above 200mph.

What version of TyrQBSP are you using (!?!?!)

I just compiled a map using tyrqbsp and .hlwads and it compiled just fine, textures intact.

Apparently this feature has been supported by tyrqbsp since April.

Not wanting to put any compilers down (past or present) I shall just say also, FYI, that there are a lot of Quake maps that would not exist today where it not for TxQBSP. IMO it had been the standard (i.e. the best) for a very long time, and was included with Worldcraft3.3-Quaked if I recall http://quakeone.com/qadapter/.

So, basically, I don't understand where you're coming from.... 

For those who use QuArK, here is a pipe building tutorial link made by Felikkz7

http://felikkz7.free.fr/tuto_pipes.html

This is awesome...