Steps to reproduce: Create lower resolution of high-res mesh with Multiresolution -> Reverse Switch back to high resolution Rotate/pan camera Looks like something is wonky when it tries showing the lower-res version during camera move. (Also, I’m getting a crash when trying to make a…

Ah this is bad. I tried with a simple mesh (sphere) but I couldn’t reproduce. Do you have a simple way to reproduce the bug? Otherwise you can simply send me the file at stephaneginier@gmail.com .

I can’t seem to reproduce with other models, either. Even ones created in the previous version. Looking at how the screwy model is structured, maybe something to do with the painted vertices? Is there a way to clear all vertex paint info? Some more information on the crashing: the crashing on rever…

It can’t be the painting since the reverse is working exclusively with the topology information (vertices and quads). I can easily reproduce the issue with your file so I’ll be able to fix it, thanks!

Awesome! Happy to help. :slight_smile:

I managed to fix the bug. Thanks for the file, nice model! The issue was that app was trying to render the lower resolution when it shouldn’t have to. Depending on the topology, sometimes I can’t reuse the lower resolution, and it was the case here. Instead of reverting to the old behaviour I ma…

Hey thanks! I had a lot of fun making it. Nomad is a dream to work with. It’s obvious you’ve put a lot of thought into the UI. And yeah, I figured it was a RAM issue. I’ve run into a couple of other similar crashes. How hard would it be to catch that kind of memory error and fail the operation inst…

I don’t think you will find many softwares that gracefully recovers from out-of-memory issue. It’s a bit of a pain. Also the “free/available” memory is typically not something that you can trust blindly. On iOS it seems relatively reliable but on Android I couldn’t get the information clearly.

1.34 should be live with the fix! [image] Nomad Change Log Lounge 1.34 multires: fix lower resolution rotate-optimisation issue (after reverse) multires: fix glb corrupt saving when a lower level of a multires is selected render: smoother wireframe and model edge shadow…

Oh nice! I don’t suppose it’ll fix this model that blew up after a crash? :weary: [image] /edit: it did not, but I’m guessing this is the other multires bug that got fixed. Ah well. I want that happy with it anyway. Good excuse to start it over.

Yep corrupted files are lost for good. Actually that’s the reason why I made this quick release, broken saves is the worst thing that can happen.

Bug with multiresolution optimization

Bug Report

stephomi January 9, 2021, 1:53am 9

1.34 should be live with the fix!

Topic		Replies	Views
Multi res reverse glitch Bug Report nomadsculpt	2	395	December 8, 2022
Loosing Reversed Multiresolution Levels Bug Report nomadsculpt	4	794	April 21, 2022
Multiresolution crash Bug Report	5	561	November 11, 2020
Multiresolution not saved Bug Report	3	470	September 17, 2021
Subdivisions get lost after crashing/restart Feature Request	2	427	May 14, 2022

Bug with multiresolution optimization

Related topics