Excellent. Thanks :)

How's the framrate now it's vised...? ( dare I ask ) 

is there anyway you could add these features to your glquake version?
1- gl_clear defaulting to 1, with same grey void color (or at least ability to change it?)
2- in noclip mode, having flymode movement instead of just walking on the plane you are on when you issue the 'noclip' command.

I only ask because most of these I use in fitzquake to debug/leakhunt maps in development, but as I'm working on sm82 its huge visdata crashes most all other engines, so I have been using your glquake.

I've also always thought it would be cool if there was a command that flew the player through the path of the pointfile in order to better hunt down leaks, etc.

Anyways, just some ideas. 

This is an extract from the vis.log:

average leafs visible: 819
max leafs visible: 2198 near (1792 -538 1120)
c_chains: 2193464855
visdatasize: 483 kb compressed from 807 kb
Session time : 160h 44m

Fps depends on the player's system, I didn't have any problems even before vis. What's maybe more interesting is to use the r_draworder cvar of WinQuake to see how far the engine see, especially over rocks. It appears to me that pulling down sky should help in this map. 

You can change the value of cvars in your cfg files at startup (or use a key to set god/notarget/gl_clear etc), I can't see any obvious reason to change the default.

Adding r_clearcolor cvar like WinQuake I can look into (if it's reasonably easy to implement). I actually prefer the bright red; I haven't found any better for leak/HOM hunting.

The noclip behaviour is absolutely my preference, I never liked the Q2 variant. Again, I can see if it's easy to add this alternative (like FQ).

Auto-flying through leak trail sounds a bit esoteric ...

Thanks for the suggestions. 

"The noclip behaviour is absolutely my preference, I never liked the Q2 variant."
You like being stuck at the same height when noclipping? Why? 

if you use gtkr, you can just load the .pts file as a .lin file in the editor to fix leaks. 

If I haven't screwed up the basic CnP job from FQ, r_clearcolor (GL: default 251 = bright red, Win: default 2 = dark grey) and sv_altnoclip (default 0) are now in and seem to be working in both engines.

Jago: Well, for me it's easier to move in noclip like that. If I want to slide up or down at the same time, I just press D/C (swim up/down) as usual. 

average leafs visible: 819
max leafs visible: 2198 near (1792 -538 1120)
c_chains: 2193464855
visdatasize: 483 kb compressed from 807 kb
Session time : 160h 44m

Hello, I have a similar message after a fast vis process for my last map, and it's the first time I see this... Is it a real problem, or simply an information message ??? I'm able to run FitzQuake without any HOM/leak problems, and all seems to work correctly, so what must I do (if there's something to do) ???
Thanks... 

is just statistics about the vis run. If you get warnings or errors in your vis printout, either show it here or send it to me and I'll take a look at it. 

I've no warnings/error (thanks to the Lord) during any process, and the above informations appeared after a "long" fastvis process... It appeared yesterday night, so I was a little confused seeing these messages...
Well, it's not a real problem in your opinion... anyway, thank you for your help... 

wor? hehe. it would have nice it they had used stroggos or something. im still sad about it them using quake2. but then, there is gonna be a quake4! fuck yes! 

The even numbered Quakes suck? 

um... this may seem like a stupid question, but how does one map for d3 with gtkradiant, and not the built in gtk/qeradiant version in d3? 

Not that I think Quake II sucked, although it would be my least fav Quake, lets hope the "rule" gets broken with #4 

you can't GTKRadiant doesn't have any support for D3. There is a version in the works with D3 support, and a beta version Ive seen going around but its seriously broke right now and not working using.

I would imagine will probably be 2-3 months until a good working build of GTKR is out with D3 support. 

working = worth
meh 

at http://user.tninet.se/~xir870k . Main feature is updated Win/GLQuake engines with very high capacity and many fixes/improvements. Please also see readmes for more details.

Any comments are welcome. 

Some people would simply say that numbered Quakes suck. 

The new version (1.5) has support for Doom 3. There are indeed a few things broken, but that's not the biggest problem users will have. The biggest problem is that the interface has changed substantially, and old users will have trouble adapting.

You can get GTKRadiant 1.5 from http://www.qeradiant.com/

The limited docs are available here: http://zerowing.idsoftware.com/radiant-files/nightly/1.5.0/docs/ 

i've been trying just to map for q1 with the thing (1.5) and it's just not going very well... why the hell did they have to go and change such a good thing? :( 

My computer situation is fixed now. If you've sent any emails in the last 3 days or so to my V21 address, could you possibly resend to my hotmail address? 

.. 

The biggest problem is that the interface has changed substantially
Yes. It's broken. :( 

Have you still not received anything? I sent copies to both your accounts yesterday. 

Does anyone have any archived threads from the old QMap? I have the "Mapping Help" thread already, but there were many others.