This is not something that we can fix. As you can tell by those logs, we are setting the values - it is up to the simulator to persist them, not us. Some have had success by running the simulator as admin, but that is generally really bad advice so I won’t call that an official solution. Here is one such case:
There is nothing we can do about this without rebuilding the app from scratch specifically for the simulator. This is not an option for us at the moment, and it would ultimately result in the panel lagging behind or being completely left out when new features are released.
The core issue is that the in-game panel shares resources with the simulator, so one will inherently limit the other in both directions (slow loading panel, low FPS in simulator). There is no way around this due to the way that the simulator is built - the only other option is to run the desktop app and somehow bring that into VR!
It’s possible that we can find a different solution in the future, but at the moment this is the best we can do given the circumstances! Apologies for the inconvenience.
Kind Regards,
Malte