Enscape functionalities grayed out

  • Rick Marx I think I isolated the cause. The Revit customization folder in my Roaming folder was not created during install (there was a mystery extension-less file in there preventing the folder from being created, maybe due to a failed install). I cleaned that section up and since then Enscape has been running fine.


    So probably not the same underlying issue as other users were reporting here, just the same symptoms (greyed out Enscape bar, which I guess means Enscape failed to initialize properly?).

    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.

  • 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.

  • 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.

    Thanks Pieter, 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:


    C:\ProgramData\Autodesk\Revit\Addins\

    and not in the Roaming profile


    When you say "file without file extension" are you referring to something below? We call these "stub" files which look like folders but they are actually files. These can compromise installation of the software, i.e. during the installation it expects path to be accessible for application to place ADDIN file in but if it doe snot get what it wants it will simply fail. deleting these Stub files resolves the issue.

    C:\ProgramData\Autodesk\Revit\Addins\2022 to be accessible but if "2022" is a file



  • 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 :)

  • I am also running into this issue on version 2020 through 2022 of Revit. I have noticed that the "0_Enscape.AddIn" file is not being created or copied into the respective version of the Revit addins folders located C:\ProgramData\Autodesk\Revit\Addins\20xx


    This is with the 3.4.0+84039 version. (Edit: I also tried with 3.4.1+85781, same results)


    I did a clean uninstall and install of that version.


    My coworker did an install, updating from 3.3 without doing an uninstall and it worked fine, and it appears it retained the .AddIn files.


    Unfortunately I can't send feedback through the app, because it is ALL greyed out.

  • Hi dgore720


    You can manually send us the necessary log files, you'll find them here:


    Enscape main plugin log files:

    C:\Users\%USERNAME%\AppData\Roaming\Enscape\Data\Logs


    Revit plugin log files:

    C:\Users\%USERNAME%\AppData\Local\Temp\Enscape\Logs\EnscapeRevitPlugin


    You can just place all the files that are contained in these folders into a .zip file and send these to us at support@enscape3d.com.


    Please also add a link to this thread and my name for context.