![]() ![]() It is undeniable that the marketing description was overstated. The flaw was not in the programming, but the marketing. The underlying fact remains that I imagine people will be disappointed with the release as it currently exists so I stand by my view. That is a big project, but I look forward to the time when I can build UI automatically in the plugin, and when you can play with Maxwell nodes in Grasshopper… so whatever the initial state of the plugin, those are some of the long-term goals.Īnd no doubt there are many challenges and you have done good work. mxx extensions, etc) and I don’t want to go too far down a dead end in the plugin with the old one. That’s good, but however functional it may be, the UIs are not exactly what I’d call nice when used to this extent, and it would be a mistake to think that custom UIs won’t be written for them.īeyond this, though writing this plugin did involve wrapping the whole Maxwell sdk (c++) for access via c#, the fact is that RhinoCommon is not the only piece of the puzzle in flux we have, for some time, been working on a new node-based sdk for Maxwell, which is much more modern and capable, and not weighed down with the baggage of a decade of ad hoc extension (understand, the current one was never designed to accommodate things like Maxwell FIRE. On the other hand, you may or may not have noticed that we start out this time with every parameter being implemented in terms of macro/script, since mac Rhino generates UI for commands. I have already gone down the road once, of writing a lot of code to work around such missing things, and will wait this time to do things the “official” way. regarding RDK support), apparently in Rhino 6. Regarding the plugin itself, indeed it is a bit of a stopgap, while we wait for the mac sdk to reach parity with the win sdk (esp. I am not going to comment on any of the licensing/packaging points, as those are outside my area (I am the plugin’s developer, and happen to be in agreement with you on much of that). Don’t hang around waiting for Mac GPU support anytime this decade though (my opinion). Also some new features, but the drawcard features are more a misfire.īut look upon it as a beta release with things improving over time. ![]() ![]() Still very familiar, but laid out better so there is more room to move on a normal screen. However, the Studio interface has been reorganised a bit. You also now only get a single plug in though, so pick carefully. You would have saved money skipping V3 as V4 is cheaper than the discounted V3 (depending on the options chosen). Unsure yet after only playing with it for an hour.īottom marks to Next Limit for offering a free upgrade to V4 if you rushed out and purchased V3 at a 30% discount. ![]() However, it does save you a little time over the previous workflow, but I suspect that I may end up staying with the old way of doing things. Material handing is a bolted on workaround. No GPU on Mac (they claim it is because Macs don’t have Nvidia cards). This i find very strange… for such an esteemed application.īe prepared for disappointment (well, I was). *not directly related, It was surprising to notice that sadly V3 Maxwell studio does not seems to support Ratina display behaving as if it was an old Win app. With my rendering needs seems to me pretty much high-end in complexity and not something a beginner can expect to achieve in the limited time until the Maxwell announced 30% discount promo expires on the 5th of Sep. it looks like it will necessitate to give it a large chunk of time to learn how to use, all before i could actually test if it is suitable for my rendering needs. Thank you for explaining about Maxwell Fire, it sounds very important for the design development process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |