APAR status
Closed as suggestion for future release.
Error description
GENERATIVE DRAFTING / ISOMETRIC VIEW IS NOT CORRECT .
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
THIS APAR IS CONSIDERED AS A SUGGESTION FOR IMPROVEMENT WHICH CANNOT BE INCORPORATED IN VERSION V5R14 PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN ORDER TO OPEN A REQUIREMENT FORM. . Incident Diagnosis Many unresolved intersections or duplicated parts between solids (collisions). The HLR algorithm does not resolve properly these intersections, so it may lead to bad results. . Development Request Justification The "Exact" projection mode in projection views and section views uses a projection algorithm that has the following restriction: In case of clash (intersection) between bodies to be projected, the result of the projection may contain incorrect results, some edges of these bodies may appear even if they should be hidden, or disappear even if they are not hidden. These clashes should be avoided, as they correspond to non-nominal cases of collision between two parts in an assembly or two bodies in a part. In this case the assembly or part should be modified, either by moving the parts/bodies to avoid the clash, or by using boolean operations in order to generate a single body resulting of the intersection (and in this case the edge representing the border of the collision will appear) The only case of clash which is nominal in an assembly is when you model a screw in a threaded hole (for example a bolt). In this case the use of the thread information on the shaft and on the hole results in a case of clash. For example a M10 threaded shaft has a diameter of 10mm which corresponds to its external diameter, whereas a M10 threaded hole has a diameter of 8.376, which corresponds to its inner diameter. Enhancing the current projection algorithm in order to solve the general cases of collisions is an enhancement request cannot be done, since a) It requires making important and impacting changes in the foundations of the algorithm b) It would lead to non acceptable CPU performance for this additional processing. We are currently studying how to solve this restriction for the case of threads, which is a mid- term development, since it requires either changing the model for threads on parts, or re-engineering the projection algorithm to support this case (which does not mean supporting all cases of non nominal clashes). This is an enhancement request which has no targeted release. . Answer and By-Pass Perform boolean operations between collided solids and put duplicated parts in no-show before drawing to obtain correct results. Note that you can use the "DMU Space Analysis" tool to check clashes. .
APAR Information
APAR number
HD17684
Reported component name
CATIA V5/NT/200
Reported component ID
569151000
Reported release
512
Status
CLOSED SUG
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2004-02-12
Closed date
2004-03-11
Last modified date
2004-03-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
11 March 2004