graphic performance

[uwam2ie]

there is a specific setting under visualation performance large model/profile may affect on the grapfic performance.
Looking at the docs there's no really definition what a specifies a Small, Medium, Large, model defines- size of a bounding box? - Can somebody explain what defines these specific profiles?
thx in ad

 

[JohnRBaker]

What version of NX are you using?

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[uwam2ie]

I'm using nx6.04
thx

 

[JohnRBaker]

The comment about 'bounding box' has nothing to do with the 'size' settings. A 'bounding box' is something which has been defined and stored with every body/component in an NX model. This bounding box is the extents of the model relative to the X,Y,Z coordinates of the part file's absolute space. This 'box' is used when performing certain operations such as performing a graphical Fit operation as well as some of the quick checks for selection and when testing whether components or bodies interfere with each other (if the bounding boxes of two bodies do not intersect then the software knows that it does not have to perform a more compute intensive body-body intersection to see if the models actually do intersect and thus interfere).

Now as for the comment about showing the 'bounding box' during the retrieval of an assembly, this just means that until the components are actually loaded, if you need to see an indication of the component, it will show you a wireframe representation of the 'bounding box' of that component. You can see this for example when you have an assembly open with some of the components suppressed or unloaded. As you move the cursor over that component in the Assembly Navigator, you will see the bounding box displayed in the graphics window.

Now as for the reference to 'size', there are two places where the term size is used in the Preference dialog. One is for hiding small objects, the system can use either the actual size or the relative size of an object (actually the size of it's bounding box) to determine if you can see these objects while performing some sort of dynamic display operation, such as panning, rotating or zooming the display.

The other use of 'size' is in the overall 'Model Size' and this is just a general classification used to apply certain preset options and settings which will control the overall display of your assembly when performing any of dynamic display operation, such as panning, rotating or zooming your display. Not that you have NO control over the settings used for Small, Medium and Large Model Size, but there is a Custom option which allows you to specify/alter any of these settings and options used in your current session.

Now most of these options only have a significant effect if you've used the lightweight Reference Sets to load the components of your assembly since starting with NX 5.0 we are now using the JT facet representations with their support for Levels of Detail (LOD's). These Small, Medium, Large Model Size settings control the actual 'Level of Detail' used when displaying the model while performing any dynamic display operation.

Note that prior to NX 5.0, before the use of the JT standard for lightweight models, the system only had two schemes to control the performance of large models, either hiding objects while performing dynamic display operations, or replacing the display of the actual component with a 'box' (based on a Component's Bounding Box). However, now we use the LOD's of the JT representations as well as the size of any one individual component.

And further note that starting with NX 7.5, the use of lightweight JT-based representations when working with an assembly will become more ubiquitous since you will no longer need to change or even worry about Reference Sets since the lightweight representation will now automatically be included in the definition of the models body along with the normal edge and face definitions. In fact, the new OOTB behavior will be to ALWAYS work in a 'lightweight' mode when opening an assembly (although this can be controlled by the user). Therefore the maximum effects of the Large Model Preferences will ALWAYS be in evident when working with assemblies, irrespective of how large or small they may be.

Anyway, I hope this helped explain what was being talked about with respect to the options and settings found in the Preferences dialogs for Large Model Performance.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[uwam2ie]

thx john,
I like the stuff in nx7.5 nice to know.
I have to handle part moulding tools from NX4 on win32 and the graphic performance is very poor long wait states.