Review a setup in the Animator

Select the part's manufacturing setup and check its machine, process, origin and ordered operations. Press Create G-code/Animator in the Setup editor. If a machine or a required plasma consumable is missing you'll get Setup Required; fix the setup first, because starting or resuming playback checks again. The Animator can show NC Actions or G-code. They're two views of the same program, so look at the posted G-code, since that's what will actually run. Generating output here doesn't save the part or the job.

Use Begin, Step Back, Play/Pause, Stop, Step Forward and End. Speed runs playback from 10% to 1,000% and changes nothing in the program or its feed rates. The time shown is the estimated machine time including rapids, not how long you've been watching, and playback speed doesn't change it. Show origin and Show contours help you read the scene; MV switches to Machine View. The coordinate and attachment indicators describe the simulation, not real switches, torch state or positions. The full Animator loops at the end; the smaller playback inside a toolpath editor stops.

At an M0 or M1, PROGRAM HOLD pauses playback before any later motion. Press RUN to acknowledge it and continue. Play alone won't skip a pending hold, each hold needs its own acknowledgement, and seeking backwards can arm a hold again. RUN only acknowledges the simulated hold; it sends nothing to a machine.

When the check finds a tool-against-part overlap and playback reaches that position, a flashing COLLISION warning appears at the top left and stays. Click it to stop, jump to the pose and highlight the matching NC action or G-code line; its tooltip names the source location, attachment, motion type and coordinates. The check samples the modelled tool attachments against the finished part: plasma attachments through all their motion, other attachments during rapid moves only, and it records the first confirmed overlap. Touching a surface isn't counted as an overlap, and probe playback doesn't predict where the controller will actually trip.

No warning isn't an all-clear. A collision further along stays hidden until playback reaches it, there's no indicator that the check has finished, and the check can be unavailable or incomplete, for example when geometry or a capability is missing or an error occurs. A warning changes nothing on its own: it doesn't add a clearance move or repair the code. Find the cause in the setup or operation, change it, regenerate and review again. The model knows nothing about your real clamps, chuck or table, so keep the machine, post and attachment geometry correct and validate the posted program on the machine.