

I'm also grateful to companies and individuals who sell their plugins, I bought dozens of great ones. That mentality, never complain, that doesn't work with me. And people have been saying it, I'm on this forum long enough, but it's to deaf ears obviously. But singling out nice people and suggesting they are inept is not a good argument. Remember that some of the developers are good friends with members here.

No one likes to see a friend get sh!t on. Especially when those friends played a pivotal role in the plugin ecosystems for many years. But when they finally get round to exposing the API fully that paves the way for extensions to build out that platform.

Imagine the possibilities when that occurs. You then have the ability to learn ruby or C+ and cater LayOut to your needs. Maybe even monetize your scripts to earn additional cash flow by sharing your creations. I have my own regards the SDK but if I sh!t on the Dev team rather than helping them identify areas that need fixing I would have got nowhere developing WrapR.Īlso, you can't be banned for saying the stuff you're saying. It's just not the best way to frame your argument. You've some really good contributions here I hope that continues. I too share frustrations with the current state of SU (and especially LO) - the performance issues / long-term bugs / missing features and the painfully slow pace of front-facing advancements from version-to-version. However, I'm also aware of how much work has gone into re-writing the back-end / graphics pipeline / API / developer tools and am willing to wait at least one more release cycle to see the fruits of these efforts before casting judgement on the efficacy / focus of development efforts. If I were leading the SU dev team I would be concerned that competitors are catching up faster on SU's ease-of-use than SU is in advancing AEC / BIM workflow support (amongst other missing capabilities) and associated functionalities.īut there's a lot of awfully smart people on that team, so you have to assume they understand their own priorities - and it is likely that the foundational work required to bring SU into the modern era has precluded the most-frequent user-requested changes from being implemented until that work was complete. Hopefully we're pretty much at that point now, and we'll start seeing a pace of positive evolution that pleases everybody. When you strip away the emotional content from these types of posts, what remains is that most users love SU, prefer to keep using it, and simply need it to get better in supporting their (professional) workflow.
