v0.15.0 - Calibration bug on new profiles created when runtime is off
I went to set up a new laptop with the latest FOVE runtime software today. I created a new profile before starting runtime, turned on runtime, and then tried to calibrate on that profile. Nothing appeared on the screen (just the usual starry sky background), but a notification still appeared to say that calibration had started, and the debug tool showed that calibration was running. I tried opening the mirror client, but it was entirely black, and I had to force quit to get it to exit.
I then tried creating a profile while runtime was on, and calibration happened as usual. I was also able to retrigger calibration from the debug tool and from my unity project.
I was able to recreate this phenomenon consistently with a few profiles. This seems like an easy oversight, but it definitely caused me a lot of grief before I figured out what had happened.
My log file is too long to copy into this post, but I can email it to the support team if needed.
-
Thanks for the bug report, and sorry that you had to run into this and figure it out.
I tried this against our latest development version (to become the next release) and it appears fixed as a result of other changes in the calibration/profiles code. So it should be fixed for good, but if you do upgrade later on and happen to see it again, let us know.
Please sign in to leave a comment.
Comments
1 comment