We think X is a fantastic idea, in fact all ideas A-Z are fantastic - but sometimes Y or even G will be higher priority for us, and X won’t be available for some time.

Our team is focused on making the product the best it can be - development takes time, effort and resourcs which can be limited and leads to certain requests (like X) missing in the next release, or potentially not there at all.

There is always a concise release schedule planned out months if not years in advance. If we receive a suggestion that we love and fits within the development tasks in the schedule we try our best to make sure it’s included in the next major or minor release, otherwise it’s added to a feature request pile which we’re continually evaluating along with our vision for the prodcut.

With that said, if the feature is on the schedule we won’t be able to promise it’s availablility until it’s been implemented - schedules change, and we don’t want to set false expectations.

We are still using Yeti 2.x in production and need more licenses, are we able to purchase those?¶

Any new license purchased will be for Yeti 3.0, but these are backwards compatible with previous versions including 2.x.

So if you purchase a 3.0 license you can use it in your 2.x based prodcution.

I have a Yeti 2.0 license and would like to upgrade to 3.0, how do I do that?¶

Yeti 3.0 is a major release which means a new license will needed and can be purchased via our online store - Studio (1x interactive and 5x render licenses) upgrades are USD$299 and Studio Render (5x render licenses) upgrades are USD$169.

No. The Indie licenses use the exact same distribution as the Studio licenses, any scenes created and edited with an Indie license can be used by a Studio license and vice versa. The only limitation is that the software can only be used on a single machine.

Additionally, there is a limit on the number of times you’ll be able to transfer the license - within reason.

Our expectation is that reaching out the Yeti Central community should provide an Indie license holder with the support needed on a daily basis. We are happy to help with basic needs (we want to make sure you can install and run Yeti) and receive bug reports (especially those that cause Yeti to crash) via our support team but it may take a little more time for us to respond.

The Indie license is node locked to a single machine and isn’t able to migrate between machines, so if you’ve purchased a license for your workstation you won’t be able to use it on a laptop. If you would like the license to float between machines we’d recommend purchasing a Studio license and use the laptop as the license server - this way you can also render on both machines.

There are a few more restrictions on the Indie license when it comes to transferring. As it’s node locked we are happy to transfer the license in the instance where the initial license was incorrectly issued, or if an old workstation has died and you need to upgrade but in general the rule is one license transfer per year.

If, for some reason, it ends up you need to transfer a license more than once we will have to charge a USD$100 transfer fee.

With that said, we’re extremely reasonable and happy to discuss if/when the time comes.

All of our licenses are per host, so you can have multiple jobs running on the same host and it will only consume a single license. When querying the license server it may report multiple handles (for each job) but these all point to a single license entitlement.

Although we understand that an automated installer would be convenient for some users, due to Yeti’s nature and how it integrates into various applications we feel that this would make more of a mess than be helpful.

If you are unfamiliar with the process of setting environment variables for your specific platform here please refer to the Setting Global environment variables section of the documentation - if using Linux you should add these to your .tcshrc, .cshrc or .bashrc files depending on what Shell you’re using.