Microstation U14 does not show existing Tags

Hi Reimo,

Reimo said:

I have Files, where U14 german does not show Tags

I agree with Jon, without an example file it's not possible to test even the basic facts like whether language version is the issue, how it works with U13 etc.

Reimo said:

The same Files worked with older Versions like SS10.

What about "older versions" like U13?

Reimo said:

we really need a version 14.1 for this bug

All bugs are prioritized when they will be fixed. One from important prioritization techniques is how many users logged Service Ticket for the same issue.

Reimo said:

waiting for U15 is completely unacceptable !

Really? Why? Do you really think there new version will be released (which I think requires a huge amount of extra effort) just because of one reported bug? :-)))

It's crazy: When 3 months cycle was used, many people complained it's too often and it's causing a lot of troubles (not enough tested by Bentley and users, CAD admins have to check the version etc.). When now we have 6 month cycle, many users (do not know whether different or the same ones) require to release versions in a middle to fix something...

Reimo said:

The problem may be related with the Tag Range of these Elements

I agree with Jon for 100%: In my opinion the file is corrupted. What is reason for square element with size bigger than 10E30 mm (size bigger than solar system?). When a design file content is absurd (and out of normal size), to discuss whether anything is bug is a bit complicated.

Regards,

  Jan

I have uploaded the example file.

U13 and SS10 seems to work.

I have 1 Service Ticket, but whole company workflows depend on that feature.

Yes, I expect a new version - because it is a critical bug for many users. I don`t care about the amount of extra effort - this can be avoided with experienced developers and a good beta testing. Beta was promised, but never seen here. Honestly, would your customer accept a bug fixing timeframe of 6 months? Than you can be very happy, my customers give less than a week.

Declare a file as corrupt is a pretty easy solution, SS10 can work with it and does not show any signs of corruption, therefore I expect U14 to work with these files the same way. And the customer has many files like that.

I have uploaded the example file.

U13 and SS10 seems to work.

I have 1 Service Ticket, but whole company workflows depend on that feature.

Yes, I expect a new version - because it is a critical bug for many users. I don`t care about the amount of extra effort - this can be avoided with experienced developers and a good beta testing. Beta was promised, but never seen here. Honestly, would your customer accept a bug fixing timeframe of 6 months? Than you can be very happy, my customers give less than a week.

Declare a file as corrupt is a pretty easy solution, SS10 can work with it and does not show any signs of corruption, therefore I expect U14 to work with these files the same way. And the customer has many files like that.

Reimo said:

Declare a file as corrupt is a pretty easy solution

Sorry, I am not interested in further discussion when the argument against evidently wrong element ranges of tags is "it's easy solution".

Reimo said:

SS10 can work with it and does not show any signs of corruption

It's not any proof. MicroStation is quite robust and is able to tolerate many types of errors. But even when they are not presented, it does not mean they do not exist. When you do not see microbes (and they do not cause any problems in many situations), they also do not exist?

Reimo said:

therefore I expect U14 to work with these files the same way.

It's not the case of CONNECT Edition generally, sometimes because of bugs, sometimes because workflows and tools have been changed and sometimes CE is less tolerant. Depending on context, some these changes looks fine, some cause troubles.

Reimo said:

This is a example file, it does not show Tags and changes to them.

The file is weird. It's true it seems it works in V8i SS10, but twice my installation crashes (which does not happen for very long time and many other files). I do not see any difference between U13 and U14, both seems to behave in the same way (but maybe I missed something).

How tags were created? All of them have incorrect range values. And it's well described issue that when the range is not correct (in this case it's not about correct / incorrect, but complete nonsense), MicroStation in any version behaves wrongly.

In my opinion the cell should be recreated (tags detached / attached and ranges should be checked) before any further testing.

With regards,

  Jan

Reimo said:

U13 and SS10 seems to work.

I found how to duplicate the issue (both in U13 and U14), which has not been discussed yet in this thread (you should provide such description and duplication workflow).

I think is crucial to analyze where the problem is:

1. Initial state: The tags are displayed correctly. (important: it's NOT the provided file)
2. In this state, tags have correct ranges.
3. In CE U13 or CE U14 (older versions not tested), use Edit Tags tool to display table with tags in tag set.
4. After OK is pressed (it's not necessary to edit any tag), the tags are modified to have incorrect ranges and are not displayed.

This issue is not simple "tags attached to cell" , because when I tested it with some my files, it works fine. But the tag sets have not so many tags. Maybe it causes the problem?

With regards,

  Jan