Thanks so much for all of your replies, you're really the best <3
Using BIOS settings and deleted EmptyStandby task, as you suggested.
Played a deathmatch just now while using the suggested changes, and snapped a few screenshots of the in-game stat graphs.
I'll attach those below.
- CPU, GPU, Memory stats
- Networking stats
Spooky. Will think more. There’s something we are missing.
I've tried deleting the EmptyStandby before, but I couldn't really tell that much of a difference.
Going to try what you said now.
- Delete EmptyStandby task
- Reset BIOS to default, and only enable D.O.C.P (turning on-board audio on, and case fans to standard)
For reference, I also just did a benchmark thingie using my setup the way it is right now.
Before doing those changes:
Sounds good. Case fan and onboard audio likely won’t matter for VAL either. Interested in your results.
Read moreI don't really know to be honest... typically, I just use the default BIOS settings.
Exceptions in BIOS:
- Turn D.O.C.P on
- Set the case fans to "quiet" rather than the "standard" setting, since I don't like them being super loud when playing.
- Disable onboard audio as I use a Fiio E10K Dac/Amp
Windows Settings:
- Power Plan ---> High Performance
- Disable Game Mode
- Disable Game Bar
- Disable all background processes under the Privacy Tab
- Use EmptyStandby as a task that's scheduled to run every 5 minutes to clear standby memory
Nvidia Settings:
- Power Management Mode ---> Perfer Maximum Performance
- Texture Filtering Quality ---> High Performance
- Low Latency Mode ---> Ultra
- Perform Scaling ---> Display
- Perform Scaling ---> Override the scaling mode set by games and progr...
If you haven’t already, you might try resetting everything to default except DOCP and see it that makes any difference.
EDIT: I would also probably try dropping the memory task.
Read more1440p is probably a problem, I guess?
Along with only using two sticks of RAM with your zen3 processor.
Using 1080p instead of 1440p, would help a lot, I think.
But it still looks like you should still be getting around 350 to 400 frames, tho... at least if you watch other people with an AMD 5800x on 1440p:
https://youtu.be/u5WYGke9MJw?t=290
You'd gain 5% to 10% performance by swapping to 4 sticks of RAM rather than using two sticks, like the video mentioned here:
https://www.youtube.com/watch?v=-UkGu6A-6sQ
I personally use 4 sticks of RAM with the 5800x, but happen to adore using 1280x960 as my resolution.
- During competitive match
- Right after killing 4 enemy players, while healing myself
- Never dropped below around 450FPS the whole round
- FPS = 400-700
...
Just saw this comment fork. All these numbers are surprisingly high for that hardware, which makes me suspect something is off timing wise. Do you have any idea what might not be default about your setup?
Read moreUnrealEngine version 4.25 is what Valorant currently uses, right?
Would that not be a potential cause of a lot of these bugs?
I feel that most of the issues we struggle with are due to "hitching", more than anything else.
I'll admit I have no clue about the game engine.
But would any of the "fixes" in UE 4.26 / UE 4.27, could potentially help at all?
The ones listed below seem really interesting interesting to me, since they mention networking improvements and fixes for hitches.
Would none of these affect Valorant positively, if the game were upgraded to UE 4.26?
Unreal Engine 4.26
- Networking Improvements
- Improvements
- "We made performance improvements to the networking Blueprints to avoid bottlenecks and disconnections. The network settings have been tuned for high load so you can have more participants with smoother object manipulation and movements"
...
These are unlikely to be relevant.
Hey again, i found another bug but this time for the Singularity Phantom. When you shoot all the parts move but they wont go back to their original position, no idea if this is also bugged for the other skins. Example pictures: https://imgur.com/a/OX2u8DS
This is intentional. As you shoot, the parts separate and go back together when you reload. During development it was way more extreme and we felt that it being too noticeable might be a gameplay advantage to be able to tell your ammo count just by the look of the gun so we toned it down significantly
- Don't have AI Suite III installed (never have on this Windows install)
- Don't have Asus Armoury Crate installed (never have on this Windows install)
I also fresh reinstall Windows completely from a USB drive every 2 weeks to 4 weeks.
- Always update all drivers
- Always run a DISM + SFC to scan for disk errors
- Always use Ethernet
- Always use a Gigabit connection
It’s worth reaching out to Player Support if you haven’t already. The input handling item you are describing sounds like it could be explained by something related to timing but doesn’t map to any known issue I am aware of from your answers. I will note that the FPS numbers you are reporting are not close to normal for that CPU.
Read more
- No Overclock
- No HPET setting
- No changes to BIOS (other than setting RAM to the D.O.C.P setting and the case fans to the proper speed)
- Raw input buffer = Off
- Have tried "on"
- On = much more responsive, but makes tracking inconsistent
- Off = less responsive, but much more consistent and stable
- I keep it "Off" due to that, and play better with it "Off"
- Mice used
- Razer Viper 8Khz (set to normal 1K polling rate, Razer Synapse uninstalled and not used)
- Zowie EC2-B
- Zowie S2
- Zowie FK2-B
All mice display the same issue.
The issues have been present since the Omen bug hotfix in 2020.
Here's that Omen Hotfix time period, although I think October 2020 saw another Omen hotfix... maybe it was October's not this one (?):
Do you have ASUS AI Suite 3 installed?
Underrated - all green screen skins
devtrackers.gg
