REQUEST FOR INPUT: Thermal throttling

[iVRy]

Some users are experiencing thermal throttling messages, which need to be resolved. The situations where they arise seem to be in some cases independent of ambient temperature or rendering load.

If you do experience this, please make note of:
- resolution
- target frame rate
- bitrate
- a rough indicator of how long before it started in minutes
- other apps/tasks running on AVP (eg. Persona)
- M2 or M5
- whether or not you are using controllers
- lighting conditions (to assess tracking load)
- approximate ambient temperature
- battery state - high, low, charging
- Wifi conditions (good signal?), light/heavy traffic from other devices

Then, restart the device (you can leave SteamVR running), and once it has rebooted start the iVRy app again. You'll resume from where you were (in VR). If it happens again, please make a note of how long before it started.

So far, in my profiling of the software I haven't come across any high resource usage that should trigger this, so there's no easy culprit to address. With your help, the app can be improved and if there are conditions which make throttling more likely to occur, they can be documented.

[LowRider]

Originally posted by iVRy:

Some users are experiencing thermal throttling messages, which need to be resolved. The situations where they arise seem to be in some cases independent of ambient temperature or rendering load.

If you do experience this, please make note of:
- resolution

3494 x 3054

- target frame rate

90 Hz

- bitrate

200 constant

- a rough indicator of how long before it started in minutes

10 min.

- other apps/tasks running on AVP (eg. Persona)

No. Force quit

- M2 or M5

M5

- whether or not you are using controllers

No, did use the gamepad connected to the pc (UEVR)

- lighting conditions (to assess tracking load)

Did try both (dark and bright environment)

- approximate ambient temperature

26

- battery state - high, low, charging

high

- Wifi conditions (good signal?), light/heavy traffic from other devices

dedicated wired router (distance 1 m)

Then, restart the device (you can leave SteamVR running), and once it has rebooted start the iVRy app again. You'll resume from where you were (in VR). If it happens again, please make a note of how long before it started.

Performance was not great after restart.

So far, in my profiling of the software I haven't come across any high resource usage that should trigger this, so there's no easy culprit to address. With your help, the app can be improved and if there are conditions which make throttling more likely to occur, they can be documented.

When I switched from Bitrate constant 200 mbps to adaptive 90 to 150 it took much loonger until thermal throttling happened (20 min).

Perhaps it has something to do with the m5. But for some reason, I was not able to connect my other device (m2).

I used the 1.1.9.10 testflight version and the latest public driver version.

[iVRy]

Originally posted by LowRider:

Performance was not great after restart.

Thanks, I don't know what this means.

Originally posted by LowRider:

When I switched from Bitrate constant 200 mbps to adaptive 90 to 150 it took much loonger until thermal throttling happened (20 min).

This is useful, thanks.

Originally posted by LowRider:

Perhaps it has something to do with the m5. But for some reason, I was not able to connect my other device (m2).

Perhaps. More likely to be the temperature, which is "warm". Not being able to connect a device is another issue, please let us discuss that in a separate thread. Please provide the vrserver.txt from after you've tried to use that device:

https://steamcommunity.com/app/992490/discussions/0/3247562523076890727/

[LowRider]

Originally posted by iVRy:

Originally posted by LowRider:

Performance was not great after restart.

Thanks, I don't know what this means.

Originally posted by LowRider:

When I switched from Bitrate constant 200 mbps to adaptive 90 to 150 it took much loonger until thermal throttling happened (20 min).

This is useful, thanks.

Originally posted by LowRider:

Perhaps it has something to do with the m5. But for some reason, I was not able to connect my other device (m2).

Perhaps. More likely to be the temperature, which is "warm". Not being able to connect a device is another issue, please let us discuss that in a separate thread. Please provide the vrserver.txt from after you've tried to use that device:

https://steamcommunity.com/app/992490/discussions/0/3247562523076890727/

I could connect the m2 now (I did accidentely disable the network access). The m2 throttles too, but now room temperature are raising (28 degree).

[iVRy]

Ok, that's actually gone backwards then, as previously you were able to run at 3660x3200, and now only 3494x3094. That's counter-intuitive, as later app versions should improve things, not make them worse.

[LowRider]

It seems to be solved. I've never had it again lately.

[iVRy]

Originally posted by LowRider:

It seems to be solved. I've never had it again lately.

Good to hear! I never really did get to the bottom of the issue. Whatever was causing it was not in all cases actual thermal throttling, but some kind of responsiveness mitigation in the OS. If it ever does occur again, please let me know and I'll dig even deeper (I've dealt with every instance I can find of actions that might be interpreted by the OS as unresponsiveness).