Reply to thread

Message

<blockquote data-quote="nodef" data-source="post: 48159" data-attributes="member: 14598">One more potential work around.&nbsp; I found two calibrationXxX.xml files.&nbsp; Only one matched my true screen resolution.&nbsp; When I delete both files and restart they are both reconstructed.&nbsp; To fix the problem, I modified the &quot;overscan*&quot; lines in the incorrect calibrationXxX.xml file to match my correct resolution (effectively making both files identical) and I can now start in full screen mode without problems.&nbsp; This seems to be consistent with Muschi's description that the initial full screen mode loads the incorrect file (mine also seemed to be off by 12x12 pixels).&nbsp; Since both files now have correct resolutions this doesn't cause a problem.&nbsp;In more detail - I modified the lines:&nbsp; &nbsp; &lt;entry name=&quot;overscanwidth&quot;&gt;1932&lt;/entry&gt;&nbsp; &nbsp; &lt;entry name=&quot;overscanheight&quot;&gt;1092&lt;/entry&gt;to match those of my correct screen resolution:&nbsp; &nbsp; &lt;entry name=&quot;overscanwidth&quot;&gt;1920&lt;/entry&gt;&nbsp; &nbsp; &lt;entry name=&quot;overscanheight&quot;&gt;1080&lt;/entry&gt;Now I can start in full screen without a problem.&nbsp; Not a real fix, but less manual then having to startup in windowed mode then switch to full screen.&nbsp; I guess the real question is what is creating the calibration(X+12)x(Y+12) file?</blockquote>

[QUOTE="nodef, post: 48159, member: 14598"] One more potential work around. I found two calibrationXxX.xml files. Only one matched my true screen resolution. When I delete both files and restart they are both reconstructed. To fix the problem, I modified the "overscan*" lines in the incorrect calibrationXxX.xml file to match my correct resolution (effectively making both files identical) and I can now start in full screen mode without problems. This seems to be consistent with Muschi's description that the initial full screen mode loads the incorrect file (mine also seemed to be off by 12x12 pixels). Since both files now have correct resolutions this doesn't cause a problem. In more detail - I modified the lines: <entry name="overscanwidth">1932</entry> <entry name="overscanheight">1092</entry> to match those of my correct screen resolution: <entry name="overscanwidth">1920</entry> <entry name="overscanheight">1080</entry> Now I can start in full screen without a problem. Not a real fix, but less manual then having to startup in windowed mode then switch to full screen. I guess the real question is what is creating the calibration(X+12)x(Y+12) file? [/QUOTE]

Verification