Vray 1.6 open beta
-
@andybot said:
There's a very painful bug with SU8 where some materials applied from the SU material palette cause an immediate bugsplat. SU7 and SU2013 do not have this problem. Not in SU7? Are you sure?
-
@andybot said:
@lcarlin247 said:
I am going crazy, i just installed the new vray for sketchup 1.6 beta, and every time that i apply a material on a surface the bugsplat screen appears, does anyone know why is this happening??
There's a very painful bug with SU8 where some materials applied from the SU material palette cause an immediate bugsplat. SU7 and SU2013 do not have this problem
Oh yes they do. Read my post above. I did a clean sweep, installed 2013 and no other plugins other than Vray. I just can't seem to fix it. I've tried alsorts of things.
-
Dunno, I've tried it with both SU7 and SU2013. I get crashes in 2013, but not consistently like with SU8. As in, I can apply a material from the SU palette and it doesn't crash immediately like with SU8. However, I gave up on 2013. I was getting all sorts of random crashes. I have actual work to do, so I removed 2013, I just don't have time to deal with this $h!t
-
@thomthom said:
Not in SU7? Are you sure?
There was a discussion thread with dkendig and valerostudio on the CG forum a little while back where this was elaborated on. For whatever reason, this error surfaced in SU8 only.
-
It was a SU observer bug. The Maxwell guys actually reported it before I was able to, but I did give them a high five for reporting it.
-
Vray 1.6 is good..
but whenever i start sketchup it produce bug splat ..
without vray 1.6 it works fine
.. please some one help -
sounds like a faulty install. Be sure that SketchUp and XMLDRSpawner processes are not running when you try to install the 1.6 beta. Also be sure that the license server isn't running. DO NOT UNCHECK ANYTHING when installing the 1.6 beta, and if you are prompted to restart at any point during the installation, do so immediately, do not click "No" and continue the installation. After the restart you will need to run the installer again most likely, because Windows had to remove some files that were locked during the attempted uninstall process.
-
@andybot said:
@anteolic said:
I really dont know where to ask this question than i ask here.
Does vrayforsu 1.6 beta has some limitation or what cause i cant get more prepass in IRRADIANCE MAP than just one.
There's an option for "multi-pass" (under "advanced options") If it's unchecked, you will only see one pass even though it is doing all the calculations. See if that is the case.
Correct me if I am wrong. So you mean we have to uncheck the Multipass option when doing render to ensure multi prepass in IR?
-
@petrusyap said:
@andybot said:
@anteolic said:
I really dont know where to ask this question than i ask here.
Does vrayforsu 1.6 beta has some limitation or what cause i cant get more prepass in IRRADIANCE MAP than just one.
There's an option for "multi-pass" (under "advanced options") If it's unchecked, you will only see one pass even though it is doing all the calculations. See if that is the case.
Correct me if I am wrong. So you mean we have to uncheck the Multipass option when doing render to ensure multi prepass in IR?
No, AFAIK that button only affects what you see in the render window, not what is going on "behind the scenes"
-
I found out, if we previously render using RT, after we back to the usual common render processing, the multi prepass won't process more than 1 prepass. If wanna have prepass rendering processing again, we have to reset the rendering option.
-
So Vray 1.6 doesen't work in Sketchup Pro 2013. Do I may have to wait? What I should do?
Thanks.
-
@kalu said:
So Vray 1.6 doesen't work in Sketchup Pro 2013. Do I may have to wait? What I should do?
Thanks.
We developed this beta, using the SketchUp 2013 Beta on one development machine, and SketchUp 8 on another. We should be 100% compatible with both versions.
-
For all the people that work in 1.6.0.23 I have an issue with the install of the new version, is some related to the beta and it shows a 30 days demo with a code and you cannot work in vray because it run as a demo with watermarks.
Only if you have an issue with a error message and a code number please contact support at:
vrayforsketchup@chaosgroup.com
They fix the problem I spend a couple hours try almost all in Mac OSX and after I give up. the customer service fix the problem ASAP.
Thanks again to the customer service of Chaosgroup, Corey, and also Andy, valero for your help.
Gonzalo.
-
Any chance for animation working in version 1.60.23?
-
I am using Sketchup 2013 & vray 1.6.023 beta. As of last night I have started getting vray watermarks over my render. I have had this version since its release, with no watermarks.
Can anyone explain why I have suddenly started getting them?
Thank you in advance
-
The beta period is over, your demo license has expired. When you upgrade to 2.0 you will receive a dongle that plugs in via USB and your watermark issue should disappear.
-
@dkendig said:
The beta period is over, your demo license has expired. When you upgrade to 2.0 you will receive a dongle that plugs in via USB and your watermark issue should disappear.
Hi dkendig,
I also have a beta 1.60.22 VR4SU on SU2013 and have just noticed I'm getting the watermark/600x400 res output treatment as well. I have to produce some renders in the next week, and I fear that registering for 2.0 and waiting for a dongle could take some time that I don't have... I live in Australia.
If I download the 2.0 demo/trial version, will I have 30 days of no watermarks, or will watermarks remain for that as well?
Otherwise, I might have to revert to a 1.49 trial on SU8 Pro to avoid the watermark.
Can you please assist?
Thanks
-
You will need to contact a local reseller. I would imagine that it would not take long for a local reseller to ship it to you. Here is our list of resellers in that country: http://www.chaosgroup.com/en/2/purchase.html?g=5&pID=10
I believe that the 2.0 demo has a watermark from the start. Our 1.6 beta gave you some time before the watermark kicked in, but this is no longer the case.
Advertisement