is moving the imported section nearer in than 32 units from the edge. I seem to recall having problems myself with brushes that close. 

... but no good. I am working with very little room left in the 4096 world-space as this has become a very 'flat' map. Ho hum, start map and three small additional maps then.

Two general questions:

How many units from the player can a generated sound be heard? I do not want the player to hear monsters being teleported in so am wondering how far away from the spawn site I need to set the trigger.

Can I switch off the monster-spawn sound from within the monster's .qc file? I cannot find a reference to the spawn .wav (r_tele5.wav?) in the .qc but has anyone tried this? Maybe it's hard coded in the engine? 

The function that plays ALL the teleport sounds is play_teleport() on line 282 in triggers.qc, so if you wanted to make ALL teleports (monsters, player) silent, you could just remove the contents of that function. (Or at the very least, comment away line 299, you might want to keep line 300 though...) 

Tusen takk!

(sum total of my trip to Hemsedal last Christmas) 

heh 

Isn't there a "silent" spawnflag on the teleporter? 

yes, but that only gets rid of the 'humming' ambient sound that trigger_teleports emit. 

Zerst�rer has a spawnflag for truly silent teleports. 

My last map suddenly run out of light.
What can I do?

light.exe
142entity - 130lights
+++ERROR+++
GetFileSpace : overrun 

if you're not, i highly suggest using aguire's light util, because it seems you have hit a limit which aguire's stuff probably removed. 

I deleted 16 torches, and the problem was solved. Could be something in the animated light count.

Never had the message before. 

tool, it must be a very old version < 1.14 (Aug 2002). Later versions have another more informative error message. 

at http://user.tninet.se/~xir870k . Main features are new attenuation formula (delay 5) and improved additive minlight in Light, engine matched validation in compilers and a new GLQuake engine especially made for mappers. Please also see readmes for more details.

Any comments are welcome. 

I'd like to start using GTKRadiant 1.5 but turning off 'Freelook in camera view' doesn't seem to work in the Preferences. Is it just me having that problem? 

What are the mapper specific features in your version of glquake? 

thanks man, this is awesome stuff.

first of all, the engine is a great idea. there are times when every engine i try to use packs up and leaves. i doubt i'll use it for much playing, because it doesn't look like you've made it any more efficient than the regular quake, and i doubt i'll make a map specifically for it either because of that, but this should help immensly with testing and such. at least now, when i hit a limit, i can keep building and testing while i try to figure out what's wrong as opposed to just stopping and searching and waiting and such. :)

also, i'm a big fan of delay 5. i didn't use many delay 2 lights in my maps after i started using fitzquake, because the overbright feature would make the lights way too bright, and i realised that this must be what it looks like in software... being able to specifiy a max light limit is great, and Kinn rocks hard for coming up with something like that. (but thanks for implementing it in your tools, aguire)

i haven't really experimented much with the new minlight setting though... i try to stay away from minlight as much as possible. :P

cheers on excellent work! 

like he said in the readme, there aren't really any features for mapper, the only feature is that almost all limits that would normally crash quake before even letting you see the map are bumped way up (ie: edicts from 600 to 2048)

it's not really meant for normal play or for mapping specifically for. 

one thing i forgot to mention, Aguire:
don't name your engine glquake.exe, because it's not meant to be a glquake replacement. glquakebjp is perfectly acceptable ;) besides, it makes unzipping it a pain, because now i have to unzip to another directory, rename then copy it into the quake directory. same me some steps, eh? ^_^ 

I have experienced the same problems. I've also reverted back to using the beta 1.3.11 because I find the changes in the interfaces of the newer versions iratating and counterproductive to what I try to accomplish. 

The "GLQuake Mapper version" just means that its focus is on loadability and viewing of large troublesome maps.

Since mappers at one time or another create maps that indirectly (e.g. via leaks) or directly exceed normal engine limits, I hope this version is of special use for them.

It's not meant as a replacement for FitzQuake or other engines, just a complement. 

I toyed with the idea of making up yet another engine name but decided against it, since all my other tools also kept their original names.

Since I don't plan to make that many more improvements to this engine (unless someone finds a reasonably valid bsp it can't load), I hope it won't be too cumbersome with the file renaming.

I'm glad you like the tools, let me know if you have problems with them. 

Sorry I didn't spot the readme..it isn't in the zip. That sounds very useful.

Headthump..I fine with 1.4 but I definitely need to turn freelook on. I've reported it as a bug. 

Day of the Lords was one that I tested the engine capacity on. Sometimes when compiling that map you get a leak near the beginning of the map.

The resulting bsp is normally not loadable in any engine, but now it is. Just fly around and inspect the whole outside of the map when it's not removed by the compiler. Then load the pts file and you can find the leak spot immediately.

Even the old SoE map soe2m4 which was mega huge before Tronyn decided to split it can now be loaded and inspected for the leak trail.

Maybe the engine can also handle the upcoming project that Tronyn is working on. 

with 1.4 the default settings uses the QeRadiant standard 'delete - insert' for the zoom-in, zoom-out instead of the 'shift mouse drag' that is second nature for me now. Changes like that are a bit irksome though I do have 1.4 set up for Half-Life mapping. 

Yes I had that problem intermittently - strangely I got it to compile (without a leak) by slightly moving one of the entities in the beginning outside area. Not sure why that would work other than perhaps reshuffling the entity order in the map file. Where is the leak?

HeadThump-shift RMB drag does work in 1.4 in the 2d windows.