For a very simple one level extruded solid, we can use expression this.GetElement().GetItem("SmartFeaturesSchema:Extrude").Distance to get the Distance. For your three levels smart feature, need more investigation.

We have experienced this as well. We discovered that you need to go into your reference's Adjust Colors settings (Reference > Properties > Adjust Colors) and check on Print Adjusted Colors for each reference that you wish to show transparency for.

Just to follow up on our issue, this does not seem to be a PW issue. I believe I nailed it down to a bug in CONNECT U16/ORD 2021 R1. The files I am experiencing the issue with were mostly created with ORD 2020 R3. I believe that CONNECT 16ORD 2021 R1…

FYI, this defect # was closed as it duplicated an existing one. The one to track now is Defect 1107547:Feature Definition toolbar keeps growing larger when users switch between models/DGNs I've just checked, it's been approved but no timeline yet.

This short video might help

Here is the "best" workflow for ORD 10.08. Verify that level overrides are on in all Base file DGNs. Ctrl + B and verify the flag next to Level Overrides is turned on. No actual level overrides are applied to the base file(s). Save Settings…

Hello, To follow up with what my colleague Jayson has answered, here is an official response from our colleagues in Development: "We are currently working on certifying the next commercial release of MicroStation, targeted for Q2/2022, with Windows…

For future readers, I'd like to note that bug 672552 is fixed in MicroStation CE Update 16.2 and also test data I used in this discussion now works fine. Regards, Jan

We noticed this almost as soon as we installed 10.10 for testing. It's a defect in the new profile view annotation enhancement for 10.10. But only in the profile view, when you annotate the profiles in your Drawing models the annotation is correct. Definitely…

My XML & XSLT are producing the correct result using the input values to the 6th place. It was my checks done by hand that were using values to the 2nd place was where the whole source of my distress lay. Oooops, but I have definitely learned something…

As a follow-up to this discussion- and with the input of Mr. Shamoun and Mr. Huston- the real issue was the particular seed file for this GCS that was the culprit. Indeed, there are no issues in running cross sections with a GCS, it was "just" a corrupt…