Store Page
Counter-Strike 2
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Counter-Strike 2

Store Page
Counter-Strike 2 >  Workshop > The Kommissar's Workshop > Crash > Discussions
Crash
Description Discussions12 Comments872 Change Notes
Lost 23 Jun, 2015 @ 2:46am
Optimization
So im just asuming that it is optimization that is causing this but if im wrong corrent me.

I dont think this map has much optimization just due the fact that i have noticed when i look towards the centre of the map i experience alot of lag (20-40 fps) but when i look at a wall i get about 60-100fps. I know this isnt my pc because it only happens on this map. If you could please fix this it would be really good thanks :D

-Lost
< >
Showing 1-6 of 6 comments
syn 23 Jun, 2015 @ 4:35pm 
What are your pc specs?
#1
Lost 23 Jun, 2015 @ 6:40pm 
Originally posted by {SøtT} RespawnPro:
What are your pc specs?
http://i.gyazo.com/d3d18c0e91fd422ad3cab283b2727d80.png <-- not scam i swear.
#2
The Kommissar  [developer] 24 Jun, 2015 @ 1:07am 
It's just the source rendering system, not optimisation, source only renders stuff if you can see it, a failure in optimisation at say, mid, would mean that you had high FPS around complex props in the 3 story building, but low FPS around complex props at mid, this would mean that the map isn't telling source not to render the ♥♥♥♥ behind you any more or vica versa. It's really fcking complex to describe, so hope this kinda helps
#3
Lost 24 Jun, 2015 @ 3:25am 
ah ok. i get what you mean, thanks for explaining
#4
Cole 24 Jun, 2015 @ 12:48pm 
Originally posted by Jack_is_my_name:
It's just the source rendering system, not optimisation, source only renders stuff if you can see it, a failure in optimisation at say, mid, would mean that you had high FPS around complex props in the 3 story building, but low FPS around complex props at mid, this would mean that the map isn't telling source not to render the ♥♥♥♥ behind you any more or vica versa. It's really fcking complex to describe, so hope this kinda helps

Where did you hear this?

You need to use the texture "nodraw" to not render things players see...

Example, if there's a fence, anything behind the fence, that players can not see, add a "nodraw" texture to the back of it.
#5
The Kommissar  [developer] 24 Jun, 2015 @ 12:53pm 
Originally posted by <TSR> Cole:
Originally posted by Jack_is_my_name:
It's just the source rendering system, not optimisation, source only renders stuff if you can see it, a failure in optimisation at say, mid, would mean that you had high FPS around complex props in the 3 story building, but low FPS around complex props at mid, this would mean that the map isn't telling source not to render the ♥♥♥♥ behind you any more or vica versa. It's really fcking complex to describe, so hope this kinda helps

Where did you hear this?

You need to use the texture "nodraw" to not render things players see...

Example, if there's a fence, anything behind the fence, that players can not see, add a "nodraw" texture to the back of it.

My god, please, don't lecture me on optimisation, any idiot knows what a nodraw texture is, I'm talking about portal flow, hints, skip, areaportals, prop fade, just, please, stahp.
#6
< >
Showing 1-6 of 6 comments
Per page: 1530 50