Enscape Portal - vote for Cosmos Assets in Enscape Merged

The most critical reason that we are migrating to TwinMotion is because of the problems that Enscape assets have created in our production documentation Revit models. Enscape's efforts years ago to solve this problem by creating low-poly assets was greatly appreciated at the time, but as our users did more and more rendering in Enscape, they larded up their models with so much junk that we couldn't navigate the models efficiently for our daily documentation work. Managing assets in the Revit model is, I think, critical to the continued survival of Enscape in the AEC industry. We need a way to pair dimensionally-accurate, low-polygon, parametric Revit families that we use for spatial arrangement and to develop accurate counts and schedules in Revit with high-polygon models at the moment of rendering. If Chaos can't create a simple way to manage assets (families) in the Revit model (not just easier for Enscape users, but easier for ALL users of the Revit model), then I doubt we will use Enscape at all two years from now. Autodesk is as much at fault for creating this problem as Enscape is, but Autodesk has zero incentive to fix the problem. So Chaos group has basically got to solve the problem of how to manage and render families in the Revit model without changing anything about how Revit works. Good luck!