Sorry, steam didn't notify me of the message you sent me earlier this week. The container in v1 has this kind of clip brush setup:
[uploaded 4 testing] zm_murkwater
- Thread starter Makaify
- Start date
Great map,but it seems like this is the new op spot,this whole area is crouch only and only accessible from the left side of my screenshot:
On the other side,you can only boost using a teammate,as there are no movable props to help yourself up: I suggest you add a box so people can climb from both sides without the help of teammates or movable props (e.g little tall box)
On the other side,you can only boost using a teammate,as there are no movable props to help yourself up: I suggest you add a box so people can climb from both sides without the help of teammates or movable props (e.g little tall box)
Those crouch areas should generally be avoided as they cause serveral problems.
1. The spots are easy to defend
2. Gathering camperz cause lags
3. Lagging servers cause player to leave
Please reconsider this spot and make it a non crouch spot, this would give the map better chances to be added after it is finished.
1. The spots are easy to defend
2. Gathering camperz cause lags
3. Lagging servers cause player to leave
Please reconsider this spot and make it a non crouch spot, this would give the map better chances to be added after it is finished.
Yeah before you modify the map any further:
1) Haven't seen it in practice but this is another crouch spot camperz might try to abuse.
2) Not sure if you can see it since it is in small letters but my net_graph shows that my fps drop to 80 when I am in that middle area ( sometimes even lower,and I normally play on 200+)
Is this an optimization issue or something?
1) Haven't seen it in practice but this is another crouch spot camperz might try to abuse.
2) Not sure if you can see it since it is in small letters but my net_graph shows that my fps drop to 80 when I am in that middle area ( sometimes even lower,and I normally play on 200+)
Is this an optimization issue or something?
V2
Both spots have been changed, no more crouching. I wasn't able to replicate the fps issue in single player, so hopefully this will also fix that. Just wondering, can you test in multiplayer if the fps issue happens when you are near that same area, just not in that "crouch spot". I am using occluders in the middle area, and in the screenshot you posted the player view is facing directly into one. It could be that the occluder is overloading the CPU calculating players that are in its effective area.
Both spots have been changed, no more crouching. I wasn't able to replicate the fps issue in single player, so hopefully this will also fix that. Just wondering, can you test in multiplayer if the fps issue happens when you are near that same area, just not in that "crouch spot". I am using occluders in the middle area, and in the screenshot you posted the player view is facing directly into one. It could be that the occluder is overloading the CPU calculating players that are in its effective area.
IGNORE/DELETE PREVIOUS POST
V2
Both spots have been changed, no more crouching. Also modified the middle container area. I wasn't able to replicate the fps issue in single player, so hopefully this will also fix that. Just wondering, can you test in multiplayer if the fps issue happens when you are near that same area, just not in that "crouch spot". I am using occluders in the middle area, and in the screenshot you posted the player view is facing directly into one. It could be that the occluder is overloading the CPU calculating players that are in its effective area.
V2
Both spots have been changed, no more crouching. Also modified the middle container area. I wasn't able to replicate the fps issue in single player, so hopefully this will also fix that. Just wondering, can you test in multiplayer if the fps issue happens when you are near that same area, just not in that "crouch spot". I am using occluders in the middle area, and in the screenshot you posted the player view is facing directly into one. It could be that the occluder is overloading the CPU calculating players that are in its effective area.