de_port_go (remake of original de_port)

What are you doing exactly? You could have addressed the above in a single reply

Honestly I think it's got too many areas at the moment. Port was a big enough map as it was but you've added more areas..

Quote from SpronyvanJohnson

What are you doing exactly? You could have addressed the above in a single reply

postcount ++

I cry a little inside thinking about optimising this map. St.Mary map also had this same issue with framerate. Not sure if they solved it since then but worth checking the level out/asking in this thread:

Have you converted much of your brush work to func_details?, no draw textures etc on hidden faces besides area portals and skip/hint brushes.

Quote from Vaya

What's your secret?eh? How do you have such high fps? It runs at 30-40 fps in some areas while it is usually at 50-60 on my computer, but it is still playable, optimization is welcomed but it is nonetheless playable I have to play it a little more, but it seems that T's do not have many options do they?

Quote from laminutederire

What's your secret?eh? How do you have such high fps? It runs at 30-40 fps in some areas while it is usually at 50-60 on my computer, but it is still playable, optimization is welcomed but it is nonetheless playable I have to play it a little more, but it seems that T's do not have many options do they?

I have:

i5 4690k

GTX 970

12gb of shit ddr3 ram (next upgrade )

Launch options:

-threads 4 -processheap -high

Launch options should help. I was still get microstutters on my set up until I put those launch options in. Getting microstutters on this map regardless...

Thanks Vaya I'll try! But about this map, I think that there should be another path from T spawn to A, otherwise you have to go through a sniper fest. Meaning that you have to use precious smoke grenades way too early in my opinion, however I may be wrong!

Quote from Vaya

Honestly I think it's got too many areas at the moment. Port was a big enough map as it was but you've added more areas..

Quote from Vaya

postcount ++

What are you doing exactly? You could have addressed the above in a single reply

Quote from AkatsukiUK

I cry a little inside thinking about optimising this map. St.Mary map also had this same issue with framerate. Not sure if they solved it since then but worth checking the level out/asking in this thread:

Have you converted much of your brush work to func_details?, no draw textures etc on hidden faces besides area portals and skip/hint brushes.

unremarkable player helped out Untor with optimizing St Mary. There was a lot of room for improvement and he did a great job at it.

We were looking at the optimisation of this one yesterday. I think a lot more func_detailing (you have some but nowhere near enough) and hint/skips is a good place to start when you're happy with the layout- IMO You could probably lose a lot of the interiors for a better playing map.

The map seems to be covered in trigger brushes too? Is this the case of showtriggers_toggle playing up or is it actually covered in triggers?

Also func_lod and occluders can help a lot to optimize the level. Hint/skips are great, but mostly don't make a lot of difference in such open maps.

Looks good, I don't think it suffers from too many props

It's a good port

You have to consider for a big openned map to reduce the number of visleaves. More visleaves in open space increase a lot vis calculation time ingame (and also compilation time). load your portal file in hammer to see if you can do something. (you can use viscluster and hint to clean stupid automatic leaves) If you need explanation I can help.

Quote from 3Dnj

(you can use viscluster and hint to clean stupid automatic leaves)

Just to clear this up: Visclusters don't alter the vis, it just tells the compiler that the containing leaves can see each other, speeding up compile.

Yeah I know. I use hint to clean leaves and viscluster when there is too much leaves that don't have any optimisation purpose (like in vistas or sky)