extreme problem slow table 2d creo 3 - version m110

[Maverik83]

Good morning, boys. I'm new in the forum and I'm writing to ask you for advice. I press that I have come from 10 years of use of inventor and from 1 of topsolid, but I create I am getting more than a scratch. I've only been using it for 3 weeks, but it seems a lot more tricky to use than other cads that are more intuitive, but vabo, I'll take my hand as always. I write to you because I have another problem. yesterday I happened to work at my first serious set in the new company. the axieme was nothing excessively complicated, will have been a hundred components with a dozen views in section prepared on the 3d so as to bring then on the 2d and 3 free movements. the problem that I encounter is in the 2d. was of an exasperating slowness, every time 20-30 seconds waiting to regenerate the view or for an extra quota. with inventor I managed to assimilate 4000 pieces and only showed them some difficulties, but on so small assemblies I never saw such a stuff. I can assume that the problem arises because there is some active regeneration option. is there a possibility to disable it and maybe set some quick command that every tot of time drives me and makes me the regeneration of the model? use creo 3 version m110.

 

[320i S]

with complex assemblies and/or with many views (which does not only concern the number of components, but also their shape and number and types of views) it is good to deactivate the automatic regeneration of views in the 2d with the option:

auto_regen_views -> no

at the level of number of components, I create has no difficulty with large assemblies (3500/4000 components are manageable), you have to analyze the situation, ram you have enough?, the components are all made in creo?, how were they made?, are they imported?, if yes, how big in term of file size? .
in any case, there are several ways to speed everything, including levels, simplified representations, family table (but only in certain situations according to me) etc.

 

[Maverik83]

First of all I thank you for the kind answer. In fact it seems strange to me that it is so slow, also because in its 3d assembly the system presents itself fluid and snappy.

I don't think it's a hardware problem, I have 32gb and at the moment I did a check and only 21% of ram were engaged, as cpu I have a xeon e5 1620 v4 that was about 10-15% and as a graphics card a p4000 picture. as I imagined and as you confirmed, it could be a regeneration always active. Now I try and see if it improves.

As for the management of levels and representations unfortunately I am using it for only 3 weeks and for me it is all new, as I take my hand I will experience something, but at the moment I already have enough confusion in the head eh.



p.s – I almost forgot. in my company you make a quite wide use of family table and almost certainly in that assieme there will have been some loaded

 

[320i S]

family tables on library components are fine, on assemblies to manage their configurations, make sense in certain situations.
I recommend that you see the simplified representations well, which are one of the strengths in creo to work with the large axioms, are not difficult to use and can be recalled also in the axioms of higher level, without returning to give them back.
in the views then, if they are only partial, it makes even more sense their use.
Finally in the 2d, you can also turn off certain views, displaying only the contour square, this facilitates even more the preparation work, at the end of work, activate and save everything.

 

[Maverik83]

family tables on library components are fine, on assemblies to manage their configurations, make sense in certain situations.
I recommend that you see the simplified representations well, which are one of the strengths in creo to work with the large axioms, are not difficult to use and can be recalled also in the axioms of higher level, without returning to give them back.
in the views then, if they are only partial, it makes even more sense their use.
Finally in the 2d, you can also turn off certain views, displaying only the contour square, this facilitates even more the preparation work, at the end of work, activate and save everything.

I will follow your advice and look at practical guides. I tried to disable the regeneration of 2d views, but if I click above the command "update design view" in the tab examines, nothing happens, it seems that the command remains enabled always.

 

[320i S]

that command is always enabled for many reasons (also due to the management of pdms, when updating read-only files, edited by other users), the option I wrote above, goes to the config.pro file.

 

[Maverik83]

hi 320, I tried to change settings as you told me, but nothing changed. Attached I put you a video where you can see the immon slowness of the system, and it is not even one of the biggest assemblies we use. Man, I feel like using a 90s pc.
My system is this:
and come scheda video ho una marco p4000.

 

[320i S]

hi 320, I tried to change settings as you told me, but nothing changed. Attached I put you a video where you can see the immon slowness of the system, and it is not even one of the biggest assemblies we use. Man, I feel like using a 90s pc.
My system is this:
View attachment 53701and come scheda video ho una marco p4000.

as mentioned above, the reasons for slowness can be many, not necessarily the machine you use, the assemblies, the parts that make up it and how they were made.

some conditions to work "good" are:
-family table should not be too complex (e.g. having many on/off features slows down the generation of parts)
- Imported parts should always be "solid", the surface groups are very heavy (for all cads, not only for creo so much to understand), especially if very small patches are present
-Simplified representations should be "daily bread" when over 500 components are present at the same level
-assiemi should always be well defined, there should be no failures of couplings, or components not fully assembled
- external references should be reduced almost to zero!, especially if the components have a generic use, if external references are needed, it would be better to have the advanced assembly and use only copy geometry commands and publication (which can be put in manual regeneration).

in the tables (as mentioned above), if even with the self-generation put off, there are heavy slownesses, better use the "specs view" and more generally, limit the use of several different components in the same table file.