Condition ' !area_in && !E ' is true. - When saving or closing models

realmsandruins

Does the issue occur in the editor or during gameplay?
Editor

If it's a gameplay issue, please specify which movement system and camera type you're using (free movement vs. grid movement, third-person vs. first-person) or N/A if not applicable:
N/A - editor

Briefly describe the issue you're experiencing:
The following error shows up when saving models. This didn't happen before

Are there any errors in the in-game debug console or external console window?

Provide the steps necessary to reproduce the issue:
I don't know how to reproduce it, but I saved one of the models in a barebones project and it still happens. It seems to be less spammy when you delete frames and goes away if all animations are removed. Seems to be animation related?

Provide a download link to the bare bones project (strongly recommended if it's an in-game issue, since this helps significantly when attempting to reproduce it; the report will also be given more priority in this case):

my-game.7z

754kB

Slayer

Just to add to this report.

Bonebrah sent me one of his models and I spent the last hour trying a whole manner of things to see what could be causing the error. (I get it too on my end).

At first, I thought it was animation related, but that was a red herring in the end...changing animation names doesn't require the mesh to be rebuilt and thats where the issue comes in....when voxels are added/changed

In the end, two key discoveries were made I think:

1) I deleted all voxels and frames (empty mesh) and saved the model...still get the same error

and

2) bonebrah made a new model and copied the voxels/frames over and that one saves without issue.
Trying to do Save As... just recreated the same issue in the new file.

Both would lead me to believe something has gone awry with the core .scn file somewhere/somehow

Now it would appear the file is not corrupt or bad as there's no major impact to the game...model still loads fine.

But just unsure what could be causing this issue with the file itself.
Bonebrah is understandly not too keen on opening 100's of models, to create new ones and copy frame by frame over lol

The issue doesnt seem to be impacting things though thankfully, but just wondering if there's something you can spot that might be causing it with this file (attached), or at least confirm if the issue is something to be concerned about.