Last week, for comparison and trying to find the best workflow I also installed the very expensive Datakit plugin for Rhino to try native imports straight into Rhino. I also can bring native NX assemblies (important for me), parasolids, etc. I could not say the same about Rhino (lots of trimming errors, blocks don’t keep assy information intact, and require manual scripts to turn blocks into layers). In fact I import massive assemblies there error free, and with a really clean assembly structure. The reasons: it’s really fast, not slower than other programs. Hi micha, I had the same experience and impression as you in the past, but lately the upload from the cloud right-side column instead of the ‘new design from file’ has started to grow on me. In the past I tested Fusion 360 - a pain for complex models, since the model needs to be loaded to the autodesk cloud It’s also a helpful tool to help you recognise that there is no holy grail, and that even the might of Autodesk suffer from the same failures from unrealistic filleting expectations. $300 a year may seem steep to a hobbyist but if you’re a commercial venture it’s a no brainier, depending on what work you produce and what tools you need.įusion must represent less than 1% of my workflow. **Startup:**If your entitlements have been designated as “Startup, ” You may use the service if You are (i) a company generating less than $100,000 (or equivalent in other currency) per year working on a project or product that is not yet commercially available, (ii) an individual working on a project or product that is not yet commercially available and is generating less than $100,000 (or equivalent in other currency) per year, or (iii) an individual using the service on a personal basis that is not for commercial, professional or for-profit use. Or you could buy Rhino (who wouldn’t) and use Fusion 360 for free in perpetuity (*for now) if you’re a student/hobbyist or: PS: You can also use whatever renderer you want, but I digress… Make sure you follow that pain by writing long rants of why Chuck can’t make as good of a fillet, import AND boolean tool as a 60K MCAD tool, etc. Or do it all in Rhino like in the old days, one tool, all pain, countless hours of manual surfacing and artisanal filleting using trimming pipes and blends. So you all stop bitching already, buy more tools and get your work done faster, charge your client more, repeat. Also expecting that much for the price of Rhino is absolutely bonkers. More importantly doing this doesn’t put me in the weird delusional state of expecting everything under the sun from Bob & Co., including controlling the future of plugin developers. I have plenty of evidence to proof that my friendships with the McNeelies have not been affected by using other tools, they seem to be very open minded. It doesn’t violate any laws or religious restrictions, and it will not make you enemies with McNeel. So yeah, it’s not illegal to use ALL THE THREE. I’ve also found that I can also use Modo for more complex SubDs. That’s just based on how I use each of those tools, your experience shoudl be different. I personally don t see Fusion360 as a replacement of Rhino, but definitely as a replacement for Spaceclaim and Solidowrks. So if you like Tsplines you can use it there. I’m finding that they complement each other quite well. While you all keep bitching, I wanted to remind you that you can buy and use BOTH Rhino and Fusion 360. Its a temptation almost beyond belief to sell out for a price FAR beyond what you could EVER hope to make selling your plugin one sale at a time. I’ve watched this play out time and time and time and time… again with AutoDESK. From a purely profit perspective, either works, and BOTH have been used by ADESK with great success since its inception. A favored variant: buy out the plugin developer, support its product for a couple of years and drop it cold. This is a marketing strategy followed by AutoDESK from its inception. Parallel develop your own competing product (360 Fusion for instance) using modules and tools from the package you bought out, to assure YOUR product’s compatibility and usability going forward, then DROP the licensing, support and development - once users are locked-in to the plugin functionality, all but forcing them to migrate to your replacement product. Support and even do some development for a couple of years or so. Here’s why: You BUY OUT the best plugins for ANY serious competitor approaching a fractional market share that’s large enough to appear on your “competitor” radar. MisterB - "…why would you continue to sell software that adds propriety functionality to a competitor’s product? " Good question.
0 Comments
Leave a Reply. |