iVRy Driver for SteamVR

iVRy Driver for SteamVR

Bandwidth / Throughput Question
Hey -
overall works great for me. I'll post more specific feedback later on but quick question first:

With resolution (per eye) at native VP 3,660 x 3,200 with let's say HL:A, I get roughly 50-55 ms at 90 FPS, which is quite good.

However, the iVry Settings app shows a throughput of 24-25 Mbps and tested Bandwidth around 60-70 Mbps, which seem very low for that resolution and frame rate, even with h.265 and HL:A. It would give a compression ratio of something like 1000:1 or even 2000:1.

The resolution and frame rate in the iVry app is correct as fpsVR shows the same.

I can't quite wrap my head around 25 Mbps throughput looking this good, as I would expect something like 120 - 180 Mbps.

Is it possible the value reported in the app isn't correct ? Or maybe it shows the static SteamVR / iVry settings throughput at that point in time rather than the game's ?

Or something ...
Originally posted by iVRy:
The correct notation is Mb for Megabits, and MB for Megabytes. The driver UI uses Mbps to and MB/s to make the distinction clear. H26x encoding rates are Mbps, and network throughput is MB/s. Throughput is not the same as H26x encoding bitrate, it includes other network traffic (eg. tracking and audio), as well as framing and TCP overhead.
< >
Showing 1-2 of 2 comments
A developer of this app has indicated that this post answers the original topic.
Apr 24 @ 11:13pm 
The correct notation is Mb for Megabits, and MB for Megabytes. The driver UI uses Mbps to and MB/s to make the distinction clear. H26x encoding rates are Mbps, and network throughput is MB/s. Throughput is not the same as H26x encoding bitrate, it includes other network traffic (eg. tracking and audio), as well as framing and TCP overhead.
Thanks. Completely missed that. The world makes sense again.
< >
Showing 1-2 of 2 comments
Per page: 1530 50