1) The Enscape material editor does not support editing the texture offset at the moment and will not for 3.1. If you configure a texture offset in the Revit material editor, that will be picked up by the renderer nevertheless.
2) The tint color in Enscape only tints the texture, the tint color in Revit tints both the texture and the diffuse/albedo color. We try to work around that, but for non-white tint color and image fade less than 100% we can't maintain a perfect 2-way-sync.
3) Unfortunately that's impossible to know upfront. It looks like Revit checks the whole appearance when changing a single property. There is nothing we can do here. Would you rather expect some kind of error message when that happens?
4) For example when you change the type to "Water" in Enscape the transparency is no longer synced, because the Enscape water material doesn't support transparency. And there are lots of those unsupported combinations for non-Default material types.
Copying some questions from the previous thread that I'm still curious about
1) texture offset is not supported: I believe this was supported before, so does this mean we should expect textures to potentially shift when upgrading to Enscape 3.1?
2) Tint color: in my first tests this seemed to be syncing both ways, but I might be overlooking something. What does "no FULL two-way sync" mean exactly?
3) What materials don't have a two-way sync? Knowing the exact list here is critical so we don't get caught by surprise.
4) Not sure what the "edge cases" are that were mentioned as limitations?