Nope - apparently you didn't read the part where they warn you to not use 2017 beta if you need to open in 2016 - the only thing you can do is save it as another solid like Iges, Step
That's what I figured. And yup, must have missed that. Thanks.
Parasolid Police...... (siren sounds,.. whirl whirl...)
..export as, Parasolid *.x_t or *.x_b (solidworks native kernel since day one, no translation)
The best format to use would be Parasolid, because that is what SolidWorks is based on.
Do File > Save As > Parasolid and under Options select the version number to match your release of SolidWorks..
It increments with each new version.
SW2017 is 28.0
SW2016 is 27.0
SW2015 is 26.0, and so on.
Bill, Thanks for that information.
I always wondered what the versions meant.
Only thing I wonder about, if it is a parasolid, shouldn't the older Solidworks versions be able to read the current Parasolid version?
Would some things not translate correctly to older versions of SW?
If we are to send files to someone where we don't know what version of the software they use, should we send in an older version (say 22) to be sure they could read or translate everything?
There are 2 versions of Parasolid: "Parasolid (*.x_t)" and "Parasolid Binary (*.x_b)".
Is one better than the other or does it matter?
We use "Parasolid (*.x_t)" when we send files to an engineer that still uses Inventor 2011 - seems to work best.
We use an older version of Gibbs software for our machine shop (2011) and the machinists told us to send solids as "Parasolid (*.x_t)" so that they can import the parts (Gibbs 2011 can't accept our 2015 Solidworks files). I don't know if "Parasolid Binary (*.x_b)".will work as well, but we go with what the machinist tells us works.
Each release of SolidWorks adds new features, which is why older releases won't "know" about newer commands.
Thus exporting a newer file with an older Parasolid version will ensure only the older feature commands are used.
I never dug that far into Parasolids.
I just thought they were solid bodies with nothing but what was needed to define the shape.
Things are not always as simple as they appear.
Good to learn new things.
As far as I know, there has been very little change between x_t versions,.. (color, linetypes,.. ?).
You can save back as far as version 8 and all later versions should read the topology without issue... with exception to maybe color, wireframe, curves,.. ?.
If you are using a Siemens product (NX, SE or UG).. there are likely certain supported entities between versions?
x_b,.. = binary, think of it as a zip file or if you've used unix, think of tar.