It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I would like to upload a screenshot as well, but no matter if PNG or JPG, in both cases it says wrong file format. Also with PNG it said the file was too large (max. 500kb) when it was only 495kb. And when I convert the pic to gif the quality is way too bad.

Anyways, after the last update all text (and some images) constantly get blurry. I use Windows 10 and tried disabling dpi scaling, but the option isn't under compatibility anymore. Instead there is "Override high DPI scaling behavior. Scaling performed by:" and there you can choose between application, system and system (enhanced), though none of those options work in this case, so it might be another problem. Also I don't let Windows upscale pixels, since I only use 1920x1080 as native resolution.

Pls fix this, otherwise I might get eye cancer when using GOG Galaxy.
avatar
Onikobe: I would like to upload a screenshot as well, but no matter if PNG or JPG, in both cases it says wrong file format.
It's png and jpg, not PNG and JPG. Rename the file's extension and make it lower case.

Hope this helps

edit: The issue was reported with some specific if you want to follow up there:

https://www.gog.com/forum/general/gog_galaxy_official_discussion_thread/post1274
Post edited February 04, 2018 by drmike
avatar
Onikobe: I would like to upload a screenshot as well, but no matter if PNG or JPG, in both cases it says wrong file format.
avatar
drmike: It's png and jpg, not PNG and JPG. Rename the file's extension and make it lower case.

Hope this helps
Thanks for this advice. Would have been nice though if this info were shown when you click attach. I presume only a minority knows that Linux' file system is case-sensitive. I just saved it in the Windows snipping tool and it automatically writes the extension in upper case. Anyways, attached to this post is a screenshot i made showing the effect of the display bug.

What's strange though is that sometimes part of the window is sharp, (not only) depending on where the mouse is. If I continously scroll up and down, everthing is displayed sharply, if I stop scrolling part of the window is blurred out.

It seems to be some kind of focus thing. If I click the first paragraph of this text, the first paragraph from "quote_17" to "/quote" is displayed sharp and the lower paragraph is blurred out and vice versa.
Attachments:
blurry.jpg (115 Kb)
I noticed the new versions of Galaxy started using the system's DPI scaling. So this might be caused by a DPI compatibility setting.

Try the following:

1. Right-click your Galaxy shortcut (or GalaxyClient.exe) and select Properties.
2. Open the Compatibility tab.
3. Un-check "Override high DPI scaling behavior."
4. Restart Galaxy if it's running.
Post edited February 04, 2018 by MikeMaximus
avatar
MikeMaximus: I noticed the new versions of Galaxy started using the system's DPI scaling. So this might be caused by a DPI compatibility setting.

Try the following:

1. Right-click your Galaxy shortcut (or GalaxyClient.exe) and select Properties.
2. Open the Compatibility tab.
3. Un-check "Override high DPI scaling behavior."
4. Restart Galaxy if it's running.
Thanks a lot but its not helping. It seems as there is some layer over it so when you select one part, that foggy layer just moves to other parts. Its annoying as hell
I think this is related to Chromium version update. I've seen the very same blurry font problem in Vivaldi browser. See forum.vivaldi.net/topic/10218/vivaldi-blurry-text?page=1 for some discussion on the matter. With Vivaldi the problem started with update to Chromium 52 and Galaxy updated the Chromium version in the last update just as well.
It seems that for Vivaldi the fix suggested in productforums.google.com/d/msg/chrome/pXTKANTZE2I/rEBWi-kYDwAJ - going to "flags" setting page of Chromium and setting FontCache scaling to "Disabled" - helped. I've only applied the fix recently, so the problem might come back again - I'm not sure.
avatar
masterring: snip
Ah ok. Sorry, I should have read the rest of the thread closer. I didn't notice Onikobe already talked about the DPI settings and that it isn't the problem. I see you already reported it on the bug tracker so hopefully they'll get it worked out.
I experienced the same issue in Geforce Experience, but was able to fix it by setting "Override high DPI scaling behaviour. Scaling performed by:" to "Application", but as mentioned earlier in this thread, this didn't work for GOG Galaxy.
So, due to another problem I experienced I decided to reinstall older Nvidia drivers (388.71) and while trying out some gaming related stuff I discovered that the GOG Galaxy didn't displayed blurred text/images anymore.
It's a known problem with CEF (Chromium Embedded Framework components) used by many WEB based tools like GeForce Experience, GOG, Chrome browser itself etc.

Unfortunately Nvidia is ignoring this issue which seems to happen only with some GPUs and latest drivers.

Are you sure 388.71 downgrade solved the issue (reboot your PC and start GOG Galaxy again after rolling back the driver)?
Post edited February 13, 2018 by hexaae
Please, report Nvidia issues here https://forums.geforce.com/default/topic/1037275/geforce-drivers/cef-chromium-embedded-framework-incompatibility-after-388-xx/
The more we are, the more chances we have Nvidia will look into this bug.
Can you please post detailed display/panel model you have? I'm in touch with Nvidia guys and they need some specs...
You can use free HWiNFO for more details about your installed hardware.
I fixed it by disabling FXAA on my GOG galaxy entry in the NVidia 3D settings panel.
I keep hoping the next graphics driver update will fix this issue in GOG Galaxy. I'm beginning to believe the problem is with the application and not the driver.
avatar
paladin181: I fixed it by disabling FXAA on my GOG galaxy entry in the NVidia 3D settings panel.
I gave this setting a try. I think it may have helped. Thanks.