array rettangolare

[The_Matrix]

I press that the new array, my opinion, is a great command that allows you to satisfy the most demanding people.
I did a test and:
- I created an extrusion with a sketch inside it (e.g. I did a rectangle)
-pattern feature and I choose the simplest function i.e. repeating axis x n times and same thing per axis y
-published again the feature pattern command and choose to change one of the many repetitions by changing the dimensional value of the sketch to obtain dimensional variables between the repetitions starting from a "source"
- recurred to change again the size of the rectangle modified previously and here I found a little problem because there is no way to change the values.
I also tried, go into expressions and change to "eat" the value but nienete to do.
Can someone tell me if he found the problem and solved it or can you tell me where I'm wrong?

for the rest it seemed quite stable and especially powerful

do so:
- create the sketch and then the extrusion you want.
- feature pattern
- select extrusion and sketch
- pattern as you want
- edit the instance by selecting the size of the sketch you need (select the share... mb3... add to edit)
- Okay.
... amended
- the Instance
- Okay.
... amended

or, if you want less features:
- make sketch internal
- subtract integrated into extrusion

Hi.

 

[matfio]

do so:
- create the sketch and then the extrusion you want.
- feature pattern
- select extrusion and sketch
- pattern as you want
- edit the instance by selecting the size of the sketch you need (select the share... mb3... add to edit)
- Okay.
... amended
- the Instance
- Okay.
... amended

or, if you want less features:
- make sketch internal
- subtract integrated into extrusion

Hi.

Okay, I also choose this or that as a procedure but I wanted to change a solid copy and leave the remaining copies as sketch size............ Maybe I missed your explanation. We do so, tomorrow morning place the file so we see together.... Meanwhile thank you

 

[Utente NX]

today I have made a call with the pm of modeling and assembly for other issues and asked specific question. . .
the component patterning was in the beta with forecast to be entered in the 8.0.1 end of January.
instead it will probably be moved forward (from voice I think that 8.5 is a hope... Probably 9).
There's a huge assembly project that I think sucked all the resources.
confirmed instead in nx8.0.1 the part module. I don't know if you tried it in the beta, if there was...

John, he told me the 9th because he considered as major the 9th.
but sometimes he does not know the commercial choices and name, as you have confirmed on your comment about that 8 will not read 8.5 as it happens between 7 and 7.5.
for that I wrote major = 8.5.

As for the part module, it was made available via system variable with beta 2.
is an automatism on a methodology already used in a shared design environment on wave links.
this automatism is definitely a help to the designers.

Too bad it's not part of the basic package.
from what I remember, is managed by the udf license.
we do not have it, as well as the wave license to is a real sin.

However it is a real step forward for shared design.

 

[Utente NX]

I press that the new array, my opinion, is a great command that allows you to satisfy the most demanding people.
I did a test and:
- I created an extrusion with a sketch inside it (e.g. I did a rectangle)
-pattern feature and I choose the simplest function i.e. repeating axis x n times and same thing per axis y
-published again the feature pattern command and choose to change one of the many repetitions by changing the dimensional value of the sketch to obtain dimensional variables between the repetitions starting from a "source"
- recurred to change again the size of the rectangle modified previously and here I found a little problem because there is no way to change the values.
I also tried, go into expressions and change to "eat" the value but nienete to do.
Can someone tell me if he found the problem and solved it or can you tell me where I'm wrong?

for the rest it seemed quite stable and especially powerful

I may have misunderstood, but it doesn't seem like this.
link to my procedure, standard for more.

 

[matfio]

hi to all, doing several tests I noticed that the variation of the size between the solids copied because:
- if I change the value of the "p" of the size to be changed of the copied solid does not update it seems that the quota is frozen
-if I edit the feature of the copied solid sometimes does and sometimes not, I leave the program and return then change the parameters
I didn't notice anything strange, but I'd say fantastic, it solves a "casino" of extra features.

place the affected file though basically equal to the usernx movie because it is the standard procedure

 

[Utente NX]

hi to all, doing several tests I noticed that the variation of the size between the solids copied because:
- if I change the value of the "p" of the size to be changed of the copied solid does not update it seems that the quota is frozen
-if I edit the feature of the copied solid sometimes does and sometimes not, I leave the program and return then change the parameters
I didn't notice anything strange, but I'd say fantastic, it solves a "casino" of extra features.

place the affected file though basically equal to the usernx movie because it is the standard procedure

Try to attach a mini video of the incriminating procedure.
I do not want that, even if the quotas of the instances are visible, it is not the correct method.

 

[The_Matrix]

concordo con alessandro... If you make a little avi...
I always work... I made a solid and on this solid applied a feature (sketch + extrusion) and made the pattern of the latter.

 

[matfio]

ecco l' avi

 

[The_Matrix]

ecco l' avi

I created an example similar to yours.
actually there is a problem by editing the size via tool expression.
to avoid it, once the value is edited, simply suppress the pattern and reactivate it, so nx recalculates it and values are consistent.

 

[matfio]

I created an example similar to yours.
actually there is a problem by editing the size via tool expression.
to avoid it, once the value is edited, simply suppress the pattern and reactivate it, so nx recalculates it and values are consistent.

we hope in a short time accommodation

 

[Utente NX]

we hope in a short time accommodation

I didn't answer you earlier, because I wait for more details, however there is an open pr.
being a new feature, I think it is resolved, in case it is an anomaly, in a short time.

 

[The_Matrix]

I didn't answer you earlier, because I wait for more details, however there is an open pr.
being a new feature, I think it is resolved, in case it is an anomaly, in a short time.

I asked at the pm whether it is a forgetfulness or a mistake or it is desired.
I'll let you know if he answers.

 

[matfio]

I asked at the pm whether it is a forgetfulness or a mistake or it is desired.
I'll let you know if he answers.

thank you very much "neo" for your availability :smile:

 

[Tequila]

thank you very much "neo" for your availability :smile:

ot: more than neo is better morpheus.. At least so was his first avatar at the time of ugoverall :wink:

 

[The_Matrix]

the pm did not answer me.. .
It is obviously a pr and not a thing intended.
in these days however there was the plm europe in linz... Maybe he didn't have time.

 

[matfio]

-I noticed that you can update the feature with update for external change without having to turn off and activate the feature.
-A strange thing I noticed also for assembly constraints that to update the status you must use the update for external change or close and reopen the axieme.
Let me explain better:
- completely convinces a component
-I add another component and constraint completely on the existing one
- I add another one and constrain it completely by taking one face and another face etc... then the knob for example inverting aligns with distance
- It happens that symbolically it is partially bound but in reality it is completely bound.

Have you noticed this?

 

[The_Matrix]

the pm did not answer me.. .
It is obviously a pr and not a thing intended.
in these days however there was the plm europe in linz... Maybe he didn't have time.

I'm chinchinated and I talked to the developer of the array. .
is an already correct pr... will put it in one of the next update.

 

[Utente NX]

-I noticed that you can update the feature with update for external change without having to turn off and activate the feature.
-A strange thing I noticed also for assembly constraints that to update the status you must use the update for external change or close and reopen the axieme.
Let me explain better:
- completely convinces a component
-I add another component and constraint completely on the existing one
- I add another one and constrain it completely by taking one face and another face etc... then the knob for example inverting aligns with distance
- It happens that symbolically it is partially bound but in reality it is completely bound.

Have you noticed this?

I tried, but it doesn't happen to me, but I don't know what it can be.

 

[matfio]

hypothesis: problem with multiprocessor?
I use the system variable ugii_smp_enable
because it seems a difficulty of updating or refresh

 

[Omen]

-I noticed that you can update the feature with update for external change without having to turn off and activate the feature.
-A strange thing I noticed also for assembly constraints that to update the status you must use the update for external change or close and reopen the axieme.
Let me explain better:
- completely convinces a component
-I add another component and constraint completely on the existing one
- I add another one and constrain it completely by taking one face and another face etc... then the knob for example inverting aligns with distance
- It happens that symbolically it is partially bound but in reality it is completely bound.

Have you noticed this?

Yes, it happens to me too (even with nx7.5), unopened with assistance and transmuted into pr ... aspect news!

Hello everyone