Managing CATDrawing Documents in ENOVIAVPM |
If you use the command Load PDM
Context in ENOVIAVPM context with VPM 1.5PTF18, a new CATProduct will be
created in V5, instead of the assembly data being loaded in the
CATProduct which is already opened and linked to the CATDrawing. On this
level, use the following methodology: do not open the CATProduct before
using the command Load PDM Context on the CATDrawing. This behavior is corrected on VPM 1.5PTF19 and later PTFs. |
Dimensions upper text |
For ANSI or ASME drawings created with V5R7SP1 or earlier: existing dimensions upper text may swap from edge to center. |
Dimension line/Extension line thickness |
For drawings created with R6GA and
R6SP1, dimensions thickness may change when opening the drawing. Workaround: To bypass this problem, go to Edit > Search. In the Advanced tab, select Drafting for the workbench and Dimension for the type, and click the Search button. Select the dimensions to modify and click OK. In the contextual menu, choose Properties, and then in the Dimension line tab, set the line thickness. |
Section views |
Patterns are not applied to sections which are tangent to 3D faces. |
Annotation thickness |
When swapping from one CATDrawing
document based on a standard containing thicknesses definition
(standards created or updated in V5R9 or on a higher level), to a
CATDrawing document based on a standard that does not contain
thicknesses definition, the first display of this second drawing may
sometimes show incorrect annotation thicknesses (dimensions, datum
features leaders, datum target leaders and roughness symbol leaders).
The following displays will show correct thicknesses. Workarounds: To handle the problem, the recommended methods are the following: just activate (or deactivate) the Analysis Display Mode and Create Detected Constraints icons. Or, use the Force Update command (enter: c: Force Update in the Power Input field), if you do not mind updating generated views. Even more efficient, just upgrade the standard to a level containing thicknesses definition. To do that, just click the Update button available in the Page Setup dialog box. |
Dimension and dress-up parameters |
In versions prior to V5R14, when
using styles parameters such as leader symbols or head/tail arrows
symbols, SymetricCircle and Circle were inverted. For instance, when
choosing SymetricCircle in styles, the annotation was displayed with
Circle extremity and when choosing Circle in styles, the annotation was
displayed with SymetricCircle extremity.
Example when creating annotation with SymetricCircle as parameter:
Symbols Circle and Symetric Circle were not inverted when creating
the following annotations:
We advise you to check in the standard files the symbols specified for the annotations mentioned in the first list:
Note that only newly created annotations listed above will be impacted. Those created with versions prior to V5R14 will not. |
Import from 3DXML
|
|
Views of products having layer filters activated |
When updating views of a product
whose visualization has been filtered using “Layer filters”, the view
will represent the filtering of the product that was active the last
time the product parts were saved. In order to take benefit of a change in the filtering of the product (either after a change of part layers, or a change of the filter itself) it is required that the parts be saved with this new filtering active. |
Advanced Bill of Material command |
|
Dimensions Between Intersection Points |
When creating dimensions between intersection
points, precisely between a 2D point and the extremity of an element
generated from 3D, no coincidence constraint is created between the
extremity of a 2D construction line and the extremity of a line
generated from the 3D. This behavior is documented in Knowledge Base article QA00000005050. |
None |
V4/V5 Standard Mapping |
During a 2D conversion V4 to V5, V4
annotations and V4 dimensions are migrated in V5 with the same property
as V4 or according the V5 2D standard defined in a *.XML file. V4 2D standard defined in the V4 project file can not be converted as a *.XML file.
|