FPFC FPS limit not respected in level [1.37.0]

[gitgizmo7]

When an FPS limit is set for FPFC, it is respected in the menu, but as soon as a level is entered (either normal play or BeatLeader replay), the framerate appears to be unlimited (900+ FPS according to Nvidia overlay). This behavior appears to persist in the menu once the level is exited until the Camera2 config menu is entered, after which the framerate returns to the set limit.

Config:
Camera2.zip

[kinsi55]

Is this exclusive to the update? What headset / vr implementation are you on and is the HMD connected?

[gitgizmo7]

After some testing, I found that this occurs on 1.36.2 as well, but not 1.34.2. I'm on Rift S, and this issue does not occur with the HMD connected (locks to 80 FPS). It occurs purely when using FPFC with the HMD disconnected. This is on Steam, and the vrmode oculus launch flag does not appear to affect this behavior.

[LazyLazyCoder]

Similar problem with Quest 3. BS 1.39.1. When I set FPS limit to 59 or 61 FPS then is respected in menu and replay. But when I want to limit to 60FPS then is not respected in replay (max FPS), but respected in menu. BS run in oculus mode and FPFC.

EDIT. I fixed it by reset nvidia settings for BS. Looks like some options set there influence fps limit.