FAQ

Welcome to the DynaMaker Frequently Asked Questions (FAQ) page.

How do I find which library to use ?

You can find all the libraries available in DynaMaker with a short description here.

How can I limit access to my application ?

You can read more about limiting access to your applications here.

I deployed a wrong version of the project.

You can red more about restoring a previous version of your project here.

How can I save and load my designs in a project ?

You can check what is needed in here and follow these how-to examples.

How can I update the model instantly when using a slider parameter ?

Doing the following should make your models update faster with a slider:

  • Go to your component:
    • go to COMP/Parameters.
    • make sure you use configurator.addUpdateCallback() instead of configurator.addCompletionCallback() , since the latter has a very short time delay.
  • If you want to see the result in your component right away:
    • go to SPEC/Presets component.
    • in your new component presets set the optional argument useUpdateCallback to true .
    • you should have the following as an example:
    const myComponentPreset = new PRESET.ComponentPreset(COMPONENT.MyComponent, { useUpdateCallback: true })
  • Go to your application:
    • go to CODE/UI.
    • go to the tab where your configurator is located.
    • set the optional argument instantUpdate to true .
    • you should have the following as an example:
    const productTab = new STUDIO.Tab('Product', generateProductToolbarItems, { instantUpdate: true })
    Updating a model instantly when moving a slider means that getModel() functions are called more frequently, so this is usually suitable for simple models and this could affect your app's performance, specially in larger products, but you can easily turn this off by writing instantUpdate: false instead.

Something is wrong with my model.

Sometimes we think that the problem is in the model, but it usually comes from the sketches that generates them. Some tips:

  • when cut/extruding, try to have a closed sketch. Make sure you end the sketch with sketch.lineToId(0) or sketch.curveToId(0) to return to the first node 0 .

My app is slow !

Everyone wants to have a dynamic product that updates very fast with certain parameters. This is one of the strengths of using Dynamaker and here are some tips you can try to improve the performance of your app:

  • Avoid calling the same function several times when maybe just once is enough.
  • 2D sketches are much faster to update than 3D models.
    • Think if you need to have 3D models in all the steps of your application
    • Try to have the 3D steps only when you don't update your model and you just need it for visualization (eg.exports).
  • Usually curves require more calculations than straight lines, specially in 3D models. Try to only use them when they are strictly needed, such as drawings or final 3D models (stl files).
  • addExtrude() and addExtrudeCut() can be performed with a sketch that consists of multiple closed sketches at the same time. For example:
    • a hollowed cylinder can be done with 2 concentric circle sketches and one single extrude (no extrude cuts).
    • multiple holes (circle sketches) can be cut extruded at the same time if they are merged into a single sketch.
  • addExtrudeCut() usually requires heavy calculations. In the tutorial My First Drawing we show an example, which says try these in the following order if possible:
    • Option 1: Merged sketch + extrude.
    • Option 2: Boolean subtraction.
    • Option 3: Extrude cut.
  • instance.getModelInstance() is the same as instance.getComponent().getModel() . If you are genereting the model of all your instances that share the same component, you are calling getModel() several times. It is enough if you generate the model of the component instead and use that for your modelInstance . In the tutorial My First Assembly we show this problem. Make sure you use bundles instead to get the component and its instances at the same time.
  • manager.updateWorldWithProduct() , specially in selection, this function updates both the models and the sketches. If you are updating only sketches you can try the following instead manager.updateWorldWithProduct({ updateSketches: true, updateModels: false }) to ensure an update only on 2D items. In the tutorial User interface we show this problem.

I want to learn more about Javascript & Typescript

You can read more about Javascript & Typescript here.

The examples in docs don't look the same as the templates in DynaMaker

We are constantly developing and improving the DynaMaker functionalities and sometimes docs get left behind. When you find out differences, please reach out to support@dynamaker.com and we will remedy promptly!

I'm stuck ! None of the above solved my problem.

We are happy to help you to solve any other problem! Contact us at support@dynamaker.com.

← Did you know...