Page 1 of 1

Screen resolution

Posted: Thu Jan 30, 2014 12:03 am
by TigerTC
I just purchased a new laptop with 1920x1080 resolution running Windows 8 and a 14 inch screen. When I run CO on it, the only option I get is to "match current screen resolution."

However, when I do that, some of the far left menu screen is basically lost -- scrunched away and hidden by the map. While not a huge deal when I can't read the entire Scenario Briefing, it is a problem when some of my menu options are hidden.

Suggestions for fixing this?

RE: Screen resolution

Posted: Thu Jan 30, 2014 12:33 am
by BletchleyGeek
ORIGINAL: BROJD

I just purchased a new laptop with 1920x1080 resolution running Windows 8 and a 14 inch screen. When I run CO on it, the only option I get is to "match current screen resolution."

However, when I do that, some of the far left menu screen is basically lost -- scrunched away and hidden by the map. While not a huge deal when I can't read the entire Scenario Briefing, it is a problem when some of my menu options are hidden.

Suggestions for fixing this?

Can you take an screenshot? I'm not sure I understand what you mean by "scrunched away and hidden by the map".

RE: Screen resolution

Posted: Thu Jan 30, 2014 11:52 am
by Lieste
Its the font scaling issue.

RE: Screen resolution

Posted: Thu Jan 30, 2014 8:43 pm
by TigerTC
Here are a couple screenshots.


Image

RE: Screen resolution

Posted: Thu Jan 30, 2014 8:44 pm
by TigerTC
And two.

Image

RE: Screen resolution

Posted: Fri Jan 31, 2014 6:01 pm
by TigerTC
?????

RE: Screen resolution

Posted: Fri Jan 31, 2014 6:02 pm
by TigerTC
ORIGINAL: Lieste

Its the font scaling issue.

What does that mean? What do I do?

RE: Screen resolution

Posted: Fri Jan 31, 2014 6:28 pm
by Lieste
The comment was meant for Miguel, really. It is an issue that has been addressed before, but not successfully in all cases (often I think a failure to actually perform some of the requested steps, but there might be some issues that aren't currently trapped).

Part of the problem is that display issues at extremely high resolutions require a high resolution screen to test, and this may not be available in the active testing team (we are all volunteers).

First, ensure that for the purpose of running this application that Graphics card & Windows font scaling is for the standard DPI setting. Next try setting program compatibility to "disable font scaling at high DPI" (Right context menu>compatibility settings for CmdOps.exe)

If this isn't enough, then report back and we can try other steps (also look back at previous threads in this Tech forum ~ there might be other steps that I've forgotten/neglected).

On one previous occasion I think an offer to supply a custom exe for testing was made, but not AFAICT actually taken up.

I gather (though not with understanding all the intricacies) that this is caused by mixed support for older windows versions, XP, 7 and 8, and the solution would be trivial if only supporting 7 & 8.

RE: Screen resolution

Posted: Fri Jan 31, 2014 6:32 pm
by Lieste
As an additional: It is *possible* that the display 'correction' isn't made and the display is as intended if running the program in a smaller resolution than native, at the cost of slightly fuzzier display.

While 'match current' may be the only option (though I'm unsure why that would be? - I get a reasonable list of alternatives, though I always "match current"), a 'fudge' might be to adjust desktop resolution to an alternative immediately before running the App.

RE: Screen resolution

Posted: Fri Jan 31, 2014 9:43 pm
by parmenio
ORIGINAL: Lieste

While 'match current' may be the only option (though I'm unsure why that would be? - I get a reasonable list of alternatives, though I always "match current

I don't have this sidebar issue but I'm also on Windows 8 and the only option I have is "match current".

Edit: Meant to say this wasn't a problem in Windows 7 - I could choose other resolutions even if they weren't appropriate.

Edit2: Also - 1920x1080 is not what I'd call an "extremely high resolution".

RE: Screen resolution

Posted: Fri Jan 31, 2014 10:25 pm
by Lieste
It is pretty high width wise for a single screen, rather than a spanned group. It is the width that is dominating the automagic windows scaling functions, and probably determining user choices for font DPI within windows.


Last time I heard* we didn't have anyone using a 1920 * xyz screen in the testing group. My own screens are 1280x1024 or 1440x960 depending on which monitor is on which of my machines (I prefer the 1280x1024 one, but it is currently in use on another machine).
A long time ago I did have a 1600x1200 19" CRT, but it's electronics died and it was uneconomic to repair (again).

*Ages ago, so possibly not current.

RE: Screen resolution

Posted: Sat Feb 01, 2014 4:37 pm
by TigerTC
ORIGINAL: parmenio
ORIGINAL: Lieste

While 'match current' may be the only option (though I'm unsure why that would be? - I get a reasonable list of alternatives, though I always "match current

I don't have this sidebar issue but I'm also on Windows 8 and the only option I have is "match current".

Edit: Meant to say this wasn't a problem in Windows 7 - I could choose other resolutions even if they weren't appropriate.

Edit2: Also - 1920x1080 is not what I'd call an "extremely high resolution".


Same here. I used to play in Win 7 with no problems. With Win8 I only get the "Match Current Resolution" option. Usually. Twice I've seen it come up with more choices; the most recent being the first time I started it after changing the Compatibility Mode to "Disable Scaling at High DPI." But I've toggled it back and forth since then and haven't been able to get the resolution choices again.

RE: Screen resolution

Posted: Sat Feb 01, 2014 4:42 pm
by TigerTC
ORIGINAL: Lieste

The comment was meant for Miguel, really. It is an issue that has been addressed before, but not successfully in all cases (often I think a failure to actually perform some of the requested steps, but there might be some issues that aren't currently trapped).

Part of the problem is that display issues at extremely high resolutions require a high resolution screen to test, and this may not be available in the active testing team (we are all volunteers).

First, ensure that for the purpose of running this application that Graphics card & Windows font scaling is for the standard DPI setting. Next try setting program compatibility to "disable font scaling at high DPI" (Right context menu>compatibility settings for CmdOps.exe)

If this isn't enough, then report back and we can try other steps (also look back at previous threads in this Tech forum ~ there might be other steps that I've forgotten/neglected).

On one previous occasion I think an offer to supply a custom exe for testing was made, but not AFAICT actually taken up.

I gather (though not with understanding all the intricacies) that this is caused by mixed support for older windows versions, XP, 7 and 8, and the solution would be trivial if only supporting 7 & 8.

I changed the Compatibility Mode as recommended and it did not solve the problem. I even set the Compatibility Mode for it to launch in 640 x 480 (ack!) and, despite the large and fuzzy display, I still had the font problem on the left side.

RE: Screen resolution

Posted: Sat Feb 01, 2014 5:06 pm
by TigerTC
Fixed, by going into Control Panel / Fonts /Font Size, and setting to 100%.

But running a 14 inch monitor 1920x1080 on 100% font size is pretty small and difficult to read in pretty much all other programs and uses, so this will take a lot of computer customization to fix.

RE: Screen resolution

Posted: Sun Feb 02, 2014 7:32 pm
by BletchleyGeek
ORIGINAL: BROJD

Fixed, by going into Control Panel / Fonts /Font Size, and setting to 100%.

But running a 14 inch monitor 1920x1080 on 100% font size is pretty small and difficult to read in pretty much all other programs and uses, so this will take a lot of computer customization to fix.

Indeed, it's a font-scaling issue (as in the user interface can't handle gracefully font DPI settings other than 100%).

We're in the process of moving on top of Windows newer API's for Command Ops 2, so we can finally handle fonts in a comprehensive way.