Then what's taking days upon days of VIS time? Is your computer older maybe? Nothing else in those shots looks particularly VIS unfriendly... 

The map is rather big (8Mb) and fast vis takes no time.
R_speeds are extremely high.
I used no func walls, and hardly vis blokkers. 

hey madfox nice theme and you've got some nice construction here but the texturing could use a lot of work. if you can't get those big bricks ending in the right place, then i'd use much smaller bricks so you don't notice when they get cut in half. in acrus10.jpg for instance, almost every brick gets cut in half at the edge, which ends up looking sloppy. also things like underneath archways and ceilings don't need to be the same brick texture. the railings i think wood look better in wood too. 

I crawled out of this map construction with my first suceedment of texture alignment. And as it was the first mistake I never saw in mapping
I experience it as a small improvement.

My first goal was to make the map excist without homs or max warnings.
Reason why I had to take advantage of the mdl files.
And as the texture count grows on 72 it still could have some more archivement.

I'm now on a P4 3Ghz and I never had a longer vising count than 8 houres. After boxing the map the vistime just raised dramatical.
And I can't delete that because the map immedeately starts leaking. 

Are you trying to beat the CDA fullvis runtime ? :P
Wide open area needs long time to compile, and regarding the shots, it looks awesome, plenty of details everywhere... You will certainely have to wait for almost the same time before seeing a 100% fullvised map...
Anyway, good luck, be patient, and we all hope to see the release soon..
Keep it up ! 

After boxing the map

are you saying you built a giant box around the entire map to get it to vis? because that would certainly explain why it's taking so long. 

fullvis runtime to beat is 1248 hours... As of today, CDA still wins :) 

Oh yeah, OK, if you can't get it to VIS without boxing that would explain your VIS times. Having the process all of the outside stuff that QBSP would normally cull away will double or triple your VIS times easily. 

You need to find the leak, MF. Boxing stuff makes baby Jesus cry. 

 

muh_bad 

'Boxing stuff nails baby Jesus to a wall' doesn't have the same ring to it. 

And on the road the map has crossed was a point where the box wasn't necessary to compile it, but then the max limit was reached and it had many hom's.

but that map ended on a burned out mobo, so make my cahsbox smile. 

http://www.suspenlute.com/stuff/hahahawtf.jpg 

Hey ! Nice shot ! 

"He" is just slow and busy as hell. 

hey, you can take all the time you want as long as you're branching out! it's good to see you've still got your roots in the community! it wood be great if you posted more shots! 

Shoots. 

http://www.suspenlute.com/stuff/bigger.jpg

kind of my take on the "r_speeds be damned" concept (though on a much more subdued scale) 

http://wantonhubris.com/blog/wp-content/uploads/2008/10/abstract_preview1.jpg

Something I'm working on involving custom textures and a sort of abstracted look for a level. This is the general look of the level. I'm keeping the more interesting things to myself for now. 

pretty cool idea Willem, although now I'm really wondering what the textured version will look like. 

of this doom2 level i was doing a while ago, but never finsihed because i had no ideas. just made because i was bored :)

http://pablo.kotogoto.com/cymk2.png
http://pablo.kotogoto.com/cymk1.png 

Neat, I like that! Could be some cool possibilities there. 

Those shots remind of me of p0rtal :) 

I like the cel-shaded style Willem, reminds of Warsow a bit.

I actually like Fern's Mondrian 'suggestion', possibly add some random primary colour surfaces (ie, keep the majority as white squares with black outline, but replace a few of the white squares with red/blue/yellow/etc (still with black outlines ofc))