Posts by Pieter

    Hey Enscape,

    The tooltip on the color slider lists some recommended values for albedo, but it does not list a white paint (I think it would be helpful if it would as it is a extremely common material, and usually the 'brightest' material in the scene)

    I assumed Enscape's material would match other PBR render engine's recommendations and put white paint somewhere around 0.7~0.8 (RGB 180 180 180) but now I'm starting to doubt this as the fresh snow value is much brighter than in other engines I've used. In the tooltip below, "New Concrete" is already brighter than the typical white paint value I'ved used in other engines.

    What is Enscape's recommendation for white paint?

    I think it's weird that the material library does not contain a "white wall paint" and a "black wall paint".

    This might sound trivial, but setting up a good PBR white paint might not be as easy as it sounds for many users. They might use a 100% white for example instead of a physically accurate albedo value.

    The problem:

    Enscape only allows local Category creation. Enscape does not recognize network folder structures. Therefore every single Enscape user would need to create and move thousands of custom assets to dozens of categories locally for it to be organized and standardized across our firm. Only to have to do it again every time new assets are added or created.

    I don't understand the problem to be honest.

    Some context: we currently have 1100 custom assets. I and another user sorted all the assets into categories. It took the both of us about an hour. After that , the categorization became visible for all users. No one has had to do extra work since then.

    When a user creates a new asset, their 'category' dropdown is populated based on the categories we already created, so it's easy for them to stick to our standard.

    The system seems to work very well for us.

    Are you saying that when you create categories and sort assets in them, this is not visible for other users using the same network folder as their asset library?

    File size depends on the file format. Enscape uses .gltf which sacrifices file size for loading and rendering speed (this is a great oversimplification).

    That the file size is larger does not mean that the model is automatically more or less detailed or 'heavier' to load, all it means is that it takes more room on your file storage.

    There could be two reasons for your asset being that large:

    - you loaded in large texture maps

    - the asset geometry has too many polygons (typically, 20.000 is the recommended max)

    In the newest preview, assets seem to follow a new naming convention in Revit. Previously it said "Enscape AssetDefinition - Name of the asset" but now it says "TempEnscape AssetDefinition - Name of the asset".

    Could it be this is a bug?

    Aside from a longer, uglier name, this is also creating issues in projects where assets were already placed. When replacing assets from the asset library, I will now have the asset loaded twice in the project: once with the old naming convention and once with the new naming convention.

    We are currently working on this feature as seen in our Public Voting Portal here under the 'In Development' tab.

    Great news! Looks like a very powerful feature set. Of course the devil is often in the details, so I have a couple of questions that weren't immediately obvious from the post on the voting portal:

    - lets say I place an asset "chair A" into a project and copy it 10 times. When I now select a single chair and override its material, will it affect only the selected chair or all of them?

    - If it only affects the selected item, will I be able to multi select and override many instances at once? (we might have a 1000 chairs in a project that need to be overridden to a different upholstery)

    - Will there be a way to apply asset overrides from within the host application (in my case Revit) or can this only be done from the enscape rendering window? The reason I'm asking is that my host application has many fast selection features that don't exist in Revit.

    - When I copy an asset with a material override, will the copied asset respect the material overrides or will it reset to the default materials?

    - Can you confirm we can also change material maps (change marble to wood) and not just change the tint color.

    - Will we be able to override materials using materials from the enscape library or using saved .matpkg's?

    And most of all: will the material overrides also be possible for custom assets? Our custom asset library is a critical piece of our workflow, so having it there would be a game changer. Also, it will not be a great experience for users that they can edit Asset A (Because it's an enscape default asset) but not Asset B (because it's a custom asset).

    Yes changes in revit 2023 made this possible, but enscaoe still had to change their code to take advantage of this feature in revit 2023. That seems to have happened with 3.5 preview 1 (it's not working yet with 3.4).

    I was part of the beta test team for this new revit 2023 feature btw :)

    can you be more specific about the files and paths? To my knowledge, both Enscape and RIR plugins (ADDIN files) are located in %Programdata% folder

    The path where the 'stub" file was located was %appdata%\autodesk\revit The stub file itself was called "Autodesk Revit 2022", therefor it was blocking the path %appdata%\autodesk\revit\autodesk revit 2022 of being created. I don't know why (as far as I can tell, Enscape doesn't store files in here) but in our case that was the reason the Enscape ribbon was greyed out. Deleting the stub file and restarting revit fixed the greyed out enscape tab. Maybe Revit just blocks (certain types of) plugins when the customization folder cannot be created?

    When you say "file without file extension" are you referring to something below?

    yes that's exactly what I was referring too! Thanks, I did not know there was a proper term for it :) This will help in future google searches and troubleshooting :)

    Can you please elaborate on "The Revit customization folder in my Roaming folder was not created during install" and provide details of fixing this issue? As far as i know, Roaming folders (for any application) are not created at the point of installation but at the point of opening application for the very first time.

    That was the point: it could not be created because at some point (either on install or on first launch) a file without file extension was created that was named the same way as the customization folder (for example "Autodesk Revit 2022"). Because a file with that name was already there, Revit could not create the customization folder (each name can only exists once in a given directory). That doesn't actually prevent revit from launching but it does prevent settings from being saved, and apparently it also caused the Enscape ribbon to be completely greyed out. Deleting the file and restarting revit worked.

    That's not to say this is the only possible cause of a greyed out Enscape ribbon of course.

    I know they are not one and the same, but it's at least slightly relevant to also mention HOW the settings get saved at the moment.

    The current system does not work with Revit projects that have multiple people working on them simultaneously (central files) . This might not be common in small offices but on large projects, this is the standard. My users are complaining to me about this every time we talk about Enscape. DanStine_TX can confirm this a daily struggle

    Ideally when the team revisits the saving mechanism of the settings, they can also reconsider how data is stored in the Revit file (as much of the data as possible should be attached to Revit elements so that Revits takes care of the worksharing details).