delivery st3

[Focus]

Is "manifiold" a problem for nx?

Hi.

 

[Tequila]

Is "manifiold" a problem for nx?

Hi.

from what I know yes, at least until nx 6.0, I read it on an English forum talking about this problem if I don't remember badly "split body".
the current version I don't know, but I assume that

 

[ipotemusa]

You can see that discussion I was lost and using search I can't find it. Do you have a link? I'd like to read it! But do you think they'll ever help us with this or is it a structural problem of the program?

So, I called the assistance this morning, and they confirmed that the non-manifold remained, and also they think it will never be settled, since solidedge works like this.....
feel a bit, but they say they listened to the utopians, is it possible that we are so few to complain about the non-manifold?? ?
it's useless to advertise that you can use files from other cad if you can't import anything (personal experience with st2)
solidworks has solved it since 2004 creating a multibody, and uses the same parasolid (which among other things provides zimenz)
inventor from what I know never had this problem (I started using it from vers 2010 by a customer and I confirm that there is nothing similar)
do we try to "torture" the assistants so they leverage the problem to the zimenz?
I have several colleagues who use other cads and continue to take me for the melts.
Maybe with st68 they will make it:

 

[cacciatorino]

I have several colleagues who use other cads and continue to take me for the melts.
Maybe with st68 they will make it:

several users have also mentioned the problem on the American forum, but the answer is usually: "But are you sure that's what it takes? make us an example where this has created a real problem."
Then when someone shows the real problem they say, "why, we think about it."

 

[Focus]

....
solidworks has solved it since 2004 creating a multibody, and uses the same parasolid (which among other things provides zimenz)
......

from here, you can see the meaning of my question... .

Hi.

 

[Tequila]

arrived yesterday the 2 licenses/ parcels of the st3.
Today I try to install it on the second pc in the office to do some tests.

 

[SE_User]

Hello everyone,

I also came across the "non manifold problem" for the bearings, first of all, due to the obligation of clarification the non manifold is not a problem, but a "works like this", then the problem of the bearings I solved by importing it in synchronous, changing the diameter of the ball and the game is done.

 

[Tequila]

Hello everyone,

I also came across the "non manifold problem" for the bearings, first of all, due to the obligation of clarification the non manifold is not a problem, but a "works like this", then the problem of the bearings I solved by importing it in synchronous, changing the diameter of the ball and the game is done.

the "works like this" is practice of the ccs team, now I have a mountain of mail with written the software works as it was designed! ! ! !
for certain things, including this of the "non-manifold" I had to become "broken [Bleep] and insist, sending the new er_submission_form that siemens wants for requests of software improvements.

the speech to import it into synchronous, how does it matter? always as assembly and then change the spheres, climb up and reimport it in par, or do you do some different procedure?

 

[dacampo]

st3 arrived at this moment... when the new pc arrives, I unload the mp and install the whole...

 

[SE_User]

the "works like this" is practice of the ccs team, now I have a mountain of mail with written the software works as it was designed! ! ! !
for certain things, including this of the "non-manifold" I had to become "broken [Bleep] and insist, sending the new er_submission_form that siemens wants for requests of software improvements.

the speech to import it into synchronous, how does it matter? always as assembly and then change the spheres, climb up and reimport it in par, or do you do some different procedure?

you can import it in two ways:

1) directly in par, but you have to change all spheres by hand
2) in assembly, open the part, pass the sphere in synchronous and change the diameter of the ball (even of a few cents), then return in the axieme and all the spheres are updated, carry out in parasolid and then re amount in part and throw away the axieme

 

[SE_User]

the "works like this" is practice of the ccs team, now I have a mountain of mail with written the software works as it was designed! ! ! !
for certain things, including this of the "non-manifold" I had to become "broken [Bleep] and insist, sending the new er_submission_form that siemens wants for requests of software improvements.

the speech to import it into synchronous, how does it matter? always as assembly and then change the spheres, climb up and reimport it in par, or do you do some different procedure?

for practice, ccsetam is also my dealer, and speaking with one of the technicians told me that the "works like this" is an elle many answers that receive from support siemens when submitting the customer's request.

 

[cacciatorino]

for practice, ccsetam is also my dealer, and speaking with one of the technicians told me that the "works like this" is an elle many answers that receive from support siemens when submitting the customer's request.

all the time I wrote for malfunctions they always told me:

1) first request: "The user can't use the software"

2) second request: "it's the normal way of running software"

3) Third request: "umh, maybe we give him a view"

4) fourth request: "It's a bug, we'll look at each other when we have time and want."


definitely the technical service siemens is not at all up to the software they sell, if then one goes to see that they are also very expensive compared to the competition.....

 

[Tequila]

you can import it in two ways:

1) directly in par, but you have to change all spheres by hand
2) in assembly, open the part, pass the sphere in synchronous and change the diameter of the ball (even of a few cents), then return in the axieme and all the spheres are updated, carry out in parasolid and then re amount in part and throw away the axieme

1-2) ok same as I did with versions prior to st, so all work by hand.

 

[Tequila]

for practice, ccsetam is also my dealer, and speaking with one of the technicians told me that the "works like this" is an elle many answers that receive from support siemens when submitting the customer's request.

I noticed that you are also veined for which same dealer. last week I installed if st3 and after doing my classic tests/test of the software and verified if they have arranged some things I sent an email to know if the transformed ir were taken into consideration and/or settled and possiblemte as I could personally verify the state. the answer was this:
the only visible thing is the status of the call, not its planning at the center of development. that do not even see it in siemens italia.not even siemens italia knows how the software develops! ! ! ! ! ! ! ! ! ! !

to those interested in the status of the call is visible here http://webtac.ugs.com/qtac/ (obviously for those who are in maintenance)

 

[Tequila]

all the time I wrote for malfunctions they always told me:

1) first request: "The user can't use the software"

2) second request: "it's the normal way of running software"

3) Third request: "umh, maybe we give him a view"

4) fourth request: "It's a bug, we'll look at each other when we have time and want."


definitely the technical service siemens is not at all up to the software they sell, if then one goes to see that they are also very expensive compared to the competition.....

as I said with my former colleague during the st course a couple of years ago, in siemens they have the "peace" like horses. They look only forward without ever turning around or looking side by side what the competition does to carp good and valid things and this also affects how assistance manages or is forced to manage customer calls for software problems.

 

[SE_User]

as I said with my former colleague during the st course a couple of years ago, in siemens they have the "peace" like horses. They look only forward without ever turning around or looking side by side what the competition does to carp good and valid things and this also affects how assistance manages or is forced to manage customer calls for software problems.

hi, of this I'm not sure, because I saw that some you want if and sw "copy" among them some things.

 

[SE_User]

all the time I wrote for malfunctions they always told me:

1) first request: "The user can't use the software"

2) second request: "it's the normal way of running software"

3) Third request: "umh, maybe we give him a view"

4) fourth request: "It's a bug, we'll look at each other when we have time and want."


definitely the technical service siemens is not at all up to the software they sell, if then one goes to see that they are also very expensive compared to the competition.....

personally with my dealer I find myself well, extra when it is the sw not to "reach" often try to give me/suggest an alternative stade, with a workaround.

 

[cacciatorino]

personally with my dealer I find myself well, extra when it is the sw not to "reach" often try to give me/suggest an alternative stade, with a workaround.

My var is very good and very ready and competent, the problem is the elephantia bureaucracy of siemens-italia and siemens-mondo.

 

[Tequila]

hi, of this I'm not sure, because I saw that some you want if and sw "copy" among them some things.

Maybe they copied certain things... especially that of the scale on the drawings, which in swx works well for years, while in if they put a straw, that is the sheet scale, that when you change scale to the view of the model, that of the sheet remains unchanged.

last year I had reported this to assistance, I asked last week, and yesterday I got the answer:
title call: drawing scale............. .
automatic message
we inform you that the call in question
was closed for the following reason:
solid edge works as designedyesterday I reinviated the email to reopen the call using the form that now wants the siemens.

You know, the problem is that every year, after the launch of the new releases of the software we find ourselves here to talk again and reopen issues that continue and never listen to us. at least know how many years they have to pass before requests are filed!! you would save time, piss, and fill the forum of usual speeches.

 

[SE_User]

I don't know sw, but I think if he has things that sw no nabbia, for example synchronous technology.
that of the scale would be useful, but personally I do not see it so important, I manage it with a persnalized property.
I would personally prefer a command that manages the "pattern table" that is now missing, rather than many other useful things whose list would be quite nourished.