compatibility obtained between v5 and v6

[SolidUser]

how will you read fromArticle, you will be pleased to discover that v5 cat users will be able to modify v6 models from within v5.

this improvement is also reflected on solidworks users, because as announced in swworld 2012, the sw2012sp5 will open sw2013 files.

 

[stef_design]

una grande cosa!

 

[RS4]

Hello solid... .

thanks to the news:36_1_13: really interesting

 

[The_Matrix]

credo The two things are a little different.

Catia: v5 will open v6 files and see features
swx: 2012 can open 2013 files and keep them as a reference.

Maybe you who are experts can confirm or refute.

 

[The_Matrix]

ps. There are 2 things to say about v6:

1) licenses are named... eh... it means that if I have 20 users of which 10 use 100% cad and others to 20% of their time I have 20 licenses. No way. like pdm... with v5 (or other cad) I can have 12/13 licenses and 10 users who use part-time cad use 2-3 that remain available.

2) v6 > v5 brings assembly but not constraints.http://gfxspeak.com/2012/05/02/is-catia-v6-over-the-hump/but one knowledgeable customer who has looked at the process says the “engineering connections” that fill the role of assembly constraints in catia v5 and other systems don’t translate. consequently, although v6 assemblies can be written as v5 catproduct files with all the parts in proper orientation, there are no constraints holding them together.

 

[stef_design]

credo The two things are a little different.

Catia: v5 will open v6 files and see features
swx: 2012 can open 2013 files and keep them as a reference.

Maybe you who are experts can confirm or refute.

I confirm! !
cmq is a step in avanto the fact that with v5 open v6 files.
Usually it is difficult to find a cad that adopts a "go on" philosophy, they are usually all retrocompatible.
Hi.

 

[stef_design]

ps. There are 2 things to say about v6:

1) licenses are named... eh... it means that if I have 20 users of which 10 use 100% cad and others to 20% of their time I have 20 licenses. No way. like pdm... with v5 (or other cad) I can have 12/13 licenses and 10 users who use part-time cad use 2-3 that remain available.

2) v6 > v5 brings assembly but not constraints.http://gfxspeak.com/2012/05/02/is-catia-v6-over-the-hump/but one knowledgeable customer who has looked at the process says the “engineering connections” that fill the role of assembly constraints in catia v5 and other systems don’t translate. consequently, although v6 assemblies can be written as v5 catproduct files with all the parts in proper orientation, there are no constraints holding them together.

1st I don't know, while 2nd I confirm.
This choice is dictated by the fact that v6 is directed to the big industry and not to the small-scale enterprise (for which there is and continues v5).
therefore hardly the big companies feel the need for constraint because they are worked with skeleton or explicit.
Hi.

 

[The_Matrix]

1st I don't know, while 2nd I confirm.
This choice is dictated by the fact that v6 is directed to the big industry and not to the small-scale enterprise (for which there is and continues v5).
therefore hardly the big companies feel the need for constraint because they are worked with skeleton or explicit.
Hi.

:smile:
we say they didn't.. .
I just saw a flying product of 30,000 components and constraint there are tons.

ps. 1st (the named licenses) is devastating. . believe me

 

[The_Matrix]

I confirm! !
cmq is a step in avanto the fact that with v5 open v6 files.
Usually it is difficult to find a cad that adopts a "go on" philosophy, they are usually all retrocompatible.
Hi.

I fear (for them... we say that bernard sciarles is our best seller :tongue who simply pissed off from the vase.
v6 has a very limited success and backward compatibility is the only way they have to try to push it a little, hoping that some big client decides to put it on some project and the suppliers leave it in v5.

 

[SolidUser]

credo The two things are a little different.

Catia: v5 will open v6 files and see features
swx: 2012 can open 2013 files and keep them as a reference.

Maybe you who are experts can confirm or refute.

I used an inadequate term.
by improvement I meant strategy, choice of retro-compatibility.
is a benefit for sure, as if users nx 7.5 could open file nx 8.http://www.youtube.com/watch?v=b6tuujtbt0s&feature=player_embedded

 

[The_Matrix]

I used an inadequate term.
by improvement I meant strategy, choice of retro-compatibility.
is a benefit for sure, as if users nx 7.5 could open file nx 8.http://www.youtube.com/watch?v=b6tuujtbt0s&feature=player_embedded

the concept is interesting and probably son of the fact that after 4 years v6 has not yet spun anyone. . .
a shame because the concepts behind are beautiful.

 

[Parametric_Ozzy]

the concept is interesting and probably son of the fact that after 4 years v6 has not yet spun anyone. . .
a shame because the concepts behind are beautiful.

I agree with beppe, I think they had to fold because of the poor results.
the concept however is very interesting especially for all those supply companies, which must always pursue the big cow.
however, they are generally skeptical, because surely there will be no way to "publish" all the features, especially those put in the new versions, created with new algorithms.

 

[RS4]

I agree with beppe, I think they had to fold because of the poor results.
the concept however is very interesting especially for all those supply companies, which must always pursue the big cow.
however, they are generally skeptical, because surely there will be no way to "publish" all the features, especially those put in the new versions, created with new algorithms.

I share your own thought....

surely the changes will be limited due to new algorithms, but I think you will have the possibility to create new features.. and work in assembly... Otherwise it wouldn't make sense.... this downgrade to v5

we will see!!! :smile:

greetings

♪