Performance Options - Load Options 2

[vegetagaru]

thread561-291919

i would like to debate a bit more the matter on the thread above.

where i work, i work with projects that have 300+ assembly's (total size between 1gb - 10gb) we work with MoldWizzard DB's and own DB's (parametric....interpartdata...blablabla), we are currently working with NX9 (but i've worked with 8/8.5/10/11 and testing 12) and i use the following Load Options

My job colleagues work with "Use Partial Loading" and when i work that way, not always updates as you "need" for example i move some components and they dont update on other assembly's, other MAJOR PROBLEM that i think it is using "Use Partial Loading" is that when you load the components NX dosnt report you if your interpart data is OK or NOK(when you dont use partial load, NX reports after loading the interpart data, the data that is NOK), i got other major issues like exclamation point on top assembly, or "OUT OF DATE" assembly's (with all supposedly fully loaded and updated and even forcing update i got problems).

on the other hand the only "problem" that i got when not using partial load is that i need like more 15 seconds to open top assembly; then i got no problems and overall performance is almost equal if not equal compared to my colleagues.

so in terms of load options (in my case parametric/expressions/interpartdata ) i think its preferable to dont use partial load to work, and use it more for "visualization", and if you want to gain performance without putting in cause your work: explore the lightweight instead of partial load (for people that work parametric/expressions/interpartdata) (and this is a thing that im trying to do, explore the lightweight and understand it a bit more)

whats your experience ?

NX8.5 - NX9 - NX 10 - NX11

 

[3dr]

With all the expressions and part interlinks used in tool design your only option is to load inter-part data and keep partial loading off.

Lightweights are better in NX11 and might be helpful. I've not had a monster tool for a while so I haven't visited that yet.

If your working with fasteners while designing you may want to nix that. I make the hole features but don't populate them till the end in a higher level assembly.
From that I make a fastener only parts list.


Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX9, Win 7 Pro SP1

 

[vegetagaru]

i dont use much the fasteners, but i think its like to: just open the "pockets" of assemblys @ the end otherwise will i get a "monster tool" on updating things (links and etc)

thanks for your feedback. would be great if more people debate this

NX8.5 - NX9 - NX 10 - NX11

 

[3dr]

I'm running high end hardware and that helps a lot.

Liquid cooled over clocked CPU @ 4.4ghz
Full banks of over clocked Memory
All SSD drives
Whip #ss graphics card

The standard corporate hardware will give you more performance heartburn when your working large assemblies.
Especially when you go to documentation. Parts lists, Top level drafting etc...


Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX9, Win 7 Pro SP1

 

[vegetagaru]

yeahp im working on a i7 5960x(with wc) + 64Gbddr4 + K4200

NX8.5 - NX9 - NX 10 - NX11

 

[designnewz]

You could Use what I have Attached below. This gives the user control on what he really wants to Load/See. Do You need to Load everything when you work?

 

[vegetagaru]

as stated above that is a fail open options when it comes for interpartlinks and parametric stuff "designnewz", you are using partial load, and you dont load interpart data.

NX8.5 - NX9 - NX 10 - NX11

 

[design0058]

We are running NX9 with the die wizard from which I'm told is very similar to the mold wizard.
This is are typical settings other than the search path. You've got to turn on the load interpart data if you want the files to update properly.
LoadOptions_SearchPaths: J:\\0-180000\\0-180000\\0-180900\\0-180913
LoadOptions_LoadComponents: load_all_components
LoadOptions_LoadFully: YES
LoadOptions_LoadWAVE: YES
LoadOptions_LoadWAVEParents: IMMEDIATE
LoadOptions_LoadSubstitution: dont_allow_substitution
LoadOptions_LoadLatest: YES
LoadOptions_LoadOption: load_from_search_dirs
LoadOptions_LoadFilters: load_no_components
LoadOptions_LoadFailOption: dont_abort
LoadOptions_ReferenceSets: "As Saved" "Entire Part" "Empty" "Use Model"
LoadOptions_ApplyAllLevels: YES
LoadOptions_GenerateMissingPFM: NO
LoadOptions_UseLightweightRepresentations: NO
LoadOptions_ManagedModeLoadOption: load_by_revision_rule
LoadOptions_BookmarkRefSets: Import
LoadOptions_BookmarkPartsLoad: Load_Visible
LoadOptions_BookmarkRestoreFullyLoadedState: no
LoadOptions_SubsetLoadBehavior: Do_Not_Update

 

[vegetagaru]

design0058 that's the idea that i "defend" aswell thanks for your feedback

NX8.5 - NX9 - NX 10 - NX11

 

[vegetagaru]

theres a discussion on siemens forums aswell:

https://community.plm.automation.si.../board-id/NXDesignForum/thread-id/6018/page/2

NX8.5 - NX9 - NX 10 - NX11

 

[Ehaviv]

Hi vegetagaru

I'll take that in my attention
when I'll using link relink works

and thank you.

 

[Ehaviv]

Sorry this belong to other thread

 

[vegetagaru]

its ok i think =)

NX8.5 - NX9 - NX 10 - NX11

 

[Toost]

I do not see a conflict between partial loading and loading interpart data.
The way it is intended to work is that NX will load everything in partial mode until it encounters an interpart "object", expressions, wave links, constraints etc, when that happens, it will use the
"rules" you set in the load options dialog, - the ones that you skipped in the image in the first post.
i.e when NX loads an interpart object and "load interpart data" is ON, should NX then load parents :
None
Immediate level only
All Levels
- Moldwizard uses long series of interpart links where you probably want everything to update.
I would guess that Moldwizard users want the "all levels" option.

This would mean that:
If the part loaded has no interpart references, it is loaded partially. Faster.
If the part loaded has interpart references, it will load the parts according to the rule fully.

See :

https://docs.plm.automation.siemens...ons_load_d:id685090:fil_options_load_scope_op

From the linked page:
"
Load Parents
Appears only when Load Interpart Data is selected.

Specifies one of the followings scopes for loading interpart data.

None
Ignores the partial load setting for components you load that contain interpart data. Those components will be fully loaded instead of partially loaded.

Note
The None option does not open extra parts. It opens only the components you specify.

Immediate Level
Fully loads all components that are immediate parents of linked data, plus any other components that would be loaded by the None option.

All Levels
Loads all ancestor parts for all interpart data in the assembly, regardless of the number of ancestor levels. The All Levels option can include parts that you did not explicitly specify to open.

So , I think that you can toggle Partial Loading back on

Regards,
Tomas

 

[vegetagaru]

the problem is when u use partial loading, and when u have all assembly's loaded you dont know if u had a problem in an interpart link because NX only reports when u dont use that option, and sometimes when you use partial load you got to force the opening of some assemblys so they update proper and even so NX will not report if there was interpart link broken.

ps. even if you use partial loading with interpart load it will not report broken interpart.

in my experience with nx atm i just mostly use partial loading for "visualization" as i dont have warrantys with it on.

NX8.5 - NX9 - NX 10 - NX11

 

[Toost]

Have you actually tried the combination i mention ?
i.e
Partial Loading ON
Load interpart data ON
Load parents : All Levels

and using this combination, you say that you then need to force update some assemblies and that NX does not report broken links,
-Have you discussed this with GTAC ?

/ Tomas

 

[vegetagaru]

i didnt tryed "all levels" just interpart data on, its not the broken links(wave) that nx dosnt report but the broken interpart expressions report is gone with partial loading, but i will test later on with those options to see if it reports and give some feedback.

i didnt reported anything because without the partial loading i get everytime and everything working as expected.

NX8.5 - NX9 - NX 10 - NX11

 

[vegetagaru]

so i tested it in a small group of assemblys (400MB - 200 .prt's)

with partial loading and "all levels" dont report

No Partial Loading - reports everytime

btw in this case i gain 2 seconds on the opening

NX8.5 - NX9 - NX 10 - NX11

 

[Toost]

Good feedback there. You should report this to GTAC.
I guess that if you load this assembly twice, one time with partial loading ON and one time with partial loading OFF,
You could then submit the two syslogs to GTAC and that would be "enough" for this Incident report. ( No parts needed to upload.)
- The syslog records the messages you see on your screen.

Regards,
Tomas

 

[design0058]

If you have an advanced assembly license you can find the link data of your assembly in the interpart link browser. You can find it here.

This is what the results will look like.