2011-05-09, 15:32
Cranial Wrote:Won't get a chance to try it until tomorrow, but I'll let you know as soon as I can.
If you can set overscan and it stays set after leaving the calibration screen, then I'd say this fixed it. I couldn't get overscan calibration to stick with current build.
Okay, I believe it is fixed. With the #if changed, I could leave the calibration screen with the new settings in force, and they continue to work after a quit and restart.
It appears if you launch with current (non-modified) top of tree, you lose your current calibration settings.