- Wed Oct 30, 2019 6:19 am
Agree on that one. It heavily depends on what's your primary software and how you're using it. And what's more important, is what exactly you need Maxwell for.
For example, my primary software is Maya. And I do everything there. I use Maxwell for visualising stuff that I produce in Maya (plus, Maya's plug-in is well developed) so for me it Makes sense to go for a Plug-in version.
I rarely use Studio - only for rare occasions, when I receive finished CAD data from our industrial designers - then might use Studio - to visualise stuff (if it's simple and does not requires any further asset development). If the asset (CAD data) that I receive requires more work (like fixing tessellation issues, or doing proper UV mapping, adding extra elements, like liquid, and other stuff) - then I just import that CAD data straight into Maya - and go from there.
Studio, however, has some benefits over plugins versions. Like procedurals, more stable extensions, convenient UI for libraries, live link with HDRLS, and other stuff ... and .. .. overall more stable (read: less crashes).
Plug-ins - are more flexible. Especially when they are well developed (Like for Maya) - they are just a blast to use, since you have all the functionality of your native app + Maxwell's amazing engine.
Honestly speaking if NL would ever adds a kick-ass UV mapping workflow to Maxwell Studio - that would be the truly hard-to-beat- app. Because most apps that are using it (assuming it's not 3D Max or Maya or Cinema - those use mostly plugins) have pretty shitty UV workflow (like .. pretty much any CAD app) - so that could be a killer feature for it.
Hope it helps