2D drawing update quite buggy.

[harry.doldersum]

Hi all,

Ran into an issue today, while doing some updates to models & then updating their production drawings afterwards.

When updating the 2D drawings, the application now either crashes completely or it trashes the updating 2D drawing after every 2nd drawing.

I would like to request you checking up on this, as this is becoming a tad annoying. 🙂

Thanks!

[krithika.sundararajan]

Hi harry.doldersum,

Sorry to hear that you're having trouble updating your drawings. In order to help us investigate this, could you share your problematic drawing with us?

You can export the drawing as .f3z and email it to: krithika dot sundararajan at autodesk dot com.

Steps for F3Z export are here.

Thanks,

Krithika

[harry.doldersum]

Hi @krithika.sundararajan,

It appears I need to export the 2D drawing with A360, as Fusion doesn't support that itself. I've submitted the file & will receive a download link, once it's ready.

Mind you, this would go to the same email address as the one that's giving the authentification issue - so, I'm hoping it will actually arrive. 🙂

On a side note, maybe I should mention that this set of 21 drawings were all experiencing the same issue yesterday. I finally worked through them by shutting Fusion down after each successful update: with a "freshly" started Fusion, the error doesn't occur - only when doing more than 1.

The issue in itself is new, though - I didn't experience this prior. Only after the last update to Fusion. These drawings themselves have been updated in a similar manner several times in an earlier stage, as they are in a development phase & we're going through small changes & tweaks to improve the product. During the earlier changes to these models & subsequent updating of the 2D drawings, this issue didn't occur. So, it *seems* to be related to the last update...

But I just add this detail for your information - I'll forward the .f3z version of the drawing as soon as I have it.

Thanks for looking into it, I appreciate your support. 🙂

Cheers,

Harry D.

[mbostonsprint]

I just recently started using the drafting capabilities of Fusion, and I can also note that it seems much more crash-prone when exercising the drawing package. I have run about a dozen drawings of relatively simple parts, all from components of the model, and I had (3) crash episodes yesterday during a day of making 5 or 6 drawings and moving back and forth between a complex assembly model and the components/drawings files. I can't correlate this crash behavior as well to the drawing activity as the initial post in this thread, but it seems associated in some way.

I can also note that Fusion doesn't seem to like sitting idle with a model open for 2 or 3 hours. This is almost always good for a crash. I haven't yet explored what my system may be doing to contribute to this, but annoying nevertheless.

[cmiller66]

Hi mbostonsprint,

Sorry to hear you are encountering these crashes.  What OS are you on?  When you crash are you being prompted to send in a Customer Error Report (CER)?  Can you please send them in then reply here with the CER_ numbers so I can find it in the database?  Those details should help us narrow down what is causing the problem.

Thanks,
Chris

[harry.doldersum]

Unfortunately, 2D drawing updating is still a severe pain. When opening in 2D drawing for an update:

- Most dimensions need reassociation

- Reassociation then doesn't work.

- Centerlines need reassociation

- Reassociation then doesn't work

- Deleting & re-creating centerlines now ALSO doesn't work.

And the previous noted errors also still occur.

Could you please look into this?   And maybe solve it this time, please? This is not a new bug - it's still the same one & it's getting more serious. This is now stopping our progress.

[harry.doldersum]

What I also noticed, per today, is that activating "shaded" view to a section view, inserts the shaded image over the existing view ("visible edges", for example) in a - say - 60° rotated position. 

So, if the line image is positioned horizontally, the shaded image is rotated in a 60° clockwise position, whilst being distorted in dimensions. Restarting Fusion doesn't help, this time.

Please give some love to the 2D drawing module. Modelling is alright - but if you can't put a production drawing out, it all doesn't have much use...

Thanks.

Cheers,

Harry D.

[cmiller66]

Hi Harry,

Sorry to hear you are having these problems with drawings - none of these problems should be happening, it sounds like there are some bugs here we need to track down.

Are you on Mac or Windows?  Which version?  Would it be possible for you to share or send me one of the drawings you're seeing these issues with?

The centerline/dimension association problem after drawing update sounds like a bug.  The only instance where this would be expected is if you create a drawing of a body then convert that body to a component - it is then considered a new entity and the annotations need to be reassociated.

The rotated shading issue is definitely a bug - this *could* be due to some change in the named view, possibly a re-defined Home view, or has the view itself been rotated on the sheet?

If you can send a f3z or share the drawings I would be very interested in taking a look.  Please share or send to: christopher.miller@autodesk.com

Thanks,
Chris

[harry.doldersum]

Hi Chris,

Thanks for looking into this, it's appreciated. I'm on a Windows 10 system.

The view that is giving me a hard time on placing the centerline back, is a normal view. It's being updated after making a modification to the model: after that, the existing centerline had lost it. In then end, I decided to remove it & place a new one - but the view isn't responding to this command now.

I should, however, indicate that the view has 2 similar holes on top & bottom side of the view: the bottom one has no issues & it's centerline is ok - but can also be replaced without issues. The same hole, on the top side of the view, doesn't want to work with me. Can't get a centerline in there anymore.

In this view, there hasn't been a conversion from body to component. The fact that I don't know (yet) how to do that & what that's for, might have something to do with that. 🙂

The rotated shading is inserted in an angle on top of the unchanged original view. Should the original view be re-defined in some way, that this appears to be unvisible to me.

On providing you with the drawing - that's no problem, I'll try to send that. I'll need to refresh my RAM on how to do that, but I'll get to it. 

Thanks & cheers,

Harry D.

[harry.doldersum]

I'm not sure, what's causing this next issue, but here it is. (Different drawing, but for the same project). When updating a section view, the hash format spontaniously changes from single to double. That's new. It's also not wanted. Removing the view & re-creating the section view immediately responds with the double hash. What to do here?

Thanks. 🙂

[cmiller66]

Hi Harry,

Thanks for the screen capture.  What was the last edit done to the design before this update was done?  It looks like the section view is cutting through two overlapping components - so the double hatch is actually two overlapping single hatches, one from each component.  Here's a simple case of what I think the issue is:

In this case I have two separate bodies, but they are overlapping, so the section line is actually cutting through both and I'm seeing a double hatch in the section view.

To export the drawing (and design it references), click the "i" in the data panel then click Open Details on Web.  When A360 opens, click the Export (down arrow) icon in the upper right and select Fusion 360 Archive.  You will then get a link to download the file (f3z).  Please send to christopher.miller@autodesk.com, I'd like to take a look.

Thanks, 
Chris

[harry.doldersum]

Hi Chris,

I'll send you this drawing too, but I can already confirm that you are correct: the double hashed component has indeed been added a second time into the drawing. It now also appears with quantity "2" in the drawing's BOM, that's printed on the page.

The thing is - on the hardcopy that I made prior (I'll add this PDF in the email), it doesn't show twice & also the drawing's printed BOM lists quantity "1".  I can't explain, how the 2nd set of components got inserted into the model...

Cheers,

Harry D.

[harry.doldersum]

@cmiller66  Hi Chris,

An update on the one of the earlier errors - setting a centerline?

While setting an centerline under an angle is still an issue with the drawing shown & similar drawings, I now *also* ran into an issue, where I could not set a normal horizontal centerline. What I tried, it wouldn't work.

Resetting the PC solved this.  This, however, doesn't solve the issue of the centerline under an angle - where 1 may work flawlessly and the other (similar one) will not allow itself to be created whatever you do.

I would gather that there is an issue with pointer management in memory  - is this related to the different versions of Fusion that we've been using, while working on the models & 2D drawings for these components?

Cheers,

Harry D.

[harry.doldersum]

@cmiller66 Just FYI, we thought we'd share this...

We've been thinking a bit on how to best get our drawing output moving forward...

As we expect that the various Fusion application updates, since the 2D drawings original creation dates, could be causing memory (read: pointer) issues, we've decided to remove all 2D drawings for this project and re-do them with the current version of Fusion. That's actually not that bad as it may sound, as updating the existing drawings turned out to be a major pain, these last days - with an ongoing stream of errors.

With the new approach, we've been steadily creating drawings today - resetting Fusion after each new drawing & resetting the PC as soon as we ran into repeatable errors. This is a workable scenario, that got us 15 new production drawings (fortunately, these aren't complex components): we're getting somewhere. 

Best regards,

Harry D.

[cmiller66]

Hi Harry,

I'm hoping you can provide some more information, something clearly sounds wrong and I'm wondering now if it's Install related or maybe a system with insufficient memory.
1.  You mentioned before you're on Win10.  Do you have a single system you are using or are you seeing these problems on multiple systems?

2.  What are the system specs, RAM?  Per the readme the minimum Memory: 3GB RAM (4GB or more recommended) 

3.  In Fusion can you expand the Help menu (? icon in upper right) and then click About and let me know the version you're using, 2.0.2xxx

4.  In the same menu there's an option to view Diagnostic Logs, can you please save those and send them to me: christopher.miller@autodesk.com

Sorry to see you're continuing to see these issues.  You shouldn't have to close/restart Fusion after each new drawings, I regularly have 4-5 or more drawings open and working fine, there seems to be something more going on here.

Thanks,

Chris

[harry.doldersum]

@cmiller66 Hi Chris,

You had asked:

1.  You mentioned before you're on Win10.  Do you have a single system you are using or are you seeing these problems on multiple systems?
2.  What are the system specs, RAM?  Per the readme the minimum Memory: 3GB RAM (4GB or more recommended) 
3.  In Fusion can you expand the Help menu (? icon in upper right) and then click About and let me know the version you're using, 2.0.2xxx
4.  In the same menu there's an option to view Diagnostic Logs, can you please save those and send them to me: christopher.miller@autodesk.com
 

=> 1. I am using a desktop PC and a laptop with Fusion. Most of the work of late has been done on the desktop, but I am seeing the errors on the laptop too. (Please also see the thread about the shifting detail view).

=> 2. Both the desktop pc & the laptop are Windows 10 systems, synchronized with the latest updates as provided by Microsoft. Both systems have 8GB RAM memory & run in 64 bit mode.

=> 3. Fusion version is 2.0.2539 (Desktop pc - I'm assuming the laptop uses the same. (Should this be different, then I'll add this later).

=> 4. I've forwarded you the diagnostic logs.

Hope this helps to solve this. 🙂

Cheers,

Harry D.