SHEET METAL error - Fusion

[xbodis]

Hello everyone,

I’m having a problem with the Sheet Metal Flange feature, specifically with the Two Offsets option. I didn’t have this issue before the latest update, but after updating I’m getting this error every time.

I enter all my inputs correctly, select OK, and the flange is created. However, when I try to edit the flange again, Fusion shows an error. Edge 2 and Edge 4 always lose their offset values after reopening the feature. I have to reselect the full edge, re-enter both offset values, and confirm again. When I reopen the flange, the same error appears.

Please help.

Thanks!

This post has been edited due to: @heather_tracy added the product to the title to help more community members find this topic.

[Warmingup1953]

Share your Fusion file?

[johnsonshiue]

Hi! Either the neighboring Flanges are colliding or the Bend Relief or the Corner Relief setting is incompatible with the Flanges. Try changing the width option to narrow the Flange width, allowing more room for neighboring Flanges.

Please feel free to share the f3d file here or send it to me directly at johnson.shiue@autodesk.com. I would like to understand the failure better.

Many thanks!

[aaronzpaul]

Hi, I'm facing same issue, 

Fusion allows you to create a "Two Offset" flange with two or more edges but when you try to edit it, it shows the error message as shown in the screenshot.
What I noticed is when only one edge is selected this issue does not occur, add a second edge and the issue occurs.

Pic_1 Show the edges that are selected.
Pic_2 show the error message and the flanges are missing.

Tried with the built-in sheet metal rules - the issue persists.

The "Two sides" flange option does not have this issue.

Fusion version:  2605.1.39 x86_64

[johnsonshiue]

Hi! If possible, please share the f3d file here. It will help us understand the issue better.

Many thanks!

[aaronzpaul]

I have attached a test f3d file, that reproduces the issue.

[johnsonshiue]

Hi Aaron,

This is absolutely a bug. I will work with the project team to understand it better and see how we can resolve it asap.

Many thanks!

[johnsonshiue]

Hi Folks,

This is indeed a known issue and it has been fixed on an internal build targeting the next update.

Many thanks!

[xbodis]

Hello, 

Thanks for your repleys! 

But im still facing the same issue...here is my file so you can chceck it out.

[johnsonshiue]

Hi! This is the same issue unfortunately. It will be fixed in the coming update.

Many thanks!