There is a spelling mistake in the ShipConstructor 2011 R2 Tech Notes included with the initial release. Every instance (5 total) of the command _SCFXDUPLICATEPRODDWGS should have been _SCFIXDUPLICATEPRODDWGS.

While updating multiple databases in the Administrator, the process is interrupted by the "Project Update Warning" message when switching to the next database. The warning message tells that, if the project database is updated from SC2008 to SC2009, it may take much longer time to perform the operation than it would normally do. The fact that the warning message pops up at each next database and requires the user to press the "Yes" button prevents users from letting the entire process be unattended. For example, users cannot run the update process over a night.

In the correct situation, if several databases get updated in one operation, the warning message should show up only once, before the first database started to update.

File paths that are shown in log records related to database backups contain double backslashes where single ones should be.

For example, a file path may look as follows: "E:\Projects\\test.bak." In the correct situation, it should be "E:\Projects\test.bak"

Supports are not sorted by name within assembly groups when selecting then in the Wizard dialog. In the correct situation, supports should be sorted alphabetically.

Using the "Auto Support" option with supports that have a non-zero "Angle" attribute results in misplacing the support from its supposed location. For example, consider the following scenario:

1. The user has created a support template in the Support Template catalog in Manager;
2. In the template, the user has assigned a non-zero value to the "Angle" attribute;
3. In the pipe model drawing, the user has modeled a group of parallel parts that run close to each other so that they can be supported with a single support.

If the user places an auto support from the support template described in p.2, the support will snap to the pipe lines incorrectly so that one pipe hangs unsupported. The misplacement occurs in the step when the user is asked to specify the length of the support legs.

An attempt to save a model drawing that contains a support that has a vertical base plate with all dimensions set to zero throws an error.

For example, consider the following scenario:
1. In the Support Template Catalog, the user has created a support definition that has a vertical base plate with all dimensions set to zero;
2. The user has saved a catalog and opened a model drawing;
3. The user has inserted the support into the model drawing.

If the user attempts to save the drawing, a saving error will be thrown.

The "re-dimension" command may fail to find an existing dimension style that is specified as a default dimension style for the spool drawing. For example, consider the following scenario:

1. In Manager, the user has created a spool style that employs some dimension style as the default dimension style of a spool drawing.
2. The user has generated a spool drawing based on the spool style that was created before;
3. The user has started the "re-dimension" command;
4. In the "Select Dimension Attributes" dialog the user has checked and then un-checked the "Override Spool Style Dimensions" checkbox;
5. The user has dismissed the "Select Dimension Attributes" dialog with the "Cancel" button;
6. The user has restarted the "re-dimension" command;

After the user clicks the "Ok" button in the "Select Dimension Attributes" dialog, the following message will be thrown: "Unable to find dimension style..." although the style should exist in the drawing because the drawing was generated with that style.
This is incorrect behaviour.

When the COPYBASE command is illegally used on a Pipe, HVAC, or Space Allocation part, the warning message should be displayed.

ShipConstructor doesn't support using the COPYBASE command on Pipe, HVAC, or Space Allocation parts. If the user attempts to use this command, the command will be ineffective. After the user selects all of the command inputs, nothing will simply happen. The behaviour looks confusing. In a better situation a warning message should be shown in the command line. The message should tell the user that the command is not supported for Pipe, HVAC, or Space Allocation parts.

A similar message has already been implemented for the COPYCLIP command.

In report definitions, the "Equipment Parts" section in the "Build Strategy" report shouldn't contain the "Length" field because the field doesn't make much sense for equipment.

Using the "Undo" command while modeling space allocations can crash ShipConstructor.

Horizontal moving of a grip point where a space allocation tee is connected to a space allocation cross modifies profile shapes and sizes of both parts. For example, the cross can grow in the vertical direction while the tee can shrink.

This is an incorrect behavior. Moving the grip point shouldn't change parts sizes and shapes in the direction perpendicular to the grip point displacement.

ShipConstructor allows entering illegal negative or zero values as a start value for the spool name autonumber in the "Spool Properties" dialog when the user defines a new spool.

If negative values or zero are entered, unhandled exceptions will occur. Some of the errors may result in the Spool Manager's being caught in the corrupted state where the user can't see the list of pipe spools that exist in the drawing. The "Spool Properties" dialog should correctly handle user attempts to enter negative or zero values as a start value for the spool name autonumber.

An icon is missing from the "New System" button in the System Manager dialog.

An approved spool will become modified if two or more of its parts are copied while the selection is done in one step.

Consider the following scenario:
1. A drawing contains a defined unmodified spool
2. Copy, Mirror, or Array command has been started and it's going to be used on the whole spool or some of its parts
3. Two or more pipe parts of the spool have been selected in a single selection operation. This could be a forward-drag selecting rectangle, or backward drag selecting rectangle, or the fence method, or a poly-line selection.
4. After Copy, Mirror, Array command execution finishes the spool will become modified

This shouldn't happen because, in fact, no changes have been made to the spool.

Some other details regarding this issue:
1. A spool with all pipe parts anchored will become modified in the scenario above
2. A spool will all pipe parts locked won't become modified in the scenario above

Provide the ability to specify units for the "Density" attribute in the Systems Manager. Currently, density units are not mentioned when the user selects a system in System Manager. The issue is relevant for Pipe and HVAC modules.

Export to DWG generates invalid AutoCAD drawings that still contain entities that require loading ShipConstructor components. If such a file is opened on a machine with just a plain AutoCAD installation, a crash may occur after a series of messages that tell that some ShipConstructor DBX files cannot be loaded. In the correct situation, drawings exported with the "Export to DWG" command should be free of any ShipConstructor dependencies.

An attempt to insert an equipment part that has quotation marks in the stock name produces the "Corrupt Memory" message. For example, consider the following scenario: in Equipment library in Manager, an equipment stock has been created that has quotation marks (") in its name;

If the user attempts to insert the stock instance into a model drawing, he or she may receive an error message that tells about the corrupted memory. If the user skips the message, the work can be continued without any visible problems. The error doesn't happen every time, but quite frequently.

In the Equipment library in Manager, all equipment manufacturer names are incorrectly displayed as "SSI.ShipConstructor.General.Manufacturer" in the grid view. This is a minor visual defect that doesn't affect the real data. All of the manufacturers that were selected for equipment class definitions are correctly stored in the project database and correctly displayed in the equipment stock edit dialog.

The "SCToggleOTFMode" command should be presented in the command menu and in the ribbon. Currently, the command is only available as a button on the HVAC toolbar.

Pin jigs may be drawn with incorrect lengths; in this case, they are piercing through the thickness of the plate. For example, consider the following scenario:

1. In a Hull model drawing, the user has created a surface that curves upwards;
2. The user has changed the surface properties so that the mold side lies inside the surface curvature;
3. The user has copied the surface into a pin jigs drawing;
4. The user has run the "Auto-Level All Plates" command to auto-level the surface;
5. The user has generated pin jigs.

The pin jigs will be generated from a zero level under the surface to the mold side of the plate. Because the mold side of the plate lies inside the surface curvature and represents the top side of the plate, pin jig will pierce the surface thickness until they reach the mold side.

The behaviour is incorrect. ShipConstructor shouldn't pay any attention to the location of the mold side of the surface. It should just draw pin jigs from the zero level until pins meet with the bottom side of the surface regardless of whether it's the mold side or not.

Object selection may consistently fail when some of the ShipConstructor commands are run under the Polish installation of AutoCAD.

For example, if the user launches the "Extract Marklines" command in a Hull model drawing, the command will immediately return the following string in the command line: _SCEXTRACTMARKLINES No marklines selected! After this message appears, the command will automatically terminate itself. There will be no error messages or additional steps where the user is, normally, asked to select the surface and individual marklines to extract them out of the surface. In another example, if the user launches the Hull "Split" command and doesn't select the surface and its cutting objects in advance, the command will fail with the "None of the selected cutting objects can be used to split the surface." message after its first step where the user selects the surface to split.

The errors were confirmed in the Polish installation of AutoCAD under the Polish version of Microsoft Windows. At the same time, the behaviour doesn't appear in the English localization.

Template intersection markings don't show up on the sightline template unless the "Show on plate surface" option is selected in the plate expansion dialog. For example, consider the following scenario:

1. The user has created a surface in the Hull model drawing;
2. The user has assigned a Structure stock to the surface;
3. The user has run the "Expand Surface" command;
4. In the "Plate Expansion Options" dialog, the user has switched to the "Template" tab and selected the following options:
- "Type" was set to "Standard";
- "Auto-Level" was checked off;
- "Style" was set to "Plates";
- "Create sightline template" was checked off.
- "Show on Plate Surface" wasn't checked.

After the expansion is done, the user will see that template intersection marklines aren't marked on the sightline template. If the user re-expands the surface while having the "Show on Plate Surface" option activated, he or she will see that intersection marklines appear on templates. In the correct situation, template intersection marklines should be marked on template surfaces regardless of the "Show on Plate Surface" setting state.

The "Sweep One Rail" procedure may produce incorrect results on specific geometry when the fixed X, Y, or Z option is used. When it happens, the resulting surface may not follow the original rail line correctly; instead, the surface's rail line may be scaled or stretched along the surface.

In Imperial projects, when units are set to "inches," the "Location Groups" dialog displays Position and Spacing incorrectly for marklines and datum lines.

For example, consider the following scenario:
1. The user works in an originally Imperial project
2. In the Hull module the user has run the 'Marklines from Sections' command and selected a surface
3. In the 'Location Groups' dialog, the user has selected one of the groups and clicked 'Edit Locations'
4. In the 'Locations' dialog the user has set units to "inches"

If the user enters a number in a field in the 'Position' column, the number will become greater by 1" after the user finishes editing the field. This is just one particular example of the incorrect behaviour. In general, Position or Spacing values may be calculated incorrectly in many different fashions. As a result of the issue, location and spacing values that are shown in the "Locations" dialog may be different from the actual locations and actual spacing distances in model drawings.

The issue is reproducible in originally Imperial projects. Changing an originally metric project into Imperial won't make the issue happen.

Marklines toggled as Forming Templates aren't displayed in bold font when the "Filter Marklines" option is used. For example, consider the following scenario:

1. In a Hull model drawing, the user has selected a surface;
2. From the context menu, the user has run the "Edit Marklines" command to open the "Edit Marklines" dialog;
3. In the dialog, the user has activated an option to filter marklines by type.

If the user toggles a marklines as a forming template markline, the markline name won't show up in bold fort although, normally, it should.

Adding trims or marklines to single curvature surfaces may distort their edges. For example, consider the following scenario:

1. A single curvature surface has been created in a Hull model drawing.
2. The surface has been trimmed along some of its edges.
3. A markline or another trim has been added to the surface.

If the newly added markline or trim happens to cross a plate edge that was created as a result of the initial trimming (step 2 in the scenario), the initially trimmed edge may become distorted or jagged depended on the particular shape of surface.

Turning the "BEVEL_OFFSET_PATH" off in the controller file may result in the bevel angle code's missing from the output.

In the correct situation, setting "BEVEL_OFFSET_PATH" to "YES" or "NO" should only affect coordinates but not the bevel angle code.

In NC-Pyros, the "Generate Complete Path" command can work slowly if shapes contain arc segments of very large radii.

Usually, the behaviour occurs with arc segments that have the start angle greater than zero and the end angle is slightly less than 2*PI. The arc direction should be clockwise.

The Input Filter -> Origin Position value isn't filled correctly when the data is loaded storage from the profile file that stores user preferences.

For example, consider the following scenario:
1. Create a new NC-Pyros preferences profile or load an existing one;
2. Use menu command <File\Preferences> to open the 'Preferences' window;
3. Go to the third Tab called 'Input Filter';
4. Change Radio-switcher in the 'Origin Position' group;
5. Save preferences in an external preferences profile file.

After reloading preferences from the preferences profile, the 'Origin Position' information on the 'Input Filter' tab won't be recreated from the file correctly. The rest of the settings will be loaded correctly.

Plate-nested penetration components ask for an update after the containing structure model drawing is saved. For example, consider the following scenario:

1. The user has created a penetration of a pipe part through a Structure plate;
2. The penetration has a doubler as a penetration component;
3. The user has nested the doubler in a plate nest drawing;
4. The user has reopened the structure model drawing that contains the penetration;
5. Without doing any changes, the user has saved the structure drawing.

If the user opens the plate nest drawing, the user will get the message that the nested doubler part has changed and needs to be updated. In the correct situation, ShipConstructor shouldn't ask to update nested parts if the parts don't change.

A fatal error and a crash will occur if a pipe with the zero minimum length defined in the Pipe Stock catalog is assigned with the zero length in the model drawing.

BOM table items that are retrieved with the Pipe Hanger Accessories collector are not labeled in viewports.

For example, consider the following scenario:
1. A pipe arrangement drawing contains, at least, one pipe with a hanger on it
2. There is an accessory package that goes with the hanger
3. A BOM table with the Pipe Hanger Accessory collector has been inserted into the arrangement drawing
4. The Pipe Hanger collector is not among the BOM table collectors; otherwise, Issue 15991 will take place

If the user relabels all parts in the viewport out of the BOM table, Pipe Hanger Accessory items won't be labeled. Manual relabeling items from parts also won't work for hanger accessories.

This is incorrect behavior. In the correct situation, labels should be visible for hanger accessories as they are normally visible for pipe connection accessories.

In the Manager, end treatments for branches and crosses are transferred incorrectly into the stock catalogue when importing a pipe stock definition.

In case of a branch, "End Treatment 2" and "End Treatment 3" will be missing the size quality. Those end treatments will only be characterized with end treatment types. In case of a cross, "End Treatment 3" and "End Treatment 4" will have the same issue. Normally, end treatments are combinations of an end treatment type and a pipe size.

Because the size characteristic is missing for some end treatments in imported branches and crosses, these stocks will be modeled incorrectly. Missing sizes will be supplemented by copying the "End Treatment 1" size. As a result, a stock that used to have different end treatment sizes will have equal end treatment sizes after importing it.

Additionally, when importing branches and crosses into a pipe stock catalog:
1. New Size Definitions that are used by "End Treatment 2" and "End Treatment 3" for branches, and "End Treatment 3" and "End Treatment 4" for crosses won't be added to the catalog
2. No errors or warning messages arise during the import process

In Hanger Stock Catalog in Manager, in-use Nominal Sizes and Material Grades can be disassociated from in-use hanger stocks.

For example, consider the following scenario:
- A hanger stock is associated with nominal size A and material grade B;
- A hanger part instance has been inserted into the model to hang a pipe with nominal size A and material grade B;
- The association with nominal size A and material grade B can be removed from the hanger stock thereby invalidating the hanger stock instance in the model.

In the correct situation:
- The In Use column of the Hanger Stock Catalog 'Nominal Size' dialog and 'Allowable Material Grades' should only show in use if the selected hanger stock is hanging a pipe with the particular nominal size or material grade;
- The user should not be able to disassociate a nominal size or material grade from a hanger stock if they are in use with a hanger stock;
- The user should be able to generate a usage log for the hanger stock and material grade or nominal size combination.

The merge process will fail on Synchronizing Pipe Part Names if the part names don't contain the Auto Number element. For example, consider the following scenario:

1. The user is working in a split project;
2. A naming convention for pipe part names consists of only one field: GUID. At some point, SSI was suggesting users to have such a naming convention to avoid naming conflicts saving errors in pipe model drawings (Issue 15854);
3. The user is merging the split project into the master project;

After the merge project reaches the "Synchronizing Pipe Part Names" stage, an "index out of range" exception will occur. The unhandled exception will abort the merge process making it impossible integrate changes from the split project into the master project.

Project Hierarchy UDAs that are removed by a remote project should disappear from the local project after merge/refresh. Currently, PH UDAs can only be added to assemblies or modified to match; however, removing UDAs is not handled.

If master/split project is missing Unit Drawings it doesn't control, an error message will happen when Navigator tries to recreate the missing drawings. For example, consider the following situation:

1. Unit drawings are controlled by the remote project;
2. The local project has Structural control over the unit to which the unit drawings belong;
3. The remote project sends a split, merge, or refresh file;
4. Some unit drawings are missing from the split, merge, or refresh file (perhaps, they were manually deleted before the file was created by the remote project);
5. Depending on the file type, the file is used locally to accomplish one of the following: recreate the split project, update the split project, and merge the split project with the master;
Note: no errors will appear at this point.

If the user starts the local project and opens Navigator, an error message will be thrown when ShipConstructor recreates missing unit drawings. The error will happen one time only when Navigator is opened for the first time. In the correct situation, the error message shouldn't appear at all. ShipConstructor should silently recreate missing unit drawings, but, because the local project doesn't control these drawings, the drawings should be recreated empty.

Moving nested profiles directly from one nest into another results in a database error upon saving the drawing. For example, consider the following scenario:

1. The user has created a nest drawing with, at least, two nests in it;
2. The user has nested some flatbars and twisted stiffeners;
3. The user has run the MOVE AutoCAD command and moved a profile part from one nest directly into another.

If the user attempts to save the nest drawing, a database error will occur. The error happens only when profile parts are moved between nests. If a plate part is moved, the drawing will be saved correctly.

In the "Report Definitions" dialog, the space character is missing in the name of the "BuildStrategy" section. In the correct situation, the section name should be recorded as "Build Strategy."

In the Edit Levels dialog, an attempt to swap levels in the secondary Product Hierarchy tree fails with an error.

Density units are incorrectly displayed with an "A"-like symbol at the end of the text string in the Materials catalog in Manager.

In Manager, the hourglass (wait) mouse cursor doesn't change to its regular state after the User Permissions dialog is loaded. All of the buttons in the dialog are 100% functional; however, that the cursor appears as if waiting was still in progress looks confusing to users. In the correct situation, the cursor should take on its normal image after the dialog is loaded.

Entering data in the Support Template catalog should be more convenient.

Currently, ShipConstructor validates the entire support template record when the user changes any of the individual fields. It leads to a situation where the user it required to fill all of the fields in a specific order; otherwise, conflicts may arise. If a conflict happens, the user won't be able to apply the value in the field until superior fields have some meaningful values.

In the correct situation, the user should be able to enter record values in any order, and the validation should happen upon an attempt to switch from the current record to any other.

Several changes are proposed to improve usability of the "Export to DWG" command:

1. Remove the "Help" option;
2. Ensure that the command can be cancelled with the ESC key;
3. Use Enter to finish the current step of the command;
4. Allow using configuration files to store user settings in the XML format.

The "Nest Scrap Utilization" field truncate value decimal digits instead of rounding them, which leads to incorrect "Nest Utilization" and "Nest Scrap Utilization" calculations. For example, consider the following scenario:

1. The user has created a nest drawing;
2. The user has nested some parts so that the nest scrap utilization equals 6.99% (the value choice is arbitrary).

If the user inserts a keyword in the plate nest drawing or displays the "Nest Scrap Utilization" column in the Nest Manager (SC Nesting\Nest Manager), he or she will see that the "Nest Scrap Utilization" value is shown as 7%, and the "Nest Utilization" value is shown as 93%, which is correct. However, if the user generated a report, the "Nest Scrap Utilization" value will be shown as 6% and the "Nest Utilization" value as 94% in the report, which is incorrect.

The "Nest Scrap Utilization" and "Nest Utilization" fields should be rounded in reports to the number of decimal places specified, rather than simply truncating the decimal part of the "Nest Scrap Utilization" value.

Denis 5/12/2010: The Dec Places field for NestUtilization cannot be modified. you should be able to set this.

Adding Required UDAs to Hangers creates database records that record the same default UDA values for all types of hanger stocks at once. For example, consider the following scenario:

1. The user has selected a UDA and assigned it as Required to a hanger type;
2. The user has specified some default value for the required UDA.

Inside the database, there will be multiple records created that record the same default value for every stock type. The extra records in the database are not only abundant but can lead to potential issues down the road.

Boolean fields should not be available as summary fields for groups in report definitions. Currently, it is possible to select Boolean fields as group summary fields. The Boolean field represents an attribute that can only have two possible values such as "Yes" or "No," or checked and un-checked.

ShipConstructor displays some compatibility issues with the Blue Beam software (Bluebeam PDF Revu CAD Edition). When the Blue Beam software is installed along with ShipConstructor, the following ShipConstructor commands and dialogs may not work:
1. M-Link dialog;
2. Update assembly drawings;
3. Product Hierarchy dialog;

As a workaround, turning off the Blue Beam plug-in is recommended while working in ShipConstructor.

The Bluebeam PDF Revu CAD Edition was designed to enable one-button PDF document creation from within AutoCAD, Revit, SolidWorks and MS Office. The focus of this software lies within large-format drawings making it easy to convert drawings of any size while maintaining quality and saving time.

In reports and BOMs, stiffener UDAs that are required and have default values may display the default value instead of the value that was assigned by the user.

This incorrect behaviour is a consequence of an internal non-critical database error where records that store default values that are assigned to stiffener UDAs get multiplied in the database. In the correct situation, the database should have one default value record by each UDA assignment.

Support non-primary Product Hierarchies in the "Predefined Assembly Drawing Format" dialog that is available in Manager under General -> Production Output -> Predefined Assembly Format. Currently, users are not allowed to select alternative product hierarchies in this dialog. By default, the main build strategy is used.

The first time the user opens ShipConstructor 2009 and connects to a project, the Licensing dialog opens, but since there are no license servers currently set, the dialog throws a License Error stating "Unable to connect to server." The same error will be thrown if an existing server is currently unavailable at its last network location. The error message should be appear in a user-friendly manner, and it should take into account two different scenarios:

1. There are no license servers set in ShipConstructor;
2. One or more existing license servers are currently unavailable at their network locations.

Automatic database backups produce files where the database version number is missing from the file name. In the correct situation, the database version should be integrated into the file name using the same format as the one that is used by the "suggested" backup when the user updates the database for example.

When registering into a project, in the "Licensing" dialog, users may see an inaccurate message that says, "License is not PS&M."

The message is displayed when no licenses are available for a certain module. The situation has nothing to do with the Project Split & Merge. The message text should be reworded to better correspond to the situation that it refers to. For example, instead of displaying the text such as "License is not PS&M," the "Licensing" dialog could just say "No Licenses."

The description at the bottom edge of the "Project Settings" dialog contains a couple of typos: "This setting indiacates the usits that the AutoCAD geometry will be drafted in." In the correct situation, the text should be: "This setting indicates the units that the AutoCAD geometry will be drafted in."

Values of the "Component" attribute of profile trims are named confusingly in reports. For example, when trimming a stiffener in a Structure model drawing, the Component attribute can take the following values:

1. All
2. Web
3. Flange
4. Both Flanges (for channel and W profiles)
5. Bottom Flange (for channel and W profiles)
6. Top Flange (for channel and W profiles)

If a report is generated, Component values that used to be "Flange," "Both Flanges," "Bottom Flange," or "Top Flange" in model drawings will appear as "Flange All" in the report. This is an incorrect behaviour. The reported trim component value should exactly repeat the value in the model drawing.

Opening of Structure model drawings that contain Standards Parts with marking on them can be slow.

For example, on a specific computer that has a reasonable performance speed, opening a drawing that contains 35 standard plates and 24 standard stiffeners may take about 20 seconds. If the number of standard plates is 60, and the number of stiffeners is 26, the loading time will be about 1 minute.

Opening and then closing a Structure model drawing when not connected to a project may crash ShipConstructor.

Mirrored twisted stiffeners may fail to have the same volume, surface area, and length. For example, an original twisted stiffener may have the following attributes:

Volume : 1757611.7281 mm^3
Surface Area: 361668.4 mm^2

If the stiffener is mirrored, the mirror may have slightly different values for the same attributes:

Volume : 1757626.7006 mm^3
Surface Area: 361670.9 mm^2

Some of the identical Construction Lines may break off from the group of their related objects as a result of modification to one of the lines. For example, consider the following scenario:

1. Two instances of ShipConstructor are running simultaneously.
2. Each instance has a Structure model drawing open. The drawings are not the same.
3. Each drawing contains a construction line that is identical to the construction line in the other drawing.
4. The user has moved a grip point of a construction line in Drawing 1. The change was applied to all related objects.
5. The user has copied the construction line in Drawing 2 creating a new identical line.
6. The user has saved Drawing 1.
7. The user has saved Drawing 2.

If the user checks the part information of the newest construction line in Drawing 2, he or she will see that the part has two identical construction lines, one is in Drawing 1 and another is in Drawing 2. If the user reloads Drawing 2 and checks the part information of the same construction line again, he or she will see that the part doesn't have any related objects. The relationship will be silently broken after the user reloads Drawing 2. This is incorrect behaviour. In the correct situation, all of the construction lines should remain related as identical.

Identical construction lines cannot be added to plate parts in one operation when the SCADDOBJECTSTOSTRUCTPART command is used. For example, consider the following scenario:

1. In a Structure model drawing, the user has modeled a plate part a couple of identical construction lines that are not used by the plate part;
2. The user has started the SCADDOBJECTSTOSTRUCTPART command and selected the plate part. Then, the user has selected both construction lines to be added to the plate part in one step.

After the command is finished, the user will see that only one of the two construction lines was added to the plate, which is an incorrect behaviour. The issue doesn't occur when non-identical construction lines are involved.

Replacing a Hull trace line with another Hull trace line does not transfer construction lines that were offset from the old hull trace line over to the new line. For example, consider the following scenario:

1. In a Structure model drawing, the user has offset a Hull trace construction line;
2. The user has run the Replace Hull Trace command (SCREPLACEHULLTRACE) on the Hull trace line;
3. The user has selected another Hull trace line to use it as a replacement for the first line.

After the operation is finished, the user will see that lines that were offset from the original Hull trace line remained at their old locations. In the correct situation, offset line should migrate over to the new hull trace line.

When plates with faceplates are mirrored, the resulting faceplates may fail to correctly acquire the mirror relationship. The carrying plate parts, however, will be related as mirrors.

The issue has a number of consequences:
1. Faceplate part names can be different from names that mirrored parts should have;
2. The "Check Group DWG" command will be saying that the relationship between the two faceplates doesn't have any justification;
3. In the "Part Information" dialog, the two faceplates won't be shown as related mirrors.

Text marking with blank text values should be prohibited on parts.

Currently, using the "Edit Component" tool, it is possible to set the text value of a marked text object into the blank state. As a result, the marked text object will be still assigned to the part, but there will be no way how to select, modify, or remove the text after the text value is made blank. This incorrect behavior leads to a number of negative consequences; for example, the Text Style that is used by the text marking will be locked in the drawing without the ability to purge it out.

Undoing modeling a stiffener on a pair of related plates may lead to a save error in a specific scenario. For example:

1. The user has modeled a plate part;
2. The user has copied the plate part to create an identical one;
3. The user has modeled a stiffener to one of the plate's surface.
4. In the "Update Related Parts" dialog, the user has confirmed creating an identical stiffener on the second plate;
5. The user has quick-saved the drawing;
6. The user has undone quick-saving the drawing;
7. The user has undone modeling the stiffener (overall, there should be 2 undo steps after saving the drawing);

If the user attempts to save the drawing now, a saving error will happen.

The "Check Group DWG" operation should try fixing bevels that are incorrectly assigned to plate parts when the user chooses the "fix errors" option.

The user may run into a situation when an incorrect bevel standard is assigned to a plate part. For example, consider the following scenario:
1. The user has created a plate part;
2. The user has assigned a bevel standard that is only applicable to certain stock types to the plate;
3. The user has changed the stock of the plate part to the one that is unsupported by the bevel standard that is currently assigned to the plate.

If the "Check Group DWG" operation identifies an inconsistency between the plate stock and the associated bevel, it should try fixing the error by doing the following things:

1. Under the same bevel code, the procedure should search for bevel standards that are associated with the modified plate stock;
2. If a new standard is successfully found, it should be used with the plate;
3. The fix should be logged in the log file.

A snipe endcut applied to a slightly bended faceplate may leave a small sliver on the faceplate. The behaviour was reproduced in a situation where:

1. The endcut was applied to a faceplate that was created along a slightly curved edge of a plate.
2. The endcut was represented by two snipes on the opposite sides of the web.

Overall, chances to reproduce behaviour vary depended on the shape of the faceplate to which the endcut is applied to.

Plate parts with different geometric shapes may still be considered identical if a specific modification is applied to their identical construction lines. For example, consider the following scenario:

1. The user has modeled a plate part which borders are defined by a set of four straight construction lines;
2. Inside the plate part, two construction lines are related as identical;
3. The user has copied the plate part and all its construction lines, so there are 2 identical parts and 8 construction lines. (Four construction lines should be related as identical.)

If the user moves one of the construction lines and, in the update related objects dialog, unchecks one of the related construction lines, parts will get modified and their shapes will become different. However, if the user opens the part information dialog for either of the parts, he or she will see that the parts are still considered to be identical regardless that their shapes are different. In the correct situation, the identical relationship should be broken.

A fatal error and a crash will occur if the user clicks "Save" or "Cancel" while routing a polyline in the profile cutout drawing. If the polyline routing is finished before the button is clicked, everything will work as it should. The error is only reproducible when the button is clicked while the polyline command is in process.

Applying a shoulder endcut to a curved stiffener leaves a sliver in the stiffener solid.

Total Area and Total Weight fields in BOM tables fail to display values for assemblies in assembly drawings. For example, consider the following scenario:

1. The user has created an assembly drawing with several assemblies included;
2. The user has inserted a BOM table that uses the "Assembly" collector and contains "Total Area" and "Total Weight" fields;

After the user updates the BOM table, the "Total Area" and "Total Weight" fields will be empty. This is an incorrect behaviour.

An error occurs on an attempt to import a weld standard that uses a text style that is not defined in the current project. For example, consider the following situation.

1. A weld standard has been defined in the project A.
2. The weld standard has an associated weld process that uses a keyword of a specific text style.
3. The user has exported the weld standard from the project A.
4. The user is importing the weld standard into the project B.

If the project B doesn't have the same text style (Manager\General\Text Styles) that is used by the weld standard, an unhandled exception will be thrown. In the correct situation, the error shouldn't happen. ShipConstructor should automatically add the text style definition that is required by the weld standard.

Introduce the new SCFIXDUPLICATEPRODDWGS command to repair duplicate production drawing records after updating to SC2011R2.

This is a maintenance command that should only be run once after the user upgrades the project to SC2011R2. The user should run this command if he or she sees that some of the production drawing names contain "$DUPLICATE$" text in the Navigator dialog. The command should be typed in the command line while any ShipConstructor drawing is opened. The command is not presented in menus or toolbars. After running the command, all records that contain "$DUPLICATE$" in drawing names, will disappear from the Navigator dialog.

More detailed information about this command is available in the Production manual.

Upgrade the set of performance monitoring commands to more powerful Diagnostic Manager to monitor performance, memory usage, and network traffic.

To replace the old functionality, the old commands such as SCSPM, SCDPM, and SCEPM should be disabled. Then, Diagnostic Manager should be made available. The commands to work with the diagnostic manager are: SCDiagnosticStart, SCDiagnosticStop, SCDiagnosticShow, SCDiagnosticExport, SCDiagnosticExportText, and SCDiagnosticManagerReset.

Automatically delete incomplete or corrupted *.rfs or *.mrg files that may occur as a result of an error during the create merge or create an update file operation. Currently, incomplete and corrupted merge or update files may be produced by ShipConstructor. In most of the cases when an error occurs, users are informed of the error; however, sometimes, the notification may fail to appear depended on how the error happens (Issue 16146).

The fact that an incomplete or corrupted file may be created is dangerous because the file may still be usable in the merge or refresh process, and it can affect the project database in a later operation. ShipConstructor should mark or delete corrupted *.rfs or *.mrg files automatically.

Improve usability and functionality of the "Project Revisions" dialog. The following improvements are suggested:

1. Provide a new column such as "Revision Sub Type";
2. Redesign the "Revision Type" control so that it's easier to work with revision types;
3. Move "Plate Nest" and "Profile Nest" revision categories from the "Stocks" group under "Structure";
4. By default, select all of the revisions type to display in the dialog;
5. Users are now warned if

Provide the ability to batch-update production drawings. The update operation should work similar to "Update Model & System Drawings."

In Profile Nest reports, provide a field that displays the Cumulative Length of the profile stock measured from the beginning of the stock up to the current nested part.

The cumulative length value should reset to zero in the beginning of each profile nest. Within each nest, the field should report cumulative length of all profile parts, green material, and kerfs that precede the current part. A similar field used to exist in profile nest reports in SC2005.

Production - Bill of Materials - Add the following columns to BOMs: "Total Length with Green," "Total Weight with Green," and "Total Volume with Green"

In the "Edit Report" dialog that can be opened from the "Report Definitions" dialog, enhance the "Repeat Header" option with three possible values:

- Once Per Section (don't repeat the header on page breaks)
- Once per Page (don't repeat the header if the section occurs multiple times on the same page)
- Each Section Page (repeat the header for all section/page breaks).

Currently the "Repeat Header" option, which is available for each section inside the report definition, offers two options only, "Yes" and "No."

Provide a new field such as "Faceplate Offset Position" in reports. The field should present the "Position" value that tells what the faceplate orientation relatively to its plate is. The "Position" attribute is set by the user in the "Faceplate Properties" dialog.

Transfer the section that explains how CUIs work from the Structure manual to the Project Management manual and extend the section with additional explanation.

Currently, the CUI explanation is incorrectly included into the Structure manual (page 7) although it is related to the entire ShipConstructor product. The section is very short and lacks some detailed information on why AutoCAD needs several CUI files, what is stored in each of the CUI files, what is the correct way of customizing the user interface through CUI files, what direct steps that need to make a customization are, how to preserve custom changes and apply them to the next installation of ShipConstructor, etc.

The section should include examples and good practices. For example, it may instruct project administrators on how to setup the product when some CUIs are loaded from the central network location.