Catia V5 have autosave
Yes it's simple to push CTRL+S, also on the car you have pedal for brake....but a lot of cars now have autobrakes for emergency. I don't want autosave because I'm tyred to push CTRL +S I want autosave for lose less work as possibile.
About saving to old version
CatiaV5 have the function "save for previous version", offcourse you lose parameters, but I have the same problem if I use Step or parasolid.And About this continuos release I don't undesrtad if whit "NX jan 2019" I will able to open a file made with "Nx jan 2020"
About your last question
you are right but what a bug? it's an error, no one pays me for solve my mistakes so for me maintenance is for have new features. Obviously, Siemens does not think like me.
I think I've read somewhere that with the new continuous release process, you'll still end up having files (e.g. created with NX1947) that can't be opened with and older NX (e.g. NX1847). Yet, I'm not sure and someone from Siemens would be more relevant on this matter.
Well, I'm not saying bug fixing is an incredibly good new feature, I'm just saying that it's maybe the major point I'm waiting in a new release.
Save for old release:
Backwards compatibility will always break when the Parasolid kernel changes.
In the past this was usually done with a new major release, but there have also been changes within a major release. These changes within a major release have been very rare. The last might have been with UGII v11.0.0 and v11.1.0, if I remember correctly. UGII v11.0 was eight releases before NX 1.0 was released, which was UGII v19.0 actually.
Production: NX12.0.2, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX (1876) | AWC 3.4 Preparing: -
Employees of the customers, together we are strong
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
@Stefan_Pendl this way it's like export like stp o igs (maybe whit less possibility of corruption) and it's works for a single file, but:
1) If I open directly parasolid I will have a part for every "body" whit the same file name (except ID)
2) If I export an assembly in parasolid when import it don't reacreate assembly structure like the original Assembly
3) parasolid don't export curves
Offcourse I can export step whit assembly infos but....critical errors....geometry corruption etc etc....
anyway this isn't the right place to discuss about it, I just wanted to express my disappointment on this new release.
Thank to all for replyes!
Did you managed to solve this problem? I am having the same issue but what I gather is that I will need a new license file for getting rid of that error?
It's a silly and stupid version level and I'm sure nearly everyone agrees.
"Coming soon, the new 2020G cellular network!"