I think that the compiler UI/program is having problems writing to the path, maybe, but you can try these simple steps:

1 - get the tools into a folder on your c:, like 'C:\quaketools\' or something.

2 - Copy your tool's executables to that directory (TxQBSP.exe, Light.exe and WVis.exe preferably).

3 - Launch a command prompt (Start-> Run (or search)-> type 'CMD', press enter, Or Start->All Programs->Accessories->Command Prompt.

4 - Navigate to the new 'quaketools' directory by typing (without quotes) 'cd c:\quaketools'

5 - Save your .map file (from your editor) into this new directory.

6 - From the command prompt you can now run your tools 1-at-a-time. Type 'txqbsp nameofyourmap', then after that you can run vis and light in the same way.

This is the way the tools are supposed to be used, using your editors UI for the tools can be problematic for a number of reasons (Windows UAC for example). 

http://pastebin.com/0K5Xj3DE

I hope I did that right. I had no idea you were talking about a website. Sorry again! :X 

Thanks for the suggestion. However, most of those instructions are rather foreign to OS X. I could look into it further, though. 

ToeTag has some weird requirements ... I THINK you have to work in the id1/maps folder or the compiler won't work. Something like that. 

/Applications/Quake/id1/<TAppli... 0x10337d0>

This looks like it's trying to interpret an object as an NSString that really isn't one. Maybe that's the root of the problems? 

Wonder of all wonders... it was so simple and I didn't think of it..

Putting toetag in quake/id1/maps actually makes it work..

Ha. thanks again everyone :D 

 

When I was youger so much younger than today, I never needed anybody's help in anyway. But now those days are gone, I'm not so self assured so I need someone to look over my map and play test it for me.

But there's a bit of a barrier: I will not change anything - not game-play, textures, lighting, music; not nuffink nohow. I just want to know if it works, can be played, and doesn't get broken during play.

I really just want confirmation that it is good enough to release to the ever eager public (all 29 of you), or not as the case may be. A kind of second opinion because it most definitely is not as I originally intended.

Anyone up for that? Just one? It's a big file... 

 

and upload the file somewhere, you will usually receive critique in no time... 

This is for a pre-release final bug check thrash of the map, so he doesn't want it to be public. 

SleepwalkR

Oh I'm sure it's something like that. It's a bug I actually fixed in what was going to be the next version of ToeTag before my Mac died and I haven't gotten back to it ... maybe one day. :P 

Competition is good for business ;-) 

Thanks for offering; send me your contact details: boss 'at' mikewoodham 'dot' com

I will be airborne for some time so I will not reply immediately. 

I think there's like 31 people who play now, thanks to TrenchBroom. 

Yeah, it looks good - if I was still mapping I might have given it a try, although I have absolutely no issues with BspEditor.

I wonder how many people really do still play Quake SP maps? 

Normally you'd have it tested BEFORE running the long fullvis..... 

"I wonder how many people really do still play Quake SP maps?"

At least the people here ^^ 

Ooops, excluding the times that I have play-tested my own map, I haven't played Quake for years. 

So I'm just packaging the map for OneTruePurple to play test for me and have a quick look at the darker areas of the map and holy smoke, there's coloured banding all over the dark corners - there'a lot of dak corners as it's a 'cavern' map.

I've only seen these areas after quick Light and quick Vis and they have never shown up with this banding before. I thought running the Utils full-on was supposed to improve the quality?

I used my i7 laptop Nvidia with latest drivers, and my Pent4 with ATI, and they both show the same soddin' thing. What gives? (rhetorical question, I just need therapy) 

 

No, I really am cracking up. Four years ago I used the same computer, same video drivers, same utils, same settings, and the same map file (FMB_bdg). The FullLight/FullVis I did then produced a perfectly acceptable dark-corners map with no banding - I have the original bsp output file, I've checked it.

Now, the only thing I have added since then is the Skip util; I didn't use the Skip texture in the map but it runs automatically as part of the batch file for a FullVis.

Can anyone shed some light on this (not too much in the dark corners though)?

What seems quite rediculous is that I can run a quick Light/Vis and there is no banding. As there's also no grey-flash or snagging etc, should I just release it not fully Vis'd.

Is that heresy? 

But you should be able to run light independently of vis anyway - removing the banding by having the x4 or whatever turned off.

So you shouldn't need to re-run vis to regenerate the light map. I think. 

Just re-do light. 

What's this about banding - care to post a screenshot?

Btw, if you still have the original .prt and .vis files, you can fix certain things that require a QBSP recompile (texture errors to a certain degree, bmodel positions) and simply insert the fullvis information on the fly.