They could blame QuArK, but for some reason they are even defending it. 

I remembered with the Koho-vis test my computer ended upon 11 minutes, which I thought quiet fast.

The map I was making turned out on 87% after 5 days and it was there already 2 days.
I scratched the map because of 3 homs and started all over again.
Now making sure all polys were on integer grid.

The map turned out alright. And it still takes 6 houres, but that's understandable, having all on grid.

Still 2 homs prevent me from publishing it. 

It is not the tool you are using (i.e QuArK), in my case this is the size of the map (i.e 7915 brushes), and the way it is built.

If you are doing crap, you can have the best equipment, it will not help you :P 

if you have a map which has 8000 marksurfaces and r_speeds never go past 400 then it will vis in a few minutes.

If you have a map with 40'000+ marksurfaces and r_speeds rarely drop below 20'000 (at level 4) then it will take days. 

If you have a map with 40'000+ marksurfaces and r_speeds rarely drop below 20'000 (at level 4) then it will take days.

You are wrong: it can take a month !!! 

Around 30. 

that's still very very slow for something which todays machine should be able to compute in minutes. 

just a tought, huge Q3 map take much time to compile? 

that's still very very slow for something which todays machine should be able to compute in minutes.

I would say yes and no: the limitations come from the VIS algorithm itself that is a recursive algorithm, so with very huge and complex map that has tons of volume to inspect (VIS is based onto volume rendering) the runtime becomes very high...

Also, a big processor, not to say a multi core processor, does not help that much. First because most of VIS tool are not coded for multi-core processor, and also compared to what I have, it would only save 20% of the runtime best case I guess (i.e i have an AMD Athlon 2600+), and the bottleneck is not only the CPU only but the motherboard fequency and peripherals access (i.e to memory particularly)

Anyway, when a process run for thousand of hours (more than a month) you have to be patient, so 2 or 3 days less will not make the difference there IMHO... as I don't have any manager pressure to sort out my map ;) 

This is very interesting. We were just talking about the saturation of CPU speeds in my computer and graphics architectures class today, especialy things like how the cpu works with fetching instructions (particurarly in terms of arithmetic processing dependacy and parallelism). It would be cool if there is a way to make this whole VIS process faster , actualy the entire compilation process, without having to sacrifice detail in the 3D model of the level. But I guess that would require re-writting a lot of things from scratch.

My interpretation of this is that the build tools such as the BSP, CSG, VIS and RAD perform a lot of heavy computations, which require CPU level ALU's (arithmetic logic unit) to compute. Seeing as todays dedicated graphics cards hold a lot of processing power, especialy when it comes to floating point calculations, and fully programmable rendering pipelines, I'm guessing it would possible to re-write and optimize the code to work the GPU's, which I'm assuming would speed things up dramaticaly. But who would want todo all that work :)? 

The Old One. 

what makes the Q1 model files so irritating incompatible to handle...argh!

repeated message, i know but I almost learned Max3d manual on importing and exporting them.
They keep dragging on verticejumps and triangle catches.
Finally had my model boned and animated then it turned out rejected.

Starting from scratch won't mind, but manipulating excisting files can be a doughnut. 

I'm guessing it would possible to re-write and optimize the code to work the GPU's, which I'm assuming would speed things up dramaticaly.

Indeed, I know some application prefers to use GPU instead of the CPU, because of the ALU performances, but it needs to adapt the software to be adaptable to the GPU... though...

Anyway, Quake standard does not like big map. It has not been built for what we are asking today. The community is constantly asking for bigger / better / more detailed maps, even if the VIS tools have made impressive progresses (thanks aguirRe !), the overall runtime is suffering... but this sacrifice is worth supporting it, as it enables fabulous maps and projects...

I think I'll try to contact aguirRe to get his point of view about using GPU instead of CPU, maybe he would accrpt to try the porting... who knows ? 

Is it possible with Quoth to have monster statues, that will wake-up on trigger event ? 

#1 I use WC 1.6 it supports a color picker. The format is Quake2 0-1,0-1,0-1 for RGB. What is considered the standard 0-1 or 0-255 for RGB.

#2 What modern tools support the 0-1 format? (not Hmap2).

#3 Must obey the use of _color so as not to screw with Quoth's light entities. 

i'm thinking this: func_wall with model key set to the monster and appropriate frame (like you set up for a monster corpse).

then a trigger that kills the func_wall model and spawns in the correct monster.

maybe some debris spawners for effect and a func_togglewall on top of the func_wall to make it 'solid'. 

OK, thanks, I'll try it.

I thought it was something available with Quoth. It may be good idea to add such feature BTW ;) 

You will probably run into a problem with the func_wall, "SOLID_BSP with a non BSP model". You can use mapobject_custom to similar effect, although you'll have the non-solid problem. 

yeah, my bad. for my original post, i should have said func_illusionary instead, since func_wall doesn't work, but i totally forgot you added in the custom mapobj entity, preach. :) 

both fly a plane 

Dale Earnhardt : "I'd hit it like a wall!" 

No problem ;) I'll test the method ASAP :D 

The real punchline is For both, their final hit was "The Wall" 

#8322 posted by Willem [24.199.192.130] on 2009/02/22 19:22:40
Dale Earnhardt : "I'd hit it like a wall!"

As for Dale Jr. I have seen him walk out of a bar with pair of fugly skanks on his arms. He'll hit on anything. 

When I run WC 3.33, it says the following for everything in the textures directory:

Error creating HLWAD: c:\program files\worldcraft\textures\id_base.hlwad ... details ...No log exists.

This is not such a big deal since I already have the Quake/Hipnotic/Raven etc textures converted and working. But if I want to convert new textures, it won't work.

Any ideas?