PhaseII is an oddity to be sure but both of these apps have a really interesting UI and are (to me) a pretty interesting part of our collective Quake lore. They were coded by a women who was injured in a car accident and kind of fell out of the Quake scene as a result. I've never been able to track down what happened to her after her hospitalization. I will email these to Spirit but here they are for the curious. No source for PhaseII unfortunately. Well worth a look IMO. That's why I wanted to get them running again.

https://www.dropbox.com/s/plh6rsopnx3c863/fraquake.zip?dl=0

https://www.dropbox.com/s/4hgvr5ojab38xnl/phase2.zip?dl=0 

Can someone point me to code that parses BSP files?

Extra beer if it's in python or the like :-) 

sourcecode on github or something :-) 

Here you have add-on for blender that parses BSP. It's a python script, so very close to what you are looking for: https://github.com/andyp123/blender_io_mesh_bsp

I don't know about any other python BSP parser, but i bet there must be more of this... somewhere... :D 

Where's the implementation for LoadBSPFile()?

https://github.com/ericwa/Quakespasm/search?utf8=%E2%9C%93&q=LoadBSPFile+&type= 

https://github.com/ericwa/Quakespasm/blob/master/quakespasm/Quake/gl_model.c#L1969

if you just want a wireframe blob, walk through the faces lump, read the firstedge+numedges values and walk through the surfedges lump from that firstedge value for numedges entries. for each surfedge indicated, look up the edge entry that it indicates - if the surfedge is negative, negate it and use the second vertex from the indicated edge entry, otherwise use the first vertex from the edge.
that'll give you a loop of verticies, aka a triangle fan. get the actual vertex positions from the vertex loop.

textures come from surf->texinfo->texture. texture coords come from dotproduct(vertexcoord, surf->texinfo->vecs[S|T])-surf->texinfo->vecs[S|T][3];
lightmaps are overcomplicated. you'll need to calculate the texture coord extents, divide by 16 and round out to calculate the size of the per-surface lightmaps. then blend the up-to-four lightmaps per surface, atlas the result somehow according to the current lightstyle etc.

collision+pvs+ents+submodels are a different matter entirely, but they're half the fun. 

Thanks you two!

I was thinking about writing a map validation tool that unzips, reads bsp, checks if everything is there and parseable. 

I downloaded this file way back 2005. I had the impression it was able to recompile the quake.exe. By means of doing so I would be able to alter some of its components in the way I had the oppertunity to create my own "quake". The file is only 700kb large, has most of subdirectories full of *.c and *.h files.

Now I finally have it installed it looks as if I'm missing something. I knew I would get into trouble, reason I restrickted myself to qcc only.

Now I have a directory /quake/utils, tried the install.bat but get redrawn to D:QUAKE/UTILS/QCC>nmake /f "qcc.mak"CFG="qcc -WIN32 Release" The command or filename is incorrect.

Where should I start? 

I know there is a Install VC++ and MASM.
order, or use DJGPP to compile the dos version.

I'm downloading a file with 1Gb info , but I have no idea whee to begin. 

nmake is microsoft's version of make. its kinda crap compared to gnu's [g]make. It comes bundled with msvc, I've no idea if there's any smaller bundles for it, but you'd need a c compiler anyway, so I wouldn't bother too much, just get msvc.

djgpp compiles for dos. if you're on a 64bit windows system then its almost useless (dosbox to the rescue?). Its available as a native dos compiler, or as a cross compiler from eg cygwin.

In this day and age, you should probably NOT start with the vanilla sourcecode. Its too limited and buggy. You would save yourself time by starting with eg quakespasm.

But yeah, I have to ask what you're actually trying to achieve? If its just making a quake mod then you don't need to bother with any of the above, just grab a base mod (like progs106.zip or some cleanqc thing like gnounc's) and then combine with a prebuilt qc compiler (like fteqccgui - the vanilla one is shite). 

Thanks for your reply!

First I'm on winxp32. I did some tinkering with qc and proqcc (now fteqccgui), and got a little familiar with it. That is.., spent weeks in urge to find a six lined string for the rat code from malice, before I found the malice qc and wondered what I missed. (I'm great!)

So in fact I'm more into trouble than I can get. What I tried to archive is searching in the AI Cafe, and sourceforge my curiosity is wakened about changing these *.c and *.h files.
As I look to the qc files there is nothing in it. While I do find them in this Quake developement CD.

So I know I am searching on the wrong place, but downloading the whole djggp file didn't get me any further.
What I try to do is get this cd working and see what's going on. Having V++ and MASM is a start, but I have no idea where I'm going.

Maybe the whisfull thinking of construckting a scuba gear, make reflecting water, or god knows. 

It would be awesome to have a tool that can tell me the modelindex of an entity without having to compile and run the map.

Is it possible to determine this information before compilation? or is it so much work that it wouldn't be worthwhile? 

Look at the code here:

http://www.gamers.org/dEngine/quake/Qc/items.htm#item_health

And here ...

http://www.gamers.org/dEngine/quake/Qc/items.htm#item_artifact_super_damage

Do you see how the items even getting precached is dependent on what items are present in a map?

It even depends on spawnflags in some cases like health boxes. And it definitely depends on the actual order that of the entities in the map file.

So it can vary for skill level -- skill 1 vs. skill 2, etc.

Since modelindex is very hard to predict, you may ask yourself why are you using modelindex?

Which is the better question. 

For sexy non-essential maphacks. I like the idea of pushing the engine / progs to its limits. 

The model name won't work?

Also are you sure you are using a model index? A brush model like "*5", that's not a model index -- that is the model name. 

sorry you're correct, I mean edict number. 

model *5 will ALWAYS have modelindex 6, guaranteed. doesn't even need to be precached.
external models have pseudo-random indexes, but those inline models will always be assigned modelindexes by the engine and with reliable ordering etc.

edict numbers depend upon the max number of players. quite a few entities like walltorches will be handled with makestatic, and so will not increment edict numbers. Again it also depends upon spawnflags as to whether the entity will actually be spawned, etc.

By far the easiest way to get this sort of stuff to work is to include a custom progs.dat so that things don't have to be guessed at, but Baker won't like that either. :P 

The "model name" is "*5". The "*5" isn't a model index, the "*5" also isn't an edict number.

Those numbers are probably determined by the order that entities (func_wall, doors, etc.) are encountered as the bsp compiler compiles the .map.

So it is probably simply determined by order in the text file that is the .map, but I wouldn't 10000% swear by that, it is just a guess that is stands a pretty decent chance of being correct. 

What are some good recommendations for a QuakeC compiler? 

 

Does anyone know what progs.lno is? 

Does anyone know what progs.lno is? 

You can ignore it for now, it isn't needed to run a mod.

(It is used for a specific engine when debugging your code, I believe that it allows the engine to return the line number that an error occurs on, aiding debugging. I've never made use of it though...) 

simply put, its a statementindex-to-linenumber lookup table.

dp uses it for just more readable error prints (no more meaningless numbers!).

fteqw uses it for step-by-step debugging, typically by hitting f5 inside fteqccgui and picking an fteqw build. you can then set breakpoints in the gui with f9 and single-step with f11. mouse-over variables to see their current values. wouldn't be possible without the info in those .lno files.

If they annoy you, you can compile with -O2 (or -Of, or even '#pragma optimise filenames'), fteqcc will then also stop generating these lno files (they arn't very useful when there's no way to tell which file they're lines of).

So yeah, they're situationally useful, but if an end user actually needs them then you already screwed up, such that there's not really much point distributing them (no harm in it, just pointless). You should otherwise just ignore them - they're totally useless on their own.