|
|
Vray Command fail
About Truespace Archives
These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.
They are retained here for archive purposes only.
Vray Command fail // Archive: Tech Forum
Post by jamesmc // Mar 2, 2008, 5:36pm
|
jamesmc
Total Posts: 2566
|
Maybe some clever scripter can write a routine to snatch the information from the VRay panel, save it in a readable format and have the ability to store in its own VRay Library to be recalled later or shared. :) |
Post by transient // Mar 2, 2008, 5:42pm
|
transient
Total Posts: 977
|
That's an excellent idea. :cool:
Of course, the garage guys have already provided so much good stuff lately, I wouldn't want to be too pushy.
But it would be nice.:) |
Post by trueBlue // Mar 2, 2008, 6:54pm
|
trueBlue
Total Posts: 1761
|
Maybe some clever scripter can write a routine to snatch the information from the VRay panel, save it in a readable format and have the ability to store in its own VRay Library to be recalled later or shared. :) It is possible with the jScript Macro recorder already. Just record your setting that you want and save them to the library. Like "Dam I wish I could render this puddle", "Who will date my Character that has cool hair", or "The most awesome default Vray settings". Some things you can not record would be Color Picker, Images/Path dependent, and Maps/Path dependent. |
Post by transient // Mar 2, 2008, 6:59pm
|
transient
Total Posts: 977
|
Thanks, I'll have to check it out. |
Post by TomG // Mar 3, 2008, 11:21am
|
TomG
Total Posts: 3397
|
Hi all,
An update on Paul's original problem, the glass shader rendering slowly in V-Ray.
Something odd is happening, and there is something of a workaround :)
First thing to note is that the three raytracing settings (Ray Limit, Min Contribution and Max Depth) do not appear to be working from the Stack (if you right click on any of the icons for render scene, object, area, these are visible in the stack).
Instead, it seems important to use the settings in the Model window, in the trueSpace6.6 panel. There is a toolbar there for render settings, one is Enable Raytracing, and a right click on this will open a small Model panel with these three settings.
They control the spawning of rays for reflection and refraction, affecting when a ray is spawned and when it is considered "not worth spawning" an extra ray.
So far both Paul and I got V-Ray to dramatically improve the rendering of the glass object, to bring it in line with the results from Lightworks. Now, we didn't find any particular settings, instead we just had to adjust them until V-Ray would render at an expected speed. Once it starts working, you can then return those values to the desired amount, and it should still render quickly (even if those settings are the same as the ones on show when you first opened the panel).
In Paul's case, he set the values to max, then to min, and then found V-Ray working. For me, I was experimenting and testing so had done various things to the settings, and it started working.
So, if you are experiencing what seems to be surprisingly slow V-Ray renders with with either transmission or reflection, it would be worth trying to adjust these settings, using Area Render in the Model side to see if you get a speed increase.
Note that the increase is significant (from 60 seconds to get 16% complete, to about 20 or 30 seconds to render the whole thing).
All these results have been fed in to the beta process, and sent over to the developers. It does seem to be a bug, so has been reported as such. Meantime, I did want to share this information so that people using V-Ray right now can benefit from this. Apologies I can't give specific values or steps to get it running!
Hope this helps!
Tom |
Post by splinters // Mar 3, 2008, 11:33am
|
splinters
Total Posts: 4148
|
Thanks for the workaround Tom and the help. Hopefully this will be of help to others.
Also, glad to know that I was not simply inept in my settings and that other forces were at work to slow me down...;) |
Post by transient // Mar 3, 2008, 2:41pm
|
transient
Total Posts: 977
|
Thanks to both of you for this, it's a major improvement.:)
All I did was drop the max depth to 3 (in modeler) and there was a major speed boost, with no apparent difference in quality. I didn't touch the other settings. |
Post by transient // Mar 3, 2008, 4:53pm
|
transient
Total Posts: 977
|
Here's a test scene I was having troubles with before, but it seems to render okay now. It took about 1 and a half hours, but I had many settings cranked up and I could have tweaked it a lot more. I had caustics enabled, soft shadows and a SSS surface, but no HDRI or DOF (I didn't want to tempt fate).
However, the memory leak issue is still there. It crept up to 1.4 gig and stayed there even after the render finished. Anyway, it's an improvement. |
Post by splinters // Mar 3, 2008, 11:51pm
|
splinters
Total Posts: 4148
|
All I did was suffer for a few days, Tom solved this one! |
Post by jamesmc // Mar 4, 2008, 8:50am
|
jamesmc
Total Posts: 2566
|
This is all Splinter's fault.
There wasn't a bug until he made it happen. :D |
Post by jamesmc // Mar 4, 2008, 4:06pm
|
jamesmc
Total Posts: 2566
|
Was just teasing in my curmudgeonly manner of course. :) |
|
