Please export the log files and, if possible, include the timestamp when the issue occurs.
The developers will review them to identify the cause of the disconnection.
Iâll forward this to the developers and ask them to reproduce the issue with the image quality set to 1.5 and test it in MSFS.
Do you mean the screen-off issue is occurring more frequently and happening sooner?
I spoke with the developerâthis issue has been reproduced and the root cause identified. The next patch should resolve it.
1 Like
Yes â it happens sooner and more frequently.
Even if I lower the image quality to 1.0, it still occurs, but much less often. In Digital Combat Simulator I use 1.0, and Iâve seen it there as well, but very rarely â in most sessions (even multi-hour ones) it doesnât happen at all.
Since I increased the display timeout, the system has been stable.
1 Like
Noted.
The devs are working on a fix.
I tried this after reading your post and so far, no issues with the screen turning off. Thanks for the suggestion.
1 Like
I am not able to calibrate eye tracking even when using this latest version. also completely uninstalled the previous version but still no luck.
Which headset are you using? Please check if the IR LEDs around the lenses are lit.
Second, check whether the âEye Chipâ appears in Device Manager.
If youâre using the Crystal Super micro-OLED, also check if the related service is running.
I am using the micro-OLED module.
yes, IR LEDs are lit. checked with my smartphone camera. also eye chip is present and the service is running.
when I try to calibrate, I am getting this message:
Okay.
Are you too close to the lenses, causing the cameras to be unable to detect your eyes?
no change when I am way back of the headset. 
Hmm, you may want to reseat the cables and try again. If itâs still unsuccessful, please file a support ticket and include the log files so our developers can take a look.
ok, will do. thanks.