Effect of version change on existing files.

[KENAT]

We are on V18.

We want to go to V19 or 20 but some of our machines are quite old and we don’t have the budget to replace them and some of our models are quite big. We have a plan to do performance testing before jumping. However this isn’t my question as such.

My question is, I know that V19 files cannot be opened by V18.

What has to happen for the files to get changed to the newer version?

Does the file actually have to be opened and saved to change it or can just opening without saving do it.

A few years ago at a former employer we found that just opening the files seemed to cause them to go to the new version but… This was based on what an add in program seemed to have trouble with, not Solid Edge itself.

I want to double check so we don’t mess things up when it comes to doing our performance testing.

Also we’ve had an incident where one engineer arbitrarily got hold of V19 and has screwed up a major assembly. Fortunately, we had a back up which was only a few days old but we have lost work. I want to throw the book at him but want to have my story straight first.




KENAT, probably the least qualified checker you'll ever meet...

 

[beachcomber]

Hi Kenat,
For what it's worth, we recently went from V18 to V19, and I never noticed any performance hit. (Unlike the change from V17 to V18 which seemd to require more memory and processing power).
As for what triggers a file to 'upgrade' I can't be 100% sure, but I would think it would be saving the file. However, if you open and save an assembly I would expect the parts to upgrade also.
A few years ago I was advised that when upgrading you should use the 'OpenSave' batch file. This little program works on whole directories, and figures out parts, sub-assys, top-levels and drafts, and opens and saves them in the correct order. BUT... make a backup first.

bc

 

[KENAT]

Thanks beachcomber, we heard from our sister site that there was a memory leak (at least in earlier service releases) and haven't found out for sure if this is fixed yet.

We have some pretty big assemblies so it would be an issue.

KENAT, probably the least qualified checker you'll ever meet...

 

[Schipperus]

Hi KENAT,

I'm not sure wether this is the memory leak you pointed out, but in update 8 a memory issue is fixed.

IJsbrand

(UPDATE 8 RELEASE NOTES)

---------------------------------------------------------
This Update addresses the following Customer Reported PRs:
----------------------------------------------------------

=====Assembly=====

PR 1592734: Fixed a problem where a drawing view did not update after changing an assembly feature.
PR 1597791: Fixed a problem with Assembly Feature performance
PR 5774079: Fixed a problem that caused Solid Edge to hang.
PR 1601204 & 5785801, 1601204: Fixed a problem where Solid Edge was not properly freeing memory.
PR 5783092: Fixed a problem with Assembly and Part file save.
PR 1604936: Fixed a problem where Windows .NET 2.0 update KB928365 causes Standard Parts to stop working.
PR 1604886: Fixed an inconsistency in Czech Standard Parts localization
PR 5783494: Fixed a problem where Solid Edge aborts using Peer Variables.
PR 1599049: Fixed a problem where Parasolid based assembly translator needs to maintain structure and bring in multiple bodies into the same part ( if name attrib matches). Note: Run/dbl-click AsmXlatorSheetsAndSolidsTogetherOn.reg file to turn on this fix, then recreate the Parasolid file and step files before round-tripping into Solid Edge

=====Part=====

PR 2083853: Fixed a problem where an Extruded Surface is always capping one end when From-To extent is used.
PR 5661146: Fixed a problem where save as .tif does not work on SEx64
PR 5770295: Fixed a problem with Cannot borrow a solidedgecatiav4 translator license
PR 5773849: Fixed a problem where formulas are not recalculating correctly.
PR 1605256: Fixed a problem where Solid Edge aborts when trying to create a projection of a curve

=====Draft=====

PR 1599332: Fixed a problem that caused a crash during DWG import
PR 1600466: Fixed a problem where replace block does not work
PR 5772730: Fixed a problem where you are unable to locate images.
PR 5779513: Modified the Mouse wheel behavior in Draft to be consistent with 3D modeling environments.
PR 5765119: Fixed a problem where Save As PDF forces draft documents being saved to be active
PR 1594976: Fixed a problem where blocks were being corrupted through copy.

---
End
---

 

[KENAT]

Thanks Schipperus,

Appreciate the info.

Does anyone know about my main question which do models get updated just from opening them?

KENAT, probably the least qualified checker you'll ever meet...

 

[beachcomber]

Sorry Kenat, I misread your posting as going from V18 to V19 - must have been the last bit about the wally who got hold of V19 etc.
How big are your assemblies? - our main GA's are 20K+ parts, with some at 30K.
Please post your comments again if/when you do upgrade.
Good luck

bc

 

[KENAT]

No problem, seems if I give too much information people get sidetracked but if I don't give enough then peoples responses don't often don't apply to my specific issue, I struggle to get the balance right!

KENAT, probably the least qualified checker you'll ever meet...

 

[PatCouture]

Hi Kenat

At my last job we had to upgrades our machines from Windows 2000 to Windows XP and then jump to V19 from V18 and those two machines really got a hit regarding performances so I hope that you don't have to go through the same thing.

Patrick