hard crash when activating the top-level component

hard crash when activating the top-level component

Anonymous
Not applicable
656 Views
4 Replies
Message 1 of 5

hard crash when activating the top-level component

Anonymous
Not applicable

Hey all, not sure if this is related to a recent update but I'm getting a pretty consitent crash whenever I re-activate the top-level component in my design. Doesn't seem to be related to any other action, but happens every time I do it.

 

The crash doesn't create a crash report either so it probably isn't being reported to anyone. I'd be happy to share the design I'm working with if someone is trying to debug. Thanks

0 Likes
Accepted solutions (1)
657 Views
4 Replies
Replies (4)
Message 2 of 5

innovatenate
Autodesk Support
Autodesk Support

Can you post a public link of the design here or share it with me via a private message (through the forum)? I'll be happy to see if I can reproduce/resolve on my end.

 

Thank you in advance!

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 3 of 5

Anonymous
Not applicable
Just sent you a PM with the link
0 Likes
Message 4 of 5

innovatenate
Autodesk Support
Autodesk Support
Accepted solution

Thanks for the file. Upon uploading the Fusion 360 archive file, I found that the top commponent was already activated. I tested activating various components in the design and the root component, but was unable to reporoduce the issue.

 

 

Since it doesn't generate a report, I'm thinking the isue may be related to graphics. It sounds similar to the issue being reported in this forum post.

http://forums.autodesk.com/t5/design-validate-document/creating-new-component-causes-crash/m-p/62120...

 

Could you test the suggestion to creating a diagnostic log file (save those) and then change the graphics driver options? If this resolves the issue, it may be helpful to get a copy of the diagnostic log files for further investigation.

 

I hope that helps!

 

Thanks,

 

 

 

 

 




Nathan Chandler
Principal Specialist
Message 5 of 5

Anonymous
Not applicable

Hey Nathan, thanks again for helping out with this. I've been away from my computer again for a couple days so have only been able to try this out today.

 

Switching to Direct X 9 does in fact fix the problem, switching to Direct X 11 does not. For now I'll just leave it at 9. I'll send you a PM with the log files

0 Likes