to meltslime: it sounds unlikely to me. there is a huge performance gap between fast-vised and full-vised version of the same map. on-the-fly fullvis during just a few seconds of loading? it's too good to be truth :-) 

That you haven't noticed them doesn't mean that they aren't there. If you don't know what is the intended behavior of a map you can't know if it isn't working well or not.

An example: i made a map where it doesn't work as i intended only in DP due to exploboxes behaving differently in that engine. The possibilities of the player noticing that something is wrong is zero as exploboxes are still working, but it still affects the map. 

Darkplaces uses it's own real time portal culling technique, controlled by "r_useportalculling" setting. Try setting it to 0 and seeing if your performance improves. The version of DP I have on my machine defaults to 2 and causes flickering all over the place on Warren's map. With it set at 2, I get 90 FPS in some of the worst spots. With the setting off or at 1, I get 160 FPS in those same areas. (using darkplaces 'showfps' command) FitzQuake lacks this command, but from what I can tell from external sources is that the engine is capped at 72 FPS, and I was maxed at all points of the map anyway, so it's difficult to compare.

Load jam5_warren in Darkplaces, note that it takes several seconds to load, and then note the million "Mod_Q1BSP_RecursiveNodePortals: WARNING: new portal was clipped away" warnings in the console after it loads. Those are because Darkplaces is trying to do basically what the compile tools do and generating it's own portals for the map when loading the map for the first time, but the same error that exists within the .bsp that prevents it from being properly vis'd is also preventing Darkplaces from generating it's own portals to do it's real time visibility culling tricks.

I'm guessing the broken portals are being hellish on DP's portal culling system and the slowdown is the result of the engine spending more time trying to decide what to render, and thus spending more time than if it just rendered everything.

So really... half the map's fault, half the engine's fault. 

for checking fps in fitzquake or quakespasm, do:
host_maxfps 1000
scr_showfps 1

note that this will mess up physics, so only use it for benchmarking, and in quakespasm at least, make sure to reset host_maxfps back to 72 because it's archived. 

to scampie: thanks for the clarification. i'll try r_useportalculling command and see what happens. i tried to recompile warrens map with h2map.exe but the whole proces failed immediately after basevis due to the error described above.

vis.exe continues fullvising the even after the warnings but the process is extremely slow or maybe it has reached some infinite loop... 

I think I pushed the architecture too far. Too many weird angles, too much stuff off the grid, etc. 

Since I come here a lot asking for stuff and this forum is always helpful, I felt like coming to just congratulate Skacky for his beautiful environment art. I wished the higher levels was playable too, but it's wonderful the way it is.

There are other specially beautiful levels in this pack (the floating castle, the chained city, ...) and I should congratulate everybody, but this blue arabic dream just got me. I'm dazzled. 

That's some awesome looking maps guys, wow! People still making these kinds of levels for quake 1 when the 20-year anniversary is just around the corner, who would have thought? 

but I dont care for the mod personally.

Would love to see skacky's map made into a real map. And mfx's too. Others a bit too arenas-ish to be proper maps. 

without having qonquer on and my god is it beautiful!

mfx's has great brushwork.

scampie's has great lighting imho, those hallways were lit perfectly! 

is where mappers go when they die, if they were good.