Reference file incorrectly offset in y direction

We sometimes experience problems with attached reference files that are not properly located. The problem arises both with attached models from the same design file, but also when attaching models from other design files. In the clip below you can see an example where the same model is attached twice but is shifted approx. 2.6m in reference slot 1 (the designfile is attached). The only difference i can see is that the orientation is inaccessible for the reference in slot 1 while the rotation is 0° for the reference in slot 3.

We use Bentley Map SS4 but the problem is the same in Opencities Map Update 5, which is where the screenshot comes from.

I hope someone can help us.

Test_Lodsejer.dgn

Parents
  • FYI

    We have been testing a little bit more, and are now able to reproduce the problem. We are in the middle of a transition from V8i to Connect, and the problem occurs when we work on DGN files created in V8i in Connect products. What causes the problem however, is a 3. party product from Addin.DK.

    We are currently using the following software:

    • Bentley Map SS4 / OpenCities Map Update 5 (this is our primary product)
    • MicroStation V8i SS4 / MicroStation Connect Update 14

    We can reproduce then problem in the following way:

    1. Create a new DGN file in V8i based on our old seed files, with one of the Danish geographic coordinate systems (GCS) attached fx. DKTM2.
    2. In V8i attach other DGN files with the same GCS attached as Coincident or Coincident World.
    3. Open the DGN file in Connect version.
    4. In Connect the GCS gets a different name DkTM2 (with a lower case k) which causes the products from Addin.DK to belive that the DGN file dont have a GCS attached. There fore we need to attach the GCS again, which is done via Addin.DK Menu.
    5. Evrything seems to be OK until we close the DGN file and open it again. Now the references files will have shifted a bit in the Y direction.

    It is not complicated to work around the problem. When we use Bentley functionality to attach the GCS the error doesn't occur. But it is still a problem that the error can occur at all.

    The Addin.DK Menu is a managed DLL writen i C# using the Interop API to attach the GCS to the DGN file, so perhaps it is in the Connect Bentley.Interop.MicroStationDGN API the problem lies.

  • The Addin.DK Menu is a managed DLL writen i C# using the Interop API to attach the GCS to the DGN file

    Good detective work in analysing and resolving your problem!

    perhaps it is in the Connect Bentley.Interop.MicroStationDGN API

    Perhaps it is, and perhaps it is not.  Surely the developer of Addin.DK is in the best position to answer that?

     
    Regards, Jon Summers
    LA Solutions

Reply Children
No Data