I'll check it ! 

I came across an old backup cd with an unfinished map from 2005 on it but I don't have all of the texture wads to with.

Does anyone know what wad has the texture db_rock05?

it must be an outside dirt / rock type texture as the brushes are in an outside area. 

... it is from bulowad (or bulowad2) texture set

Check it out there http://www.quaddicted.com/wads/ 

Thanks JPL!

bulowad2 is the one. 

different versions of the Quake 2 textures?

either in maps or wads or zips or whatever?

Im particularly interested in any quake1 maps which use ported Quake 2 textures. I have the full intention of finding some textures which are better than the ported Quake 2 textures in quaddicted/wads.

I can do my own conversions but my attempts at converting the stock quake 2 textures or the standard hires replacements has had funky coloured results........ 

metl's oblivion? 

is there a waterfall sound in the quoth pack?
what is it called if so? 

That's what I told him. Oblivion is nice. 

There is a waterfall sound, the path to it is

sounds/necros/water6.wav 

Sound is of course singular in the quake directory structure, so I meant to put:

sound/necros/water6.wav

Then again, when you add paths to call sounds you have to omit that directory name anyway. 

Every time I go to the Check for Problems tool I get a list of errors that are no real errors, like this :

"The entity contains keyvalues that are not used in its class. You can fix this error with the Fix button."

I've not tried using the fix button, I'm not sure if the entities will be deleted if I do.

Anyone know how I can get rid of this problem ?
It's quite annoying because the Check for problems tool is quite useful for pointing out mistakes with vector manipulation. 

This comes from the keys which are specified for each class in the FGD file. Its not a "real" problem, and clicking on fix wont remove the entity. Infact clicking on fix wont do anything really!!!

All of the "real" problems are usually at the bottom of the list. I always start at the bottom of that list and work up. You get any illegal brush errors there, or bad textures etc.

One thing which you get in WC is brush models with no volume (no brushes attached) which are often situated at position 0,0,0. You can delete these by clocking on goto error, closing the "find problems" dialogue and pressing delete ;) 

http://games.softpedia.com/get/Tools/Valve-Hammer-Editor.shtml

This link is to a hammer.exe file which you can put in your WC DIR and then just run from there.

Then you can see how similar Hammer 3.5 is to WC 3.3! (its sooo similar i only noticed one real difference - you can load pointfiles and see them in the 3D window. in 3.3 they would only show up in the 2D views). 

Anyone know how I can get rid of this problem ?

just open the fgd file, find the relevant entity (or baseclass) and add any used keys that aren't there.. voila, errors be gone! 

Thanks a lot !
I'll have a look at .5, I take it the Quake adapter will work for that version too ? 

Well that's what I mean. I ran into this file whilst looking for a hammer installer. All I did was drop the only file in the archive (600kb) which was hammer.exe into the Worldcraft directory and clicked on the exe. I had already been using the Quakeadapter WC3.3 setup and this seems to use the same configs and everything.

Its not an installer, its a program.exe file :) 

Will take a look at that.

Don't use the fix button for that error message - what it does is delete all the keys it thinks are broken - so it removes all your entity configurations.

Need to get the RMQ fgd to stop reporting that crap.

In fact the only time you want to use Fix or Fix All is when you get a Texture Axis perpendicular to Face. The rest of the time it's best to just use the problems thing to find it, then fix the thing yourself. Like you've been doing from the sounds of it.

The perpendicular texture thing causes a corrupt bsp - and the chances are you won't even notice it since it doesn't affect all OS' / setups. Its caused when manipulating objects with vertex editing / slice. 

hahaha thanks! 

corps_removal? 

add to def.qc:

void () CorpseThink =
{
self.think = SUB_Remove;
self.nextthink = time + 30 + random() * 30;
};

All monsters in last death animation (ie example shambler):

void() sham_death11 =[ $death11, CorpseThink ] {};
 

Thanks to Ricky who owes me 90 bucks Quest doesn't work on Win7 64bit and the Virual XP Mode doesn't help either, because of some fullscreen issue.

Gtkradiant 1.5 then (couldn't get the newer branches to run, there's no fool-proof installer/pack). What's really bothering me, though, is that one is so restricted to the entity definitions. You can't use custom entities without adding them to the def file first. So there's some stuff I can't do and don't know how to change it. For example, triggers are defined as brush-based and it's impossible to use them as point ents (and vice versa, e.g. an info_notnull with a brush) - doing so, Gtkradiant will disregard their position/dimensions in the display windows and move them all to the map origin.
What can I do about it? Is there an option to make the editor less anal about such things? 

Try another editor maybe. There's bsp editor and maybe soon thanks to willem / ericw Toetag windows edition.

QuArK as well - although I hate the interface.

I think I remember you saying you hated the one from WC.

It's a pain upgrading OS. None of the Quake stuff just works any more. 

I told you I was dual booting XP and Windows 7, and the way I see it is you havent lost anything, only the ability to run a REALLY old piece of software.

Try using Hammer.

FOR THE LOVE OF GOD!!! 

Worldcraft/hammer is only slightly more flexable about interchanging point entities for brush entities. If you remove the definition of an entity from the fgd file, then you can place it as either, which is helpful for func_illusionary. It does mean that you lose all the smart edit functions though, so for anything more complicated than func_illusionary it gets annoying.

The hack we incorportated into quoth was to create a series of wrapper functions like:

void() func_wall_point =
{
self.classname = "func_wall";
func_wall();
}

You can then define a "point" version of the entity in the def file.

I suppose you could also do this with a preprocessor of your map file added to the compile process. It could just do a find and replace in the .map file of "funcpoint" for "func". Assuming you never use the phrase in text fields or textures. Replacing

"classname" "funcpoint

with

"classname" "func

might be safer... 

ijed: Quark? lol

Ricky: So do I. But I told I would come back and complain no matter what. I actually might use a hammer on this computer sooner or later (and then come back to you to complain).

Preach: Yeah, I guess editing the def file and dublicate the entities in question is the only way. I don't need the smart edit functions except for the difficulty spawnflags.