'Nuff said.
A360:
Actual toolpath:
Solved! Go to Solution.
Solved by paul.clauss. Go to Solution.
I'm having the same when generating 2d adaptive wrap toolpath.
But at the end the toolpath is in its place.
Ivan Stanojevic
In yours I see the unwrapped geometry during calculation though, just one of the steps as it unwraps the geometry to calculate before re-wrapping. I'm presuming it shows up fine after calculation?
@brianrepp anyone out there see how this happens? I would think it's just an un-updated CAM display issue that hasn't followed with the functionality.
@Steinwerks wrote:
In yours I see the unwrapped geometry during calculation though, just one of the steps as it unwraps the geometry to calculate before re-wrapping. I'm presuming it shows up fine after calculation?
@Steinwerks Yep, I'm seeing this only during the calculation. It looks fine after.
Ivan Stanojevic
Just so I'm clear: it sounds like there are 2 different issues:
1) the wrapped toolpath is shown in the wrong location (in space) in the A360 viewable of the model.
2) The wrapped toolpath is in the wrong place *during calculation*, but shows up in the correct location when the generation finishes.
Is this accurate?
Thanks,
Jeff
My only report is on the first. I believe that issue 2 is a non-issue when the CAM shows (accidentally or not) the intermediate calculation projection plane. As long as it gets re-wrapped it's fine, and I haven't seen it fail.
Issue 1 is just that if you are sharing a file publicly, it seems that A360 ONLY shows the intermediate calculation and NOT the actual wrapped toolpath. That is a real bug IMO.
Edit: Just follow the link and highlight the toolpath in CAM:
Hi @Steinwerks, @jeff.pek, @ivan.stanojevic
Thanks for bringing this one up! I have heard that the calculation representation of the toolpath is expected - the 2D toolpath is generated and then wrapped.
The flattened toolpaths in the A360 viewer, however, are unintentional. I have logged an issue for this (LMV-3421) and we will be looking into it. Please let me know if you have any questions!
Thanks @paul.clauss!
We're also tracking this as CAM-6854, as the fix will come from our team.
Thanks for the report.
Jeff