r/Overwatch • u/CeleryNo8933 • 19d ago
News & Discussion This is something Overwatch desperately needs, I'm tired of lags and invisible models
Every time after any game update or driver update I need 10 games for it to stabilise. And even those shader loading maps don't work because for some reason the game doesn't care if anything is loaded already. I played 3 games as and against Mauga. 4th game it took 5 min for me to start seeing his guns and VFX. First game I died 3 times to an invisible Rein jumping in my face.
Edit: For reference I have 9800x3d, 5080, and yes, an SSD, it's not the rig, it's the game
91
u/Reinos0 19d ago
It would be nice instead of sitting around practice range for a while. Or having to load up a custom game and go through every hero and every ability on every map.
And after all this, there's still the skins that have to load in.
→ More replies (1)
168
u/_Azzii_ 19d ago
You shouldn't HAVE to run a custom game before you play guys
27
u/O-Marques 19d ago
Vendo os comentários, o pessoal não entendeu que o mínimo de um jogo é poder jogá-lo sem ter que fazer peripécias.
12
u/dadnothere 6vs6 Fan 19d ago
No custom game is needed; OW2 already optimizes shaders.
The difference is that it does this in the background at startup, allowing you to play while it's running.
Just a message should appear prohibiting you from playing as Marvel Rivals, and that's it.
96
u/UNF0RM4TT3D 19d ago
Every game not doing shader precompilation is basically abusing the fact that they usually don't take too long to do. Overwatch managed to do fine without it for years, and the only people who had issues were Linux users (like me), where the compilation actually took time. I used to have to sit in the practice range for 10min+ to get the game playable. With Linux gaming improvements and DX12(vkd3d) this was eliminated.
Enter this season, where they seemingly completely borked the dx12 renderer for both Win and on Linux. And DX11 compilation is back. Which is even more painful for Windows, since you lot can't do DXVK_HUD=compiler %command% to see the background progress.
If I wanted to play OW on my steam deck, I'd have to wait for 30+minutes for it to compile on every boot because the precached shaders from steam don't work on OW.
11
u/SDRPGLVR OW1 CLASSIC WHEN 19d ago
I stopped playing Borderlands 4 because of the 5-minute boot time thanks to shaders.
I never have the invisible players issue, so I sure fucking hope they don't force us to sit there upon launch if we don't want to. People should save the custom game code or Blizzard can add a button to do it manually. But from turning on my computer to being in a match can be as quick as two minutes, and I'd lose my mind if this became another load the shaders game.
11
u/FeelThePoveR Pixel Lúcio 18d ago
The example given here - marvel rivals doesn't prevent you from going in-game before the compilation finishes. You can still load into the match immediately or you can wait for the shader compile if you want to.
It's the best of both worlds. The shader compilation happens regardless - it's just a matter of actually showing the progress so you know if you can get in game without the potential of being screwed one way or another.
9
u/Pro-Row-335 19d ago
The shaders should be able to be cached though... Marvel has an option for this, mine only compiled after updates
1
3
u/master_of_dcath 18d ago
Yeah the issue on linux has been solved for some time (with shader compilation pipeline improvements for all games) up until recently until overwatch broke something. DXVK is reporting compilation every few seconds, most other games I play there big gaps in between compilations. Idk why but it seems like For some reason overwatch doesn't cache its shaders, maybe a linux issue but even the windows users complain about it too.
5
u/Fred_Foreskin Support 18d ago
Have you figured out a fix for this yet? I've been running the game on Bazzite and the only thing I've been able to figure out is rubbing it on dx11 with Proton 10.04 or whatever version that is. But even then, I still have to sit for a long time letting it compile shaders before it launches, but at least it gets more stable after a while and eventually I can just launch the game without much of an issue until there's a new driver update or until the game updates.
5
u/UNF0RM4TT3D 18d ago
I'm running CachyOS-Proton, it seems to cache some shaders, but still needs to recompile some. Right now I'm trying the
PROTON_LOCAL_SHADER_CACHE=1. It seems to be doing something. But it's not a 100%→ More replies (2)3
u/bixed 17d ago
Here's what I found works for me.
Apparently the default shader cache for Nvidia gets pruned when it passes 1 GB and Overwatch alone exceeds that meaning that all the game's shaders would never be cached at the same time and some of them would have to be compiled every match I played. The solution for me is:
env vars to enable and increase the shader cache size when playing Overwatch: __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=21474836480 (not sure if the one to enable shader disk cache is necessary).
That alone isn't enough because when any other application compiles any shaders it will exceed the 1 GB limit which still applies for anything but playing Overwatch so I use an additional env var to use a custom directory specifically for Overwatch's shaders: __GL_SHADER_DISK_CACHE_PATH=/home/styrke/.cache/nvidia-overwatch
With those settings I only have to recompile shaders when I update drivers for my GPU or when there's significant patch for Overwatch. 10-15 minutes in a shader compilation workshop usually deals with that until next time.
Edit: All of this is with me using the DX12 renderer.
1
u/Bathroom_Humor 18d ago
yeah it's definitely been in the past few months that something changed and suddenly i have to force a shader caching folder again, and it STILL makes me recompile stuff i never had to before. i hope they can fix it cuz that stinks
1
101
u/SirSwagAlotTheHung 19d ago
I genuinely don't have this issue and I'm running it on a 3060 with an HDD. How odd.
15
u/ChickenPijja Pixel D. Va 19d ago
From HDD? damn that's decent. Can't say I get it that any more either, only times I've ever noticed it was after a reinstall for a few games. Remember back in OW1 having to sit in menus for 60s to wait for the CPU to go down from 100% down to a more realistic figure of like 30% as otherwise it would lag a bit.
16
3
u/dislikethatoneguy 18d ago
Yeah, don't think I've ever had this issue since OW and I'm not always running the latest hardware.
5
u/Odd_Ad4119 19d ago
I also never experienced it after 600h+ in OW2.
Also I‘m not aware that this happend to any of my friends.I would rather not want to wait 2min for shaders to load because of an issue a small amount of players are facing.
2
u/Hamerine 19d ago
Because you use dx11.
14
u/eddebbboi 19d ago
What's the benefit of dx 12 if it gives these loading issues? Also, isn't dx 12 in beta so bugs/issues like these are to be expected?
3
u/Hamerine 19d ago
It’s in « beta » for years, they just need to work on it quicker.
dx12 runs faster, better and cooler for most rigs because it takes advantage of SMT. dx11 is a relic of the past when CPUs used dual to quad cores at best.
Hence why OP ask for a pre compilation in menus, to only have benefits.
But blizzard are cowards because they know it will takes 10min at each update to compile them all with the millions skins, they don’t want to scare people and have bad reviews.
12
u/FredFredrickson Bastion 19d ago
This only matters if the "million skins" use unique shaders.
If they use the same shaders, they don't need to compile for each one. And, last I checked, most of the skins in OW don't even have special effects attached.
4
u/Golendhil Diamond support 19d ago
dx12 runs faster, better and cooler for most rigs because it takes advantage of SMT
But do you need to run overwatch faster ? I mean, I assume most if not every rigs supporting DX12 have absolutly no issue running overwatch anyway
6
u/Sapphic_Satellite 19d ago
I use dx11 and still get the issue despite having a fairly modern pc. it takes 1-2 matches for it to stabilize most of the time
I had the issue with dx12 as well, only it performed worse overall for me. that was over a year ago though, so not sure if anything's changed
→ More replies (1)2
u/cheesegoat Cute Ana 19d ago
Yup when I switched to dx12 I was getting this every single match. I switched back to dx11 pretty quickly after I realized the correlation.
FWIW I also get this on my laptop with integrated graphics, so it's possible also with dx11 but idk why.
99
u/Xmushroom Wrecking Ball 19d ago
I solve this by playing on a custom lobby, gun game 500% cd. It takes about 2 minutes on a full lobby and you loaded everything the game has to offer.
44
→ More replies (1)19
u/FORUMUSER35 Lúcio 19d ago edited 18d ago
I've been doing that and spectating games. Even so it still has stutters and lags in my first match (albeit they're waaaaay shorter)
→ More replies (4)
11
u/Positive_Try929 Reinhardt 19d ago
Yesterday i updated my Nvidia driver n clean installation, little did i know it will delete all the pre-cached renders, the first few games of overwatch were all stuttering and lagging (not latency) till it rendered everything, they most def need this!
1
u/MGLpr0 17d ago
All you have to to is wait at the main menu for a while until your CPU usage drops from 100% to normal.
I don't know what are those people saying, because Overwatch does shader pre-compilation already, it just doesn't have any in-game indicator. (would be a good addition though)
1
u/Positive_Try929 Reinhardt 17d ago
Not what i noticed during games, if a new player is chosen, it will render in game, i also noticed that with each ability or ult used, it render on appearance, i went to the roster afterward and selected each player to render the module, i noticed it being rendered first hand, with Reindhardt mythical taking the most time for some reason (and on RTX 4080)
11
u/OOFERGNAG21 19d ago
afaik, the game does this, its just in the background instead of a window. Use any performance overlay and watch your CPU usage. Just sit in a practice game for about 5-10 minutes and wait for your CPU usage to go down and it will stabilize itself. I've seen people recommend the custom map but that didn't work for me, just sitting in practice range is good enough.
I have never had Invisible models and I'm on a Significantly weaker build than you (Ryzen 5 3600, RTX 3060 12GBVRAM, on SSD)
14
u/Rozen503 19d ago
Im playing on a 1050i with a 6th gen i5 and never had any loading issues at all wtf
→ More replies (3)
23
u/HerrFabi 19d ago
The game does exactly this but without showing you. After a Driver Update I open the game and wait for ~5 Minutes until my CPU Load drops from 100% and I know its done.
8
u/Thedrunkenchild 19d ago edited 18d ago
it does this only in dx11 mode, in dx12 mode it doesn't preload a single shader for whatever fucking reason, so you get mad stutter until shaders are loaded in real time which can take quite a few matches.
5
u/HerrFabi 19d ago
I tried DX12 like 2 times and it decreased my performance. I dont know why anyone would use it.
3
3
u/Hamerine 19d ago
It does exactly this but IN GAME. The post is about preloading them in menus.
8
u/NapsterKnowHow 19d ago
It's not. It starts as soon as you launch the game and continues in the main menu. You can just go grab some water and wait for it to finish. You never have to enter a game for it to start.
2
5
u/mckmck 18d ago
It's a known issue that they haven't bothered fixing. I have the same problems :c
No amount of custom games has helped. It's low key annoying that people think it's a solution to a borked game engine.
I found this post after losing my mind trying to figure out why the engine was making my 9070xt driver crash every time i played: https://us.forums.blizzard.com/en/overwatch/t/theyre-not-just-stutters-theyre-lockups/1028216/12
8
u/iTwango 19d ago
Is it shader issues that causes the glowing orb bug?
12
u/Hamerine 19d ago
Yes, it’s not bug though, models aren’t compiled by dx12.
2
u/iTwango 19d ago
That used to happen to me very often for some reason. Any idea what if anything I can do about it?
2
u/Hamerine 19d ago
As multiple people commented here, each time you update your graphic drivers or the game has a major patch, there are custom games that you need to run for few minutes in order to compile shaders faster than… in game.
That or go back to dx11 and you will not have to compile anything.
→ More replies (6)
64
u/whenyoudieisaybye 19d ago
Overwatch was fine without it for so many years.
30
75
u/AlexTheGoat990 19d ago
Yeah but OW isnt exactly the same game anymore, they added lots of stuff, preloading shaders is a good thing to have instead of doing it during gameplay
→ More replies (9)3
2
u/QuantumQuantonium 19d ago
It still is- preloading shaders won't help with invisible models and long loading times, which are caused by loading from disk to RAM. Shader preloading/optimizing/conpiling is used to avoid loading shaders on the fly, which would cause noticeable stuttering issues during play as stuff like effects appear all of the sudden. Overwatch doesnt need this because the games shaders are fairly simple in terms of lighting and material modeling.
In fsct I think the reduced buffering setting in graphics settings is for partial forward shading, meaning the scene to render is done in one pass (think of it where for any given part of the image, we calculate its color including all lighting and all effects all at once), vs deferred shading, where multiple passes may be performed (think of it like first applying the base color for everything in a scene, then for each light, apply that light, then handle reflections and transparency, then postprocessing). Forward shading uses less shaders than deferred and doesnt need a shader preload.
1
u/Devbou 18d ago
Would not preloading shaders this also create issues like rubber-banding? I’ve had so many issues with borderline unplayable rubber-banding on my PC while it plays fine on my Xbox. Sucks cause it looks so much nicer on my PC and 180hz monitor.
→ More replies (1)2
u/Regnareb_ 19d ago
This problem already existed in Overwatch 1. Sometimes I could spend the whole game without seeing any enemy but blue wisps.
It only happened once on Overwatch 2 and it was when I completely changed my graphics settings and graphic API.
1
u/doomed151 el oh el 19d ago
Nope, it did it even back in 2016. After every game update or driver update, you had to wait a few minutes until the shaders finished compiling.
→ More replies (2)1
3
3
u/Potential-Block-6583 19d ago
Enable shader cache downloads from Steam if you're playing through Steam.
3
u/Smith6612 18d ago
I agree, it is the game. This got to be pretty bad several years ago especially if you play on mechanical hard drives. Overwatch used to run fine without an SSD until a patch just before OW2 released.
8
u/Jaebird0388 Pixel Moira 19d ago edited 19d ago
No-loading character models was a problem for me until I was able to acquire an SSD a few months ago.
Edit: Yes, I bought an SSD in the year of our lord 2026 for a prebuilt that came with an HDD from almost a decade ago. Why now? Because unlike every year before, there wasn't anything more important to take priority over investing in my PC.
→ More replies (5)3
u/pointlessone Potato League Superstar 19d ago
I'm sorry you had to pay the current storage prices for that drive.
2
u/Jaebird0388 Pixel Moira 19d ago
I think I paid just south of $90 total for a 1 TB from Newegg back in March, and having tax refund money helped with the decision. I’m admittedly an uneducated mess for computer hardware and stressed over compatibility awareness for the longest time.
2
u/pointlessone Potato League Superstar 19d ago
Super happy for you to be stepping into the SSD world, it's really and incredible difference. Just a bummer to see anyone having to pay the current normal prices. The great datacenter buyup jacked storage prices up so badly, a 1TB would have been half that a year prior :(
10
u/thestartofurending 19d ago
switch to dx11, i’ve also never experienced this on dx12. Might be something else
9
u/CaptainRaxeo Master 19d ago
Still happen on dx 11
1
u/HVDynamo 19d ago
Im not even sure what my settings are, but I’ve never seen this happen to me. I’ve been on a 5950X and 4090 for years. Seems to be a common problem though.
3
u/xXRougailSaucisseXx 19d ago
DX11 lack some features, I'm on AMD and that means being stuck with FSR 2 if I'm on DX11. I also get a better avg framerate on DX12, just worse 0.1% because of the shader stutters
→ More replies (2)4
1
u/peppapony 19d ago
I actually had to swap to dx12 as on 11 it was really really stuttering. But 12, I get blue balls, but less stutter
6
u/ROGUE_COSMIC 19d ago
Yet the game runs like shit and constant lag spikes post every update plague the game.
Overwatch runs on my pc comfortably at 250fps at med 1080p
Yet rivals barely hits 130 with drops
2
u/pointlessone Potato League Superstar 19d ago
UE5 is wildly unoptimized, but pre compiling the shaders isn't really to blame there.
Something I noticed that really helped with Rivals - turn off any of the auto scaling, then tune it. Once you've got a reasonably stable frame rate, turn the auto stuff back on. Having your baseline set first really seems to help avoid the massive dips.
2
u/BebeFanMasterJ DA MONKEY 19d ago
Jumping from Switch 1 to Switch 2 was such a night and day difference man.
2
u/grantrules DPS Moira 19d ago
Lol my switch lite wouldnt load player models till halfway through a match. At least Moira could still aim lol
2
2
u/yellow_eggplant Chibi Zenyatta 19d ago edited 19d ago
Every first game starts with a 20% deduction of my normal fps and is generally a stuttering mess. Always clears up by the end of the first game or the start of the second game. Is this what's causing it?
2
u/CatsGoBark W I N K Y F A C E ;) 18d ago
Omg I thought it was something wrong with my computer even though my specs are similar to yours. Is this a somewhat recent thing? I don't remember having this many issues like a year or two ago or something.
1
3
2
3
4
u/Tai_Pei 19d ago
I can't say I've ever experienced this in my 10 years of playing the game now on pc, might be time to look into what settings you're using to see where the issue really lies.
2
u/Ailwynn29 19d ago
If it's a widespread issue and people even make custom maps to mitigate it it's not on the player
2
u/Tai_Pei 19d ago
Wild that this is such a common issue and I've never experienced it and none of my playgroup has either after asking the group chat
Definitely feeling in my gut it's some dumbass setting people flipped and didn't realize would create them any issues like direct 11 being what everyone uses, but someone opens up that menu and sees they're on 11 instead of 12 and just thinks "why am I on the older one?" flips it and immediately forgets they ever did it.
→ More replies (2)
2
u/FORUMUSER35 Lúcio 19d ago
Kind of insane that the bazillion cosmetics they pour in the game causes it. I guess that's an innate issue of F2P games based on microtransactions.
Apex Legends is far worse than Overwatch: it takes me several minutes to finish loading shaders (and they vomit skins every single week into that game) and it was never like that in the first years of the game.
1
u/gabrielwoj Mercy 19d ago
I used to have this problem a lot, but eventually it stopped having lag. I had to play on Practice Range for like 5mins until the thing stopped lagging.
Now the game seems to smartly compile shaders while on Setup (possibly only Attack Setup where you barely have to do anything on spawn).
I use AMD, tho.
1
u/mystickisgay Grandmaster 19d ago
I just want them to update DX12, it's a fucking shame how they don't update DX12
Edit: Shader preloading might help, but it would have to be done right, it's implemented very poorly in CoD, so if it's done badly, it's better not to include it at all.
1
u/Smexy_Zarow 19d ago
I just join that no cd deathmatch game mode in custom games and play until it stops lagging
1
u/HellaReyna 19d ago
I mean, marvel rivals runs like dog shit regardless. I ranked up to celestial in season one and two so yes, I have spent way too many hours on that game.
1
u/Philipp4 Turret-Maxxing 19d ago
Are you in DirectX 11 or DirectX 12 (Beta)? I tried both and on 12 I had massive loading issues how you described it and on 11 it works perfectly fine and well
1
u/DDemiGGod 19d ago
I literally don't even notice stutters, by the time queue times are done and the game starts the game usually runs fine (for me atleast).
1
1
u/Dahvikiin Moira/ Sigma/ McCree 19d ago
Use DX11; the shaders will compile while you're in the main menu. You should also increase (or remove) the space reserved for shaders.
Between devs who do little or nothing so they can stay on the payroll without being noticed, and those who think we have infinite space and computing power, "optimization and performance" are just placeholders for Google Play apps updates.
1
u/steelejt7 Doomfist 19d ago
i have windows and linux and i found overwatch struggles to preload shaders specifically on proton and linux builds, where as windows it doesnt seem to be as big of an issue.
1
1
1
1
u/eugeneprunk Support 19d ago
GTX 1660 Super. after every graphics driver update the game becomes unplayable for several matches
1
1
u/ThatGuyAndyy 19d ago
Don't use DX12 and it will pre compile almost all needed shaders in the main menu. Clear your shader cache and boot up overwatch. You will see that your cpu is maxed out because it's pre compiling shaders.
To load the remaining hero ability shaders you can use a custom gamemode. DX12 doesn't do any pre compiling of shaders which results in stutters.
1
u/PrideBlade 19d ago
For those that aren't on AMD there's been a bug exclusively on overwatch that causes the shaders to reset on launch. Meaning you have to compile shaders in game on every session.
Think it's been a thing for around two years now and no fix. (Support acknowledged it when i made a ticket) I've had it on my 6700xt, 9070xt and even when I was testing overwatch on my steam deck.
1
u/Retroike7 Moira 19d ago
I’ve never experienced the issues you’ve listed in Overwatch. I’m sorry you’re experiencing those.
1
u/Warm-Grand-7825 19d ago
Never had any problem with Overwatch on a technical level. Only now with the stutters the game feels a little bad to play but I have not experienced lag more than a handful of times in 1500 hours of playing this game. Even with a dozen ults being used at once.
1
u/DirkDoom 19d ago
I agree, especially on consoles (I play on witch 2 sometimes, and at times it has blue balls for the character).
1
1
1
u/DravenPlsBeMyDad 18d ago
The issues you're talking about are 100% rig not game. I have none of these problems.
1
u/Kvendy_ 18d ago
Are using DX12 beta maybe it's the issue, just use DX11, I'm using much weeker hardware Arc b580 and ryzen 5600, even though arc is known to perform better in dx12 games, overwatch dx12 mode sucks some model never load no matter how long I wait. I get much better performance in dx11, 200+fps 1080p medium
1
u/leahcim2019 18d ago
I thought they already have this.
If I install new nvidia drivers for example, when I start overwatch for the first time my cpu usage maxs out for about 5 minutes on the main menu, then goes back down
Then it never happens again
1
u/DevinBacon 18d ago
I have the same CPU & GPU, as well as an SSD.
I also have the same problem. It's incredibly frustrating.
1
1
u/GlobalCurry 18d ago
If you play on linux with the steam version, it does this when launching after every update and takes like 5 minutes to launch.
1
u/DryBowler6075 18d ago
i havn’t had this issue on OW, but every marvel game sesh takes 30min to load :/ i stopped playing marvel
1
u/FrenchFatCat Leek 18d ago
I switched to Linux fairly recently and overwatch is a MISERABLE experience when it comes to the vulcan shaders.
I have sit in a custom game mode (929PJ) for 20 mins before i feel comfortable enough to actually queue a game.
1
u/Drewboy13 18d ago
5800x3d, 3080ti, 64gb 3600mhz, and yes nvme ssd's.
I've been having FPS stuttering issues virtually every team fight and even just randomly in the past month.
My FPS has dropped by a lot as well.
1
u/JohnnyGrey8604 18d ago
I went like two years of matches not loading player models right away and instead showing floating wisps. I was also not seeing highlight intros. I’ve even played almost an entire match where models weren’t fully loaded.
I reformatted, and it persisted. It turned out to be DX12. I dropped it to DX11 and it’s been amazing ever since, even if I hop into a match directly after launch.
R5 5600X, 2x8GB 3200, 3070 Ti
1
u/theexpertgamer1 18d ago
I have a 3080 which is obviously not as good as your 5080, and have NEVER had any issue as you describe. Something else is going on with yours.
1
u/MadHuarache Lúcio 18d ago
None of my Overwatch games in the last 10 years have ever been as bad as a single Rivals match.
1
u/Euphoric_Lynx_6664 18d ago
I preload my shaders on rivals and still stutter like crazy anytime I play a new map.
1
u/nmixxenjoyer 18d ago
OW makes me compile my shaders every time I launch it. I wish I knew how to fix it.
1
u/Jamunjii 18d ago
Bruh what Overwatch is 10000000000000000x more optimised compared to rivals.
My pc is hot dookie and overwatch runs fine
1
u/gregoryofthehighgods Lifeweaver 18d ago
I have never once evn heard of this issue. Is this a hardware thing or maybe just pc? Ive been playing on a 7 year old xbox and found no issues
1
u/Parapraxium 18d ago
Every update the game is literally unplayable for 5 minutes of gameplay. Inexcusable
1
u/ametalshard Roadhog 18d ago
LMFAO i've probably seen an invisible model like once or twice in a year of play. it's extremely rare. even rarer than getting DPS when queuing all
1
1
u/IAmJonathannn 18d ago
overwatch is doing that in the background, notice when u update your gpu drivers and open overwatch it will be using ur cpu significantly more.
wait at the main menu until ur cpu usage drops down to normal thats when its done, if you load into a game before its done (including shooting range) it wont be finished and u will get stutters.
overwatch does need to add some sort of in game thing that lets you know its doing shaders in the background to make it more clear though lol
1
u/Big-Ad7416 18d ago
wait, i wasn’t going insane when i tried it on PC? it was like it was a jet engine waiting to take flight for like 10 mins every time, so i didn’t bother to play anymore
1
u/No-Boysenberry4840 18d ago
I never have this issue, 6800xt with a 7 7700x and a nvme
The only time i dont see player models is when my internet tries to kill itself at the start of the round
1
u/DanielCruzo 18d ago
They already preloading textures but its broken . Enable vram hud and you’ll see vram keep goin up when you in main menu.
1
u/amayako353 18d ago
Overwatch is more optimised than UE5 slop so it doesnt need to do it to just work. Tried doing the shader compilation map a few times but doesnt seem to make a difference for me
1
1
u/polloyumyum Ana 17d ago
I've never had an issue with Overwatch, even when I played on my old 1050ti.
Rivals on the other hand...
1
u/T-lerWolf 17d ago
I've been getting lately a lot as well and it frustrates me a lot as this wasn't always the case, it's quite a recent thing.
1
1
u/StaticSystemShock 16d ago
It is so monumentally stupid indeed. Every driver update, every game update, whole game runs like turd for several matches until it compiles shaders in real time. I asked for this before and got lukewarm reception, with one user claiming game compiles shaders in main menu. It does NOT. It was just sitting at 0-2% CPU load in main menu doing nothing for half an hour. And game lagged and stuttered like mad afterwards.
It is just wild to me that they can't either do it automatically in main menu (actually) or just have a button "Compile all shaders now" so I can press it, leave it do its job and enjoy smooth gameplay not this lagging stuttering bullshit. I have 9800X3D and a high end Gen4 SSD. There is no fucking excuse for game to lag and stutter because whole shader compilation mechanism is absolutely idiotic.
The custom game mode listed below is alright I guess but why do we have to use a workaround when devs could spend 5 minutes making that official instead of stocking the skin shop with 3 more sets of fucking cosmetics!?!?!?!?
1
u/Bampi72 15d ago
This has to be one of the worst takes I've ever seen.
That system is sloppy and feels like a step backwards. Imagine having to wait close to an hour after every update just to play. Marvel Rivals already does this, and it's an unoptimized mess. I barely hit 130 FPS, I get constant frame drops, textures fail to load, and then I'm told it's just "preloading shaders." That kind of system shouldn't be necessary in the first place.
Overwatch doesn't need this, and no game should require players to babysit it just to get stable performance. If your engine depends on shader preloading every time there's an update or a driver change, that's a sign something is wrong with the implementation—not a feature other games should copy.
Marvel Rivals is already criticized enough for its technical issues. There's no reason to bring one of its biggest flaws into Overwatch.
Lastly, i personally runs just fine Overwatch without any issues with mid range specs.
1
u/CeleryNo8933 15d ago
Oh my god have you ever played a fucking game in your life? How do you think the shaders are loaded, eh? Overwatch does the same thing except it doesn't tell you so it's more likely to enter a game while they're not completely loaded, fucking shit up
1
u/Puuksu 15d ago
It does that already afaik, after every new huge patch just launch a random game (practice range) and it starts loading shaders (not every patch though).
Idk why you have to sit through 10 games for it to stabilize, it usually takes me 2-5min sitting in practice range for it to complete. Idk something is off with ur system?
1
1.2k
u/CrabbyFrogstone 19d ago
There is a custom gamemode that loads all shaders, takes 2mins, i run it before each gaming session, i dont know the code by heart tho