[XVM is editing WoT.exe's Compatibility (Windows)]

I just confirmed it's not because of xvm (now with the DPI flag off).
I am annoyed because the contour icons in the playerPanels are not to proper size and thus hardly readable. (and that's without xvm as well)

Judging by windows explorer manual scaling - they are 2 clicks smaller than "Large Icons" or I'd assume 80% of normal size.

Anyhow I'd consider this thread closed, thanks again for your assistance :)

[XVM is editing WoT.exe's Compatibility (Windows)]

Unfortunately you are right...
Thank you for your time. I was just following on a plausible cause.

Back to the drawing board.

[XVM is editing WoT.exe's Compatibility (Windows)]

You are correct - win7, 24'' 1920x1080 60hz monitor

UI scaling is either auto or x1. I've played around with preferences.xml but nothing yields better results than x1 (tried a range from 0.9 to 1.33)

 

1. 100% 

2. Attached (64 bit, it was the larger of the two)

3. I assume the DPI-Aware flag is the Compatibility setting. And yes 1080p is available (and selected).

 

 

 

 

 

 

[XVM is editing WoT.exe's Compatibility (Windows)]

So this is a problem I originally posted in Aslain's forums (because I thought it's because of the modpack).
After some investigation there was a conclusion that XVM is actually causing the underlying problem.

 

The problem:
Text is not displayed correctly and is hardly readable.

Examples: Ingame  , How it actually looks
How it shoud look

 

Now a user there suggested that the Compatibility for WorldOfTanks.exe is set with the "Disable display scaling on high DPI settings". And indeed it was.

However, whenever I remove it and start the game, it was reappearing. And that only happened when there were mods installed.
So with the method of exclusion I singled XVM as the culprit.

 

Video proof (2:02 min)

(Explanation of timeline in the video description, if needed)

 

Attached python and xvm logs from the video.

 

Problem appeared with patch 0.9.20.1.1 (Halloween patch)

 

P.S. If it's not obvious, I am looking into how to stop that behaviour so I can have the text in the client displayed properly.

 

 

python.log

xvm.log