Need some optimization help

I saw your map and not all the textures are packed, please fix that.
As for the optimization, use mat_leafvis 3 and mat_wireframe 3 to see what visleaves are present and what is currently being rendered.

Read this article from Valve's official site.

For the general design of the map, I would suggest:
1. Get rid of the death hatches in the corner, they'll be annoying (but maybe open them if the round is too one-sided?)
2. Make the boundary between the space station bits and the moon surface bits more pronounced: Metal cubes won't grow on artificial walls and there should be only temporary-looking platforms bolted onto the asteroid surface.
3. Add noise to the moon displacements, even the area around the pit, to make them look more organic.
4. If you notice lag, consider using more opaque walls instead of windows. You can use a 3D skybox to fake looking into another area.
5. More arrows to let us know where amongst the details we should actually go.
6. You're in outer space, where it's night all the time. Spotlights can go a long way toward making the players focus on important parts of the map.

Thanks for sharing!

It might be a shiny surface, so perhaps the envmap isn't packed and that's why I'm seeing a missing texture error. Or maybe it's a bad glass texture.
If you have modeling experience I would suggest making a different waterfall texture or use a displacement with the waterfall scrolling texture. GCFscape is good for unpacking stuff in tf2.

https://steamcommunity.com/id/CyberenB/home/
Check the latest screenshots.

Kill_the_Bug said:

textures not packed? I used compile pal for the first time to compile and pack then changed folder names and run map to check for the missing textures and missing models didn't see any - I'll check again thanks

Click to expand...

If you're having trouble packing files with Compile Pal, try with BSPZIP (command-line but pretty simple; let me know if you need help with that.)

you have a lot of yucky areas on the map where windows that aren't func_details are cutting into your visleaves.






it's either that or maybe i just decompiled your map wrong somehow.

edit: mat_leafvis tells a different story, but would like to say that there are just some strange areas where nearly the entire map will be rendered if you stand there, but go away if you just jump a bit. particularly, the first point from mid.

Evidently it's not func_detail if it's still cutting vis.