While idle, the OVR service writes developer logs to
user\AppData\Local\Oculus\Service_timestamp.txt. I'm not big into
spending I/O queues on writing things like 'yep there are some VR
accessories present' for a service that intends to run indefinite...
Tape or tack is still the answer. Note that keeping the Rift active for
hours focused on a static scene risks LCD burn-in, causing a shadow of
the static scene over new content.
Someone needs to update OVRLibraryService.log to the log rotation you've
got going on for the service and perflog. I installed OVR in October
2018 and OVRLibraryService now consumes 386MB.
You won't break anything significant by changing your system clock. Your
event logs will be confusing as hell and your file modification dates
will be all wrong, but it's unlikely anything will be affected in a
serious way. The only thing you open yo...
