http://kneedeepinthedoomed.files.wordpress.com/2010/08/curves11.jpg is a waste of brushes btw. You could do with one less. Make the two outer ones end in the edge and then use one "cake slice" for the middle one. 

Lawl. Name and shame. That's horrible.

Also, doing it properly would generate a lot less than 1 extra face (which is more important than brush count) since the Q1 compilers are horrible for that (afaik, and as compared to the D3 bsp compiler). 

if you're going to have a middle 1:1 slanty brush the two either side of it should surely be 1:4 & 4:1.. 1:2 & 2:1 doesn't need that brush in the middle

sorry to derail the thread necros :P for what it's worth i've been using this tool for a while now & recommend it wholeheartedly! 

 

...and in the beginning you got other things to worry about than whether a curve you made has 4 or 5 brushes. :)

I'll try your tool tomorrow necros, I need to install some .NET framework update first it seems. 

there's no reason to teach a sub-optimal technique unless it's easier to use... it's the things we learn first that stick with us the longest. 

I carve all of my maps out of one large solid brush, for example. 

 

Thanks. 

"The application failed to initialize properly (0xc0000135). Click on OK to terminate the application."


In other words: I can't even start it up.

Win32 XP pro SP3 

this requires the vb .net runtimes (it's a vb app). 

That explains :) 

I finally gave this a try and I like it. But:

* When I compile my new map using Tyran's tools and your frontend, VIS crashed after it is done ("Windows has detected an error, app stopped working, blabla...") and the whole process is aborted. When I use my shell scripts to call the same VIS executable, it works without crashing. oO

And a suggestion:

* What about a huge "COMPILE" button on all forms of the GUI so you don't have to go File=>Compile via the menu?

And I have a general question on the point files (lin vs pts) which is not directly related to your tool though. How do you tell the VIS tool which pointfile format you want? I guess there is a command line parameter but I couldn't find any info on that. 

* When I compile my new map using Tyran's tools and your frontend, VIS crashed after it is done ("Windows has detected an error, app stopped working, blabla...") and the whole process is aborted. When I use my shell scripts to call the same VIS executable, it works without crashing. oO

if anything crashes, it was not directly caused by my gui. what my gui really does is just create a batch file when you compile and then it runs the batch file.
it IS possible that something in the generated batch file is causing the crash however.
the way i generate the batch file is to call the compiler programs with their full path names
ie: "C:\Quake\Compilers\vis.exe" instead of just "vis.exe". it's possible that may be causing the problem... but that's just a wild guess.
if you can tell me where to get the specific tyrann vis, i'll take a look at it.
tbh, you'd be better off using aguirre's compilers as they are much more up to date: http://user.tninet.se/~xir870k/

* What about a huge "COMPILE" button on all forms of the GUI so you don't have to go File=>Compile via the menu?

i could add that, i guess. if you look next to the 'compile' option in the menu, you'll see that the Ctrl+C shortcut is available instead, which i find faster. ^_^ (Ctrl+R for Run, Ctrl+P for pointfile)

And I have a general question on the point files (lin vs pts) which is not directly related to your tool though. How do you tell the VIS tool which pointfile format you want? I guess there is a command line parameter but I couldn't find any info on that.

you can't. my gui just renames the files to the appropriate extension, but quake compilers always create .pts files (and it's qbsp that makes it, not vis, btw :) ) 

Could have had the shortcut idea myself I guess. ;)(but I wrote this some days after I tried it and at work where I didn't have the tool).

Peg told me about exactly the compile tools you mentioned today, thanks for the link.

And on the point files: Ah k, I thought they were in different format but it's just the extension. Thanks for the clarification. 

a question; are they supposed to be copied with the bsp to the output folder? my output folder was the same as my working folder until recently, but i've changed and noticed only the bsp gets copied across now.. 

no, the pts files do not get copied automatically from work -> output. in fact, pts files should never appear in output.

source folder: where you work and save your map. pts file ends up here when you press CTRL+P.

work folder: source .map is copied here and all the crap involved in compiling is here (.prt files, .vis files...)

output folder: the only thing that goes here is the .bsp file. 

 

it makes sense to have it output with the .bsp imo, as when you type 'pointfile' in quake it searches in the same directory the map was loaded from. at the moment you have to copy it manually each time, which is a bit of a pain when on a mass plugging session 

ah ok

i didn't know anyone used the builtin pointfile thing anymore, i figured everyone used editor pointfile loading.

http://necros.quaddicted.com/downloads/ne_q1spCompilingGui103.zip

here's a fixed version that copies both pts files and lit files into the output folder. thanks for bringing those two things to my attention. :) 

i'm still a vintage WC1.6 user so that option isn't open to me :D

tanks! 

the link to this on your site appears to be dead. i would plug my old harddrive in and copy the file over to my new(ish) PC but, you know, i'm pretty lazy. 

http://www.quaddicted.com/files/tools/ne_q1spCompilingGui103.zip 

Thanks for reminding me. I've been slowly moving my stuff back to wordpress but the links haven't been updated. I'll have to point to quaddicted mirrors (probably the only sources for now at least) until I can get my own hosting going.