Support dont sent the file.!!!
Plzzz answer!!!
Support dont sent the file.!!!
Plzzz answer!!!
It’s already Saturday night over here; you will get it on Monday at the latest.
Best regards,
Vlado
LOL @ Vlado! I love your new signature! Seems very fitting right now. ![]()
I wish I could hang a sign on my office door that says something similar.
Hang in there, it’s almost over.
Hi there,
Is the Beta open to users with an educational license or is it exclusive to commercial license users?
I’ve asked to become a beta member but in meanwhile I’ve a question about the beta:
if I’ve understood well Chaos send me an updated license file for the dongle but when beta will expires, if I don’t buy the upgrade I imagine that Vray 2.4 still works regular… Is it correct??
I asked the same thing, and this is what support responded with: “Yes, your license for V-Ray 2.0 is not affected in any way. You can install and use V-Ray 2.40” So no worries on that.
So this single render node we’re getting with the new ui workstation license, Is that so that you can render on your workstation, or so that you can DR on another machine?
In other words, can I render with my workstation and dr to another machine, or only on the workstation with this single node license?
Hi Morne,
The render node license is used when a node renders (or we could say when a machine needs to access V-Ray rendering core library).
In this aspect, local render or network render (DR,…) are one and the same, each of them consume one RN license per machine.
So with the 1 User license including a single render node license, basically only your local machine can render either through Production render or RT render.
Let me know if any other questions.
Oh wow ! So what you are saying is that the 1st option for upgrade 1+1 its Not workstation+ slave render but just workstation render?
Jip, just when we thought it couldnt get any worse
Damn
I did not see that 1 coming :c
The render license is not tied to your workstation; you can use it to render anywhere, on your workstation, or on a render node, but it is just one license (i.e. it is not possible to render both on your workstation and on another machine). With that said, upgrades for multiple render nodes are available.
Best regards,
Vlado
Having been in marketing for many, many years I must say your ability to communicate new pricing models and product combinations to customers somewhat leaves something to be desired. When Chris said:
" If you are an existing V-Ray 2.0 user / for upgrades:
1) Upgrade V-Ray 3.0 User license (1GUI + 1 RN) : 300EUR
2) Upgrade V-Ray 3.0 User license + 5 Render nodes (1GUI + 6RN total) : 500EUR
3) Upgrade V-Ray 3.0 User license + 10 Render nodes (1GUI + 11RN total) : 700EUR
You can see that we already have the option 1 User + 5RN you suggest for both new license (2) and upgrade (2). We did our homework
Why don’t you consider these options ?
Last edited by Chris_ChaosGroup; 09-07-2013 at 11:22 AM. "
I think most people assumed that a “GUI” would be able to render on it’s own, i.e. your workstation is not a node.
You are correct unfortunately. I agree wholeheartedly that the whole thing could have been handled soooo much better.
Best regards,
Vlado
I haven’t had too much difficulty understanding the new licensing model(s), but then again there have been points raised in this thread that I hadn’t considered. I think some clear cut visual representations of the difference between the two licenses and the pricing structure would be a big help for both sides. ![]()
There is 2 points that have not been mentioned in this thread:
1- CG fees are dropping more and more while client are looking for superproduction that require more time. 10 Years Ago still image price (western Europe) was done for at least twice the price as today.
2- Drastic change in license policy may boost the pirated version.
There could be a correlation between this 2 points!
Fraggle
It’s a large problem alright and it’s being well documented in the vfx world at the minute. There’re very few other industries though where we quote on a job based on some vague ideas, execute it three times over but get paid for it once. We’ve got business model issues first and foremost, if we solved those then we wouldn’t be worrying about redundancies or 50 dollar vray rendering licenses ![]()
Firstly, this depends what industry you’re working in. Secondly, hardware costs have dropped massively since I first started doing CG professionally 13 years ago. £1’500 can get you an incredibly capable machine today, which when adjusted for inflation is truly amazing. Thirdly, the steps in producing CG today are not the same as they were 10 years ago - in our pipeline (if two people have a ‘pipeline’) V-Ray plays no small part in that. I look back at old projects and the hoops we had to jump through compared to today and the advances are incredible.
I admit as a very small outfit upgrading isn’t going to cost us a great deal compared to most but even with the price increase I consider the return in value for V-Ray’s continued development and fantastic support a drop in the ocean.
what about 1b) V-Ray 3.0 User license (1GUI + 2 RN) : 350EUR ?
one for the new workstation and one for the old workstation… ![]()
Hi Everyone,
Let me try to demystify our licensing and explain from where we started until where we are now.
Prior V-Ray 3.0, V-Ray has always been using the same terminology - this can be checked via the V-Ray License Server → interface and (different) render licenses.
Interface license is what we also refer more accurately as GUI (Graphical User Interface). This GUI license is used whenever you need to access the user interface of V-Ray to setup some parameters, typical example is when you open the Render Settings to define the GI solutions, set the color correction, distributed rendering,… All what is specific to V-Ray.
What happen when you do not have available GUI license ?
if you open the V-Ray render settings, you will see an error message “Could not obtain a license (-xxx)”.
(*) We can also give the example of PhoenixFD - the Phoenix interface license (or GUI) is used when opening the Phoenix user interface to setup a simulation.
Phoenix is not a rendering engine, it does not render and so does not have any render license - it uses V-Ray to render.
Render licenses were until now split is different sub-categories : local render, DR render, Network/Batch render, RT render. Lots of them so quite complicated to follow.
With the new licensing, we simply regroup them in 1 single type called “Render node” (RN) license.
Therefore it becomes very easy to understand – whenever a machine needs to access the V-Ray rendering core library, you need 1 render node license.
What happen when you do not have available Render node license ?
if you launch a V-Ray rendering, you will see an error message in the V-Ray log window stating “Could not obtain a license (-xxx)”.
There is no value added to provide a GUI without at least one render node, otherwise you could not even do a local render or even setup a V-Ray shader in the material editor – that’s why the first offer in for new license or upgrade includes at least 1 render node. From a user point of view, the minimum you want to purchase is 1x GUI + 1x RN, what I refer as “User license” in my explanation.
As mentioned Vlado, the RN license is not tied to your hardware nor limited to local render. So this should be seen as part of the render license pool you have available for rendering.
From there, everyone has different needs and requirements - that’s why we provide different options.
If anything is still unclear about the new pricing structure or if anyone would like to check a concrete example, feel free to ask either on the forum or to our sales email where our team will reply you quickly.