Valorant Dev Tracker

Make sure it's a msg not chat -- chat disabled.

Can you do a traceroute to 162.249.72.1 and paste results? Still seems too high.

You should not be getting 55 from Lux to any of the adjacent locations. What is your ping in practice?

ComHem looks stable to me -- can you run a traceroute to 162.249.72.1 and paste the results here?

This might actually come down to match-making.. Luxembourg is difficult. You're right in the middle between 3 interconnection points (Paris, Amsterdam, Frankfurt) but the experience should be consistent. Frankfurt seems to win out most of the time. I'll keep an eye on it in coming weeks once the population starts to ramp up.

Which ISP please. Will look into it.

Hmmm if it's dropping to 2.4 it's definitely downclocking from the 2.6 base. With those temps it's likely due to thermal load. Try seeing what you can do to run cooler and see if you can get those clocks to the 4.2 turbo the processor supports (likely can't maintain, macbooks/laptops can actually have a pretty hard time with cooling). A cheap quick test can be to very carefully set your laptop on some ice trays to see if you can get temps down. Please be extremely careful if you try this. Other options can be to buy laptop stands with built fans. Other options can be to try finding some fan control software and maxing them out.

Also try not using the external monitor. I've seen some weird HDMI issues that can cause gpu stalls for external monitors. When you switch monitors be sure to put your resolution back down to 1080 and not the 2880 I think your mbp supports.

Anyways I do have to get going now. It's pretty late here. I hope this helps!

Hmm that's a hard one. I've definitely seen weird things when I used to use a bootcamped macbook for gaming.

You might check if your settings got reverted accidentally. With a Radeon Pro 560x you might be gpu bound especially if you're playing at higher resolutions. Try some of the GPU fixes (lowering Res, turn off improved clarity, turn off antialiasing). Does that change your framerate? If it doesn't you're probably CPU bound. Maybe a thermal issue? You can download a tool like HWMonitor to check on that, see temperatures and clock rates.

From the data I've reviewed I don't see specs dropping 50% average framerate even from best patch to worst patch. It's probably best to reach out to player support for something like this. They can maybe go through more of your computer's data and help find anything odd.

Howdy,

I want to dive in and address some quick points on how we think about performance and what you can expect from launch. First let me just say that we see launch or 1.0 as the starting line. We're in this for years to come. Perf is part of that commitment.

Performance is a wide range of topics but in terms of top priorities for perf we have 3.

• Accessibility : We want people with low end computers to be able to join their friends in VALORANT. So invite your buddy with his Intel HD 4400 to game with you. They won't be slamming 144FPS down but hopefully they can have fun. For the most part, we seem to be hitting the mark here, there is ongoing work to get all character ability VFX in budget here but it's coming along at a fast rate. We improve a number of abilities every patch. Patch .50 fixed a rather large issue introduced with .49, one of our key GPU optimizations regressed and we had to go fix it up again.

• ...

1.) I appreciate the response and won’t dismiss your concerns here. Team definitely hears it and is extremely careful in how they go about validating issues. From what I know, everything is still manually reviewed and validated before being implemented as a track/ban methodology, so what I mean by “aggressive auto banning” is not a sentient big data AI deciding the vowel “E” is scary and taking action but more the team can say “yeah we know how this thing works, ban it,” and they can do that en masse. False positives terrify EVERYONE, which is why it’s also a VERY common FUD (fear/uncertainty/disruption) tactic employed by cheat developers - they spread rumors that the anti-cheat bans someone for an innocent thing (it’s not) and maybe they can stall the confidence of the anti-cheat developers and continue their lives.

2.) I head up communications on the V team, actually. I just happen to work with every dev to know the underlying issues.

I've had some discussions with the engineering team at Charter/Spectrum and they do balance the exit points for Florida between Atlanta or Dallas depending on their own core capacity. You shouldn't be seeing the packet loss issues that were present weeks ago but unfortunately It's still taking 50ms to get you to our point of presence in Dallas. You can see that fluctuation in the 2nd hop between 11ms and 29ms which is the reality of being on a large cable access network. Your first hop is unusually high. Are you on wired ethernet and how old if your router?

Can you DM me a trace to 192.207.0.1? I'll see if I can find something we can tweak here.

We'll have game servers in Tokyo!

If Riot Support committed to it, they'll stand by it. For them to do it takes more manual work on their end. When I say "Shard Transfer" I mean a one button process that wouldn't require Riot Support or VALORANT Dev Team intervention.

I deleted the comment because I figured our anti-cheat lead could answer if he wanted to, but for anyone watching the response was "lol no one gets banned for auto hotkey"

You've certainly turned this argument into a giant strawman. I never said false bans don't happen, I just happen to know the anti-cheat team has been fairly meticulous about how they do manual bannings so far and you're swinging a fairly meaty anecdotal example with no evidence of your own.

I also know a lot of cheaters DO get banned and come in saying, "I was super innocent I just uh wanted to install a new driver while playing solitaire," and that becomes a strangely repeated fact so we seem to be at a crossroads of slinging anecdotal information.

There's a bunch of different factors impacting performance. It's useful to think about bottlenecks: what is currently the slowest part of the game? Removing that bottleneck improves framerate until you hit the next slowest piece. Then you optimize that piece, then the next, and so forth. The slowest piece is different depending on scenario (ex. shooting a gun, running around the world, lots of abilities firing) and depending on hardware (i.e. how fast is your CPU vs. GPU). The pieces also change as we add and update content and behaviors.

Sadly there's not currently just one chunky piece that we can fix to unlock dramatic improvements. We're working on a bunch of different pieces that each unlock fractions of a millisecond every frame. Combined these optimizations add up to more FPS.

On older machines VALORANT's performance tends to be constrained by GPU. The game's overall performance on these machines scales directly with the quantity and complexity of what it has...

We have a bunch of developers grinding on performance. Some performance work will land in the launch patch. Additional performance work will land in future patches. We will continue to patch the game regularly; launch is just the beginning.

There was a miscommunication about the servers at launch, sorry!

We'd like to have them in place by the end of the year, but a lot needs to go right for that to happen. You'll hear more from us as we make progress!

Ahhh no, sorry mate :(