"Lele's VRay Tools" Script Pack:Realtime Sky Added

[visumporec]

All i can say that is really fantastic and very useful tools!
One more thanks, Lele
... e veramente grande il lavoro che tu fai...

[^Lele^]

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.

[crazy homeless guy]

Lele,

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.

Thanks, Travis.

[^Lele^]

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.

[glorybound]

Exposiometer script

Where can I find the Lele's Vray Exposiometer script?

[ruud3dv]

Are you ok, glorybound? :P
Read the first post

Greetz, Ruud

[glorybound]

Duh

Holy Moly!

[^Lele^]

err, updated the realtime sky to include one new typo bug (fixed ) and a better overall usability (better match with default physcam exposure in 1.5 final)

[wxyz]

Error loading biped problem?

Has anyone else gottern an "Error loading biped problem" on reloading a scene after incorporating bthe matrix exposimeter in a toolbar?

[^Lele^]

The UI configuration and the max Cpp coded plugins ones are quite unrelated
This much i can assure you
However, if you feel this is the (repeatable) case, please send me the culprit scene over, and i'll investigate it.

[palibebeh]

Lele - my HERO!!

Your camera converter just saved my life and a lot of time - manual conversion from max's FREE camera, when it's path is tracked frame by frame is a real pain in the mouse...

thx man, I owe you one

[wxyz]

Bip Fix

If the bip is returned to figure mode before the save I do not get the error. Just a bip with a loaded animation and a physical camera gives me the reload error. Max 9 -32 bit-Windows XP Pro SP2 Extion 1 Release 3
QX670o 4mb ram

[^Lele^]

what the exposimeter does is to render an image, analize the framebuffer pixels, and find a measure to multiply the ISOs (or divide the shutter speed) by.
The ONLY thing modified inside your scene is actually the physcam parameters: iso or shutter speed (or white balance colour).
I fail to see the relation between the script and the crash.
It may sit with the physical camera, from what i can understand, but i would love a file to see it with my own eyes, and in case try to find a workaround or a fix.

[^Lele^]

Thanks for sending me the files, wxyz.

There IS indeed an issue with the exposimeter and bipeds (and you mentioned, afterburn too).

It has not to do with the script directly, rather it has to do with the Max 9 Render Presets handling, which the script saves before modifying them for the exposure phase, and reloads upon exposure completion, but does so through the max method for it (ie. no obsucre custom code there).

Create a Biped.
Save a render preset from the render dialog.
Load it back, save the scene, done: the file won't open anymore.
Also, the filesize will decrease by roughly 150K from before the preset was loaded.
That happens ONLY with max 9, independently of Vray being contained in the presets, or being the current renderer, so my idea is that it's truly an Autodesk thing to fix.

So, rather than changing the script, I'd suggest you to do as you said: do the exposure before adding either a biped or (if that's the case) an afterburn item.
Better still, there's another, easier, thing you can do is to save the file before exposure.
Expose at will, and note down the ISO value you find to work for your camera.
Reload the previous version, and modify it by hand.

Sorry for this, but i feel it's not worth it to write a custom presets saver for this type of issue, as that one works pretty well in many other instances.

[dbuchhofer]

ouch rough bug.. would it be worth adding a check for bipeds in the scene and a warning msgbox?