It's because pulling teeth is unpleasant.
There was this old lady from Karelia living in the same apartment complex area. She sometimes took care of kids etc, everyone knew her. I was playing at the yard, a nanny was looking after us. I was maybe four and had a tooth that was loose. I told this Karelian granny about it and she, being the vigorous person that she was, promptly ripped it out. I remember spitting blood for a long while after that. The snow turned red. Fascinating. 

... nice of her? 

I can see her yelling, 'get up and walk it off!' 

Use 2/3 point clipping instead. It actually works and doesn't shit the bed regularly like vertex pulling in radiant does. 

pjw,

Use the what now? 

I'm at work now and don't have radiant installed here, but there should be a button/command to toggle clipping mode. Maybe a button at the top that looks like 3 points connected together?

Clipping mode allows you to define a clip plane (using either two or three points, so it can be tilted on whatever axes) and use it to clip brushes (as you would clip paper with a pair of scissors). You can discard either part or keep both.

This basically allows you to come up with whatever shape/angle you wish without resorting to vert manipulation, which is crap in radiant when it comes to brushes (as you well know). 

Vis is not nice. Im running it with -numpercent, base went from 1 to 100, then it says Full. So far it just says Full. Dont like it! Will Full go from 1 - 100 in the same ways as Base did? 

pjw,

Oh, that kind of clipping. The 2/3 thing threw me at first. Right. I'll try that. Thanks. 

While mapping yesterday, I did something and I don't know how to change it back. My mouse cursor became a hand within WC and all it does is scroll through the 2d views. I cant zoom in, nor add any brushes or entities. I'm stuck in this "scroll" mode. I have never had this happen to me before, and I don't know how to get rid of it. I've tried reinstalling WC to no avail. Anybody have a solution? 

After checking in Hammer it seems that your space key is stuck somehow :P 

Well, that was weird. Right after I posted here, I loaded up WC and the problem was gone. I'm almost positive my space bar wasn't stuck in any way. But at least now I know what to do if it happens again. Thanks. 

quake vising goes through 2 'passes'. the first, base vis is what you get when you do the -quick. the full is the actual vising... it'll go up to 100 *eventually*.

depending on the level, it can take anywhere from 10 minutes to uh...2 or 3 weeks. 

When its done, I'll post my new level. Eventually. How long did it take to do the Warpspasm levels? 

Overnight. Some didn't take too long, a handful of hours (5-10). The worst was Sealed City, because the vis blocking was so bad. 

CDA took 1248 hours... I hope you do not have wide open area into your map ;) 

Its one big wide open area with v. tall buildings!! Still going, hasnt said 1 percent yet... 

you haven't blocked the vis console window with mouse or keyboard and verify that vis is still hogging the cpu. 

You set windows priority for vis to high?

I think we talked about this but I can't remember.

I think it was the obvious answer - 'you can, but it's risky'. 

option -priority #, where 0=below, 1=normal (default) and 2=above. This only affects thread priority and is not risky in any way. You're probably thinking of setting process priority to High or even Realtime, which is usually a very bad idea.

In any case, you typically don't raise the priority for a cpu-intensive app like vis, you lower it so other apps can run.

This way you can vis in the background while playing a game or whatever and as soon you stop keeping the cpu busy, vis will return to full power.

You typically raise priority for apps that normally block a lot on I/O operations (disk/network etc) like copy-processes or similar. Then they will operate faster if you also have a cpu-intensive app running at normal priority.

Priority is not a gas pedal ... 

Vis sucks.

I have gotten to the point where I have discovered the autosave feature! Yippee! It has only failed on me once so far (AAARRGH!!).
Like it because if I want to know how much progress has been made, if I restart the computer, or stop the app, then restart it again (from worldcraft prompt, with only vis selected) when vis starts (as long as it doesnt fail to read the saved vis file) it tells me roughly how much progress has been made!

I think Im pushing 13-14 percent!!!

Question:
Does the process window get to a point where it nolonger has any room for more text?
It often looks as if it has frozen!

Tried '-priority 2' but got bored with it (its pretty boring anyway).

What do you mean 'make sure you havent blocked the vis console window with mouse or keyboard'. How do you make sure vis is still hogging the cpu without pressing ctrl,alt and delete? Or is that what you would have me do?

Also, using XP, I always run compile tools from Worldcraft. Not being a programmer or anything, is there another way of running them?

If anyone can answer any of these questions (AguirRe), say something funny or say something to boost morale, it would be much appreciated! 

It's not VIS that sucks, it's mapping in a way that does not work well with Quake/VIS. 

Large open areas with little vis blocking always result in long processing times. Sometimes it even takes days to get one single portal done.
Don't run vis from Worldcraft, run it in the command prompt with -v. You can break the process with ctrl+c to resume it later (safer than restarting the computer). 

So many questions ... Like neg!ke says, don't run any tools from inside WC, its console window is not very good. Use a std command prompt "dos-box" for builds.

If you're using the AutoSave feature to see the vis progress, something's seriously wrong. Don't do that, you'll just slow down the vis operation by constantly restarting it. You'll get plenty of progress info while it runs if you haven't disabled it.

In a real console window, you can block the process by e.g. starting to select text with the mouse, pressing Pause or other user input. Use Task Manager in XP to see that the vis process is using almost 100% of the cpu.

Finally, if you've only reached 13-14% after running for a long time, you're looking at ages to reach 100%. The fullvis process almost always slows down *very* much in the later stages and the final few percent can easily take 50-90% of the total time. Ask JPL for details if you want to know more about vis patience ...

You'll probably have to clean up your map if you want to be able to fullvis it before the year 3000AD. Remove/simplify/func_wall brush details, add proper vis-blocking, split map etc. 

Use a std command prompt "dos-box" for builds.

he means the windows command prompt. don't go installing DosBox and trying to compile in it. 

support two cores?
Because Cpu gets never over 60% when vising