HE10407: DISPLAY IS NOT PROPER FOR A LARGE STL FILE WHEN TESTING USING TH E C:TESTVISUPERFODRAW

APAR status

• Closed as Permanent restriction.

Error description

• Scenario:
  Open the CATPart.
  use c:testvisuperfodraw
  note that the rotation of the part is not continuous.
  Also the total time required is huge.
  .
  Expected Result:
  The rotation performance should be continuous and also the
  time should be reduced.
  

Local fix

• empty
  

Problem summary

• Scenario:
  Open the CATPart.
  use c:testvisuperfodraw
  note that the rotation of the part is not continuous.
  Also the total time required is huge.
  .
  Expected Result:
  The rotation performance should be continuous and also the
  time should be reduced.
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN CATIA
  Additional Closure Information:
  Incident Diagnosis:
  Display is not proper for a large stl file when testing using
  the c:testvisuperfodraw
  Restriction Explanation:
  Explanation for the performance difference between sample and
  reference part:
  The reference part contains a little bit less than 3 million
  triangles, as given by the "c:triangles count" command.
  The sample part contains a little bit more than 10 million
  triangles, as given by the same command.
  In this context, the measurement can't be the same for both
  parts; a x3.5 ratio can be expected in the measurement
  between the two parts.
  Explanation for the overall performance measure:
  When a model is loaded from memory and rendered for the first
  time, we need to put in place some memory data structures to
  ensure that it will be drawn correctly. These structures are
  updated when new objects are rendered (for example when they
  become visible) and this can happen several times when the
  first full rotation is executed. All this management has a
  cost in performance that can explain the non-continuous
  effect during the rotation.
  After the full first rotation, all the memory structure are
  in place and the second full rotation should behave better
  (more continuous).
  Besides this, the rotation performance can change from one
  frame to the other because we???re not rendering exactly the
  same content in each frame. In particular, some objects that
  may be considered too small for being rendered one frame, may
  be rendered the following frame because they???re no more
  considered as being too small. This has an influence
  especially if the objects are highly tessellated. This can
  explains why some acceleration and decelerations can be
  observed throughout the entire full rotation.
  This behavior can be changed by modifying the following
  Tools/Options in General/Display/Performance :
  - Level of Detail ??? Static and While Moving
  - Pixel Culling ??? Static and While Moving
  For example, in the model provided by the customer, there is
  no Level of Detail so this option has no effect. On the other
  hand, performance difference can be observed if you change
  the Pixel Culling Static value.
  In terms of performance enhancements, no additional
  improvement can be performed on the provided model.
  By-pass:
  Increasing the Pixel Culling Static value for the customer
  model will accelerate the Visualization time and also the
  rotation is more continuous.
  

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