We believe we're seeing recovery after a network re-route with one of our providers.
The issue reappeared, we're moving routes away from the problematic exchange. Should hopefully resolve recurring issues.
We believe we're seeing recovery after a network re-route with one of our providers.
The issue reappeared, we're moving routes away from the problematic exchange. Should hopefully resolve recurring issues.
Is it a bug or is it meant to be like that. That's why I posted it here not bugs.
It's not exactly a bug; more of a limitation. We want to address this but it's a non-trivial task and it's competing with a lot of other high priority stuff. We'll get to it at some point, but unlikely to happen soon.
Hope that clarifies, at least.
We believe we're seeing recovery after a network re-route with one of our providers. Anyone continuing to see the same errors on login?
Well, it did recover for about 30 minutes, seeing something similar crop back up
We believe we're seeing recovery after a network re-route with one of our providers.
We believe we're seeing recovery after a network re-route with one of our providers. Anyone continuing to see the same errors on login?
I have a question, do you know how i got false banned? I submitted a ticket and they told me that i wrote scripts and that is why i got banned. Now i don't know how to write scripts and what scripts. So it must've been something else. Maybe it's vanguard being oversensitive? Or maybe there is some sort of virus on my pc.
I can't tell you for your specific case but sometimes a detection method has false positives. The most common source of false positives are cheats from other games (which we generally don't want to ban for) but sometimes we make mistakes.
Usually if we make mistakes or deploy a too aggressive detection we try to fix accounts immediately without waiting for the player to submit a ticket but there's a chance that something goes wrong with that process.
If you think you've been banned falsely I recommend another support ticket, usually a second support ticket isn't helpful but during this beta when we're still figuring out our processes and procedures sometimes tickets get answered incorrectly.
I recommend talking to Player Support they might be able to help you out!
Says shortly after .49 in the notes. With the most recent being .47 and the release of this article, I'd say 2 weeks is a safe estimate?
Our numbering's a little weird with this one. 0.49 is next week. We did a double patch in the .47 version due to needing extra testing time on what was going to be our .48 version. We decided to hold it as there are several backend changes that we wanted to make sure didn't have negative impact cross game.
I've already answered a few times in this thread and many others. We're actively looking into AMD optimizations, we know that it's slower than Intel.
Sorry I wasn't able to find anything exactly related to the AMD optimization only posts in wich people talked about the issue. I'm new to reddit but i see the devs are pretty active in here, I appriciate it. Thanks for this cool game and keep up the good work.
Thanks! Sorry if I was short. It's been really stressful lately. Thanks for your kind words :-)
Can I run at 30fps?
CPU: Intel Celeron B815 2.4ghz
GPU Intel HD Graphics 4000
RAM: 4gb
OS: Windows 7 Home
Maybe? It will be a bit rough.
do you think the problem will be fixed soon ?
Hoping so, we're in contact with one of our third-party providers to understand the errors we're seeing in the service.
We're seeing issues crop up around Germany. We're still investigating if it's on our side or more generalized ISP or routing issues).
Issues appear to be localized to Germany. Still gathering details, but getting reports from some users from there on League as well.
Almost exact same as /u/ownersen :
different error codes, could log in after double digit amount of times, EU Germany - Bavaria
We suspect there might be some ISP or transit issues, as our alerts on internal systems are eerily quiet.
on EU - Germany - State: Rhineland Palatinate
"there was an error connection to the plattform. please restart your game client." "errorcode 40" and sometimes "errorcode 28" and "errorcode 7".
could login after 20 attempts. but now match history wont load, store wont load. and cant find a game. same problems like the last 3 days.
Looking into this
Which shard are you experiencing issues? North America or Europe? Also which general location are you playing from (state or country)?
Thx for the update.. wanted to ask about server stuff. A lot of players in central florida with spectrum(a partnered ISP) are getting way higher ping times than with League and really high and often packet loss. I have contacted my ISP multiple times and they say they are looking into it and I have filled out a ticket but I feel this may be an issue that Riot and the ISP need to work together on. This is impacting multi thousands of players as charter/spectrum is quite large
This is being actively worked on - there are some kinks to work out with ISPs in connecting to our Riot Direct points of presence in Florida & Georgia.
There's a lot of new network surface with VALORANT that hasn't existed previously with LoL - we are glad to have this Closed Beta opportunity to experiment with you guys and try to optimize everything before we operate at full launch scale.
We don't have a lot of Riot devs in your location of the world, and your collective playtest data is invaluable :)
Read more
Region: NA
Type of Bug: Technical / Vanguard anti-cheat bug
Description: When launching the game, it skips the launcher, goes right into the game, gives me the initial Riot loading screen, then moves to a new error stating System Reboot Required due to Vanguard anti-cheat.
Video / Screenshot:
Steps to reproduce: After launching the game, it gives this error almost immediately after showing the Riot loading page.
Expected result: No error message and proceeds to main screen.
Observed result: The error prompts and forces me to quit out of the game.
Reproduction rate: 100%
System specs: AMD Ryzen 5 2600 3.4, 16GB RAM, Windows 10 64 bit (10.0 build 18362)
I've attempted to r...
Thanks for the update, sorry we couldn't get you unstuck sooner!
We're trying to make this process less opaque (and annoying) for players, expect some improvements in our next patch.