2018-10-19, 10:20
(2018-10-07, 22:36)fritsch Wrote:Hi Fritsch,(2018-10-04, 14:02)menno Wrote:(2018-10-03, 15:33)Milhouse Wrote: Those with the artefact problem, can you please test the following builds:I didnt have time to do all of them, bu I can confirm D does not have artifacts for me (asus chromebox 2014)
1002b: Generic - same as #0813
1002c: Generic - 1002b + PR14291
1002d: Generic - 1002c + PR14282
1002e: Generic - 1002d + PR14295
1002b should not have the artefact issue, while 1002e should have the artefact issue. I'm not expecting c & d to have it, but who knows for sure so please test them too.
Assuming the issue is confirmed as starting with 1002e then I might try and narrow it down to the specific commit with additional test builds.
Edit: We still need a debug log from an affected build which may reveal some specific GL/mesa behaviour that is hardware dependent.
Do you have custom configured OVERSCAN values? E.g. in kodi's gui calibration? Can you reset them please?
Woud this be considered custom settings?
Code:
<resolutions>
<resolution>
<description>1920x1080@ 60.00 - Full Screen</description>
<subtitles>1015</subtitles>
<pixelratio>1.000000</pixelratio>
<refreshrate>60.000000</refreshrate>
<output>HDMI1</output>
<xrandrid>0x48</xrandrid>
<overscan>
<left>21</left>
<top>13</top>
<right>1826</right>
<bottom>1054</bottom>
</overscan>
</resolution>
<resolution>
<description>HDMI1: 1920x1080 @ 60.00Hz</description>
<subtitles>1042</subtitles>
<pixelratio>1.000000</pixelratio>
<refreshrate>60.000000</refreshrate>
<output>HDMI1</output>
<xrandrid>0x48</xrandrid>
<overscan>
<left>0</left>
<top>0</top>
<right>1920</right>
<bottom>1080</bottom>
</overscan>
</resolution>
I do remember back in the days you had some special settings for this chipset and hw scaling and something i believe with 20% etc, I cannot find that in the current version though anymore. This is a snippit from guisettings.xml