ShipConstructor Latest News

12.08.2009 - ShipConstructor Increases Parts per level by 50%

03.03.2009 - ShipConstructor 2008 R4.0.1 has been released on the ShipConstructor website as an update. This update can only be applied to ShipConstructor 2008 R3 or later. This update uses a new database version (1.4.1.0) and therefore you will have to update your databases. R4.0.1 contains many new features and improvements which are described in the R4 What's New document.
Important! ShipConstructor 2008 R4.0.1 requires 1200 level lock licenses. Do not download this release until you have contacted your local sales representative to update your locks.
The update has been posted on the Support Page
You can find TechNotes (whitepaper) for R4.0.1 here: http://www.shipconstructor.com/support/sc08_technotes/SCLatestReleaseNotes.html
Object Enabler R4.0.1 has been released to support R4.0.1.

02.01.2009 - ShipConstructor 2008 R3.0.3 has been released on the ShipConstructor website as an update. This update can only be applied to ShipConstructor 2008 R3 or later. This update uses the same database version as R3 (1.3.3.2) and therefore you do not have to update your databases.
Important: This update contains a critical fix for R3 nesting and is recommended for all R3 users. Please read the following Knowledgebase Article: http://www.shipconstructor.com/kb/questions.php?questionid=1757
After installing the update, follow the steps outlined in the KB article.

The update has been posted on the Support Page. You can find TechNotes (whitepaper) for R3.0.3 here: http://www.shipconstructor.com/support/sc08_technotes/SCLatestReleaseNotes.html The R3 Object Enabler is compatible with R3.0.3.

20.11.2008 - ShipConstructor 2008 R3.0.2 has been released on the ShipConstructor website as an update. This update can only be applied to ShipConstructor 2008 R3 or later. This update uses the same database version as R3 (1.3.3.2) and therefore you do not have to update your databases.
The update has been posted on the Support Page
You can find TechNotes (whitepaper) for R3.0.2 here: www.shipconstructor.com/support/sc08_technotes/SCLatestReleaseNotes.html
The R3 Object Enabler is compatible with R3.0.2.

28.10.2008 - ShipConstructor 2008 R3 has been released on the ShipConstructor website as an update. This update can be applied to any version of ShipConstructor 2008. This update uses database 1.3.3.2 and therefore requires you to update your project databases using Administrator.
The update has been posted on the Support Page
You can find TechNotes (whitepaper) for R3 here: http://www.shipconstructor.com/support/sc08_technotes/SCLatestReleaseNotes.html
Object Enabler R3 has also been released to ensure compatibility with SC2008 R3 and previous versions.

Before installing R3, please read the following Knowledgebase Articles:

How to migrate your old ShipConstructor AutoCAD Profile to R3

Message when launching R3 for the first time: CUI file “shipconstructor2008.cui” is an incompatible format and can not be overwritten.

09.02.2008 - ShipConstructor 2008 R2.1 has been released on the ShipConstructor website as an update.

ShipConstructor 2008 R2.1 includes ShipConstructor’s revolutionary new feature: Split and Merge. Split and Merge is designed to support work on a single ShipConstructor project by multiple disconnected project sites. It allows project administrators to partition responsibilities in a project to any number of split projects through creation of project splits and their associate project split file. Geographically separated users use the project split file, given to them by the master project administrator, to create a ShipConstructor project on their local project server. The project created from the split file behaves like a normal ShipConstructor project but is aware of its relationship to the master project and the areas of responsibility delegated to it by the master. Likewise, the master project is aware of all split projects to which it has delegated areas of project responsibility.

As work progresses on a partitioned project, split projects create and send merge files to the master project for processing. The merge files will update the master project with all work performed against the split project in the areas of responsibility delegated to it by the master. Additionally, the master project creates and sends refresh files to the split projects for processing. The refresh files will update the split projects with project content contained in the master and other split projects. Upon completion of the project, the master project contains the complete model including work performed by all project participants.