Yet Another D@#@$% Crash - The Curse of the Timeline

Yet Another D@#@$% Crash - The Curse of the Timeline

TrippyLighting
Consultant Consultant
834 Views
8 Replies
Message 1 of 9

Yet Another D@#@$% Crash - The Curse of the Timeline

TrippyLighting
Consultant
Consultant

Fusion crashes when simply hovering (not clicking) over a symbol in the timeline.

 

Here is a link to the screencaast as embedding results in a warning that invalid. C'mon guys that has been reported alerady an cannot be that ifficult to fix!!!

 

https://screencast.autodesk.com/main/details/f6b12eff-2318-437c-9202-c137cfc4f5dc

 

Yes, I can share the file.


EESignature

0 Likes
835 Views
8 Replies
Replies (8)
Message 2 of 9

innovatenate
Autodesk Support
Autodesk Support

Is that for another grouped item? Does the same fix as last time work?

 

Send me the file nathan.chandler@autodesk.com.

 

Thanks,

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 3 of 9

TrippyLighting
Consultant
Consultant

Hi Nate,

 

Honestly, I don't know if it has to do with joints. There is one joint in the file that has a problem, but it is much further down the timeline and is in a differnt component.

I don't know what exact element in the design this item in the timeline relates to becausue F360 crashes before the name pops up. It will take some investigation.

I filed CER_106259853

 

IIRC I've already shared the project with you. The file is "LED lamp". That one is actually done and I'l leave it untouched for a while.


EESignature

0 Likes
Message 4 of 9

innovatenate
Autodesk Support
Autodesk Support

If I do a Compute All from the Modify drop down menu. I get the below warning/errors:

 

Warning: Joint Origin1: 

Warning: Some input geometry cannot be found.
Cached geometry will be used.
Try editing this feature to reselect the lost inputs.
Warning: Some input geometry cannot be found.
Try editing this feature to reselect the lost inputs.
Warning: Joint Origin1:
Warning: Some input geometry cannot be found.
Cached geometry will be used.
Try editing this feature to reselect the lost inputs.
Warning: Some input geometry cannot be found.
Try editing this feature to reselect the lost inputs.
Warning: Joint Origin3:
Warning: Some input geometry cannot be found.
Cached geometry will be used.
Try editing this feature to reselect the lost inputs.
Warning: Bottom Hole:
Warning: Some input geometry cannot be found.
Cached geometry will be used.
Try editing this feature to reselect the lost inputs.
Warning: Top Hole:
Warning: Some input geometry cannot be found.
Cached geometry will be used.
Try editing this feature to reselect the lost inputs.

 

The leads me to Stud v1:1 located under LampArm assembly:4. - Note Lamp Arm assembly:2 changes names after compute all is performed which is a bit odd...

 

I can right click on Stud v1:1 or Body1 located in Stud1 v1:1 in the browser and select Find in Timeline. This will expand that group that is causing the crash in the Timeline. You can also activate Stud1 to drill into the timeline features. I note that a couple of warnings are still showing for this part. The construction planes seem to have lost their references as well. I suspect this is the root cause of the issue. The construction plane in Stud v1:1 are referencing some other geometry (possibly from another part) that is no longer in the assembly. 

 

To be frank, I'm not 100% sure how the file is getting into this state and will have to get back to you. If I edit the reference planes and reset thier references to the default construction planes for stud, the work planes seem to be okay, but there are still issues with the Joint Origins. Can any of these be eliminated? 

 

 

You may want to look at replacing this problem Stud component with a freshly rebuilt one. I believe this is the same one that caused problems last time. 

 

I've exported an archive file of the design in its problematic state. I haven't modified the design in your Project.  I'll add the archive to the other report for development to reference, dig a little deeper and get back to you with my findings.

 

Thanks,

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 5 of 9

TrippyLighting
Consultant
Consultant

I've not used "Compute All" before. I'll try and see if I can track this down and provide some feedback t help you guys track this down so we can get to a state where things don't crash.

Some of the joints that are created using joint origins can be replaced, but my designs can be VERY parametric and on occasion formula driven where a single dimension changes the dimensions of most compoennts in the design.

(heck, I have not even REALLY started to break things 😉  ). That means that the joint orientation will also have to respond to changing circumstances and in some cases a oint origin is needed.


EESignature

0 Likes
Message 6 of 9

TrippyLighting
Consultant
Consultant

As you've mentioned in your post, the Stud sems to have a problems with the construction planes.

Actually it would appear to me that F360 has a problem with exporting parts that include construction planes as part of their design, as well as with importing parts with construction planes!

 

I had come across this before, but forgot about it. When first transfering this Lamp desing into F360 I dind not exactly understand how to create a reusable components and basically had to toss my first assembly. Then, as  backup measure I designe all the single parts in spearate file so I could re-insert them if I screwed something else up, or in case another assembly file became not recoverable (The fact that a referenced sketch cannnot be moved into the (only) component that references it is hard to believe and a rather blatant oversight!!! ).

 

Anyway, the first thing I did in the single compoent file was to create a componet and then the sketch for the base extrusion, then the body for the base extrusion etc.

However, if that file is inserted it will turn into an asembly with exactly one component in it. That was not what I had wanted, so I opened each single file and exported the component to eleiminate the unneeded level. These exported compenents had probelms with the construction planes and I had to re-select them in each file. That was not immediately apparent when opening each single file as there were no yellow highlights in the timeline.

 

However, the Stud now is also in that project as a single component file. A Compute All in that file does not return any errors.  I did not touch the Stud design after I inserted it into this Lamp file, so F360 does "someting" with the construction planes on import or during the design provces that's not qite kosher!

 

Long storty short: Construction Planes need to be looked at!


EESignature

0 Likes
Message 7 of 9

TrippyLighting
Consultant
Consultant

I was able to fix the things related to the crash.

 

The construction planes for the horizontal Top and Bottom holes into the cylindrical body of the Stud were missing their reference to the original XY-plane they were offset from.

I checked the references in the (single component) Stud file and they are corrent and intact. Inserting the Stud into an empty new file leaves these references intact, so somehow during assembly into the lamp design these Stud construction planes are loosing their references and causing this odd behavior.

 

Quesion: is Compute All always manually triggered or does this automatically happen sometimes ? these issues did not turn up until Compute Al was triggered, so I'd like o have a guideline as to when to run it so I can avoid unnecessary crashes 😉


EESignature

0 Likes
Message 8 of 9

schneik-adsk
Community Manager
Community Manager
Compute all only happens when a user fires the command from the toolbar.
All other computes are a compute minimum to update. Think of compute all as a force rebuild all.

I rebuild all before saving my work for the day. Just to be sure.
Kevin Schneider
Message 9 of 9

TrippyLighting
Consultant
Consultant
@schneik-adsk
Thanks for the info. I'll definitely keep using the Compute All command!

@innovatenate
As posted above I was able to fix the problem with the the construction planes. I have posted another thread with a screencast explaining the joint origin problem.
https://screencast.autodesk.com/main/details/56259bec-1d6d-4248-a32b-6d18fc6f2ca3

EESignature

0 Likes