I understand that the underlying problem of what I'm about to address is deep in the code of the Revit API, Revit, and how a PC's resources are made available (or unavailable, for that matter), but I need to present this as an important challenge for the Enscape team, which is:
How can live changes occuring in Revit get delivered to Enscape faster to the point where it truly feels seamless?
For reference, I have a powerful PC (4.7 Ghz Overclocked, Windows 10, 32GB RAM, GeForce 1080 Titan Ti, M2 PCIe SSD) and I've been running it on a campus project of 4 buildings, probably totalling in 1.2GB in size. If I move a bench family in the garden areal with an arrow key, it take approximately 15 seconds for Revit to "re-print" back to Enscape, and for Enscape to update. Additionally, the Revit window steals focus from Enscape during this process, so I can't really make the move, and then quickly jump back into Enscape. Recently I've been using the pause live updates because I can't get the seamless integration with the software yet.
I can imagine for some of you that this may seem unreasonable, but at our firm, the design cooker is a fragile, quick, and spontaneous process where every billable second counts, and every 15 seconds waiting on the computer is another 15 seconds remembering your steps, and even more than that if you get distracted while you're waiting.
How can this be reduced to less than a second? Whichever company can deliver the speed we need will be the one we truly invest in.