I think it a bad habbit from lightning.
Some other area's I could rebuild right, but this one stays on place.
In the earlier maps nothing was wrong.
I can use a clip brush but it feels like patching.

What happens in a compiler when I have,lets say 15 warnings, and I trie to trace them.
When I go on adding brushes sometimes the warning count gets lower.
Is it because the compiler can't see the other warnings anymore or is it just a limitation in the messages.
It feels so rude to trace warnings that later on in the proces just are vanished. 

Well, some warnings are caused by things done during compiling as opposed to something you did in the editor, so when you change an area, it might affect how the compiler treats the same brushes.
Making hull1 and hull2 is the most obvious example because the hull expansion stuff is sometimes very touchy about the brushwork but also things like cuts on faces and the portals that are generated can change just by adding a single brush. 

I succeeded to make new brushes and now they are away.

Only the static entities are hard to light.
Sometimes it 's bright, then it darkens.
I've heard they receive their lighting from under but that's a difficult part in some spaces. 

probably had something similar when q2 mapping, and fixed it by removing decimals from texture alignment.

So resetting texture alignment on that brush might help too 

It's a brush with a sharp point.
Often I experience to get a Cut_node_portal warning at the point.

If I keep the brush concave(not 3 but 4sides) and hide the smalles side into the wall brush it was gone.
Rule is not to let brushes overleap but in this case it's the only way.
If the wall is an outside wall often the leak effect starts calling.

Strange to see the brushes split in game after compileing, but usefull to trace errors. 

Hi All, I am trying to move entities from the original E1M1 map to one that was released with CTF and has lots of entities like triggers and doors etc. removed. The trouble I am having is with the lights that are triggered just past the quad as you head down the spiraling path. The trigger near the quad door turned into a door withthe word ' trigger ' on it, and it opens when you hit all the red buttons. I must have assigned it a model by accident? there seems to also be a trigger counter for the buttons and activates the lights? Can anyoneexplain the proper operation or list the entities that are for those things? 

http://quakeone.com/qadapter/

If you download the quakeadapter, (and Worldcraft 3.3, and install them as instructed) you will be able to find the quake-defs-by-czg.fgd file in the Worldcraft DIR. (under Windows, you need to install WC3.3 to 'Program Files' (not ... (x86/)).
This file explains to an extent how all of the different entity types work (well it will tell you what attributes each one can have etc). I have trouble findind said .fgd file anywhere else, that is why I recommend you download the quakeadapter for WC3.3 - it's the only place I know of where that fgd file can be found.

AFAIK the entity 'targetname' fields are filled with random indexes ('17239830'), rather than meaninful names (i.e. sliver_key_door), so you will have to probably play the original map to find out the exact behaviour of the entities in the map. 

Edit:

...in the original id maps. 

are you trying to transfer them from one bsp to another bsp?

you will not be able to do that if the number and combination of brush models (doors, triggers) do not match. the .map file would need to be recompiled. 

I was assuming you were working on .map files.

If you are trying to mod the BSP files then dont.

Just get the .map sources, load them into an editor, and it will all start to make sense :)

If you recompile the original sources with a modern compiler you can actually achieve better lighting, transparent water, more efficient visual optimisation. 

Got the Qadaptor installed. I dont have the .map files or the .ent files its been a while since I compiled a map, I used an old program called BSP a long time ago, think it was DOS , and it would take the ents and compile them into the map, and form a bsp if I remember. 

M:\QuakeArchive\madfox\compile\winbspc12\winbspc.htm 

sorry, that's my own.

http://quakeone.com/navigator/

maputillities/winbsp(decompiler) 

Here are the original map sources from Quake:

http://rome.ro/2006/10/quake-map-sources-released.html

You can load them into your editor! 

cheat! 

http://www.bspquakeeditor.com/

IT's certainly one of the more attractive modern editors, and it's open source if I recall.

You basically have to build the map in your editor, then you run the .map file through three compilers:

QBSP (TxQBSP is the best at the moment IMO)
This makes the physical world model that is the bulk of the .bsp file, and it also populates the .bsp file with all of the entities you have put in the .msp file (solid entities like doors, and point entities like monsters, ammo, light sources and scripting entities (which have a location even though they don't physically appear in the game))

Light
This adds a chunk of light data to the .bsp file, after making a 'light-map', basically every pixel of texture in the map is given a brightness.

Vis
This 'visually optimises' the map, for running speed. It adds a chunk of 'vis-data' to the .bsp file, which tells the game engine, whilst it's running the map, which parts of the map to draw depending on where the player is stood (so it doesn't have to draw the whole world-model in each frame, when you can't see 90% of it anyway)

Once you have run all of these compilers on your map/bsp file, your map will be 'fully compiled' and ready to run.

If you wan't to add CTF to the original maps, you can load the .map sources linked above into an editor, save your .map file after you have added your entities for CTF functionality, and then compile the .map file into a .bsp file, and light and optimist the resulting .bsp file. :) 

Can be flagged in the map file as 'not in deathmatch', I'd imagine that CTF is a type of deathmatch effectively (anyone?).

This way, if you play singleplayer then doors etc will be there, but when you play DM/multiplayer they will be gone.

id software used this feature to add multiplayer support to all of the singleplayer maps in the original Quake. It means you don't have to pack two full-sized different versions of the same map into the game package. 

http://code.google.com/p/realm/downloads/detail?name=bsp-0.96e-opensource.7z&can=2&q=

More here:
http://forums.inside3d.com/viewtopic.php?f=6&t=4685&start=75 

average leafs visible: 593
max leafs visible: 2546 near (-288 224 704)
c_chains: 2003978043
visdatasize: 1058 kb compressed from 4668 kb

Elapsed time: 63h 35m
State time: 13:42

G:\Bsp\Bsp96b\Quake\Maps\pause
Press any key to continue...


What are c_chains 'cause that looks an awfully large number? What is State time? 

Just saw this at I3D: it's possible to have Gtk- and NetRadiant display the actual models for entities instead of the colored boxes. You need to edit the entities.ent file and add the model path to each entry, e.g. model="progs/player.mdl". They are loaded from the pak file, but are displayed unskinned (unless, I suppose, you extract the skin somewhere). The big problem is that only the model is shown, not the bounding box, which makes correct entity placement unnecessarily awkward. 

I had the same with my map.

Awfull lot of vising time, but I gave up at 67houres.
Recompiling some real small brushes to func_wall made it up to 8 houres.
For vising it takes too long.
My example

average leafs visible: 389
max leafs visible: 1544 near (-352 -152 -158)
c_chains: 1540051406
visdatasize: 668 kb compressed from 3718 kb

Elapsed time : 8h 58m
Session time : 8h 59m
State time : 1h 43m

I don't know for state time.
I don't think it are the c_chains, more some queer effect of brushes.
Try hiding extensive places with a big cube. 

Try comparing the bsp limits...


18087 planes 361740
65325 vertexes 783900
29085 nodes 698040
1743 texinfo 69720
56641 faces 1132820
58573 clipnodes 468584
15487 leafs 433636
64691 marksurfaces 129382
236371 surfedges 945484
127066 edges 508264
447 models 28608
96 textures 2493028
lightdata 1639628
visdata 863654
entdata 193675

vertices, clipnodes, faces and marksurfaces are usually the ones to max out first, but sometimes nodes can too. it depends on how you map.

in most (all?) modern engines like fitzquake, the limit for vertices, clipnodes, faces and marksurfaces is 65536.
limit for nodes is 32768.

 

Oh, I am not concerned about limits. And 63 hours vis time is not a problem: I just start the computer, shut the door (noisey fan) and take a peek each night before I go to bed. I just wondered what c_chains were.

No, the map is fine, plays fine, looks fine; and I only use FitzQ so going over a few limits is fine. 

RickyT23 posted a link to BSP editor. Anyone use it? Can it do things better than Hammer?
I tried it out for a few minutes (lots of buttons). Is it worth learning? 

I've used it for many years and never found anything better (but I did stop looking once I had used BspEditor). It is worth learning but use the tutorials and read all the notes because although it has a general Microsoft look and feel, it is not intuitive.

I use version 96B because later versions omitted support for Tony Brownlow's complier routines, and I use that program call to run my own compiler. However, the later versions do have some good additional facilities, so if I was starting again, I would have used the latest version automatically and never have know about the support for Brownlow.

Nevertheless, the built in batch file processes work just as well except that you have to write additional routines to make use of all the features of later compilers.

I have never understood why more people did not latch on to it?