HD61546: PART : UDF VISIBLE IN THE CATIA TREE BUT NOT IN 3D MODEL - DMU

APAR status

• Closed as Permanent restriction.

Error description

• PART : UDF VISIBLE IN THE CATIA TREE BUT NOT
  IN 3D MODEL - DMU
  Requirements:
  - You must install ENOVIA DMU Navigator in local to
  reproduce the problem.
  - Copy feat files to C:\Program Files\Dassault
  Systemes\R16_SP04\intel_a\resources\graphic if
  Enovia DMU Navigator is installed in C:\Program
  Files\Dassault Systemes\R16_SP04.
  .
  Scenario:
  1- Open CATProduct
  2- In Catia tree you can see a part but you can't
  see it in the 3D model
  .
  

Local fix

Problem summary

• PART : UDF VISIBLE IN THE CATIA TREE BUT NOT IN 3D MODEL - DMU
  PART : UDF VISIBLE IN THE CATIA TREE BUT NOT
  IN 3D MODEL - DMU
  Requirements:
  - You must install ENOVIA DMU Navigator in local to
  reproduce the problem.
  - Copy feat files to C:\Program Files\Dassault
  Systemes\R16_SP04\intel_a\resources\graphic if
  Enovia DMU Navigator is installed in C:\Program
  Files\Dassault Systemes\R16_SP04.
  .
  Scenario:
  1- Open CATProduct
  2- In Catia tree you can see a part but you can't
  see it in the 3D model
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  CATIA
  Incident Diagnosis
  Udf instance not visible in 3D viewer when CATIA
  is launched without UDF code available.
  Restriction Explanation
  Since the code corresponding to the UDF is not
  available on the DMU install, the backup startup
  protocol applies on the condition that no .feat is
  added in the runtime view. Thus you should remove
  the CATUdfDesign.feat and CATUdfGeneric.feat files
  that are added to the runtime view. With correct
  backup startup, the 3D visualization should be
  correct.
  But since the UDF instances are coming from an old
  UDF modelization (with a valuated result out
  attribute), the backup startup does not work
  correctly. The problem has already been identified
  and corrected. It consists on unsetting the
  attribute, using the Upgrade command. But there is
  no way to perform safely such a thing on a UDF
  instance inserted inside a design. Thus the UDF
  instance must be deleted and replaced by a new
  one coming from the instantiation of the UDF
  reference after upgrade.
  This can be done in V5R17 but not in V5R16 since
  it requires a change of modelization and thus a
  change of configuration level, which cannot be
  performed in a Service Pack level, nor a HotFix
  level.
  By-Pass
  Bypass in V5R16: add the KT1 or PKT licence to the
  DMU install
  .
  

Temporary fix

Comments

APAR Information

• 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