This is sort of a Re-up of an older topic.
Quote from Simon Weinberger
we tried to switch to the API introduced in Rhino 6, which is the preferred way if you ask McNeel. With this implementation we get edge softening works, decals and better material IDs without any code from our side. We really want to make the switch ourselves.
Unfortunately there are serious shortcomings regarding live updates when editing blocks. You can see the same problems when using Cycles (switch to Cycles, edit blocks, end editing, see how Cycles renderer gets out of sync). In our opinion it's better to have a synchronous rendering, even if this means to miss out on a few other features. You can try it out for yourself and give feedback. How serious are these sync problems in your opinion?
McNeel is aware of the bugs in the API, probably it's not as easy to fix as it might seem. I'm not aware of any ETA for the bugfixes.
In my opinion support for the Render Mesh modifiers trump live sync any day, as far as my testing showed as soon as I switched Cycles off and then on again the problem was solved? I'd prefer restarting Enscape for the times I'm editing blocks over not having edge softening at all. I'm also guessing this is a bug that the rhino team will try to squash and when that time comes Enscape is already ready to go?
We, at our office, use edge softening on a daily basis to get a decent level of realism without bulking up the model and destroying the Make2D capabilities for printing. This allows us to work on the same file for a much longer period without having to create break-off files for render, 2D work, and so on.