CentBrowser Forum - directwrite issues with 4.2.9.152

Pages: 1 2 3 4

(04-12-2020, 05:19 PM)ChromiumIQ Wrote: [ -> ]Assessment of fonts is subjective. The user adjusts the fonts to suit their needs. Do not want to configure, use what you have.

Sure. But there is something that has changed between versions 4.0.9.112 and 4.1.7.182, and it's obvious on my system.

Ideally i would like cent browser devs to either make it work like before, or to tell me what do i need to do. It's fine if it's involves flags, extensions etc.
But changing system wide settings, like clear type and the like will not work for me, i like my system fonts without any "improvements" and smoothing.

(04-12-2020, 06:15 PM)PavelX Wrote: [ -> ]
Sure. But there is something that has changed between versions 4.0.9.112 and 4.1.7.182, and it's obvious on my system.

Ideally i would like cent browser devs to either make it work like before, or to tell me what do i need to do. It's fine if it's involves flags, extensions etc.
But changing system wide settings, like clear type and the like will not work for me, i like my system fonts without any "improvements" and smoothing.

Ask the developer directly through the Offers and Support browser.

Chrome has no Cent functionality, thin fonts. I don 't see the point of using Chrome for myself.

(04-11-2020, 05:16 PM)PavelX Wrote: [ -> ]This didn't help much, font still looks terrible on some sites.

Nope, didn't see any difference at all.

"Smooth edges of screen fonts" is the lesser evil so far. But i'm not so happy about the result, and will gladly try something else if you guys have more ideas.

You might want to try "Disabling" chrome://flags/#font-src-local-matching since that worked for me. I am running Win 10 64bit and was experiencing issues with DirectWrite font rendering on various websites. It worked fine in the previous versions of Cent, until now. So I "disabled" it instead of "enabling" it, and it worked perfect! Hope it helps your situation.

Thanks to Barry's advice.
Additionally, you can try appending this command line in "Other settings"->"Startup command line":
--enable-features=LegacyWindowsDWriteFontFallback,FontSrcLocalMatching

Thank you both for the suggestions, unfortunately i don't see any difference changing this flag and adding this command line.

I have exactly the same problem on my second machine as well. It's probably because of the same settings, like disabled ClearType maybe?
It's also Win10 x64.

Is --disable-directwrite-for-ui still working? I have no effect (4.2.9.152).

(04-14-2020, 02:35 PM)Jigsaff Wrote: [ -> ]Is --disable-directwrite-for-ui still working? I have no effect (4.2.9.152).

No, only --disable-direct-write is supported.
It disables DirectWrite for both UI and web page.

(04-14-2020, 06:57 AM)PavelX Wrote: [ -> ]Thank you both for the suggestions, unfortunately i don't see any difference changing this flag and adding this command line.

I have exactly the same problem on my second machine as well. It's probably because of the same settings, like disabled ClearType maybe?
It's also Win10 x64.

Remove all other command line, try only appending this:
--disable-features=RendererCodeIntegrity

(04-14-2020, 04:45 PM)CentBrowser Wrote: [ -> ]Remove all other command line, try only appending this:
--disable-features=RendererCodeIntegrity

Again, it looks the same.

[attachment=796]

(04-15-2020, 06:40 AM)PavelX Wrote: [ -> ]Again, it looks the same.

The result of my actions is a good font.
Вам советуют, а вы как капризная особа, нос воротите.

Pages: 1 2 3 4