Closed Narazaka closed 2 months ago
Good point, I haven't experienced the situation that timing was unable to keep on sync. Its look like it is similar what #29 described (which I'm not quite sure what was the cause yet).
Do you think I should increase the threshold constant value internally or expose this value to inspector?
Do you think I should increase the threshold constant value internally or expose this value to inspector?
I think so.
I have experienced this situation not that many, but my friend who has low spec PC (GTX1660 and low CPU) complains that he faces that situation many times in my world and it seems to happen even if other people does not experience it
So, if I don't misunderstand, this issue might happen when network latency too high and/or hardware rig is too low ended?
I think so partially but not certain. My env is i7-13700KF, RTX3090 and Pimax 5K but I experienced especially when there are many people present (10 or more).
and my low spec friend: maybe 4-5 people
and this happens even if he is the video owner.
Understand. Certainly need to increase threshold value.
The changes were made and will be included in next release.
In some situations, maybe especially high load, the video playback point repeatedly moves back and forth in small increments, making it impossible to watch the video at all.
VRChat log says
so I think that SyncTime() is being called repeatedly because the duration difference threshold is too small.
VisVid sync threshold is smaller than common other video players like below and cannot change from inspector. VizVid: 0.1f iwasync: 0.92f USharpVideo: 0.85f