Questions about rendering applications for SketchUp
-
@chippwalters said:
I would've thought these developers would've have thought through this a bit more-- especially in such a competitive space as SU rendering. For instance, my 3D apps including SketchUp Pro, Thea, Vue 9 Infinite, KeyShot, Modo, Lightwave all allow you to install on more than one computer, as long as it's the ONLY one being used at a time. Funny how 'restrictive' and somewhat 'proud' the SU plugin renderers are-- especially when it's clear they're not even the best ones out there.
Ouch... Not even the best ones out there... 
Sorry... To me you seem to compare apples with oranges...
The price for TWR is far lower compared to the price of any of the other applications you've mentioned...Nevertheless... I'll see what I can do to get the developers of TWR to re-view the license policy...
I'm not saying that there will be any changes, cause as others already have pointed out...@d12dozr said:
...that at such a low price ($99), purchasing two licenses for two work machines is reasonable investment.
Perhaps there's room for license policy improvements with upcomming release of TWR ver. 2...!?
-
@frederik said:
Not sure how it works in Maxwell, but if you want to add or change something to your model/scene, you can select only these amendments/changes, export them and in KT as well as in Thea, you can use the merge option to add the amendments/changes to your scene, without the need to re-set and start all over with materials, lights etc...
I'm not sure I fully understand your explanation of the workflow but I'll explain how it works with maxwell. Within the SU plugin you setup all your materials, lighting, etc. Then you can export portions of the scene or the whole scene to an .mxs file (or you can just render directly from SU). The .mxs file is your studio file where you can further tweak materials, settings etc. I'll import my high poly objects into this scene, place them, clone them, etc. If part of my SU model changes you could just delete that part within studio, export that part from SU, and then merge that into the studio file. I personally find it easier to just delete the whole SU portion and merge the whole thing back in. The SU export doesn't take more than a minute or so even on a very large model so it's no big deal.
Regarding the licensing, just in case Twilight wanted to take a look at how Maxwell works. You can open maxwell on as many computers as you want but if you hit render it searches the local network to see if there are any other renders running. The loophole would be if you had two computers that weren't on the same network but I think it's still a good convenient system.
-Brodie
-
@unknownuser said:
I'm not sure I fully understand your explanation of the workflow...
It's similar to your description...
I'm sure you'll see some nice changes to the TWR license policy in the future...
-
Will there ever be a Mac version of Twilight?
-
@dale said:
Will there ever be a Mac version of Twilight?
I'd say yes...
Can't say when, but I'd assume it to be together with release of ver. 2.0...Chris have bee struggeling with a Mac version ever since TWR ver. 1.0 was released, but I believe he has a solution for ver. 2.0...
-
So when is v2 out
-
A couple key thing developers need to remember about licensing, is
- It should not get in the way of legitimate users.
- It should not allow casual users to be able to easily give it to their friends "to try."
- It should NEVER prevent a sale.
Keeping hard core pirates from being able to hack copy protection is for the most part useless, especially if it conflicts with number one above. We know that most, if not all true pirates will never pay for legitimate software-- so no sales revenue is lost One of the best things you can do to protect your product is to continually update it, with a notification in your app of new update available.
It's now very popular to consider licensing to individuals and not machines, just as Maxwell does. Good conversation.
-
-
I just wanted to post an update on the licensing situation in Shaderlight.
For Shaderlight 1.2 we incorporated a new licensing system which has made the installation process much more straight forward for our community. However, we discovered that a limitation of this new system was that we were unable to allow multiple activations on a license code or have the ability to transfer the license to another machine. We have been working to resolve this and importantly maintain the straight forward licensing.
Our development team concentrated on allowing multiple activations on a single code, new commercial Shaderlight activation codes can be used twice so you will be ok to activate your Shaderlight license on your office and home computer. The licensing of Shaderlight allows you to have Shaderlight installed on 2 machines, but only use 1 at a time.
Customers that have an existing Shaderlight license will need to contact support@artvps.com and their license code will be modified.
Martin
-
@martin-art said:
I just wanted to post an update on the licensing situation in Shaderlight.
For Shaderlight 1.2 we incorporated a new licensing system which has made the installation process much more straight forward for our community. However, we discovered that a limitation of this new system was that we were unable to allow multiple activations on a license code or have the ability to transfer the license to another machine. We have been working to resolve this and importantly maintain the straight forward licensing.
Our development team concentrated on allowing multiple activations on a single code, new commercial Shaderlight activation codes can be used twice so you will be ok to activate your Shaderlight license on your office and home computer. The licensing of Shaderlight allows you to have Shaderlight installed on 2 machines, but only use 1 at a time.
Customers that have an existing Shaderlight license will need to contact support@artvps.com and their license code will be modified.
Martin
That sounds great Martin. Thanks very much!
Advertisement