"Asset cannot be placed" Error

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.
  • Hi, using latest Enscape in Revit 2022. When we insert certain assets from the asset library we get the error message "Asset cannot be placed. The name 'EnscapeAssetId" is already in use. Parameter name: parameterName."

    Screenshot attached.



    It happens with some of the furniture assets. I think it may be related to copy and pasting some of the same furniture assets from older Revit files using older versions of Enscape assets. When you paste the older assets into the newer file, the proxy mesh is visible, but do not render in Enscape. If you delete and re-insert the same asset, you get this error message. Its a unique condition, but is there a way to purge out the older Enscape asset definitions? We're trying to avoid having to re-build the file.

    • Official Post

    vince1 , thanks a lot for your report and I'm sorry to hear about this of course.


    Right away since you receive this error message at hand despite removing the Assets from the scene, please be aware that certain assets can still be integrated into families within the project, even if they haven't been placed anywhere, so I suggest verifying whether these are also still present or not.


    You can do that via the "Planting" category in the project browser:


    After removing the assets this way the error dialogue should not pop up again and re-placing assets through our library should become possible.


    Let me know if that doesn't help or in case of any further questions.

  • Thanks for helping, btw. Here's what's even stranger. There is another asset that I copied from an older Revit project using an older version of Enscape - Sofa 002. Sofa 002 still exists in the current version of Enscape. If I drag the family Enscape AssetDefinition - Sofa002 into the plan the mesh shows up as if everything is normal. However, it does not render in the newest version of Enscape. It is invisible.


    If I delete the family Enscape AssetDefinition - Sofa002 from the Properties Menu, then re-insert it from the Enscape Asset library, I get the error message: "Asset cannot be placed. The name 'EnscapeAssetId" is already in use. Parameter name: parameterName." This is odd, since I just deleted this exact family. Its almost as if the old Enscape asset definition of Sofa 002 is still in use, or the new Enscape cannot translate the difference from the old Enscape asset.

    • Official Post

    Thanks for helping, btw. Here's what's even stranger. There is another asset that I copied from an older Revit project using an older version of Enscape - Sofa 002. Sofa 002 still exists in the current version of Enscape. If I drag the family Enscape AssetDefinition - Sofa002 into the plan the mesh shows up as if everything is normal. However, it does not render in the newest version of Enscape. It is invisible.


    If I delete the family Enscape AssetDefinition - Sofa002 from the Properties Menu, then re-insert it from the Enscape Asset library, I get the error message: "Asset cannot be placed. The name 'EnscapeAssetId" is already in use. Parameter name: parameterName." This is odd, since I just deleted this exact family. Its almost as if the old Enscape asset definition of Sofa 002 is still in use, or the new Enscape cannot translate the difference from the old Enscape asset.

    Thanks a lot for your reply.


    We have actually found out the cause behind this problem and it's now filed as a bug which will be resolved as quickly as possible.


    Here is an excerpt of a workaround shared by one of our developers:

    "There is a workaround: adjust one asset of the same family in any way (move, rotate, change color if its a customizable one etc.). The adjustment can then be reverted again and the placement should work just fine from there on. Note however that this might be cumbersome if the project has a lot of different assets because this needs to be done for every asset family individually as soon as you want to add a new asset of that family to the project."


    I'll notify you here once again too after I know when exactly the fix for this is coming.

    • Official Post

    vince1 , just to notify you, we have now released our latest service pack 3.5.2 which resolves this problem without a workaround required anymore. Let me know in case you still experience any further issues of course in the future.