PowerShape 2013 Xforce Keygen X64 X86
Hanry Moreno
It is pretty obvious that PowerShape has not really changed much in several years. Do you think Autodesk will eventually stop updates and totally kill it? In it's current form it works for us, so I am not really interested in finding another solution or learning Fusion 360. F360 is just so radically different from PowerShape that I struggle to even get started. PowerShape is the only modeler I have ever used, since the days of DUCT, so switching now is not so fun.
Like you, I'm a PS user since it's first release (I had a very short brush with DUCT in '98). I can also use other systems now (such as Siemens NX) but in the world of pattern making nothing came close to the combination of powershape/powermill for getting stuff done.
I could list a handful of bugs (or 'quirks') that have been present for over 14 years - eg, unlock a workplane using the workplane dialog and it doesn't re-enable the 'Master' checkbox. That's true for PS2008 -> PS2021 (I've yet to test later versions). A really minor issue and I'm sure it would have been reported many times over the years. I'll bet PS still poops it's pants if you accidentally try to shut your PC down with it open Another niggle that's been there since at least 2008.
Why do I keep bringing up 2008? Well PS8080 is the last version I have a perpetual license for and when Autodesk calls time on PS I'll be going back to it, even if that means maintaining an off-grid Windows 7 PC to do so. I was running PS8080 as recently as 2018 anyway when I first jumped on the subscription bandwagon to work with a new and big customer.
I think this is going to be my last year of paying for the renewal so as the user-base drops away and the upkeep outweighs the demand, clearly they'll have to drop it. Perhaps it could go the way of ArtCAM and be sold off to a 3rd party?
It's hard to gauge the size of the user base. These forums are hardly active and nothing like the Delcam forums of old. I've recently considered publishing a Udemy course for PS but I seriously doubt the level of interest.
Thanks for the feedback. I could not guarantee that I have those files or the dongle, but even if I did, I don't know if I'd want to go backwards. It would be an interesting experiment to see if it's possible.
I switched to VISI a couple years ago when the writing was on the wall with PS. Fusion is nowhere near the modeler for tooling as PS or VISI. I wanted to stay with PS it was just hard to keep sending the money with no updates. With VISI it's like PS with all the updates you could ever imagine. It really is great for tooling. So many options for ways to do things. Especially splitting and parting surfaces. And it's perpetual.
A family member of our boss switched from PS to VISI many years ago for mold making. They were very happy with the switch at the time. For what we do, PS really works well, but I can see VISI as a great option if we ever had to switch.
Working in a pattern/mold tooling shop, I too have been using Powershape (formerly DUCT) since the late 90's, very efficient with it and very disappointed it's no longer being further developed or supported to any degree. Trying to learn and use Fusion 360 the past several months has been extremely frustrating and almost not worth the effort anymore, I cannot even come close to doing what I can do in Powershape to design pattern and mold tooling models. Definitely concerned as to what AUTODESK plans to do with this product in the future. As for now, I will enjoy doing what I do best with what I have. Comments welcome!
Shame as powershape works really well, only updates I see are the extra solid model commands but they run in the background so you dont actually see them. It is stable and useful and runs rings around the Inventor guys when they cannot do anything. more so now as we dont update inventor, powershape we pay for due to the amount of formats it can use and as mentioned before It fixes issues we can get with inventor.
The powershape opcode raises an input signal to a power with pre- and post-scaling of the signal so that the output will be in a predictable range. It also processes negative inputs in a symmetrical way to positive inputs, calculating a dynamic transfer function that is useful for waveshaping.
The powershape opcode is very similar to the pow unit generators for calculating the mathematical "power of" operation. However, it introduces a couple of twists that can make it much more useful for waveshaping audio-rate signals. The kShapeAmount parameter is the exponent to which the input signal is raised.
To avoid discontinuities, the powershape opcode treats all input values as positive (by taking their absolute value) but preserves their original sign in the output signal. This allows for smooth shaping of any input signal while varying the exponent over any range. (powershape also (hopefully) deals intelligently with discontinuities that could arise when the exponent and input are both zero. Note though that negative exponents will usually cause the signal to exceed the maximum amplitude specified by the ifullscale parameter and should normally be avoided).
The other adaptation involves the ifullscale parameter. The input signal is divided by ifullscale before being raised to kShapeAmount and then multiplied by ifullscale before being output. This normalizes the input signal to the interval [-1,1], guaranteeing that the output (before final scaling) will also be within this range for positive shaping amounts and providing a smoothly evolving transfer function while varying the amount of shaping. Values of kShapeAmount between (0,1) will make the signal more "convex" while values greater than 1 will make it more "concave". A value of exactly 1.0 will produce no change in the input signal.
I'm new to powershape, and to powershape macros. I need a bit of help here: I'd like to be able to export my surfaces to a folder within the model path. Where I'm stuck is stripping off from the path the model name, and adding a folder to save in. What are the commands I should use? I've spent sometime searching the old forum and the powershape help. Here's what I have:
Thank you both for your replies. I went with rafael's code on this because it's a lot shorter; but when i have more time, i will dissect both codes to try to learn powershape macros better as it looks like i'll be using powershape more... with that said, i need a little more help to bring this home. the code returns the correct file path i'm looking to use, but gives me an message box saying supplied path is invalid. what is the command to enter the path and file name for exporting? I did add a file extension to the $full variable
Is the Execute Command similar to the Do Command in powermill? As I understand the Do Command, that is a way to back door a solution when the language doesnt quite support what you want to do. Is that the case here, or is Execute Command a commonly used thing in Powershape?
b1e95dc632