devtrackers.gg → RiotNu
RiotNu

RiotNu



13 Oct

Valorant 1.10 Bug Megathread

Comment

Originally posted by trisckit

  • Region: NA East
  • Type of Bug: Map/Sound Bug
  • Description: On Icebox, when my framerate encounters a dip, the audio lags behind and becomes very choppy. Capping framerate so that it never dips makes the problem go away. This does not happen on any other map
  • Video / Screenshot: Me testing it on Icebox. Me testing uncapped framerate on Ascent
  • Steps to reproduce: Uncap your framerate, walk around/shoot/use utility on Icebox.
  • Expected result: Audio plays fine regardless of framerate
  • Observed result: Audio becomes choppy when framerate dips, on Icebox only.
  • Reproduction rate: 100%
  • System specs: NVIDIA GTX 1050Ti, Intel Core i7-7700HQ

For others that are hitting this, it'd be useful to know what hardware your have. Thanks!


20 Aug

VALORANT Patch Notes 1.06

Comment

Originally posted by CaseyDesmith1xxx69

No fix on killjoys split bug yet lol

Fix is in the patch.


11 Aug

What does the "Limbo" setting do?

Comment

Whoops. This setting is for internal testing and shouldn't be displayed. The setting doesn't do anything in the live game.


07 Aug

Longest OT ever in valorant?

Comment

Originally posted by RazorRipperZ

How long after that game was Draw inplemented?

Not sure. More than a year. OT didn't end up in its current form until after launch. We had more important stuff to build for players first.

Longest OT ever in valorant?

Comment

A long time ago there was no draw and I had a game go into the 30s. That game changed me.


06 Aug

New info on Joules

Comment

Originally posted by Altombre

I’m honestly not sure, I’m not a designer or engineer so I don’t actually work in game code.

The short version is that it involves file dependencies and time spent on cleaning up the remaining orphaned assets is time not spent on something more valuable to players. Please pardon our dust and ignore the detritus.

We've learned a lot since the early days of the project, and we're better about how we structure current content.


03 Aug

Valorant client not even starting

Comment

Originally posted by ELIteGinger64

This is still an issue in patch 1.04, when are we getting a fix?

Sounds like your issue is something else. If you haven’t already, create a player support ticket and they can help you out.


07 Jul

Valorant client not even starting

Comment

Originally posted by TacoTurd

Any news on the fix being validated?

This will be fixed in patch 1.03.

Valorant client not even starting

Comment

Originally posted by Pykeeboi

When will the update be released, I really want to play Valorant

This will be fixed in patch 1.03.


18 Jun

VALORANT Patch Notes 1.01

Comment

Originally posted by [deleted]

[deleted]

Not in the near term. There's a threshold where it can make performance worse not better, and right now our testing has 8 logical cores as the point where it starts providing value.

Valorant logs are constantly being written to and taking up space on drive

Comment

Originally posted by ThisIsKindaDifficult

Thank you for the response! Could you clarify what is being fixed? Is it the large log file sizes or something else?

The large log file is caused by an errant warning spamming repeatedly. That’s fixed. The game also periodically deletes old log files.

Valorant logs are constantly being written to and taking up space on drive

Comment

We have a fix for this in the next major patch. It's safe to delete these files if you need to reclaim the space before then.


17 Jun

VALORANT Patch Notes 1.01

Comment

Originally posted by FolX273

Hey thank you guys for adding multithreading support it's obviously a technical challenge to get right.

With that said I'm pretty bummed out it's not in my game options. In the same boat as many others, 4GB Vram needs to have it too. I just tested this specifically and I literally get two times the FPS on CSGO with Multicore rendering option turned on/off.

Specs: Ryzen 7 3550h (turbo clock 4Ghz) and GTX 1650 4gb. Obviously this is a laptop setup but I get respectable frames as it stands in the 100-120 FPS range. But looking at CSGO I can't help but feel it could be better

We're going to lower the VRAM requirement from 6 GB to 2 GB in the next major patch.


11 Jun

You just lost hundreds of megabytes of free space after playing VALORANT? Check and delete log files

Comment

Originally posted by [deleted]

[deleted]

Thanks for the heads-up. We've got a fix for this in the upcoming 1.02 patch.


09 Jun

VALORANT Patch Notes 1.01

Comment

Originally posted by ExRcanian

Is there a definitive list for what specs are required for the setting to be available? I have a 2600X and I'm not seeing the option in the graphics quality settings.

It currently requires 8 logical cores and a Nvidia or AMD GPU with 6 GB of VRAM. These requirements may change in the future.

VALORANT Patch Notes 1.01

Comment

Originally posted by RiotBrentmeister

Hope they help! The Multithreaded rendering is going to be very dependent on spec + where you measure FPS.

Multithreaded rendering's biggest improvements will be in the Range and when running around maps. Other factors become the limiter in heavy combat, and we're still optimizing more.


04 Jun

Two 170mb updates have destroyed the initial fantastic launch FPS!

Comment

Originally posted by A-White-Cornerback

It definitely has somewhat impacted it, I was getting 290-350 FPS yesterday and now I’m barely hitting 250.

And I’m not sure if you have any say in map rotations, but I have played ascent 8 times in a row now, and I’m starting to get sick of the map. I know y’all want us to play it and get used to it, but after 3 in a row, could you potentially make it so we won’t get that map again?

Edit: just for more info

My specs are

Vega 56

I5 8600k (5.0ghz)

16gb 3200 ram

2tb ssd (it’s not the fastest ssd, but it’s samsung q or something like that)

I’m gonna restart my pc rn and I’ll update this again if it fixes

Edit: so the issue might be vanguard actually. I’m seeing it taking up around 30% cpu in task manager and dropping valorant down to 65%.

I still have lower fps after the restart

Thanks for the details (and I saw the edits).

Two 170mb updates have destroyed the initial fantastic launch FPS!

Comment

Originally posted by HeyItzShane

One question, What were the updates changing?, I dont see any mini patch notes so is it just bug fixes?

It had a couple of targeted bug fixes. We don't think those changes should have impacted performance, but we're looking into it.

Two 170mb updates have destroyed the initial fantastic launch FPS!

Comment

Originally posted by [deleted]

[removed]

If you see the launcher validating files after a crash it means the game detected corrupted files when trying to load game content. It should self-repair but if you see it more than once there may be an issue with your RAM or disk.

Two 170mb updates have destroyed the initial fantastic launch FPS!

Comment

What hardware are you running on?