It would be great to add .PA, .PR in extensions for hits, arrays (...)in assignments.

Allow theoretical numbers to be locked on individual features making it possible to prevent them from changing. This would give us a more elegant solution than turning a theoretical number into an expression by dividing by 1.

I would like actually create surfaces based on a point cloud

....like the MultiExecute Wizard can do.

Please do the same you did for Sphere Scan Strategy Avoidance move on 2026.2.

Sphere Scan Strategy

When you add a custom color (for example CAD model color), that custom color doesn't show up in other routines. If you want consistency across routines, you need to keep a separate list of any custom colors you use, and manually add them when needed. I'd love it if custom colors could be remembered globally.

Another good option would be to insert a picture from camera (within Optiv machines) among report pages and due to that have an opportunity to see the part details

Hi, 

as CMM programmer I would like to appreciate to have some more options in PC-DMIS Fusion reporting 

Printing CAD report:

To have header on every page.

To hide some labels or to have an option to drag them to another report page.

If I rotate CAD on one page, it stays in this position on all pages. I would like to have different CAD positions within pages (each page different CAD position).

Evaluation of distance with both feature displayed (i.e. two points distance - I need to see related lines to both points, not just to one as it is)

I will probably add more points over time as I started to work with PC-DMIS Fusion

David 

I want the combination of cylinder + width and circle + width to be allowed to be used as common datum. Currently it is not. According to ISO 5459 rules, this would be equal to be using the [DF]-modifier when the datums are separated. While using DF is fine, allowing the common datum combination removes the risk of unnecessary questions or discussions on how the final report should look, making the report mirror the requirement in the drawings.

I would like to submit a feature request for a future update of PC-DMIS. The goal is to improve programming efficiency and safety by introducing an option to create a Move Point directly along the vector of a selected point or surface.Currently, creating clearance or approach moves often requires manual coordinate calculation (\(X, Y, Z\)) or utilizing complex expressions to offset a position relative to a measured point. Introducing a native "Move Point Along Vector" feature would significantly streamline this workflow.

Proposed Functionality & User Interface Integration

1. Context Menu / Dialog Option:
   • When creating a MOVE/POINT command, users should have a checkbox or dropdown option labeled "Along Vector" or "Offset by Vector".
   • Alternatively, right-clicking an existing point feature (e.g., PNT1) could offer an option: "Create Move Point Along Vector".
2. Input Parameters:
   • Reference Feature: The source point or surface from which the vector is derived (e.g., PNT1).
   • Distance (Offset): A positive or negative numerical value representing how far along the vector the Move Point should be placed.
     • Positive value: Moves away from the surface (clearance/retract).
     • Negative value: Moves toward/into the surface (approach).
3. Code Execution / Command Line Representation:
   The command in the Edit Window could look similar to this:pcdmis

   MOVE/POINT, ALONG_VECTOR, FEATURE=PNT1, DISTANCE=50.0
   

   Kód používajte opatrne.PC-DMIS would dynamically calculate the absolute \(X, Y, Z\) coordinates based on PNT1.X + (PNT1.I * 50), PNT1.Y + (PNT1.J * 50), and PNT1.Z + (PNT1.K * 50).

Key Benefits

• Increased Efficiency: Eliminates the need for manual math or writing custom expressions for simple approach and retract moves.
• Improved Safety: Reduces human error when calculating clearance points on complex, angled surfaces.
• Parametric Flexibility: If the nominal position of the reference point changes (e.g., due to a CAD update or alignment shift), the Move Point updates automatically because it is linked to the feature's vector.
• Cleaner Code: Replaces complex script-like workarounds with a clean, native PC-DMIS command.

Thank you for considering this request to enhance the offline and online programming experience in PC-DMIS.