🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

Inspire Freezes When Loading a Save File Loading, File Stuck at 90% Loading

User: "Edo"
Altair Community Member
Updated by Edo

I have a save file of a print I am trying to make and it has been a great first experience using Altair transitioning from Fusion360.

However my file now suddenly doesn't want to load, it always gets stuck at 90% roughly. Is this a known issue? Is there a fix? It feels like loading older versions of the file still cause the same issue. I would love some help otherwise the work will be lost!

image
See loading stuck progress here ^

Find more posts tagged with

Sort by:
1 - 3 of 31
    User: "Edo"
    Altair Community Member
    OP
    Updated by Edo

    Guess I will consider my file and work lost.... Next time i will keep model and simulation separate

    User: "GTT Adam"
    Altair Employee
    Accepted Answer
    Updated by GTT Adam

    Guess I will consider my file and work lost.... Next time i will keep model and simulation separate

    Hi Edo,

    Unfortunately, your model freezes for me too.

    image

    I've tried to open your model from multiple different versions of Inspire with the same result.

    If we open the Python Window (View >> Python Window) we get a little more info, shown below:

    image

    For some reason, it is calling for the end of file. Since we can't open the model up and the input file is binary, it's not possible to tell what has corrupted this file. In general, special characters and file paths on servers could cause these issues, so try to avoid that in the event they were present in your model.

     

    Thanks,

    Adam Reid

    User: "Edo"
    Altair Community Member
    OP
    Updated by Edo

    Hi Edo,

    Unfortunately, your model freezes for me too.

    image

    I've tried to open your model from multiple different versions of Inspire with the same result.

    If we open the Python Window (View >> Python Window) we get a little more info, shown below:

    image

    For some reason, it is calling for the end of file. Since we can't open the model up and the input file is binary, it's not possible to tell what has corrupted this file. In general, special characters and file paths on servers could cause these issues, so try to avoid that in the event they were present in your model.

     

    Thanks,

    Adam Reid

    Thank you Adam for trying to rescue it. I will task to avoid doing any such thing in the future, weirdly all I did was begin to add loads to the model and then this happened.

    I have redone the model fortunately as i had noted down all the dimensions and it wasn't a huge bother (this time), but it was surprising.

    Thanks again for trying to help.