Summary

Title:Saving error
Category:Crash/Critical
Status:Fixed
Posted By:eloison ( Erwann Loison )
Date Created:30 October 2015

Problem

Description:

Hello again,

I'm not sure when and how this happens, it happened a few times on all builds so far, but I have no real clue of what is causing this or steps to reproduce. Attached is a capture of the error (it only happens when using lucid).

Steps to Reproduce:
 

Attached Files:
Image 1

This indicates that recorded data has been corrupted by something. If you ever track this down steps to reproduce would be super helpful.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

Everytime it happens I try to identify the problem but so far no luck. I don't give up tho :)

I think I narrowed it down, it happens when you paste lucid modifier as instanced AFTER it has already some recorded data simulated:

 

- Create a simple scene like a collision plane and two objects

- Assign one of the lucid properties to one of the object

- Run some simulation/test

- Copy lucid modifier and paste it as instanced on the second object

- Try to save: The error shows up.

 

So this is mostly a user error, although it would be better if it wasn't generating an error I suppose :) Trying to paste as instanced a modifer that already holds the recorded data of another object. If you simulate again and save, the error will not happen. If you do the previous steps without simulating before pasting as instanced, the error will not happen either.

 

Best regards

I will check it out, thank you for taking the time to narrow it down. It isn't a user error if you can put the system in this condition.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

No problem, my pleasure. By user error I mean that obviously now that I know what is causing this, it's not surprising it might generate an error if not handled specifically :)

Fixed in next build

Marsel Khadiyev (Software Developer, EPHERE Inc.)

Great, thanks