Reply to thread

Message

<blockquote data-quote="nodef" data-source="post: 69675" data-attributes="member: 14598">Here's my take on the problem.&nbsp; I haven't had time to look in detail, but I hope&nbsp; here's some useful information.&nbsp; If I look at my logs, I see several places where the player attempts to deal with a screen size (1932x1092) which is larger than my screen. (1920x1080).&nbsp; In previous versions by editing the configuration files so that a file for the wrong size (1932x1092) actually pointed to a correct configuration for the correct size (1920x1080) the problem would go away.&nbsp; This doesn't seem to work in the latest update.My guess (it may not be&nbsp; a good one) is that the code is computing an incorrect screen size -- when using VMR9 exclusive mode to open this screen which is larger than the current resolution, the video driver is defaulting to the blank screen.&nbsp; Obviously, this would be driver dependant, so the problem might not show up for everyone.&nbsp;&nbsp; Just browsing the code, it looks like the overscanwidth is getting set to the larger size (which is reported in the log) , and a sanity check statement in the code is setting the current screen size to be equal to the oversizewidth.This might also make sense with respect to the font size fix.&nbsp; So going out on a long limb, is it possible that someplace in the GUI code that the screen size is computed in a manner such that it gets increased based upon the size of a font.&nbsp; (i.e. with the larger fonts, something is going beyond the edge of the screen)I agree this is a big problem.&nbsp; I don't have much experience with this code, but if I get a chance, I'll try to track things down in more detail.</blockquote>

[QUOTE="nodef, post: 69675, member: 14598"] Here's my take on the problem. I haven't had time to look in detail, but I hope here's some useful information. If I look at my logs, I see several places where the player attempts to deal with a screen size (1932x1092) which is larger than my screen. (1920x1080). In previous versions by editing the configuration files so that a file for the wrong size (1932x1092) actually pointed to a correct configuration for the correct size (1920x1080) the problem would go away. This doesn't seem to work in the latest update. My guess (it may not be a good one) is that the code is computing an incorrect screen size -- when using VMR9 exclusive mode to open this screen which is larger than the current resolution, the video driver is defaulting to the blank screen. Obviously, this would be driver dependant, so the problem might not show up for everyone. Just browsing the code, it looks like the overscanwidth is getting set to the larger size (which is reported in the log) , and a sanity check statement in the code is setting the current screen size to be equal to the oversizewidth. This might also make sense with respect to the font size fix. So going out on a long limb, is it possible that someplace in the GUI code that the screen size is computed in a manner such that it gets increased based upon the size of a font. (i.e. with the larger fonts, something is going beyond the edge of the screen) I agree this is a big problem. I don't have much experience with this code, but if I get a chance, I'll try to track things down in more detail. [/QUOTE]

Verification