insane amount of crashes with fillet and thicken command

[cekuhnen]

push n pull a feature and thicken the shell after the ouline is rounded results in permantent crashes

Fusion works for minutes and then says bye bye

sounds to me that there is a bug here because I can reproduce it over and over again.

here is the file: http://a360.co/1DSBDWg

[cekuhnen]

I am actually pretty satisfied with Fusion for solid modeling.
Some of the tools lack details like rails have no G1 or G2 ability and such.
And I think in the up-coming updates those functions will be improved.

I personaly the more I work with those solid modelers start not to be very convinced of them anymore. Sure the modeling is good. but the process and time it takes is painful and I think slow.

I am much faster in Alias or SolidThinking.

My dream would be to have their 3d sketch and surfacing abilities in something like Fusion mixed with what Fusion currently offers.

That would be a truly hybrid and improved workflow and toolset.

[Anonymous]

Hi Claas, Even though I did not report this, you are right. I had seen these crashes over and over again. It also crashed sometimes when trying to move a group of selected components into a newly created "Main Component". It is almost an instant crash. But there is a catch on this, this component moving crash only happened to editing old files there were produced before the big move to WIP. I never reported this and I do not intend to pursue this. But I failed to edit an older file made before the WIP movement which is quite important. I really hate the idea of not able to move a group of components formed by Bodies and move into a Main Component. I could not share this file because it belongs to my client's project. Most of the files in problems could not be shared. I do hope the team catches all these but they had already made lots of improvement within a short time. I like the program of course!

[jeff_strater]

we are investigating this problem.  It appears to be specific to this model, and not a more general problem.

We don't yet have a solution for this, but we will continue to pursue one.

Thanks for sharing the model, it helps a lot.

Jeff Strater (Fusion development)

[cekuhnen]

You are welcome Jeff. Hope you will find that little code bug 😉

[Phil.E]

Thanks for posting this.

I just want to add a little comment and request:

For those of you who wish to help with Fusion quality, if you can repeat a crash we can fix the crash. It's that simple. So if you find that a particular workflow, or model, or anything crashes Fusion and you think it will repeat, please post the model or send me an email. This is the most efficient way to get these problems addressed when you find them. Many of you do this, and it's appreciated immensely. I'd like to encourage anyone else to do the same.

And of course, my usual reminder, pardon me if you've seen this before. if you get a crash, fill out and send the form please.

[cekuhnen]

Not sure if it is possible but could this form include a Send crashed Fusion file as well?

[Phil.E]

That's not a bad idea. Or just the link to the data, via check box so it's voluntary.

One limitation currently is the CER form is used by all products. We'd need to craft our own.

[cekuhnen]

plus it would need to create a snapshot of the file with the last work step done before the crash.

[Phil.E]

That is what CER reports contain, among many things - a list of the last 30 or so commands.

When combined with a good description (provided by the user, something other than    ) the command list can be very helpful. I've solved many crashes by simply reading the user comments, looking at their last couple commands, and trying on my own to reproduce it.

This is why we ask kindly for good CER reports. It's your way to help us help other users and yourself. Thanks Claas, you do a great job of this!

[cekuhnen]

Thanks - besides this bug/crash there wasnt much to report on lately. Fusion got pretty stable! 😉

[San_Escobar]

I haven't experience the same issue crashes while fillet things, but here what molesting me... 

Playing nice with Fusion, I try to change Appearance, right click > appearances > Plastic - Opaque - Yellow Matte, Drag material to the part and boo ya! crash!

Also, I notice that before when Fusion rarely chashed, it used to Autosave, so when I restart the software it would carry on from last touch.
but now just shut down and that is it. No even sorry message!

IMO, it is important to have different appearance, as in my case I render things on VRED and different colours make my life easy.

Is there any way FUSION Team could make the update, something optional???

Cheers! 

[Phil.E]

This is a graphics crash, they provide no CER or backup file.

Can you check your graphics diagnostic and copy/paste the results here?

Thanks!

[Phil.E]

[San_Escobar]

Hi Phil. 

Have I missunderstood you comment, it is an issue with Graphic Card? is it what you are saying?

Don't get me worng, but prior the latest (AUTOFORCED) update Fusion was running like charm. 

Thanks for your attention and here is my Diagnostic for your review.


   
Cheers!

[Phil.E]

Thanks.

All updates are going to be mandatory, FYI.

I'm saying that the kind of crash you describe usually come from graphics, it's not the only possible cause.

Let's try to figure out if it's model, hardware, or software specific.

• When you drag any material onto the model does it crash, or only specific materials?
• Is it only a specific body or component? Can you drag the same material onto other bodies?
• Can you try it on another machine and get the same crash?

Can you try the same crash workflow when Ambient Occlusion and Antialiasing are turned off? Does it still crash.

Thanks,