Skip to Main Content
Chaos Enscape Ideas Portal

The online platform for Enscape users to submit, vote, and collaborate on creative suggestions.

Material Studies in Enscape

Ability to iterate and save multiple material iterations / options within Enscape. Materials do not automatically revert back to the design tool. Multiple material options may be saved and explored.

This is for the purpose of lightweight material discussion / exploration / discovery during design in Enscape which is not practicable in the design application. Geometric changes in the design application maintain material iterations / options in Enscape.

For example: If the kitchen casework in the design application changes, the materials options assigned to the casework remains attached.

Another example: If the material to a pendant lamp changes, and the number of pendent lamps increases from 3 to 4 lamps, the material iterations are automatically applied to the new lamp.

Material studies initiate in multiple methods:

  1. The new material study view already contains the materials from the design application

  2. The new material study view started in a neutral "white" mode to which new materials are added to selected objects.

  3. Existing material study views may be duplicated from existing material study views and further iterated and modified

Materials study views of the same design file may be kept private or shared with other Enscape users working on the same project.


  • ADMIN RESPONSE
    Feb 19, 2025

    This is a very interesting use case that we definitely see value in.
    However, it comes with two downsides.

    1) When assigning materials to surfaces, we are only using functionality that is provided by the host application. Adding our own, additional material assignment and prioritization functionality would be costly and also slow down performance.
    2) Besides different rendering styles, we always want to maintain a single source of truth: the CAD project. What youo can see in Enscape should always be what is set up in the project.

    Again, the use case is sound. But I don't see this being implemented in the near future.