From now on, this one will be the main thread for the script pack.
Grab it from here: http://www.scriptspot.com/3ds-max/leles-vray-tools
Remember to cast your vote if you like it, my ego does need the pampering, thankyou ever so much. :lol:
It contains:
Anything to Physcam
VRay Light Monkey (freshly added as macroscript)
Matrix Exposimeter
PPT/LC Calculator
Physcam Auto-Focus
Physcam Parameters Cloner
Physcam Presets Deck
VRay Stuff Collector (Updated to collect IES profiles as well)
VRay Render-time Infos (Updated not to throw up an error if a skylight is present, and to let you know if any material has reflection/refraction interpolation active, and with which min/max settings)
Realtime Sky (Allows for realtime updates of the VRay Sky map in the viewport background. Any change to sun position or parameters will be reflected in viewport in realtime)
Install Instructions:
Unpack the lot (with subfolders) into a temporary folder of your choice.
Open Max (8, 9 32bit, 9 64bit), then from the menus do “Maxscript->Run Script” and point to the “main_installer.ms” file (do NOT drag and drop or run individual scripts.).
Choose from the interface what you want to install (make use of the “?” buttons by the side of each script name), and press the install button.
Follow the on-screen infos.
Licensing: The pack is free for personal, and non-commercial use.
If you use it in a business environment, do support the developer (ME!) through a small donation via Paypal: my time is as precious as yours.
Bugs, feedback and new features:
Report bugs through the email my profile sports.
Oftentimes, a stripped down scene is very helpful in reproducing and squashing the bugs.
Use the same email to request new features, knowing that timing and availability of both bug corrections and new features may and will vary greatly, compatibly with my daily engagements.
I am every hungry for Feedback.
PLEASE let me know if the script doesn’t start, throws up exceptions and so on.
Often it’s MY fault, but it’s somewhat hard for me to check it on my own during developement: i NEED your feedback.
Last but not least, did i mention i’d love for you people to get in touch with some feedback? :lol:
Yeah, if I can just push the donation point further.
These tools are extremely helpful and I imagine alot of you use them, especially in a commercial environment.
So send the lad some greenbacks, the tools are well worth it, let alone the continued improvments and fantastic support
tbh, what i’d find most useful is info telling me whether i checked the “Don’t render final image” box, and whether the LC and Imap’s are set to save, and their modes. those are the main reasons i end up cancelling important renders to double check settings.
i was wondering how you have thought about the vraysky. if i use this in a scene and autoexpose. the sky colors is wrong ( to dark) thought i have read somewhere that’s a bug of RC3, but i’m not sure. any suggestions on that front ?
I don’t quite understand what you mean by this post, pixelstudio.
If you refer to the matrix exposimeter, all it does it to try and set the scene colours to 1.0 float (average, as per the weighting and brightness ranges chosen).
To have a brighter sky, darken the materials (whatever your RC. that’s how it works throughout), and the other way around.
If i misunderstood, please reply and let me know (sorry i overlooked this thread entirely for a while, my bad…)
Watching the new feature videos for max 2008, i thought it would be nice to have the VRay sky to update in realtime already from version 8.
I just added a script that does that.
Re-download the pack and have fun.
p.s.: the instructions are included in the \realtime_sky folder, or in the corresponding installer ? button
quick edit: it’s strongly suggested to keep the Background Texture Size at something like 256 in the vieport driver preferences to obtain optimal realtime performance. If updates seem sluggish, slow, or impossible, that’s what you want to change.
Customize->Preferences->Viewports->Configure Driver->Background Texture Size-> click on 256
I don’t seem to be able to change this from the maxscript side.
If anyone knows how to do it, please let me know.
Hopefully you can help, because I need to resolve this problem when I get into the office in the morning.
Forgive me if I can’t remember the names of things, I am on my home computer right now.
I used your tool to convert standard max cameras to vray physical cameras. As I was working, I decided to delete the original Max camera. Apparently that was a bad idea. I sent the job to BackBurner to render, but it keeps erroring out. Again, I am at home, so I can’t remember the exact terminology. It is something like… Right Birds Eye camera defined but not found in scene. Or something along those lines.
Any idea on how to correct this, without recreating the cameras by hand? I can post the exact terminology in the morning, but thought I would get a head start on trouble shooting it.
The issue you have seems to be due to the fact that the converter parents the new camera to the old one.
This, though, should only make the physcams lose their animation, not have max error out.
Make sure you haven’t got the render camera in a locked state (in the render panel, at the bottom).
An important note for the VRay Realtime Sky users: it’s strongly suggested to keep the Background Texture Size at something like 256 in the vieport driver preferences to obtain optimal realtime performance. If updates seem sluggish, slow, or impossible, that’s what you want to change.
Customize->Preferences->Viewports->Configure Driver->Background Texture Size-> click on 256
I don’t seem to be able to change this from the maxscript side.
If anyone knows how to do it, please let me know.
