# Improving Markup Quality in 2D Views

**URL:** <https://discourse.slicer.org/t/improving-markup-quality-in-2d-views/36700>\
**Category:** Development\
**Created:** [June 11, 2024, 2:42pm UTC](https://discourse.slicer.org/t/improving-markup-quality-in-2d-views/36700 "2024-06-11T14:42:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 11, 2024, 4:36pm UTC](https://discourse.slicer.org/t/improving-markup-quality-in-2d-views/36700/2 "2024-06-11T16:36:41Z")

</div>

You can enable interpolation, for example MSAA or FXAA.

MSAA interpolation can be enabled in application settings / Views / Multi-sampling (MSAA) → 4x (or higher for smoother results with higher computation cost).

FXAA can be enabled with a short Python code snippet. See example in the image below: left with FXAA, right without interpolation.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/5/0/508f7a50adcafc60be2b32ab9e6c02db3ec7f16b.jpeg)

See in this topic how to enable FXAA and some more information on interpolation:

> [@Antialiasing in in slice (MPR) views](https://discourse.slicer.org/t/antialiasing-in-in-slice-mpr-views/21140/4):
>
> Multi-sampling is the true antialiasing method, but that would mess with the Z buffer, and therefore with hardware-accelerated picking that is used for markup nodes label display and control point manipulation, compositing volume rendering and surface rendering, etc. Also as @pieper mentioned there seem to be some some issues with it in recent VTK and Qt versions (for example, I don’t think the MSAA setting has any effect right now on Windows). Alternatively, you can do screen-space antialiasin…

---

_[View the full topic](https://discourse.slicer.org/t/improving-markup-quality-in-2d-views/36700)._