[Closed] MaxScript & VRaySphereFade
Hello,
this is a very specific problem with VRay (1.5 SP2), I know I should post directly on ChaosGroup forum but they don’t want me to post if I don’t have a VRay license (!) (ok! but I won’t buy licenses if I can’t resolve this problem, and since I can’t ask to their developpers on their forum without a license!! It’s some kind of vicious circle…)
Anyway,
I’m trying to add gizmos to the atmospheric “VRaySphereFade” but the original max methods to do so (<atmos>.numGizmo; appendGizmo <atmos> <node>; deleteGizmo <atmos> <node>)do not seem to work, and the VRaySphereFade.gizmos property is an array parameter with a fixed size, where the only way to append or remove items is by clicking on the boring “Pick” and “Remove” buttons in the environment window ‘-__-…
So, if anyone has ever been blocked or has resolved this problem, please help!!
thanks,
Paul.
Have you tried sending them an email with your problems, I’m sure if you’re ready to buy the plugin, but are evaluating this particular problem, they’d be more then willing to help you out… I would…
But I don’t have vray so can’t help you with that.
Goodluck,
-Johan
I tried…twice…
but I also found a post from a dev on their forum talking about the problem, and they solved it apparently, but not in the demo, apparently
thanks for your advise!
Paul.
http://www.cgplusplus.com/online-reference/vray-properties/
I think you need to use the vraysphere maxscript to add gizmos to the node
instead of the max ones
oh wait … you allready tied that
WOW! didn’t knew that doc!
That’s worth a solution to my problem
thanks a lot!
Paul.
I asked about this problem in the vray forums, and can confirm that it is not working for 1.50 SP2, both using append gizmo and trying to directly assign an array of nodes to the gizmo property of the vraySphereFade.
I assume when they say it is fixed it means it will be released with the next version.
I have been a bit frustrated with the initial lack of maxscript support for vray materials and atmospherics and Vlado has been quite responsive with some of my requests. I just need to wait for teh next SP to see the fixes!