In updating to release 10.16.00.80, users are reporting default line styles not plotting correctly. Specifically styles 5 and 7, which we use to represent topography. This ONLY effects users that are updated to release 16.
Plot driver has not changed, file is not any different.
If user is backed down to 10.15.02.11, everything is fine.
How things look in U16:
How things look in 10.15.02.11:
Adding plot configuration file as well as a small section of the topography file. Again, users that do not have U16 aren't effected. All files were created in Connect with a company seed file. Nothing about the file, the way it was started or constructed has changed. The only common denominator is the update to Connect 10.16.00.80.
6404.blackwhite.pltcfg
8688.TOPO.dgn
Thanks for taking a look.
P.S. I'll add that these are line strings and complex chains. They are referenced/copied from a shapefile tile of our local county contours.
I would file a service ticket for this. It would appear that something has changed in the way Microstation is interpreting linestyle plotting between vertices between versions (which would be really bad...). Bring this to Bentley's attention so they can at least catalogue the defect :-P
I will ask, do "plain" lines come out fine? Just to confirm that it's vertexed elements.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
After reviewing the service ticket results and weeks of sending files back-and-forth, the result/determination of this was reduced to a Medium priority and was basically reported if things work in U15, then keep using U15 and don't go to U16.
This was frustrating and ultimately disappointing. I don't know if there's a fix coming or if this will just evaporate and not end up addressed/followed up on.
Actually no, Tuan. My updating this thread and our back-and-forth shook loose an update. There's a defect # now and either the Support Engineer or I will follow-up with posting it!
that's great Stephen, keep the "update" coming then I guess
"The defect number or we call it as a bug now, is internal within Bentley. You will not be able to access it.
Once we receive communication form dev team, I will update you on the topic. You may update other users that this is found to be a defect in application and we will receive update form Bentley once the issue is fixed."
That's weird. It could be a new Bentley policy, but I and other users have been given filed defect numbers all the times for the sake of tracking them.
FYI, defect number is 697510