This is terrible news. I would have at least hoped that a v3 plugin would be available for Sketchup 2017 given the very close release times with Maxwell 4. This is basically forcing the user base who use the plugin to upgrade. Shame. Bloody good job I bought the v4 upgrade in the Black Friday sale. I'm currently in the middle of several large projects, all in v3 and didn't want to have to upgrade until such time as the v4 teething problems have been ironed out- I was hoping at least to be able to start using Sketchup 2017, but seems I will be stuck with 2016 for a while longer.JDHill wrote:Sorry, it will not be possible to make a Maxwell V3 plugin for SU2017.
Unfortunately, no, it wouldn't be possible for someone to do that, because the main problem has not to do with API changes, but rather binary ones -- along with changing the Ruby version, they also changed the compiler they are using, to one that is not even yet supported by the Maxwell SDK (not even for v4, I mean). That's something that can be handled for v4, because the SDK would have had to be built with that compiler at some point in time regardless, which ends up being now, precisely because of SU2017. But to support v3 would involve going back in time in the Maxwell code and getting everything running with this compiler, before then doing the same thing in the plugin, and though it may technically be possible to do that, it is not feasible, since it's not necessarily trivial to change compilers, given the third-party dependencies involved.CDRDA wrote:I assume that the new APIs in Sketchup 2017 make updating the Maxwell v3 plugin as well a time-consuming task. Perhaps someone in the community can work out how to make it functional... If that doesn't break any T&Cs of course...???
On support they tell me that the case was created […]
Part of this is my fault, I know. I accidentally […]
Hey J, Yes, the assistants have not been added ye[…]