# Loosing Reversed Multiresolution Levels

**URL:** <https://forum.nomadsculpt.com/t/loosing-reversed-multiresolution-levels/6579>\
**Category:** Bug Report\
**Tags:** nomadsculpt\
**Created:** [April 19, 2022, 8:47pm UTC](https://forum.nomadsculpt.com/t/loosing-reversed-multiresolution-levels/6579 "2022-04-19T20:47:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephomi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.nomadsculpt.com/stephomi/32/19583_2.png) [@stephomi](https://forum.nomadsculpt.com/u/stephomi)\
**Post date:** [April 20, 2022, 12:30am UTC](https://forum.nomadsculpt.com/t/loosing-reversed-multiresolution-levels/6579/2 "2022-04-20T00:30:51Z")

</div>

It doesn’t store the multiresolution to save memory, it’s done by design.

However Nomad tries to reverse the mesh if it has multiresolution at loading, but only for polycount \<400k (or maybe a different threshold).

If you the reverse fail, try to load the file again by enabling `keep topology at import` in the Settings.  
(in some case reverse can fail because Nomad merges some duplicate vertices or faces here and there).

---

_[View the full topic](https://forum.nomadsculpt.com/t/loosing-reversed-multiresolution-levels/6579)._