Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1189178" data-attributes="member: 82144">Following up on another bug report, I noticed updates in this thread too. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek!    :eek:" loading="lazy" data-shortname=":eek:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!    :oops:" loading="lazy" data-shortname=":oops:" />Seems to me that the problem here is caused by Windows, HDMI, or GPU driver.[USER=103549]@JimCatMP[/USER] There's nothing unusual in the log sections you identified. If Windows' resolution is actually 1280x720 then that's what MP's resolution should/will be as well.My theory for your situation is as follows.Windows has applied a default resolution - in your case 1280x720 - between startup and successful GPU driver initialisation and HDMI handshaking. After initialisation and handshaking completes, the resolution should step up to 1920x1080. If you start MP after Windows' resolution has settled to 1920x1080, MP's resolution should also be 1920x1080. On the other hand, if you start MP while Windows' resolution is still 1280x720, MP's resolution will also be 1280x720. So far so good. The question is whether MP handles the step up from 1280x720 to 1920x1080 as it should. Usually MP handles such changes fine... but it's completely reliant on Windows providing a notification that the resolution has changed. If Windows doesn't provide a notification, MP's resolution won't change. Note that the "settling factor" part of my theory would explain why you can't reproduce the problem except immediately after cold boot or restart.Ahhh, but did you check the Windows resolution before or after MP started?Windows' resolution could have changed between MP startup and you checking it. In theory if that had happened, MP's resolution should have changed too. However we haven't got log files to confirm whether Windows did or did not notify MP of a resolution change.Ideally you need to check both before and after starting MP.One more point: updating to MP 1.15 (or at least 1.14) may change the situation because of a particular bug fix. I think the bug fix went into 1.14 final, but I'm not 100% sure.In short: more information and experimentation required.[USER=50482]@azzuro[/USER] Now with full Watchdog log files I can see your configuration:<entry name="ignorefullscreenresolutionchanges">yes</entry>So MP is ignoring resolution change notifications from Windows. I think that is the source of your problem. Try to untick the option in "general" -> "startup/resume settings".Also...If you really want to avoid problems, order should be:<ol> <li data-xf-list-type="ol">TV</li> <li data-xf-list-type="ol">AVR</li> <li data-xf-list-type="ol">PC</li> </ol></blockquote>

Verification