I use 1.5 

I am using 1.3.8 (SD version of radiant) with a special entity.def and various shader files to remap all the textures to the root. I can't use 1.5+ because of the Intel video bug. 

Also using 1.5.
Works like a charm imo. 

Well that is a striking concept. My dog would never say not to a piece of cheesecake I'm sure. 

I'm looking for the source of a certain texture. Can you remember where you got the crate texture named f_051 from? Light brown wood. It appears in autumn.wad, for example. 

SV_RecursiveHullCheck: node number 34226 outside 53513 - 54143 for edict door, model *48

I'm not actually looking for help with this, I just thought it was an awesome message. 

Hi,
Does anyone know where to find the newest or best qbsp, vis and light programs ? For Quake (worldcraft), I mean.
Thanks ! 

http://www.quaddicted.com/tools/map_compilers 

a lot ! 

the link to light.exe was broken, so i tried to fix it, but it still doesn't work because the filename has uppercase chars, but the link is not being generated with uppercase even though the source page has them. 

That is terrible, what a stupid bug. Maybe prepending http://www.quaddicted.com would work. 

 

you dont say 

yup, that worked. 

Is there a way for spawning a megahealth with info_multispawn? 

The way you're supposed to to it use the classname "info_health" everywhere you'd usually use a monster classname, but also set the second spawnflag on the info_multispawn - spawnflags on the info_multispawn get passed onto the things it spawns. Not tested this particular case though... 

Thanks. 

Haven't touched the map for a couple of months and today I go to have a play-test because I think it's ready for a full vis and this pops up. FitzQ carries on OK but what am I looking at here; good, bad, or forget it? 

If it doesn't crash (which it does in some cases) then), it's probably forget it but it can be fixed nonetheless, I think. 

there is something to do with entity links. that message means that fq is avoiding a crash by fixing the link.

It can be cause by setting origin of bmodel entities during a touch function. probably other things as well. 

Are func_breakable's supposed to be damaged by monsters? In my last map at least two people got an ogre to open the ROS secret and I wanted to incorporate something like that in mission 2. But right now for some reason the brushes break when the player shoots them but not when ogre grenades explode on them. 

I suspect the problem is not specific to a func_breakable, but is down to the way radius damage applies to brush entities. The grenade does damage to all brush entities whose centre-of-mass* is close enough to the grenade. If your func is large enough, grenades on the ground won't reach it. One test would be to turn it into a shootable func_button and see if that can be triggered.

A possible (untested) solution if that is the problem would be to add a set of point-sized, 1 health trigger_once entities that target the func_breakable. Spread them around enough to give you good coverage.

*Here centre-of-mass means the centre of the bounding box enclosing the brush object, not a calculation based on volume or density. 

Shootable triggers don't work as point entities unfortunately - a point can be touched, but in order to receive damage it needs to have a volume.