Projects with V8i and Connect

Good morning,

We are venturing into trialing CE before we fully roll it out company wide. Before I implemented it as a trial, I took this opportunity to fix a few minor issues with out current workspace, such as tweaking dimension styles and text styles, cleaning up seed files, and reorganizing cell libraries (as well as a couple other minor things probably). These edits were done in a "new" CE workspace that is separate from the V8i workspace. With the exception of some new cell libraries, all the file names are the same, but have been reorganized within the CE workspace. While running our trial, we have created new projects within CE and have also tried to bring older V8i projects up to CE, and either process has resulted in many bugs. One issue was the scales.def that had to be updated for the new format in CE. As far as I know, the V8i version and the CE version of the scales.def are essentially the same information, just format difference. Once I worked that out, it cleaned up some issues, but still more persist. We will get strange behavior with the text, dimensions, custom line styles, and references. It seems like the issues happen more often when we go back and forth from the V8i workspace to the CE workspace. For instance, we will be working on a file within CE and then there is an issue with it. Instead of stopping the production, one of my guys would open the file in V8i and continue working while I try to address the issue. Once I fix the issue, he would open it back up and continue in CE.

Is this back and forth creating more issues as we go? What would be the recommended transition to CE? Do we have to move the whole office at once? Is there a way that we can work on the same project with a mix of V8i and CE? I understand my current setup would require maintaining two workspaces and any change I make in one, I would need to make a similar change in the other so they are in sync, but is it creating other issues as we do this?

Thanks,
Ken

Parents
  • I would not recommend using the 2 versions on one project. You don't have to move the whole office at once, but I would say possibly taking a new project or a smaller existing project and work CE into the transition. You can have both V8i and CE on the same box, but again - I would keep them separate as far as projects and configurations.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Is this to say that CE is not backwards compatible for all intents and purposes? If this is the case, it makes migrating to CE a bit riskier and much more complex. Am I missing something?
  • FWIW Parametric Cells don't display with the proper symbology in V8i. I think I filed on that one some time ago.
  • Unknown said:
    I have noticed that if I open a file V8i with a hatch pattern, and then go to CE and try to "Match Pattern Attributes", the annotation scale gets changed to 1:1. This doesn't change any text or dimensions that are currently placed, but the 1:1 scale will be applied to any new text and dimensions.

    Defect # 421510 is reported for the same. Thanks for reporting.

    Unknown said:
    There was an instance that kept happening (I think in one file, so it may be an anomaly) where we would activate a reference, draw a rectangle, and then hit undo to get rid of the rectangle. As soon as undo was invoked, MS would completely crash without warning.

    We could not reproduce this at our end. You mentioned in your post that this is file specific. Providing DGN which cause a crash, that would help a lot.

    Unknown said:
    We also have an issue when we edit text that is underlined, when we accept the change, the underline will be touching the bottom of the text. This would happen even if we begin to edit the text, but not change anything, and then accept it. This didn't happen in V8i, so I am curious as to how to address it.

    Defect # 347102 was filed for this issue. It will be fixed in upcoming release.

    Unknown said:
    Those are the issues that I recall so far. There were some issues early on with the Scales.def file not matching the older version exactly, but I think that has been cleared up.

    Scales.def is changed in MS CE so it is expected to have few differences.

    ~Sumit



  • Unknown said:
    Ken Harrison
    We also have an issue when we edit text that is underlined, when we accept the change, the underline will be touching the bottom of the text. This would happen even if we begin to edit the text, but not change anything, and then accept it. This didn't happen in V8i, so I am curious as to how to address it.

    Defect # 347102 was filed for this issue. It will be fixed in upcoming release.

    Sumit.  There is a similar issue with the Background Settings for text.  Units are not getting read or stored properly.  I don't believe its been fixed yet.

    Edit:  Theres also something screwed up with line spacing.

  • Sumit,

    If I see the problem happening again with the sudden closing of MS, I will let you know and pass along the file. However, I don't see us getting in and working with CE anytime soon, at least until the next release. We just can't afford to be the ones testing the software for these common issues.
  • Hi Ken,
    Greetings!

    Apologize for inconvenience caused.

    Out of four we could reproduce one and has plan to fix them in upcoming release.

    2 crashes are random and those were not reproducible at your end and our end as well, with information provided. If you have submitted crash to our server, I will try to search by your name and see if stack can be generated to analyze and fix it.

    Sharing minidump and exception log help in fixing random crashes.

    Scaled.def is expected change.

    ~Sumit



Reply
  • Hi Ken,
    Greetings!

    Apologize for inconvenience caused.

    Out of four we could reproduce one and has plan to fix them in upcoming release.

    2 crashes are random and those were not reproducible at your end and our end as well, with information provided. If you have submitted crash to our server, I will try to search by your name and see if stack can be generated to analyze and fix it.

    Sharing minidump and exception log help in fixing random crashes.

    Scaled.def is expected change.

    ~Sumit



Children
No Data