Recommended Posts

People having problems with DirectWrite, do you have ATI cards?

It seems Nvidia and ATI cards render the text differently, Nvidia cards have light sub-pixel colours while ATI cards have very strong colours, to the point where you get a very noticeable rainbow effect with a string of text like "llllllllllllllllllllllll"

Edit: And when you're taking screenshots of it, use PNG as the file format, JPEG destroys the colour info on purpose (The human eye can't see it very well, so no point trying hard to save it) unless you change settings in the encoder.

I have problems with directwrite, and yes, I'm using an ATI card.

The colors are better in the latest nightly.

However, I don't see this as a D2D/DirectWrite/Microsoft/GPU problem, because of one fact, and that is that text looks great on IE9 which uses it aswell.

People having problems with DirectWrite, do you have ATI cards?

It seems Nvidia and ATI cards render the text differently, Nvidia cards have light sub-pixel colours while ATI cards have very strong colours, to the point where you get a very noticeable rainbow effect with a string of text like "llllllllllllllllllllllll"

Edit: And when you're taking screenshots of it, use PNG as the file format, JPEG destroys the colour info on purpose (The human eye can't see it very well, so no point trying hard to save it) unless you change settings in the encoder.

I don't see any colors or rainbow effect on my card, to mee the rendering is just way too blurry, especially with the lllllll example you posted. A lot of letters just look blurry/washed out compared to cleartype.

post-159052-0-77855500-1295547585.png

You notice in cleartype the rendering looks very consistent, in Directwrite some letters look alright and others look very faint and blurry.

I don't see any colors or rainbow effect on my card, to mee the rendering is just way too blurry, especially with the lllllll example you posted. A lot of letters just look blurry/washed out compared to cleartype.

post-159052-0-77855500-1295547585.png

You notice in cleartype the rendering looks very consistent, in Directwrite some letters look alright and others look very faint and blurry.

Yeah that's what I see too. Strange thing is, I don't have that issue at work on the same version of FF4 (which is running on XP). Could be a monitor/cleartype thing. :s

I don't see any colors or rainbow effect on my card, to mee the rendering is just way too blurry, especially with the lllllll example you posted. A lot of letters just look blurry/washed out compared to cleartype.

...

You notice in cleartype the rendering looks very consistent, in Directwrite some letters look alright and others look very faint and blurry.

Yeah, that's the sub-pixel positioning causing that. GDI is designed to render text to CRT monitors (it's from Windows 3), while DirectWrite is designed for LCD displays and as such doesn't have a lot of the limitations GDI does (ClearType is bolted onto GDI, while DW is designed around it)

You get more accurate glyph rendering, more accurate inter-character spacing, and more accurate line lengths than you would with GDI (and it's much faster too). Compare this under GDI to DirectWrite, GDI simply can't scale and place the glyphs properly due to it's limitations.

Yeah, that's the sub-pixel positioning causing that. GDI is designed to render text to CRT monitors (it's from Windows 3), while DirectWrite is designed for LCD displays and as such doesn't have a lot of the limitations GDI does (ClearType is bolted onto GDI, while DW is designed around it)

You get more accurate glyph rendering, more accurate inter-character spacing, and more accurate line lengths than you would with GDI (and it's much faster too). Compare this under GDI to DirectWrite, GDI simply can't scale and place the glyphs properly due to it's limitations.

Well I have and lcd and think it looks like crap, it may "technically" be better but most people seem to share my opinion that it looks pretty awful lol.

It does look better at large font sizes, but at normal font sizes it is pretty bad :/

Compare this under GDI to DirectWrite, GDI simply can't scale and place the glyphs properly due to it's limitations.

The rainbow effect is quite visible for Segoe UI:

font-style%2C%20font-weight%20%26%20font-stretch%20tester%20-%20Mozilla%20Firefox%204.0%20Beta%209.png

And here's an example from my laptop with Intel HD Graphics (also switched to the onboard discrete GeForce GT 335m and got almost identical results):

font-style%2C%20font-weight%20%26%20font-stretch%20tester%20-%20Mozilla%20Firefox%204.0%20Beta%209.png

Clearly there's a contrast difference.

edit: The previous screenshot was captured on a machine without SP1, while this one does have SP1. Not sure if there might be a fix inside the service pack with regards to DirectWrite rendering.

ugh, confusing.

I've always gotten the results shown in your second screenshot (pre-SP1 with an 8600GT), and I've only ever seen the results from the first screenshot on ATI cards (even a few Mozilla devs have the same issue). I wonder if it's due to the ClearType settings Windows use.

That's because xp does not support directwrite

Well I guess that'd be why then :p

The ClearType settings also has an effect on it. I've tuned CT and restarted programs, and have gotten worse/better results depending on how it's tuned.

I wonder if the people having the problem are the ones that have used the ClearType tuner in Win7?

I should point out that |||||||||||||||||||||||||||||| is not normal text. I don't think it's surprising that DirectWrite isn't designed around displaying those perfectly.

In the previous comparison, iiiiiiiiiiiiiiiiiiiiiiiii was displayed next to it ... and it looked fine. It's still an unlikely collection of characters, but more realistic at least.

Of course it's not ideal that |||||||| can look odd, but it's not the end of the world.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!