#Stutters on 1000 Mbps
77 messages · Page 1 of 1 (latest)
Hell, even 450 will start to micro-stutter after a bit
Yeah, Same thing happens to me whenever I do 300 and up.
with what codec and connection?
Wired, h264
Don't think you can achieve 1 Gbps with wireless and h265 xD
with hevc you should target 150-200
its much more efficient - thus more suitable for use over wireless connection
just use presets, dont touch bitrate slider or it will get messed up
what does statistics graph show when it stutters?
i dunno what decode is like on pico 4 pro - but all these headsets have some limit - and when it artifacts or stutters thats a sign
quest2 and quest3 seem to have similar limit of 150-200 hevc
i only use wireless and only use hevc
HEVC looks terrible even on 150 and on 200 it starts to have higher latency while still looking not the best (maybe because of AMD)
And I remember on Quest 2 it was smooth as hell with 1 Gbps over wire before Zucc decided to mess ALVR up and introduce the "snow" artefact
And as I see on Pico this artefact is not present
So I would like to find out what happened, why it now stutters like that when the first time 1 Gbps was introduced to ALVR it was buttery smooth
you might be right - i can only comment on my experience with nvidia 3090/4090 and quest2/3
dont have amd card to do comparison
usually problem is on headset side - pc has no problem encoding it
unless you have certain special cards that i cant mention without triggering the bot
but the thing is it never was like that before I gave up on ALVR with Q2's snow flake artefact
alvr just uses the hardware of your system
RX 6800 XT
and so do the other vr programs
I know
if you mouseover the stat graph when it stutters can you observe what is causing it?
is it pc render or pc encode or headset decode or network?
it seems like it has something to do with frame buffering
ive read reports about this stuttering a lot lately
@blazing rain @wild timber sus
please try different versions of alvr and tell devs if you think some version is better
you can use the alvr launcher to easily download and install different versions
I am not exactly new to ALVR xD
good - so you know how to reset to defaults and do clean tests
ye
Around what version people started complaining about these stutters?
Might be better for me to just jump on there
but you are comparing two different headsets right? should not expect same result
variables are encoder performance on pc side - and decode performance on headset side
quest2 decode performance we all know - and alvr presets target majority use-case
what is different about pico 4 pro?
no
No snowflake artefacts at all
so it has better decode?
that means you can pump it more
1000 is rookie numbers it seems
on q2 before v54-55 it was the same except the stutters
just hit it with more until you see artifacts or stutters
and make sure to use high entropy test not low entropy (ie static scene)
in fact dont even bother testing unless its something with very good graphcis and action (not beat saber)
but do you know? @warm halo
nope but i see other people compaining
use old version of alvr if the new one is a problem
seems like on 20.10.0 there is no stutter at all
Do you think you could bisect further using nightlies? Otherwise this will never be fixed
you mean from 20 nightlies move up to the latest and see when exactly this problem came?
Finally got away from the Zuccy ecosystem of botching updates to the point of affecting hardware
Have you tested the nightlies yet
I don’t know if we’re talking about the same snowflake artefact but personally it was due to FFE and since the rust rewrite it got fixed
I had a sort of white streaks across the screens
the bitrate behavior is completely different in lastest nightlies
so whatever settings were good in the past are not gonna be good now probably - tune your settings again
It may have been another fix, that happened around the same time of the rust rewrite. Yoyobuae made some changes to the shader to make it less heavy
bitrate mode has been on constant 30Mbps for months lol
in latest nightlies that actually does what it says and thus image looks bad