|
Update to the latest version |
Scroll |
In this section:
General Information about the version update
Procedure for updating the version of operations
Features of updating operation versions in model instances
General information about the version update
As new versions of the KOMPAS-3D system are developed, operational algorithms are refined and new modeling capabilities are introduced. Consequently, the behavior of certain commands may change, as may the appearance and properties of the resulting objects.
When working in the current version of KOMPAS-3D with models from earlier versions, it is possible to update certain operations, including matings, to the current version.
Updating operations has both advantages and disadvantages.
Advantages:
•If new features—such as new controls—have been added to the command in later versions, these features will be available after the update.
•If the command’s algorithm has been refined to optimize the construction process, the result of the operation will be adjusted after the update; for example, in some cases, the smoothness of the fillet transitions will improve.
•If the command’s algorithm has changed compared to previous versions, the result of the operation will also change after the update, for example, the composition of the resulting objects.
Disadvantages:
•If certain command features have become unavailable in later versions—for example, if selecting certain object types is now prohibited or some options are missing—then these features will not be available after the update.
•If operations lower in the Construction Tree—i.e., created after the operation being updated—are associated with it, errors may occur in those operations after the update. For example, the reference objects for the operations will be lost. This is because the result of the operation is recreated when the version is updated. To correct errors, you must edit the operations to reflect the changes.
•After updating an operation’s version, its result may change unexpectedly. In this case, you can edit the result or cancel the update.
If an operation cannot be updated to the current version, it is updated to the nearest possible version. For example, a projection curve consists of several contours but has no child curves, since it was created in an earlier version of KOMPAS-3D. In the current version, curves of this type are created with subordinate objects. The update does not provide for the appearance of new objects in the Tree. Therefore, the curve cannot be updated to the current version. It is updated to the closest possible version.
|
Version updates are available only for operations of the current model. If you need to update the versions of a component’s operations while working with an assembly, switch to “in-place” or “in-window” component editing mode, select the desired elements in the Tree, and execute the version update command. |
The version update is not performed for the following objects:
•The origin or any object within it,
•objects excluded from the calculation,
•objects for which editing is disabled,
•objects created using KOMPAS-3D add-ons.
|
Updating the operation version may cause errors in the model. Therefore, if the model works correctly in the current version, has no significant defects, and does not require the use of new functionality in older operations, it is not recommended to update the operation version. |
Procedure for Updating the Version of Operations
|
Before updating the version of the operations, it is recommended that you back up the model in which the update will be performed. |
Procedure
1.Specify the operations to be updated.
The following options are available:
•In the Design Tree, which displays the Design history, specify one or more operations,
•In the Design tree, which takes the form of a model structure, specify individual operations, or a section of the tree containing operations of a specific type, or an object (such as a body) to which the desired operations are subordinate,
•In the Design Tree, select the versioms whose operations you want to update.
|
If necessary, you can specify the root element of the tree. The versions of all operations in the current model will be updated. However, this approach is not recommended, as changing the version of some operations may cause errors in others. |
2.Run Update version of selected features command.
3.This command is available if an update is available for the selected operations.
After the command is executed, the system checks whether each selected operation can be updated to the current system version. If so, the version is updated to the current one; if not, it is updated to the latest available version. If a version update is not available for one of the selected operations, that operation is ignored.
The number of operations whose versions have been updated is displayed in a message. If the selected operations already have the current version, a message appears on the screen stating that no version update is required.
Updating operations in model instances has specific characteristics.
When the version of the operations is updated, the model is automatically rebuilt.
3.Evaluate the result of the update.
•If you are satisfied with the changes, continue working with the model. If necessary, edit the operations associated with the updated one to correct any errors.
•If the result is unsatisfactory, cancel the operation.
Features of updating operation versions in model instances
When you select an version in Version Tree, the version of all operations in that version is updated. If you need to update specific operations, make the version the current one and select the desired operations in the Model Design Tree.
Version updates to operations performed in the original execution are propagated to dependent versions.
Operations in the main version and independent executions are always available for updating.
In dependent executions, only those operations whose link to operations in the source execution has been canceled are available for updating. If the link is restored, the version of the operations in the dependent execution will become the same as in the source execution. Learn more about canceling and restoring connections for execution objects...
