otherwise it would completely fullbright

and don't forget to run light.exe 

Use QW and then cokeman's mvdparser. You can specify what information you want in the output with templates. Should be possible to get pickups etc. from it.

https://github.com/JoakimSoderberg/mvdparser

I used it for https://www.quaddicted.com/tools/frag_heat_maps_from_mvd_demos

There are also tools for protocol 15 demos but I haven't found a user-friendly one. Will probably be investigating them later this month. The SDA guys should have stuff. Maybe http://speeddemosarchive.com/quake/qdq/tools/demtool.html 

Are you using the newest tyr tools for light and vis?

It's possible VIS broke somehow. In Quake turn "r_showtris 1" in console and just make sure that the whole level isn't being rendered at one time, which may indicate something doing wrong at compile time.

This is assuming you're running light.exe and have some lights thrown about in the map, which is what to check first. 

Ok thanks. Yea something broke and I got the idea to try different compile tools and that fixed it. 

It's like spy said. Light.exe adds the lightmap information to the compiled bsp provided there are light entities in the map. 

If a moving brush entity, e.g. a func_train, is being blocked by a player or a monster, does this affect the behavior of other entities riding it in any way? Technically, it's still in a "moving" state, right? Would that impact on any active/inactive monsters on it, specifically their movement/AI routines? 

Seen anything like that, especially with trains. Typically they affect nothing and nothing affects them apart from a direct targeting and the obvious movement of creatures placed on top.

The only oddity I've seen there is with dead monsters, who'll sometimes slide on horizontally moving trains, and doors.

It's possible however that a mover is doing damage to a creature (even if it's 0 damage) which in theory could interrupt / reboot it's state.

Just conjecture / vague memory though. 

I am trying to get my maps to work with Darkplaces and I have setup all my bmodels (doors, buttons) with skip on their hidden surfaces. I have been using your newskip.exe program to move the skip surfaces around inside of the bsp, but strange things are happening.

Projectiles often fall through the bmodels with skip surfaces and traceline functions cannot recognize the objects anymore. If I compile without the newskip.exe the bmodels are all fine. I checked that the objects have the correct bbox and min/max setup but I cannot see what is wrong.

What exactly does newskip.exe do? I want to be able to explain to LordHavoc so that I can log a bug with him about Darkplaces and hopefully get the situation fixed. I really want to keep the skip surface function but I need to get more details. Can you help? 

basically skip tool will re-arrange the faces in the leaf or bmodel so that the skip faces are at the end of the list, then it changes the "num faces" count to be lower.

so if you start with this:

NumFaces: 6
Faces: A B C D E F

And B and C are skip-textured, you get this at the end:

NumFaces: 4
Faces: A D E F B C

So B and C are still included in the list, but won't get drawn because the engine will stop after drawing the first 4 faces.

Also the source code is included in the newskip archive, so Lordhavoc should be able to look at it in more detail if he wants to. 

thanks :) 

I thought it deleted the faces. That explains why newskipped bsps when loaded into another map as a .model still render all of their faces even when loaded by themselves they don't render. (Yeah I was playing around with the idea of instancing (you know like source engine!) multiple bsp's which works almost perfectly but would be absolutely horrid for performance in my case since skipping doesn't work. That and you get fireflies between mating surfaces of zero thickness (think tri-soup where two brushes only share an edge)); 

Wait how does the engine render entity .model's like for monsters and brush entities? Is there a way to have a skip utility that causes certain faces of a bsp to have the pink index color of transparency applied to them? 

The latest tyr-qbsp removes skip surfaces completely during compilation (instead of hiding them at the end of the surface list) in case that helps. 

Interesting, I didn't consider that use case when creating the tool. It should be possible to support it, though tyranns new absolute kind of makes my tool obsolete. 

"Absolute" should read "qbsp" -- cursed iPad autocorrect 

Darkplaces doesn't treat skip surfaces as simply tranpsarent faces by default like normal engines. Instead, to DP it's pretty much like they aren't there, so shots pass through and they don't block visibility. Check the sv_gameplayfix_q1bsptraceline* cvars, they can revert this behavior. 

i wish skip worked on external bsps. that would be radddddd 

Sounds like tyr's does? 

This question has probably been asked before but after hours of Googling, I have to turn to you. I've been using GTKRadiant 1.4 for Quake 3. I would like to use the same editor for Quake. According to several readme's from different maps, this should be possible.

Google has thought me GTKRadiant 1.5 has a gamepack for Quake and should be easy to configure. However, I don't like 1.5. I'm spoiled like that :)

Quake ED by Sikkpin is mentioned a lot. But all I find are dead download links. There doesn't seem to be a site for it.

Other editors are mentioned of course but before switching it would be great to hear if it's possible with GTKRadiant. If not, links to Quake Ed by Sikkpin would be appreciated since that one seems to be the best fit for me (based on what I read). 

The Quake gamepack should work with either version. Worth a try. 

Looking into it. Apparently official support is dropped for 1.5 and later. So no official gamepack download. Currently looking for mirrors :) 

A slightly modified version of it is available here.

And while I'm at it, might just drop this link as well: q1maptools.zip 

Should be pretty easy to pull that data out of a demo file (assuming you have code lying around that reads demo files, I have some oddball Python at https://code.launchpad.net/~mwhudson/+junk/demp, Mandel has some C at https://github.com/mandelmassa/libdemo or you can ram the demo through lmpc and parse the text). 

Thank you for those files. Unfortunately, the pack doesn't seem to be compatible with GTK 1.4. I got pretty far and solved several errors but eventually it would still crash.

Maybe someone else has any ideas? Otherwise a link to Sikkpin QE would be appreciated. 

You can totally use GTK1.4 with q1, but it requires some small bits of hackery.

Basically, you extract your texture wad as jpg or tga and store them like a q3 texture pack.
Then, when you go to compile, you convert the map that was saved from GTKR (which will be a q3 .map format) into the q1 .map format with a converter program. then you compile as normal.

When i get home, I'll see if I can dig up my old guide for this.