Z origin of text in Properties stopped working CONNECT

Recently my ability to change the Z Origin of text in Properties->Geometry has stopped working. I can adjust other element's elevations just fine, but text no longer works. 

This is file specific and also effects new files from seed. Some existing files it works. Other files it won't. I can adjust it just fine in existing problem files with ORD.

What setting got flipped where the ability to change this to 0 broke?

Thank you!

Microstation CE Update 15 - 10.15.02.11

Parents
  • test3d-textgeometry.dgn

    Just to note that this issue is also being investigated in SR # 7001241705.

    ----------------

    I have tested this operation with a new DGN file in MicroStation CONNECT Edition (Update 15 ) 10.15.02.11 with some basic text and I am able to adjust all of the Geometry - Origin X,Y,Z values ok.

    There is a possibility that either something is wrong with some of your files or there may be issues with the type of text elements in these files. Have some of these files been produced in other Bentley or 3rd party software packages? You mentioned OpenRoads Designer. Have these text elements been produced in this software? If you are saying you've produced new files which are also affected, are you using the seed files that come in the latest version or could they be from an much earlier version?

    It would be very helpful if you could provide example design files where we can try to reproduce your issue and possibly see whether there is some wrong with the files or text elements.

    FYI You might also like to investigate the use of the new Set Element Elevation tool which was ported from the old Civtools companion application.

    https://communities.bentley.com/products/microstation/b/microstation_blog/posts/new-in-microstation-connect-edition-update-12---set-element-elevation-tool

    Regards
    Andrew Bell
    Technical Support
    Bentley Systems

  • I haven't discounted file issues, but that leads into my opening the file in ORD, attempting the same process and having success. It seemed like a program issue and not a file issue. Although it may be a result of ping-ponging between the two programs.

    No, the files & text elements have not/were not created in any 3rd party software or ORD. Used the MicroStation seed we create files from daily. And for years, for that matter. Which would mean they were seed files from a much earlier version. I don't understand how that could be a factor. Yet. But creating a new file in MS and have the problem still occur is baffling when it hadn't happened before.

    The new Set Element Elevation tool is great, but it blows out the justification of any text. This is why I either change the Z in Properties or go the more tedious route of using Accudraw to 'move' its Z elevation by the inverse. I only use Set Element Elevation for text as a last resort.

    Uploaded the file I was working in at the time I posted. Hopefully it can shed some light on things.

    GRADING.dgn

  • This bug has changed to this new number when it was moved to the development teams new ADO logging system:

    Bug 660654: Cannot Change Geometry Z Value Of Text In DGN Files

    It has been approved for a fix in a future release, most likely the 2023 version.

     please raise a new Service Request and we can link this bug for future updates.

    Regards
    Andrew Bell
    Technical Support
    Bentley Systems

  • Still not fixed in the 2023 version. Two years, 3 versions and still waiting.

    New Service Request, Case CS0044452.

  • Andrew, I appreciate your response to my filing a new case on this issue.

    Bentley needs to hear this was a core functionality of the program that the developers broke and still can't re-implement after OVER TWO YEARS. When I submitted my new SR with a 'high' priority (because TWO YEARS), it was backed down to 'medium'. Promised to be fixed in a future release. I've been hearing that for too (two) long.

    It effects EVERY MicroStation user from U15 to 2023.

    This was an in-process case that was never attended to or resolved, then dumped awaiting one of us to put it in the new CSM Service system.

    Priority should remain 'high' given everything documented above and the lapsed time. Bentley has developers working the world-round. Six months to a year for another 'future release', to only Beta test it and probably still won't see the functionality returned is a hollow promise. Wait for the next release! Digital Twins! Four-D design!

    The workaround, as suggested and the results described by Peter Vallieres, doesn't work. It creates more work.

    It's reasons like this that people who have been using MicroStation for two to three decades (like me) have come to despise this program and Bentley for it. We're tired of making excuses to our users.

  • Priority is moslty related to how critical the issue is and how many users affected.

    Can you post an example? Did you try restoredefaults?

  • It affects EVERY user running MS CE from U15 to 2023. So, at least hundreds of thousands of users globally?

    Examples were posted above starting April 26, 2021.

    Ran restoredefaults and got this:

    Does not bode well. And no, once again, restoredefaults did not address this issue. Although it did fix a different one.

Reply Children
No Data