Render frames smaller than settings say

I made a callback, which should clean such issues with borked effects automatically on file load.
Put this into your scripts/startup, and it should just print out a listener line if a file is loaded with bad effects, stating it deleted it (or them. one line printed per effect deleted.).
Unfortunately i can’t make it more informational, as the effect can’t be queried for properties (name, class, and so on), but it should avoid max crashes and non-rendering.
vrayPostLoadScripts.zip (407 Bytes)

Thank you, that is very helpful.

Please re-download and overwrite the script.
I forgot 3 characters, it would only delete the first such effect.
The zip linked now works on multiple ones, in case.

I’m the developer of psd-manager and had a look at the provided max file (would have been glad to look at it earlier, if someone hat contacted me).
The max file is simply broken (inconsistent data), it has no trace of a psd-manager effect in it or anything pointing to it ever having been there in the first place. This max file basically says “I contain 1 render effect”, but there is actually nothing there. So 3ds max crashes when it tries to do anything with it.

If you have a normal max file with a missing plugin effect, it would show up as usual in the UI as a missing plugin. You will receive a message stating which plugin is missing (the max file holds which original plugin DLL was used to create it etc). You can modify and save the file again, the effect data will stay intact. In this case here however, there is no such information in the provided file (I actually checked the binary data using a hex editor). So from the max file I can say - nothing points to psd-manager being used here. If ever, then the problem is with the code that removed it before it was saved.

I have never seen such a file before. I was wondering if there is any code in V-Ray that deals with removing old V-Ray Lens Effects that still were implemented as render effects? I just thought of these render effects, because James mentioned it being related to older V-Ray files.

Daniel

Indeed, the effect had absolutely *no way* to be queried, it could have been anything at all from what we could see.
Thanks Daniel for taking the time to look into this, anyway!

If this still has anything to do with my original post, I don’t use PSD Manager, which is probably why there is no trace of it.

I just wasted a good half an hour on this stupid button trying to understand why my image was saved half the size…This is the worst button in the frame buffer and needs some serious rethinking or redesign.
It’s impossible to see when is on or off.

Maybe an earlier version? They appear to have changed it so it’s now as the attached.

So it’s orange now..I still would rather see 100% all the time on that icon, not a 50% button, there’s not even a 100% option in there so you cannot revert to normal, the only clue that is “ON” is a slight different color grey icon when becomes enabled, that button is very close to the other buttons too, there should be more space,it’s easy to select that by mistake and not notice…Well thanks for the image, good to know of the improvement.

Ah no, I meant to show that it is grey when off, orange when on. It was totally irritating when it was just grey/slightly different grey before :stuck_out_tongue:

I am confused now fixeighted, I’m on Vray 5 still…does Vray 6 now has an orange button when is on ? You mean you just did that in photoshop? the documentation shows no new feature for this.

Hehe no it’s not PS, it’s Vray 6.10.08 when toggled on :slight_smile:

Ok cool…thanks.

​

Not sure if OPs issue was ever resolved, but maybe it helps with future issues. There is a small option in the render settings of Vray, at “IPR options” that say “fit resolution to VFB”. It’s on by default If I’m correct. This will override your desired render size and just render whatever resolution is given to the VFB by size of the VFB window.

If Vray stops immediately, you should take a look into render log. It usually happens to me due to an insane amount of triangles, caused by too large/too many or too high resolution of VrayDisplacement. I’m no expert, but it probably means that your machine runs out of memory and tells Vray to go fck itself, stopping the process.
​

This fixed it for me… i thought that setting meant it would zoom in/out to fit the image.

This however only affects IPR (it’s in fact on by default.), not “offline” rendering.
There is another, new place to look into, now, and that is the camera settings: each camera can now specify its own resolution, and while the setting is off for old scenes, it’s easy enough to forget on after toggling it.

​

I think this also overrides the “fit resolution to VFB” setting, as I didn’t have any issues until i stopped using resolution override due to a bug in Vray that breaks the region render when resolution override is on.