Valorant Dev Tracker

Hi! I responded here. It’s a bug. Sorry about that. :(

https://www.reddit.com/r/VALORANT/comments/iliw41/prime_classic_skin_sfx_gone/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

We are! We just need to wait for another fix first then we will have it out. Really sorry about that. :(

Thanks for caring about the skin and asking these questions. It’s honestly pretty cool that people care so much. Didn’t expect this when we made all this stuff.

So with this skin we wanted to try something different. We’ve done really out there stuff like Elderflame and Prime and such. But there are players who want something simpler that doesn’t have VFX/animation/audio but don’t just want a new paint job on their skin. So with Spline we took a really cool and abstract design and tried to keep the rest basic for someone who wants a fantasy and new gun model without all the bells and whistles, but also still wants color variants. And actually there is some “VFX” in the orbs. We used a tech that would create a really cool material that’s basically like VFX. It’s just less out there than some of the other VFX we’ve done. Once again, different type of stuff for people with different tastes. Let’s see what you all think!

As for knife variants, we would have loved to d...

This is cute. Our team was getting a kick out of it today. It’s cool to see people liking some of the fun buddies so much. Nice work!

It’s meant to float. We were experimenting with a floating mount and thought it would be cool for this thematic that’s more abstract. The whole thematic has a bit of a floaty feel to it.

Commented above but don’t want you to miss it:

It’s a bug, I’m so sorry! You’re just noticing this on the Classic, right? We have a fix and are waiting to see if we can pair it with another unrelated fix before we deploy it.

I commented above but want to make sure you don’t miss it:

It’s a bug, I’m so sorry! You’re just noticing this on the Classic, right? We have a fix and are waiting to see if we can pair it with another unrelated fix before we deploy it.

It’s a bug, I’m so sorry! You’re just noticing this on the Classic, right? We have a fix and are waiting to see if we can pair it with another unrelated fix before we deploy it.

This is our current suspicion, but we want to give it some more time to breathe before digging in this deep. But yeah, her playrate has gone down a chunk - so if I were to guess, it seems more likely that the "autofill" less experienced Sage players are picking her less on this patch due to the nerfs, and more experienced Sage players are sticking to their guns, making the nerf seem less consequential then it actually is.

We'll have to see how it plays out over the next few days and then assess the Sage population at that point. Good intuition on this!

!pin

https://twitter.com/PlayVALORANT/status/1301231649254854656

I think we're fighting each other on this sticky here...but uhh... I'll leave that alone now.

Cheers and sorry again for the confusion!

Hey all -- Sorry for the confusion here. There was a bit of a delay in the schedule rollover following the delayed patch.

That has now been addressed for all regions where the latest 1.07 patch is live and will be available for all our EU friends once their patch goes out this evening. If you log in now, you should see a shiny Spline bundle.

Once we addressed some of the hardware configuration problems we were able to scale linearly with number of cores. You can just take the number of cores on the system and multiply it by three. We use a variety of sized servers depending on regional availability and cost but they all perform the same. The largest I've seen us use is a 56 core system that hosts 168 games or 1680 players.

Sorry that's pretty far outside my area of expertise. In general, most of the interns I've worked with have been with us over the summer. However, I don't think that's always the case. I'd say keep an eye out on riotgames.com/careers for any updates!

If you're interested in the engineering aspects of reflex. I'd also recommend thinking about how frames make it to the display more and reviewing the graphs in the reflex article. We often talk about a game being CPU/GPU bound as if those are two binary options. The reality is that a game can be both CPU/GPU "bound" in a way. Simulation happens first, then render. The input latency is the sum of these two things, not the longest of the two if that makes sense. However, they can be partially parallelized!

We get a surprising amount of data in a 24 hour window given how international our game is - obviously we'll have to continue to see how the winrates trend, but "adjusting to nerfs" normally results in much lower winrates early on, as players learn their new limits, as opposed to overperforming.

We'll continue to monitor Sage, but as it currently stands she's still quite strong - there's no reason to believe she's gutted, people have just very consistently thought that Sage was weaker than she actually is.

For this, we definitely thought about the trade off. In the end though, the hardware you play on is going to give you an advantage. Players with 144hz/240hz/360hz monitors are going to have an advantage over those without. Players with better ISPs that give lower latencies and no packet loss are going to have an advantage. Players with high-end machines are going to have higher framerates. Players with gaming mice with higher poll rates and better sensors have an advantage.

In the end, our goal for VALORANT is to make the interface between you and the game as responsive and seamless as we can possibly make it. To that end we're happy to support any hardware or software features that reduce the friction that input latency causes between what your brain/body can do vs what we can represent in game.

We try to weigh the pros/cons of supporting any technology against fairness and accessibility. Honestly if this was technology only supported by the 30XX series cards we mi...