This changelog entry presents a variety of notable updates and improvements to the platform. It introduces new functionalities such as material overrides for GLTF/GLB models, a custom fonts API, and a tags filter feature for selective geometry generation when using the component handler. There are also enhancements to dimension styles and defaults, the ability to dynamically show and hide visible metrics, and the addition of an automatic outline. The update further includes the implementation of a clipping planes API for precise control over object visibility, as well as the introduction of a Design Automation Service for seamless generation and export of STEP-files. Lastly, the changelog addresses several bug fixes and compatibility improvements with AutoCAD for generated DXF files.

Material override for GLTF/GLB models​

Added the ability to override materials for GLTF/GLB models in the application. This allows developers to apply custom materials or textures to specific parts of the models. Read more about it here.

Custom fonts API​

Introduced a custom fonts API that allows developers to define and utilize custom fonts within the application. The default font has been normalized to use Liberation Sans for both the scene and exported drawings, replacing the previous setup of Helvetica for drawings and Liberation Sans for scenes. Read more about it here.

Tags filter when generating geometry from the component handler​

Implemented a tags filter feature that enables users to generate geometry selectively based on specific tags assigned to component instances. Read more about it here.

Improved dimension styles and defaults​

Enhanced dimension styles and default settings. Improvements include new default options in layouts, new line terminators for dimension lines, and enhanced presentation for compact cases. Read more about it here.

Dynamically show and hide visible metrics​

Implemented the ability to dynamically show or hide visible metrics. You can now display or hide specific metrics with a simple function call. Read more about it here.

Automatic outline​

We previously introduced selective geometry interaction, which enables users to interact with individual geometry elements instead of the entire model. Additionally, an automatic outline can now be displayed when interacting with geometry, providing visual feedback and improving the user experience. While we're working on more detailed documentation for the automatic outline, please reach out to support@dynamaker.com if you would like to know more.

Clipping planes API​

Implemented a clipping planes API that enables users to define and control clipping planes in the application. This feature allows for more precise control over the visibility and display of objects by selectively hiding or revealing portions of the scene.

Studio.setUpdateGeometryFunction(async (data, worldControls) => {
  // ...

  const clippedGroupId = 'my-clipped-group'
  const clippingPlanes = [new SKYCAD.Plane(0, 0, 1, 10), new SKYCAD.Plane(1, 1, 1, 20)]
  worldControls.setClippingPlanes(clippingPlanes, { groupId: clippedGroupId })

  await worldControls.updateGeometry(geometry, { groupId: clippedGroupId })
})

While we're working on more detailed documentation for clipping planes, please reach out to support@dynamaker.com if you would like to know more.

Design automation service​

With our Design Automation Service, you can now effortlessly generate and export STEP-files from your application regardless of if your app uses static models or not! You can read more about it here and here.

Various improvements​

• Added missing return type for Studio.openParameterModal()
• Enhanced the handling of some parameter types outside of a configurator in the toolbar
• Fixed a bug related to save/load of configurations in UI Studio
• Fixed a bug related to the light position in the room scene
• Fixed a bug that prevented the loading of RGB encoding from GLB files
• Fixed a bug that sometimes prevented more than one instance of the same geometry from loading
• Fixed an issue where the set-camera and request-image commands from top/bottom views would occasionally not have the x-axis positioned horizontally
• Fixed the UI update for text parameters when their underlying value is updated
• Corrected the newValue behavior in the setUpdateRule() function for text parameters
• Fixed an issue with the setValue() function for text parameters
• Improved compatibility with AutoCAD for generated DXF files

The recently added Studio.createFormModal() makes it easier to ask for user input, for instance, when submitting a quotation request. You can read more about it here.

Also this update improves camera rotation, zoom, and pan on touch devices. By default, one finger triggers interaction (selectionEvent), and zoom is done with two fingers. You can change this behavior by using the Studio.updateCameraSettings() function and passing in the desired values for the oneFinger and twoFingers options.

For example, if you want rotation to be triggered by one finger instead of interaction and zoom-and-pan by two fingers, you can use:

Studio.updateCameraSettings({
  touch: {
    oneFinger: 'rotate',
    twoFingers: 'zoomAndPan',
  },
})

As for zoom-to-mouse, the default value of the camera setting zoomToMouse has been changed from true to false. We believe this is a more sensible default for most applications. If you want, you can enable zoom-to-mouse like this in your app:

Studio.updateCameraSettings({
  zoomToMouse: true,
})

Until now, all geometry that you add to the scene in DynaMaker has been interactable. From here on, the default behavior for new applications will be that you as a developer get to control what geometry groups can trigger selection events.

You might notice that we've begun to replace the term selection with interaction in the context of events triggered by the mouse or touch screen. This is in part because we think it is a better description of what is actually happening and in part to differentiate it from the manager.select() and manager.getActiveSelection() API.

To enable interaction events for a given group, set the interactable argument to true when updating the geometry.

Studio.setUpdateGeometryFunction(async (data, worldControls) => {
  // ...
  await worldControls.updateGeometry(geometryGroup, {
    interactable: true,
  })
})

To not break existing apps, this behavior is opt-in and controlled via an argument called useSelectiveGeometryInteraction in the ADVANCED tab. You can also add this argument manually to your existing application if you would like to use it there.

export function productConfigurationFactory(): STUDIO.IProductConfiguration {
  return {
    // ...
    useSelectiveGeometryInteraction: true,
  }
}

For even more control over interaction events, you can use the interaction plane. If the mouse/touch does not intersect with any interactable geometry group, the interaction plane is used. By default, the default interaction plane is the ground plane (0, 0, 1, 0).

// set the interaction plane to be the xz-plane offset by 100
const plane = new SKYCAD.Plane(0, 1, 0, 100)
Studio.setInteractionPlane(plane)

// completely remove the interaction plane
Studio.clearInteractionPlane()

Check out this newly added CSS snippet that can help you create a responsive layout for your DynaMaker application!

With the new Quote File Service, you can now use your DynaMaker application as a REST API in addition to all its previous capabilities! A common task could be to generate a PDF and attach it to a quotation or send it in an email, fully automated on the server. You can read more about it on its documentation page.