I'm working on my first big toposolid since R26 launched. I want to preface by saying, as lackluster as improvements to R26 were, the ability to add layers to subdivisions, as well as recess them into the main toposolid, are incredibly beneficial features. Being able to have elements like parking lots remain associated with the main toposolid rather than having to have it as its own toposolid is incredible helpful. However, it leads to one problem (so far), and that's the condition below.
When a parking lot, or some other recessed element, meets a paving element that is either level with or slightly above the main toposolid, like a sidewalk, there isn't an obvious way to create a ramp here to transition the heights. Before R26, I would actually cut the sidewalks back a bit, and extend the lower paving into that void, and raise its elevation to meet. But now, since its all one toposolid, changing an elevation point would raise all of the elements shown, meaning the height difference between them would remain.
The best solution I can think of is to utilize the previous strategy for just the ramp portion. So remove a section of the toposolid where the ramp would be, and then add a new toposolid for just that small portion. While the desired form is achievable with this, it leads to the same problems we had before R26. If the toposolid around the ramp changes at all, the ramp will not change with it. It will also have to be independently adjusted to match the changes. Its obviously easier to manage this with just the ramps, rather than the entire parking area or streets or whatever it may be, but its still not ideal.
Has anyone else tried to work with this yet? Have any workflows been adapted beyond what I've come up with? I have some thoughts for the idea forum that could help, but I don't know how doable they are nor what kind of timeline implementation would be. So I assume we'll have this current system for at minimum R26 and R27 before it can be addressed.
