Posts by dsm

Reminder: If you encounter any issues with Enscape (including installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Feedback button as detailed here. Thank you for your understanding.


    Looked through the documentation and discussions ... and have also done some personal benchmarks.

    Verifying what is the advised general settings for day-to-day stability and performance with Enscape (we are using it for both Revit and Enscape).

    • Is it advised to generally have 'Hardware-accelerated Ray-Tracing' and 'Ray-Traced Sun Shadows' enabled to start?
    • Do enabling these two options substantially affect performance ... such as:
      - causing GPU memory to run out for larger scenes?
      - causing GPU to be taxed more and produce excessive heat (though its within thermal threshold, our mobile workstations are already running warm-hot with Enscape = warm keyboards)
      - cause Enscape framerate / navigation performance to drop (similar to when Ray-tracing is enabled in PC games)
    • I have seen in discussions that enabling these ray-traced options as the resolution for light leak issues (especially on later version of Enscape).
      Do you anticipate this becoming more of an issue ... and should most enable these ray-tracing options by default due to this?

    Weighing the pros and cons with advising all our users ... if these ray-tracing options should be enabled or disabled by default.

    Thanks for any guidance / clarity on this!

    - Ed

    Image textures assigned within procedural materials (e.g. Tiles) still render in Revit 2017.

    However, in Revit 2019, Enscape is not able to render the texture. It instead only shows the base (generic) color.

    Assuming this is due to Revit 2019's change in approach with its materials (legacy vs new appearance assets).

    What we are finding though is that in Revit 2017 ... we are fine with the lack of support of procedural materials (e.g. Tile) ... since the underlying Tile Appearance texture image can still be rendered.

    However when upgrading Revit 2017 projects to 2019 ... the change is jarring as the Tile Appearance texture image is not rendering anymore in Enscape.

    Note: We are using Enscape v2.5.2

    Please let us know if there might be an update where the Tile Appearance texture image might get support under Revit 2019 (can be rendered similar to previous version of Revit).


    Using Revit 2017 - 2019 with Enscape v2.3

    Has Enscape view / camera synchronization been disabled / removed with Revit.

    The following knowledge article mentions that its available for SketchUp, Rhino and ArchiCAD ... but there is no mention if it as feature with Revit.

    There is also mention of a "Camera Synchronization Behavior" drop-down field option (with Settings window) ... back in Version 1.5 (see attached image and link below).…ew-and-improved-workflow/

    This option is not available anymore with version 2.X


    This is stemming from the SketchUp forum discussion below:

    IES file always externally referenced -or- can it be embedded / saved within SketchUp file

    If Enscape continues to externally reference assets instead of embedding them (e.g. IES, custom textures, skybox map, etc.) ... it would be beneficial to have an interface / utility that allows for all externally referenced assets to be accounted for and re-linked.

    This would be especially be useful and allow for rapid adjustment when a SketchUp file is shared in an environment / setup where paths to these assets are different (local vs networked, different project folder, etc.).


    Thanks Simon for clarifying that IES files were embedded in the past. It would be beneficial if this was the case again.

    To echo Sling3r's comment ... we also share SKP files between different groups and offices who access/rely on different network paths.

    Just knowing the IES file name is not helpful enough ... as users frequently won't know where to obtain the file itself (local or network path-wise).

    If and when they do find the IES file, they still then have to individually/manually reapply them (match them up).

    The same goes for custom bitmaps (environment map) applied via Enscape's material editor.

    So if embedding IES files and custom bitmaps into the SketchUp is an option again ... that would be of great help.

    If embedding is prohibitive due to possibly increasing the SketchUp file size too much (resulting in instability) ... then perhaps:

    - External referencing is the way to go

    - External referencing could be bolstered with functionality to list down and account for all IES / custom Enscape bitmaps (+environment map) within a file

    - This external reference list feature could then also be used to re-link missing IES / bitmap assets to their appropriate local/network path en masse


    Not sure if this has been clarified / addressed. Didn't see clarification on this in Enscape IES usage documentation and in forums.

    Are IES files used in a scene always externally referenced when applied?

    Or can it be (should be) embedded into a SketchUp file ... so that when the file is shared or moved to a different network path / computer, the assigned IES data files automatically work.

    Finding that when the SketchUp scene (with IES data files applied) is shared / moved / worked from another location ... we have to reassign the IES data file for the lighting to reappear / cast again.