just wondering if it is simple enough to have 2 plugin.ini files and use the -p switch on the max exe to be able to switch between the beta and the offical releases?
how would licensing work in this case?
what about render farm?
or is the beta stable enough to not worry about this?
The Beta is relatively stable, but not stable enough to completely move away from 1.1.2. In fact, we have 4 different builds installed on our network, including 1.1.2, 1.4.5 and some intermediate betas that were locked for specific projects to avoid breaking the pipelines. There are some features that are under construction in 1.4.x and might not be completely reliable, especially Matte Objects which we are working on right now.
You can use different plugin.ini files to switch between the versions. If you are using Deadline, you can also submit jobs with alternative plugin.ini files.
How exactly you will handle the plugin.ini switching is up to you. On the workstation, you could even have a single plugin.ini with two entries and remark one of them with ; to disable loading manually. Then you could just edit the file when you want to switch (which I think shouldn’t be very often).
I personally am using the latest build in production and it is working fairly well, but be sure to read the Known Bugs and Limitations list…