VRay Next - Light Lister Max Script Error

[dreidesign]

I'm getting an error when I open the Light Lister "--Unable to convert: undefined to type: Float"
In this line (595):
if ( not bit.isFinite (vrayLLister.getLightProp vrayLLister.LightIndex[vrayLLister.count][1] multiplierProp)) do (
.....

[anna.zaharieva]

Hi,

Can you send us the scene, please?

Best Regards,
Anna

anna.zaharieva@chaosgroup.com

[dreidesign]

Scene sent!
I also got this error in an empty scene when just adding one vray light.

[dimension3plus]

Same here! Any solution?

[dreidesign]

For me this was related to the Verge3D Plugin I got installed. This automatically adds Verge3D options to new created elements. And it seems that the light lister doesn't like that options in vray lights.

[dimension3plus]

Same here Thanks. Can't even remember why I installed it in the first place.

[JezUK]

Yes, I too now get this error and I too recently installed Verge3D in the last few days and now Light Lister is not working as described.

Haven't tested to see if it is actually Verge3D that's the problem, but Light Lister was working before, no problem...

[Morne]

I queried this with the Verge guys and their attitude was that its not their problem as they don't do anything to the Light Lister Script.

Did any of you guys manage to resolve this issue? Only thing that worked for me was to uninstall Verge3D and re-install VRay.

It is a little annoying that they add components to everything, even if you dont use it. Then everytime you merge something from a scene, all the Verge stuff comes with, even if you have it uninstalled


Maybe the higher ups at ChaosGroup can get into contact with the Verge guys and we can get this annoying issue resolved?

[^Lele^]

They seem to have a MXS tool which removes all their custom parameters, though.
Also, there's an option which may be the culprit for adding all that stuff, under the verge3d menu: "auto assign verge3d parameters"

See if either helps.

[Morne]

They seem to have a MXS tool which removes all their custom parameters, though.
Also, there's an option which may be the culprit for adding all that stuff, under the verge3d menu: "auto assign verge3d parameters"

See if either helps.

Thanks Lele, I'll check it out next time I need to use their plugin again...

[dreidesign]

We are working quite often with Verge. I simple keep the "auto assign verge3d ..." option off, just like Lele already pointed out. You most of the time dont need these. I then only add them for example for the camera by hand.
But maybe chaosgroup can "fix" the light lister anyways? I dont know if this is heavy work our even possible, but can the lightlister maybe just use their own options? So that no matter which parameters are getting added to vray light, even from other plugins, that this doesnt interfere?

[^Lele^]

If anyone has access to nightlies for v.5, could you confirm the issue has gone away?
I have just installed verge, created a vray light, checked Verge3D added the parameters, and then opened the VRayLightLister, without issue.