I cleaned it up a bit. Hmm, don't know if I could notice much difference.

The mouse is still responsive, I can look around quickly but walking is in slow motion... isn't that weird? Shouldn't both be slow??

U said walking is slow but looking around isnt , have u checked ur the actual fps the game is running at ? The level lookz like it should run fine even if it's all made out of geometry.

Have you written the player-Action of yourself? If yes, increase the Speed-Variable, if not, set the Force-Skill higher. Maybe that's it...

which version of Gamestudio do you use? 6.4 can get very slow from my experience.

I'm using templates for movement. It works fine on my laptop, so I'll have to use that allthough I need it for a gig, guess I'll have to do that with some drum machines and stuff. Might work out ok anyway :/

Now the biggest problem is disappearing surfaces. Half of my level turned invisible when I applied the right textures on each object. So I did an experiment, put default texture on my entire map... and voila! I can see all the surfaces again!! Obviously something wring with my textures. What is the safest texture format to use??? pcx?? ...how large... 64x64???

AAAaaaaaghh... I'll have to stay up all night to try and finish this by 10 o clock morning.

Seems my textures had been accidentally saved in a strange resolution... 243,875 pixels/inch. The default texture is 96.... could something like this cause so much trouble?

I'm don't really have the necessary experience and knowledge to offer adequate WED tips, but I'll give it a shot anyway.
*Snap all block geometry to the grid.
*Do not overlap, snap instead.
*Do not create planes (blocks) thinner than 2 quants.
*Move the faces and vertices yourself. Try not to use CSG Subtract.
*If possible, instead of using holes or null spaces,
---use textures to simulate static portals (windows, doors ).
---There appears to be a fair amount of holes/null space in your level.
---Using textures instead, may increase performance significantly.
*If accurate lighting isn't truly necessary,
---you can compile components/rooms separately to map entities
---to save time on compiling.
---Select the faces of the component and click "finish".
---Save the .wmp geometry group for the map component.
---To open the file in another instance of WED,
---double-click the .wmp map geometry component just saved.
---Compile to map entity in the other instance of WED.
---Close the other instance of WED.
---Return to the first instance of WED which contains the main level.
---Add the map entity just compiled.
---Line the map entity up with its uncompiled duplicate geometry
---in the main level.
---Delete the uncompiled duplicate geometry in the main level.
To reduce compile time use "flat" instead of "shaded".

Hurray!!! Chainging to flat instead of shaded got my surfaces visible again, and it runs a bit faster I think. I'm back in business! =D Thanks testDummy!!!