SO I have just configured a rotary on my Onefinity but I set it up to run along the Y-Axis (instead of parallel with the X-Axis) which I think would technically make it a B-Axis rotary and not an A-Axis. I have a post processor that wraps X to A and I have set up an external driver so I can run it as an A-Axis and it works great so far. Except, I think the visualizer is getting very confused by the fact that my g-code contains Y, A and Z movement instead of X, A and Z movement that would occur with a true A-Axis rotary. Am I correct in my observation that the visualizer does not properly display toolpaths that are wrapping the X axis around the A axis? If so, any chance of updating that so that it correctly diplays both true A- Axis and B-Axis pretending to be A-Axis rotaries?
Yes you’re correct that we currently can’t process these files correctly and also correct that checking the orientation along the Y-axis makes it a B-axis. The updates to support a B-axis could be doable, but I think there are still some remaining items we’ve have to do to still finish ironing out A-axis all the way before doing B-axis support. I’d imagine what it would look like would be a toggle in settings, a change in logic anywhere we’re handling the A-axis to have it be a B-axis instead, and then updating the visualizer to display those movements correctly