You don’t even give people a chance to reconnect if your application crashes before the game starts. Thousands of games without issue and I get slapped as a leaver. Big lol.
Forum Moderator Note: Calling out individual developers or the development team in your title or post is against our forum guidelines. Doing this may result in a temporary suspension of forum posting privileges. Please focus on discussion of the feedback/suggestion in your thread.
Well since you’ve only left once due to this you surely only have a 10 minute penality, go play a round of quick play or take a quick break to get drinks or snacks then continue.
Unless yKnow you’ve left more than once and thus have a longer suspension.
It’s the “first offense”. It’s just incredibly annoying that their weakness becomes someone else’s punishment. No other application has issues, and it’s an error code specifically from their system, meaning it can be tracked.
I’ve had the render device issue about three times myself (thank god twice when launching overwatch and once in qp)
It’s a pretty rare issue, usually overwatch just can’t find your driver (I had to briefly move overwatch to my smaller drive for it to work, feelsbad)
The issue shouldn’t persist, but if it does I’d suggest going to the Technical Problems section of the forum c:
That’s up to you.
It’s not a big issue from what I’ve seen, those 3 times are across 3 years 
Hope it doesn’t come back , enjoy your competitive game.
Dude , they let people farm stats so they get to play without any skill and you think this is laughable? XD
ok
so I had this issue for the longest time, and you have to disable everything starting in the background when you don’t have it on
if you do contact support tell them that or if they can find my old tickets
May have been an issue with shadowplay I guess? There’s no real way to tell it’s fixed. Just kinda hoping it doesn’t happen again. What’s sad is that this is an error their system caught, and I’m not sure it’s something the user can intentionally replicate. With that knowledge, the system should be smart enough to know that it was a problem they anticipated in their code and undo the “leaver penalty” ESPECIALLY on a first “offense”.
I get that they can’t track disconnects, but this is something completely different. I also get that no system is perfect, that’s what error handling is for in the first place. But to just punish the user because you’re too lazy to follow the logic through? I could understand if the game was already locked in and 11 people had a bad experience and I was the only other factor, but this happened as soon as we matched and nobody lost anything besides me. Yeah, I got it all back within an hour, but there’s still a strike against my account that shouldn’t be there.
It’ your PC’s fault, not Blizzard.
That’s not right. My PC has no issues, that application had an issue. My drivers never failed, only the application failed. So if their service lost communication to my drivers, there’s something they failed to account for on their end.
Just update your drivers. It’s not blizz’s fault
My drivers were up to date lmao, is this a blizz alt account or something? This is a really simple development concept. I don’t blame my customers when my systems throw errors. What terrible practice.
This error is something on your end I’m pretty sure
I’m fairly confident it was related to Shadowplay. Their system having an issue with Shadowplay is NOT a problem on my end. It’s a problem on their end that they’ve failed to handle without crashing the application.
I have shadow play and have no issues.
(Editing this comment since I can’t reply concurrently)
I really believe this is more closely related to Competitive feedback. Since the error was caught and handled by your system, there’s justification to negate the penalties applied against the user account. I know it’s possible because I handle this kind of thing (on a smaller scale) on a daily basis.
Errors are going to happen. As I said earlier, no system is perfect. However, the errors that you CAN account for don’t need to punish the consumer. I find it hard to believe that this was a complete oversight of the entire team, and moreso a decision not to put another process on top of your system that only fails .01% of the time. I get that, from a business perspective.
But it really sucks being in that .01% when I invest so much time in your work.