Page 1 of 1

[RESOLVED] unit status unreadable

Posted: Fri May 13, 2016 4:08 pm
by nudn1k
Hi everyone,
the screenshot shows a example how the unit status looks after any scenario runs for some seconds. If the unit is not moving or turning (or command is paused) the status display does not change. The click spots are still there, just difficult to hit.

I have this issue since I installed Command on a new PC. The Hardware is new (Skylake, Asus Max. VIII Ranger, Samsung SSM), except the graphic card (GTX 560). OS is Win 10.

So far I tested Command Build 817+823 /Nvidia 364.72 and Command Build 825 /Nvidia 365.10.
Apart from this Command runs extremely well and fast.

Any help would be appreciated.


Image

RE: unit status unreadable

Posted: Fri May 13, 2016 4:35 pm
by mikkey
Hi nudnik, what is your DPI setting? If you have more than 125, so try change it to 100 or 125.
Or the problem may be your ASUS application, then it might help you this

RE: unit status unreadable

Posted: Fri May 13, 2016 4:49 pm
by nudn1k
Thanks mikkey!
That post did not show up in my search.

RE: unit status unreadable

Posted: Fri May 13, 2016 5:38 pm
by mikmykWS
Wonder if there is some rational reason Asus is adding this. Hmm. Must research.

Mike

RE: unit status unreadable

Posted: Sun May 15, 2016 6:27 am
by Vampir
Sonic Suite 2 is an application to use an integrated sound module Supreme FX 2015 which is mounted on the ASUS ROG motherboards.

RE: unit status unreadable

Posted: Sun May 15, 2016 7:26 am
by mikmykWS
Yes I got that far by why on earth is it messing with how our game (and other apps) render stuff.

Mike

RE: unit status unreadable

Posted: Sun May 22, 2016 3:35 pm
by Dimitris
IIRC this was an issue also with FPC-RS.

Maybe Asus hates MG [:)]