 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Well I don't but this seems pretty critical. This is what I get when I try to compile: "The file d:\games\quake\id1\maps\jatkuu.bsp was not built. Do you want to continue?"
If I click 'yes' it just prints the following in the compile window: ----------------------------------------------- ** Executing... ** Command: Copy File ** Parameters: "D:\WORLDC~2\RMF\JATKUU.map" "D:\games\QUAKE\ID1\maps\JATKUU.map" ** Executing... ** Command: D:\worldcraftFULL\Q1Tools\QBSP.EXE ** Parameters: D:\games\QUAKE\ID1\maps\JATKUU outputfile: D:\games\QUAKE\ID1\maps\JATKUU.bsp WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush with duplicate plane WARNING: brush plane with no normal ************ ERROR ************ Line 4478 is incomplete ** Executing... ** Command: D:\worldcraftFULL\Q1Tools\LIGHT.EXE ** Parameters: -extra D:\games\QUAKE\ID1\maps\JATKUU ----- LightFaces ---- extra sampling enabled ************ ERROR ************ Error opening D:\games\QUAKE\ID1\maps\JATKUU.bsp: No such file or directory ** Executing... ** Command: D:\worldcraftFULL\Q1Tools\Vis.exe ** Parameters: D:\games\QUAKE\ID1\maps\JATKUU ---- vis ---- ************ ERROR ************ Error opening D:\games\QUAKE\ID1\maps\JATKUU.bsp: No such file or directory ----------------------------------------------- So no BSP is created - I can't play it. Even the old bsp with the same name disappeared along with this problem. Any suggestions? that is what I would recommend doing.
Open up the map in a text editor. I would bet you a donut that 4478 is the last line in the text and it is lacking a '}' to encapsulate the worldspawn entity. ...the six milllion 'brush with duplicate plane' errors aren't a problem, but that 'brush with no normal' error at the end is AFAIK a compile breaker. Fix that brush and you should be right.
So I just have to find the brush first. Could it be a cylinder I created? The error occured for the first time a bit after I had created the level's first cylinder brush.
but MapSpy might be able to find the bad brush. It's designed for Q2, but it's also great for finding BSP problems in maps for all Q-engine games.
http://mapspy.gamedesign.net/ Any idea what this is?
---- Vis 2.29 ---- Modified by Bengt Jardrup File: E:\Games\QUAKE\ID1\maps\opstart.bsp 166 portalleafs 645 numportals State file out of date, will be overwritten testlevel = 4 Using Bengt's latest tools, have checked the Tool Tips txt, doesn't say anything regarding this. it took 28 seconds to VIS a real small room on full, which is I thought was odd. is when the vis save is out of date w/relation to the bsp file.
usually happens when you compile a map again and the statefile for the vis processing is out of date. you can safely ignore this. If I were to bevel every rivet texture like this, and other textures throughout a map along the walls and floors...
http://www.phait-accompli.com/q/crap/bev.jpg What would that add significantly too, if anything? :P
you're wpoly count will go up quite high as will clipnodes unless you clip _all_ those surfaces marksurfaces will be affected too, i'm sure, but not by how much it would look damn cool, but lighting may also be a little strange at times unless you use a high anglesensitivity setting un aguire's light program. I realized exactly how bad this would become doing this for every texture just to compensate for lack of bump-mapping and not forcing the player to use a custom engine...
It sure does look nice though: http://www.phait-accompli.com/q/crap/bev2.jpg http://www.phait-accompli.com/q/crap/bev3.jpg *sniffle* Could be doable for a small map... that sort of technique works a lot better in quake3 (and quake2 probably,) where the inverse lighting model is designed to flatter it a lot more. Quake's lighting model seems to work best with big, simple geometry with high-contrast textures for details.
all this is my opinion of course.... why do all your screenshots look so washed out? like you're using the old glquake -gamma feature or something.
Maybe the problem is the bevels are too big anyways.
Heres a question about Bengt's tools. I've checked the readme's and stuff and can't find any info on water transparency. I know you can type r_wateralpha x.x in the console, but apparently this only works for maps that were compiled with support for wateralpha, correct? Cause I tried it in a test map, it worked. I tried it in an id map, it didn't work. Would it not be wise to set the wateralpha in an autoexec for the player, or just tell them to type it in. Washed out? You must have a bright monitor, it looks fine to me. Screenshots end up as really dark TGA's, I up the gamma to about 1.5 to 1.9 depending and they look better.
What does anyone use to export Q1 skins? I have Qped which manages PAK files, it can view the skins properly, but you can't export it - just the
So I'm testing my skin in progress, have added it to the MDL, then it's going in a custom pak. QME has a limit of 20 frames, cannot export Ogre.mdl and MDL 'Quake Model Editor' says 'floating point overflow' :|
If you're just looking to swap the skin on a model, adquedit will suffice. But because it's such a handy program to have around in full, I'd recommend getting the full version of QMe. t's handy for editing the mesh or animations of a model, plus gives you a preview of the skin on the model straight off. Add to that the two click removal of any fullbrights, and it's more useful than anything else. The full version of 3.0 can be found at http://www.edgefiles.com/files/9100.html
You can use the patch that comes with the 3.1 demo to turn this into the full version of 3.1. Thanks about the full QME but the file is not at any of the servers linked there. I'll go hunt around for adquedit.
What is it that the doors are doing/not doing wrongly?
I can see that you have some multiple-triggers that seem to be unattached, but give us a clue and someone will help.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |