![]() and your post having +12 upvotes shows you're not alone. Could you tell me where you got this wrong information from? It's not the first time I've read it. after the viewmodel and tracer update in 2018, the tracers have become very accurate and actually represent where the bullets will go on the client side. Valorant doesn't have muzzle flash fellas.Įdit: `r_dynamic 0` is not cheat-protected and does the same thing, use this one I encourage you to try yourself, and also try `dlight_debug`, it will spawn a dynamic light using the same system. I wouldn't expect a fix because it's a pain in the ascii to do it, but r_dynamiclighting should be non-cheat protected. This is a known problem area for Valve because they put profiler blocks all over the place ( ). The problem is slightly masked by using mat_queuemode("multicore rendering") but not really. (I am using linux but the problem is going to be similar). The issue is the dynamic lighting system calls D3D LockRect() which forces a stall while waiting for the GPU to deliver data. Want a fix? Here's another one in the same spot, shooting, with `r_dynamiclighting 0` ![]() ![]() Here is a tracy waterfall while shooting with muzzleflashes on 3 surfaces. But actually all that stuff is nothing compared to the amount of lag caused by muzzle flashes. Have you ever wondered why you drop 100+ fps while spraying? You might assume it's a combination of the sounds, animations, tracer effects, particles, and other. (+18) □ CS2 PREMIER SUBINDO! | NOVIDADES. Rerun: PGL Major 2024 Open Qualify Dia 3. Subreddit Rules Message Moderators Official CS:GO Blog Discord
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |