Vray not for me ?
-
I meant the ASGVIS manual. Too bad I can't afford that Legrenzi manual. But I have had accumulated a collection of pdf tuts from the Web.
-
@steel.monkee said:
I meant the ASGVIS manual.
Look for the main V-Ray manual to learn V-Ray. V-Ray is V-Ray no matter what software it hosted by.
-
funny. i have the same with other engines. because i have used vray and i could say comfortably that i started understanding it and be mindful on what others have been successful or not. now when i tried other render engines, i become frustrated and always compare them with vray. i guess its all about having that comfort level whenever you start another software.
I guess one thing that i have learned from this thread...
Shine and be creative with the software where you are comfortable and used to, and if you want to use another one try the trial version before you buy it.
-
yes, the demoversion.
But Vray remains very limited as a renderengine for SU. Simply because all you can render is one SU-file. With Maxwell you render as much as you like SU files combined in one MXS file out of Maxwell's Studio. This means you can can do so much more than is possible with VfSU. Regardless of how comfortable you are with either render app's. Especially with todays plugin's and their generated high polygon organically shaped objects.
Francois
-
I think Vray is an awesome render engine, once you get it, you love it.
The problem is that it's not studio, that is the ONLY reason I cannot use it in my workflow any longer, I like Twilight and Podium and they also are SU restricted (rumor is they are going studio soon)
-
@solo said:
I like Twilight and Podium and they also are SU restricted (rumor is they are going studio soon)
Don't know if Podium is going studio soon, but you can say that Twilight already have two studio options...
You can setup materials, lights etc. in TWR, export to XML and use Kerkythea or the new Thea Render as Render Studios, where you can adjust things, merge with other models etc...What I find "funny" with all this is, that users seem to have prefered a "build-in" solution in the past...
I believe Podium was the first to intergrate with SU, then came VfSU and Twilight Render was released for about a year ago...
Reason for the "build-in" preference was that users didn't want all the hazzle with exporting, importing etc...
Now this seem to have changed again... -
I still prefer built-in vs studio. But, since SU is stuck at 32bit, which works fine for SU itself, render engines really need to be 64bit these days to make use of modern hardware. And it's most likely because SU doesn't appear to be moving towards 64bit that people want to go studio to get rid of the 32bit restraints.
-
@frv said:
I startup SU frequently and startup got very slow with Vray installed. Up to the point I got frustrated with my regular workflow that does not requires rendering all the time.
If you bought it in the last three months, you have bought the new version which is very buggy, as of now. In order for you to not waste your money, give Vray a chance once a new update comes out. I tell you this because I'm in the betatesting program of vray, and since the release numbered 1.48.66 the beta has now gone up to .83. In the meanwhile, a lot of problems have been addressed, and I think hopefully in the near future the upgrade will be released to paying customers too.
Don't get too discouraged: if you have spent money on it you should at least try to make it work once!
P.s: The fact that you cannot re-sell the license is really a bugger, I admit that!
-
@frederik said:
You can setup materials, lights etc. in TWR, export to XML and use Kerkythea or the new Thea Render as Render Studios, where you can adjust things, merge with other models etc...
Yeah? Interesting.
@broomstick said:
P.s: The fact that you cannot re-sell the license is really a bugger, I admit that!
Yeah. It's a restriction that serves no purpose anymore, nowadays.
-
@broomstick said:
@frv said:
I startup SU frequently and startup got very slow with Vray installed. Up to the point I got frustrated with my regular workflow that does not requires rendering all the time.
If you bought it in the last three months, you have bought the new version which is very buggy, as of now. In order for you to not waste your money, give Vray a chance once a new update comes out. I tell you this because I'm in the betatesting program of vray, and since the release numbered 1.48.66 the beta has now gone up to .83. In the meanwhile, a lot of problems have been addressed, and I think hopefully in the near future the upgrade will be released to paying customers too.
Yea - the patch will sort out many issues.
Ad for loading time - I also find VfSU takes longer than I can bother to wait every time I want to start a new SU instance. I often have one SU window open where I render, and a couple of other windows where I do not need SU loaded. I use my V-Ray Toys plugin the keeps VfSU disabled all the time - and let me load it on a per session basis. -
Frederik wrote:
@unknownuser said:
What I find "funny" with all this is, that users seem to have preferred a "build-in" solution in the past...
I believe Podium was the first to integrate with SU, then came VfSU and Twilight Render was released for about a year ago...
Reason for the "build-in" preference was that users didn't want all the hazzle with exporting, importing etc...
Now this seem to have changed again...I guess it is a little funny, but unfortunately this change is not by choice or preference, but rather necessity. With a competitive market one needs to up ones game and that usually involves more elaborate modeling, high poly trees,vegetation, cars, etc.
With Sketchup being so poly restrictive one needs to compile render scenes outside of SU and what better than a studio based render solution to do so.Personally I prefer the simplicity of an in-house render solution, but alas those days are gone, unless SU can attend to their vintage core and get it in-line with this millennium.
-
According to most betatesters for SU, Google has set its mind on keeping SU as it is.
In other words, SU will last just as long as it takes for the competition to catch up or unill the plugins have taken over the whole app.Highend rendering is rather normal these days, even for students in their second year. Sketchy edges and "profiles" are no longer meant for clients, just for indoor use within the office. SU has become just a modeller instead of the presentation tool it was. Therefore a Studio solution to render is these days much more acceptable and even needed.
Francois -
Whether I render or use Sketchy output all depends on the stage of the projects. We find that rendering realistic images too early on in the project get people too caught up in details that are yet not determined nor important.
-
I agree Thom,
but the problem is that clients these days get rahter more than what you can do with SU. In the early stages of the design I render my models like scalemodels in for example in wood and glass. Those are very appreciated and do not confuse the discussion with details to be considered only later in the process.SU images, sketchy or not have a certain cheap look and feel, not always suitable for all projects.
-
Yes, it is all a matter of fitting the visuals to the project and project stage.
And rendering models of models is a very nice style that I like.
-
@unknownuser said:
@frederik said:
You can setup materials, lights etc. in TWR, export to XML and use Kerkythea or the new Thea Render as Render Studios, where you can adjust things, merge with other models etc...
Yeah? Interesting.
Twilight to Thea do work indeed. You may need to tune up materials as Kerkythea/twilight materials cannot be directly used in Thea. Materials will be automatically converted when KT xml scene is opened at Thea.
-
@thomthom said:
Whether I render or use Sketchy output all depends on the stage of the projects. We find that rendering realistic images too early on in the project get people too caught up in details that are yet not determined nor important.
I strongly agree.
Advertisement