Those errors are only related to the fractal shaders, so if the rest of the map looks ok (more or less like in the trailer and screenshots) it should be playable. I have tried the map on Intel HD 3000 and I got the same errors. I think it's because these GPUs don't support doubles which are used in the fractals.

"unknown command: volcolor" error seems to be typo, sed -i 's/volcolor/volcolour/' ac2.cfg fixed it;
this helped me to clear shader errors:
sed -i 's/dvec/vec/g' ac2_shaders.cfg
sed -i 's/double/float/g' ac2_shaders.cfg
anyway, thanks for great map, just finished it, was really amazed by muh graphics

Wow, "volcolor" must have changed to "volcolour" just a few days ago, I didn't notice anything while using the svn but I might have missed it since I made the map in base Tesseract and I get "unknown command: volcolor" all the time there.

Cool, thanks for the feedback and AO tip. You should've played the map with original non-broken config :P Most of the things got broken by our editing, that includes the looping corridor and overbrighted lights (fixing volcolour typo doubles the volumetric light intensity). I've cleared out most of the stuff outside the map and tried to add collision to the rocks. It works but I still had to noclip them in some places to avoid weird collisions. I've also fixed the teleport at the tower of worlds. Since the edited config did have some bugs I'll need to do more testing before including it.

As for the blue puzzle with the bridges, you can figure out how to cross them by carefully looking around.

Well before you include anything or change too much on your part, i've been doing more optimizations to the code and there's more things i need to go over with you. Taking a quick look at camloops made me want to smack you :p

EDIT: I've been going through this thing all day on and off, fixing things, optimizing, cleaning code. At first i horribly broke everything. Shaders, lighting, triggers. I was able to fix all of that though, and even the blue corridor (which was simply a missing $). I have marked areas of interest in the script which i don't know if they need changing or removal, and for now i'd like to think that the code is mostly proper, albeit very messy, as 2000 lines would entail (maybe i should break it all up in many files just to get back at you for being stubborn :P)

For now i'll await your return, and i'll show you how nicely this all runs again once you're back, as well as improve all this MOAR! :)