Corrupted Save Stock Killing my workflow

Corrupted Save Stock Killing my workflow

RCSDesign
Contributor Contributor
452 Views
2 Replies
Message 1 of 3

Corrupted Save Stock Killing my workflow

RCSDesign
Contributor
Contributor

My projects get pretty big in size and there is a lot of 3D profiling.  I have learned that if I don't break up my roughing/semi roughing/semi finishing/finishing into separate projects Fusion really starts to bog down and take forever. 

 

In addition to breaking up my programs each one requires a bunch of offset faces to make my boundaries and finishing go much faster.  I have learned that there is just about only so many entities Fusion can take on screen at a time before the hangs really get frustrating.  

 

Breaking up my programming into separate projects has become "the workflow"  and the "save stock" feature to move the rest machined stock from project to project is critical here. 

 

I have come up against an issue where it seems like the "saved" stock is becoming too big or complex maybe for Fusion to save properly.  On my 3-4 setup in a row of machining over the mesh stock and saving it to continue in the next project it is corrupting the mesh and not allowing me to import it into the next one.

 

Workflow to repeat this error in linked file -

 

Simulate all operations

When simulation finishes right mouse click "save stock"

Upload that saved stock into a project folder

"import" into new project

 

That is when the error "could not open file" or "file is corrupted" will hit.  Which is weird because I can plainly see the thumbnail of the mesh file in my projects folder and it has worked with this same exact workflow for the past 4 setups on this project and for dozens of other projects in the past 2 years.

 

These models I am working with are MUCH larger than ones I have in the past and I definitely see where every time I overwrite that stock and save a new stock it gets larger.  It starts at 3mb for the first setup and this last one that errors is a 540mb .stl file. 

 

I am "assuming" I am hitting some sort of file size limit somewhere in the cloud that is corrupting this.  If that just is what it is then ok but I would like some sort of verification because man spending hours simulating operations and uploading them just to get a corrupt file which means I have to completely change my workflow really sucks.

 

Please message me for the password to the file link

 

 

https://a360.co/3qssyDn

0 Likes
453 Views
2 Replies
Replies (2)
Message 2 of 3

seth.madore
Community Manager
Community Manager

I can reproduce this issue. I've reached out to the appropriate team to see if they have any feedback.
Quick question; are you working with the same .stl across several documents, or is this all contained in one file?
Have you tried the "From Preceding Setup > Continue Rest Machining workflow? This grabs the .stl file that is created via In Process Stock and uses THAT instead of the need to export and re-import an .stl file. Of course, this doesn't work cross-document, which is why I asked.


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 3

RCSDesign
Contributor
Contributor
  1. Create file with models and intial setup.  (File 1)
  2. Run the ops designated for that one, run simulation save the stock stl.
  3. Copy relevant solid models and create file 2 fresh with no manufacture data. (File 2)
  4. Upload stock STL from file 1 and import into File 2

I repeat that process into file 3.... file 4 etc.  Basically simulation cutting over top of the previous files stock stl. 

 

I am not sure if the increasing file size is because of that "over cutting" of the stock file or just as the stock gets more refined down to the finish level the facet count increases.  

 

Again I am not certain that the increasing file/facet size/count is the culprit here.  I am just guessing since that is the only real variable in my process.  

 

I have not had a chance to try out the in process stock feature.  It mostly a time thing on my end and since I have experienced slow downs with multiple setups in the same file (my actual start to finish operation count is usually a couple of dozen ops spread out between 6 or so "setups") I assumed I would still see those slow downs.

 

I intend to try the in process feature but my concern is this will exacerbate the issue as the setup count increases.  I run pretty lean here and a day worth of trying out a new feature on the "hope" it'll work is a touch ask sometimes.

 

 

0 Likes