The first report that this issue was apparently fixed was on December 9, 2022 5:07 AM.
The issue started reoccurring on approximately December 9, 2022 8:00 PM.
These three FFlags were changed on December 9, 2022 9:57 PM (could be delayed, read below). I viewed these changes using Roblox FFlag Watcher, selecting the PCDesktopClient bucket, and searching “VR”.
The most likely timeline of events is that:
- The issue was at first internally fixed.
- Some other internal change happened (not related to the FFlags), which made the fix not work anymore.
- These FFlags were changed in an attempt to remedy the issue. However, these FFlag changes were ineffective, and Roblox engineers are still working on this issue, which is why it hasn’t been resolved yet.
Of course, there’s a possibility that FFlag Watcher could be delayed by a few hours. Another version of events could be that:
- The issue was at first internally fixed.
- Due to miscommunication between Roblox engineers, the FFlags were changed and made the fix not work anymore.
- If this is what actually happened, this seems like a very simple solution on Roblox’s part! They can simply change the FFlags back to their state prior to the unfixing, and the issue would finally be resolved.
This is all speculation though, so take these two timelines with a lot of salt. No one except Roblox engineers would know what actually happened and how to remedy this.