vray_beta_3.4 Feedback?

[LOAM]

I have signed up for the Beta, when it asked how many copies I selected 4, are we still required to use our current lic dongles for this beta as we are getting "failed to check out valid license" pop ups and nothing works. Any ideas?

[sebastien_berthier]

go to http://localhost:30304/#/
and choose online licensing.

[vicke50]

When I tried to render a animation SketchUp close down after the second image every time even if neither cpu och ram usage was close to 100%, I tried to download vray 2.0 and do it again and now it works without problem.
Is this a bug you have knowledge about or can it just that the rendering was to heavy for my computer? I hade to redo material setting so it can be that I haven't set in all material settings again.

[Peter.Chaushev]

When I tried to render a animation SketchUp close down after the second image every time even if neither cpu och ram usage was close to 100%, I tried to download vray 2.0 and do it again and now it works without problem.
Is this a bug you have knowledge about or can it just that the rendering was to heavy for my computer? I hade to redo material setting so it can be that I haven't set in all material settings again.

Hello,

Have you enabled the following settings in V-Ray 3.4 for SketchUp?
Global Switches > Additional Settings > Batch Render checkbox
Output > Animation > Animation checkbox (also make sure you have properly adjust the FPS value).

Kind regards,
Peter Chaushev

[eliotbnz]

I've been battling a couple of issues - some minor, others not so. I'm certain it's just me being stupid, so hopefully there are answers!

1. Proxies. When I open an existing proxy (SKP file, not vrmesh), it renders out just fine. When I import it to a project, no dice. Vray tells me the vrmesh file (despite me importing the skp version) is not present in the file location - in some instances, these vrmesh files were made by other people and I have either downloaded or been given them. This never happened in 2.0. If I remake the proxy, it works fine, but this is painful!

2. The ol' save your IR and Light Cache maps trick. Render a tiny version of your image, save the IR and LC maps, then re-render at full resolution to save massive amounts of time. Not sure if this is an antiquated trick now, but I still use it as I only have one workstation. Doesn't seem to work anymore - I've tried bucket and progressive. Anyone tried it?

3. Materials. In the past, all of my geometry would be given a base colour, and I would then edit the diffuse/reflect/bump etc inside the vray material editor. Now when I do that, I just get a pure black material in the SKP viewport with no means to edit the texture size/mapping. The workaround is to apply the texture using SKP's mat editor first, THEN use the vray editor. Double handing?

4. Materials 2. Is it possible to import vrmats onto an existing material? I see one can import vrmats as NEW materials, but I can't figure out the former.

5. Vray RT CUDA. Whenever I use this, anything with an alpha channel (leaves for example, with an image is mapped on geometry) doesn't work - vray doesn't render the transparency. My GTX970 is up to date with drivers. Works fine using production mode or RT with CPU. Edit: Fixed this by adding an alpha map to transparency, but seems odd regardless, particularly as it was assets from the Skatter plugin hidden in the ProgramData folder.

I think that's it. Brilliant work though, massive speed increase, love the denoiser and the general increase in UI quality is appreciated.

[boothy]

Hi Eliotbnz

All good questions, unfortunately I have not had enough time with the beta to test some of the yours points yet but I agree I am already missing the vrmat import. Version 3 does however have the ability to copy and paste material so we can always open a new material and copy content to another. This may be slightly a long way around compared to a direct import but could possibly be much more flexible overall. I have not tested render with copying and pasting materials yet but material detail\layers seems to be copied OK although the entire material is replaced just like the original import did. Would be even better if we could copy and paste individual material layers I suppose.

Boothy

[LOAM]

Is there any way that I can keep my install of version 2 running in SU2016? We need it for some current projects that I am working on but I also have SU2017 and would like to run V3 on this only, it seems to want to have to uninstall version 2 in the process of installing version 3.

Any ideas?

Of course I am an idiot, there is an option to "not uninstall previous versions" within the customise section of the V3 installer. I'm all good.

[tedvitale]

Yes! You need to have 2.0 already installed on 2016. When you run the installer, deselect 2016 from the install location list and then open Customize. Uncheck "uninstall previous versions" and Bingo! you should be good to go from there.

Edit: I just read your edit. Glad you're up and running!

[andybot_cg]

I agree I am already missing the vrmat import. Version 3 does however have the ability to copy and paste material so we can always open a new material and copy content to another. This may be slightly a long way around compared to a direct import but could possibly be much more flexible overall.

Please bring back context menu to load a vrmat to replace a selected material. I use that all the time in 2.0, and this copy/paste workaround is irritating, especially with a long list of materials.

[LOAM]

Is anyone having issues with windows (save as, material browsing etc) opening behind the main sketchup window? I think I've isolated it to only happening when I have the asset editor open and completed a render. I was wondering if it was SU2017 related but its doing the exact same thing on a different machine in the office running SU2016 :S

[tedvitale]

Is anyone having issues with windows (save as, material browsing etc) opening behind the main sketchup window? I think I've isolated it to only happening when I have the asset editor open and completed a render. I'm wondering if its SK2017 related :S

Are you working in Windows 7? It is a known issue and we are actively working towards a solution. I've heard in some cases a GPU driver update will fix the issue, but that's not necessarily a fix in all cases. We are working on it though.

[LOAM]

Are you working in Windows 7? It is a known issue and we are actively working towards a solution. I've heard in some cases a GPU driver update will fix the issue, but that's not necessarily a fix in all cases. We are working on it though.

Yeah its W7, driver is up to date. At least you know about it and i'm not going insane

[LOAM]

As a work round clicking on any vray window (asset editor, frame buffer, progress window) will bring the "lost" window to the front again.

[LOAM]

3. Materials. In the past, all of my geometry would be given a base colour, and I would then edit the diffuse/reflect/bump etc inside the vray material editor. Now when I do that, I just get a pure black material in the SKP viewport with no means to edit the texture size/mapping. The workaround is to apply the texture using SKP's mat editor first, THEN use the vray editor. Double handing?

I'm seeing this with Toon materials as well, the workspace just displays black objects.

To reproduce;

1. Create a material, in this case a brick texture and apply it to an object.



2. Render it



3. Create toon material, select the base material and apply it to material



4. Render it



Its doing something unexpected to the base material mapping as well, it appears to be blurring it?

[tedvitale]

Yes, this is a known issue. We are currently working on better ways to represent the in-app representation as well as the scaling issue you have shown in your toon rendering. I believe, though I could be wrong, what is happening here is we are not accurately extracting the UVW information when you apply the toon material to the object. Thanks for the report!