Skip to content

Commit 0f3723c

Browse files
Terminology fix.
1 parent 42d709a commit 0f3723c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/remote-rendering/overview/features/z-fighting-mitigation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom:
1212

1313
# Z-fighting mitigation
1414

15-
When two surfaces overlap, it isn't clear which one should be rendered on top of the other. The result even varies per pixel, resulting in camera view-dependent artifacts. When the camera or the mesh moves, these patterns flicker noticeably. This artifact is called *z-fighting*. For AR and VR applications, the problem is intensified because head-mounted devices naturally always move. To prevent viewer discomfort, Azure Remote Rendering offers z-fighting mitigation functionality.
15+
When two surfaces overlap, it isn't clear which one should be rendered on top of the other. The result even varies per pixel, resulting in camera view-dependent artifacts. When the camera or the mesh moves, these patterns flicker noticeably. This artifact is called *z-fighting*. For augmented reality and virtual reality applications, the problem is intensified because head-mounted devices naturally always move. To prevent viewer discomfort, Azure Remote Rendering offers z-fighting mitigation functionality.
1616

1717
## Z-fighting mitigation modes
1818

0 commit comments

Comments
 (0)