New update is very buggy on the CAM side

[agerkhardtTTLAW]

Since the new update yesterday I have been having nothing but problems on the CAM side. The latest on is stock generation in simulation. I keep getting this error. 

An unexpected issue interrupted the verification process before completion.

This can sometimes be because of problems with the in-process stock (IPS) mesh. In Preferences > General > Manufacture, enable In-Process Stock - Mesh Check Safety, then try again.

If the error continues, report it.

I have already checked those boxes, and updated my graphics card

[seth.madore]

Can you share a file or screenshots/video of what you're running into?

What are your system specs and O/S?

[agerkhardtTTLAW]

This is what comes up when trying to simulate with the machine

[seth.madore]

And what are your system specs and would you be able to share your Fusion file here?
File > Export > Save to local folder, return to thread and attach the .f3d/.f3z file in your reply.

[agerkhardtTTLAW]

I rather not put the file here if there was somewhere I could send it that would be better

Windows 10

Intel i9-14900KF

Nvidia RTX A2000

[seth.madore]

You can email it to me: seth DOT madore AT autodesk DOT com
Please reference this thread so I understand the context 🙂

[agerkhardtTTLAW]

Seth I keep trying to email you but its being rejected as spam can you e mail me agerkhardt AT afiglass DOT com

[seth.madore]

File received, I'll follow-up with some findings and see if we can't improve things for you.

[seth.madore]

Unfortunately, I've not been able to find a workaround. I was hopeful that some adjustments to the Adaptive toolpaths would improve things, but nothing came of it 😞

I've opened CAM-63390 to investigate this issue, I'll update you when I know more.

Was this a file you had programmed and successfully Machine Sim-med before the update?

[agerkhardtTTLAW]

I have not machined it yet but I programed it and simulated it the day before the update and there were no problems

[seth.madore]

We've confirmed (internally) that this is a regression. The error lies in our CAM Simulation technology, we're triaging the issue and see if we can improve the results in a timely fashion.

[agerkhardtTTLAW]

Is there a timeline on when this will be fixed? I don't like running things without and accurate simulation 

[seth.madore]

No, sorry. You're going to have to use non-machine simulation for this model. Fortunately, as you're on a 3 axis machine, you're not at an extreme risk of head/machine collisions. We are going to work on this as quickly as is possible, but no timeline on when that will be completed.

[dames123]

@seth.madore I also noticed if you simulate an entire setup the stock is good resolution, if you simulate just one toolpath down in the sequence the stock that represents the toolpaths you skipped is very bad resolution. Not sure if this is related. I don't remember having this issue in the insider version.

[daniel.schaefer9P5YP]

Hey,

we are an Autodesk Reseller from Germany and developing our own postprocessors. We are facing the same issues since a past update. We are using the in-between-moves for the machine simulation. The Problem in our case is when we use the in-between-moves with the post function machineSimulation(). Sometimes the issue also appears if you overtravel a machine limit. The error message is kind of confusing. Also what I mentioned is when you uncheck the "stop at collision" option, you can proceed by pressing "ok" and continue the simulation. We have a lot of trouble because of these issues. When you need more information, we are likely to share it. What we cannot share are our postprocessors. 

For example we had in one case the issue in a customers postprocessor. And I found a workaround.

Replacing the line:

//Faulty behavior
machineSimulation({a:0,b:0,c:0, coordinates:MACHINE, mode: TWPOFF});
//Fixed the problem
machineSimulation({a:0.0001,b:0.0001,c:0.0001, coordinates:MACHINE, mode: TWPOFF});

[seth.madore]

Please drop me a DM (direct message) with a link to a part that you can share and that demonstrates this issue. We do want to resolve this issue, so the more data points we have the better we can grasp what's needed and the severity of the issue.

[daniel.schaefer9P5YP]

I wrote you a DM. Thanks!

[daniel.schaefer9P5YP]

Hey, could you specify where you made these settings? Windows, Fusion or the graphics driver? I would like to try it.

[seth.madore]

What is this P9P you're referring to? Google suggests you're referring to a mobile phone, which suggests this is a spam post.