Can a file created using Vray 3.0 still be rendered in Vray 2.4 ?

[JezUK]

I've created a scene using the beta 3.0, now I need to use a machine that has 2.4 on it.

Can that work ?

[vlado]

Yes, you can do that. Just be sure to set the image sampler to something else than "Progressive" before you render in 2.4.

Best regards,
Vlado

[Dariusz Makowski (Dadal)]

This question is very popular... maybe add it to FAQ? =D

[JezUK]

Thanks Vlado,

I had to uninstall my copy of 3.0 back to 2.4 just to understand what the problem was and now see that I have used VRayBumpMtl I think it was called - which I believe wasn't in 2.4.

Now that I know that that was the problem I will remove that material from my scene and and render those scenes in using 2.4.

So I need to put 3.0 back on in order to edit those materials.

I've tried reinstalling 3.0, but the trouble is, when I try to start the service for VRay, I get this error message;

"One of the following licences are required: - WibuKey 250897:7758101 Failure reason: A suitable WibuBox entry was not found (17)".

Please can you advise me what I need to do ?

Kindest regards,

Jez

[Dariusz Makowski (Dadal)]

Long shot, try restarting PC ? Or restarting License - kill license task and start again.

[JezUK]

Hi Dadal,

I tried that - no fix.

I guess this is the time when I get to understand what/how this licencing really works, it's all a black art to me

[vlado]

I had to uninstall my copy of 3.0 back to 2.4 just to understand what the problem was and now see that I have used VRayBumpMtl I think it was called - which I believe wasn't in 2.4.

A version of VRayBumpMtl material for V-Ray 2.4 is available here: http://help.chaosgroup.com/vray/misc/

"One of the following licences are required: - WibuKey 250897:7758101 Failure reason: A suitable WibuBox entry was not found (17)".

Unplug the dongle and plug it back in (maybe in a different USB port).

Best regards,
Vlado

[Preisler]

Remove the dongle and reinsert it again.

[JezUK]

Thanks everybody, I got it fixed.

It was as you all say, removed dongle, updated the Wibu drivers and reinstalled dongle that fixed it

Thank Chaosgroup (technical support was FANTASTIC !)