Minor bug in Briefing Menu with enable Anti-aliasing in Hitman Codename 47

Hiya, the Anti Aliasing works perfect in Hitman Codename 47, however I noticed some minor bug, specifically in Briefing Menu when Anti-Aliasing is enabled.

dxwrapper-hitman.log

Any thoughts ?

P.S. I use Nemesis2000's Widescreen Fix , in script folder I've edited h47.ini to set it to 1360x768 resolution, since my ATI Catalyst Control does the scaling to fit my monitor if it helps.
Also I have enabled these options only:
[Plugins]
LoadPlugins = 1
LoadFromScriptsOnly = 1

[Compatibility]
Dd7to9 = 1

[d3d9]
AnisotropicFiltering = 16
AntiAliasing = 8
And no, AnisotropicFiltering is not the cause of the bug, only Anti Aliasing option.

[elishacloud]

This is a seam in the game because the vertices are too close to the edge of the pixel. It's not a bug in dxwrapper. I may be able to add a feature to change the center location of the vertex and it may fix these seams while possibly causing seams in other locations.

Another option could be to disable anti-aliasing on these textures, but that would be custom work for this game and I want to prevent custom work as much as possible.

BTW: other games that have this type of issue include:

• Knight Rider 2
• Star Trek: Armada

A concise explanation

Anti-aliasing determines a pixel's color based on how much of that pixel is covered by a polygon rather than treating it as simply on or off. When an edge passes extremely close to a pixel boundary, only some of the anti-aliasing sample points may be covered. Older games often position adjacent polygons so close to these boundaries that tiny rounding differences leave some samples uncovered, causing those pixels to be blended with the background and producing visible seams between polygons.

An intuitive analogy

Imagine painting a floor with a roller:

• No AA: If the roller touches a tile at all, the entire tile is painted.
• AA enabled: The tile is divided into several smaller squares, and only the squares the roller fully touches get painted.

If two painters are painting from opposite sides and each stops just a fraction of a millimeter short of the other, the tiny unpainted gap becomes visible. MSAA reveals those tiny gaps because it measures partial coverage instead of assuming every touched pixel is completely filled.

More detailed explanation

Without anti-aliasing, a pixel is usually treated as either fully covered or not covered at all. With multisample anti-aliasing (MSAA), however, each pixel contains multiple sample points. The GPU determines how many of those sample points are inside the triangle.

For example:

No Anti-Aliasing (1 sample)

+-------+
|       |
|   /   |
|  /    |
| /     |
+-------+

The sample is inside the triangle.
Result: 100% color.

With 4x MSAA:

+-------+
| x   x |
|   /   |
| x/  x |
| /     |
+-------+

x = sample locations

If the edge passes through the pixel:

• 4/4 samples covered → 100% color
• 3/4 samples covered → 75% color
• 2/4 samples covered → 50% color
• 1/4 samples covered → 25% color

So the pixel is blended with the background according to its coverage.

Why seams appear

Many older games were written before MSAA was common and assume that adjacent polygons share an edge perfectly. In practice, floating-point rounding or slightly different vertex calculations can leave the edges only microscopically different.

Without AA:

Polygon A | Polygon B

████████████████
████████████████

Each pixel is simply considered inside one polygon or the other, so the join looks solid.

With AA:

Polygon A | Polygon B

██████▒▒████████
██████▒▒████████

If the edge falls very close to a pixel boundary, one polygon may cover only some of the MSAA sample locations while the neighboring polygon misses those same samples due to tiny numerical differences. The result is a partially covered pixel that is blended with the background, producing a visible light or dark seam.

Thanks for detail explanation, to be fair it's small issue with MSAA, comparing to when using Dgvoodoo2 which straight up shows garbled text and corrupted glyphs on UI text, so overall it's small price to pay for it when using Dxwrapper, and besides I don't like using Reshade myself personally to remedy Anti-aliasing situation, but nice to have additional options, thanks for good work.