I have been corresponding with an SW user and he has some very interesting comments to make at times. One of the things he presents is the idea that move face in SW is basically as powerful as direct editing is in SE, or Synchronous Tech for you purists who are not happy with ST 😉 . So he sent me some video links from Youtube and one in particular caught my attention.Now I assume that if you are trying to augment your position for or against that you are going to make an effort to find something that will buttress your positition. So I am using one of the video clip links sent to me as an example of parts done in Move Face in SW
I recently posted on “Editing Around a Pattern” and his contention was that it was as easy to do in SW to. One of the things I mentioned to him was the fact that the file size basically does not grow or change with edits in ST and does not create ever expanding file sizes and complexities that can blow up on you later. The edit I did in my post for instance went from 911KB to 956KB for the first edit. Then reversing that took it to 954KB and reversing that again took it to 957KB and nothing was added to the “History” or Path Finder on this part. I presume I could do this a hundred times and it will stay in this range and back and forth two times each was good enough for me to make this assumption. No size baggage and no added complexities.
So a couple of days pass and I go to see the video links and I decided after looking at the one shown above I would show how I do it in ST6. At this time I will be doing the paper tray and the bracket and perhaps the “Desk Tidy” will be in the future. I want to point out the growth in the complexity and size of the history trees that happen with parametric history based modeling and what I have to believe is the ever growing size of these files and I assume the potential for trouble. I can see the history tree in the video and it is ever growing. Now one of the really nice things about ST is that if what you are doing works it will always work again. If SE accepts what you do and it shows up in the feature tree, or Pathfinder as it is labeled in SE, it is stable and will not blow up. In my experience it either works or it does not and I never have dependencies in the ST Pathfinder that will do the atom bomb thing on my part. I will say though that once a week or so for reasons I don’t understand SE does not like what I do and it tells you that it is quitting now and your data after your last save is lost. Of course auto-save stops this from ever being a serious headache. Now here is a caution about auto-save and SE and this one has tripped me up a few times. In ZW3D I can step back past a save and go into edits before the save. There is a cache in there that allows this until it is cleaned out when you shut the program down. In SE when you save you don’t ever get to go back past that point. Now maybe there is something that will allow you to do this but I have not found it. Where this comes into play primarily for me is when I am experimenting on a part to find the best way to do what I want. These are the times when SE decides to shut down and so I am left with the choice of save and don’t get to re-play the part or don’t save and perhaps lose the part.
My parts were done in ST6, exported as IGES and then brought back in to ST6. A cautionary note here about imports and this applies to STP and IGES files. I round tripped this Paper Tray in parasolids and the edits worked fine as is. When I did the same in IGES to keep as close to the SW example in the video it did not work. The practice the SW user used in geometry inspection is a good habit to get into. the equivalent here in SE is under the “Inspection” Tab and is labeled “Optimize”. In the case of this paper tray part “Optimize” corrected whatever was holding up the ST edits and it worked flawlessly after that. There will be three videos on editing imported files. There will also be one working directly as a native file. In some important ways in history based modeling it is cheating when you work on an imported file. In the native file you have in parametric history based stuff dependencies and ever growing complexities that can and do often cause trouble and doing a round trip is a way of trying to get away from those problems. I think you who are not familiar with ST will be fascinated with what can be done and how little files sizes and feature counts change here with edits.
Join me as I show how this user does this in SE ST6.