Hey all,
I’m having an odd minor issue. I’ve set up a scene and my render size is 1920 x 1080. It says so in the settings and on the render dialogue when it’s running. But the VFB is saying it’s 960x540 and the rendered frames saved are coming out at the smaller resolution.
I’m fairly sure I haven’t touched any unusual buttons so why is it rendering at only half the size it should?
I’m on Vray 5 hotfix 2 and Max 2021.
Yeah that’s what I thought but that button is greyed out and unselectable. It appears to be down though.
You would need to check the render size button on the top of the vfb…it defaults to 50%.
EDIT: they beat me to it 
Unlikely, but did you specify the render resolution manually in the v-ray vfb settings, in the render settings panel?
It is disabled while IPR is running ?
It seems disabled all the time. If I IPR render in window it does nothing. If I do a normal render with my settings it is still disabled but somehow active. I’ve got around it for the time being by just rendering at double the resolution but there doesn’t seem to be a way of turning it off.
Any script/render pass manager going?
Nope. And it’s only just started doing it as well. I was rendering the same scene yesterday with no issue. All I’ve updated is some maps on the geometry.
Well, we have no feature which allows rendering of a percentage of an arbitrary resolution, besides the IPR button (which in your case is greyed out, as it should be for final renders) and which isn’t sticky.
So, it could have been possible that a different, incidentally half-sized, resolution was specified in the VFB settings, but if doubling base resolution doubles the output, it cannot be us.
I would investigate if you dragged in the scene a callback which would be entirely capable of taking renderwidth and renderheight and reset them to their respective halves.
Even if, in another scene/session, you have been trying stuff out, bad code could make things stick.
Does another scene behave the same?
If it’s only this one, and it does it with a single sphere, please send it over for investigation.
I think it heard you and altered itself back out of fear. I just pressed render again and it’s fixed itself. I am confused but I’ll take that as a win.
Ahah, whatever works!
I had this issue too, spent ages trying to work out why and gave up as had to move on. Ended up merging into a new scene. Also sometimes when I press render, nothing renders. VRay just starts to render and says done straight away. Again merging into a new scene is the only way I could fix it.
Indeed, the more i hear of it, the more it smells like a scene-persistent callback.
I’d love to see one scene doing this, truly.
I haven’t managed to replicate the resolution bug but I have just come across the bug I mentioned where the scene doesn’t render. VRay just starts to render and then stops, only way to fix it is merging into a new scene. Or uploading the Chaos Cloud seems to be OK. Here is the file: Dropbox - Error - Simplify your life
Confirmed in max 2021.1.
Resetting render settings and quick rendering crashes max to desktop, which produces a nice minidump.
Thanks for this.
Hi, it’s an interesting one. The scene seems to have an invalid effect attached (it’s enough to open the Environment and effects dialog and 3ds Max will crash). I’ll be trying to understand a bit more on this, but I guess not much could be taken from it. As a workaround one could delete the problematic effect before anything else with MaxScript, for this particular scene:
deleteEffect 1
Best regards,
Alexander
Yes this was another bug I have been experiencing as well. Some of these files were created in older versions of VRay and 3ds Max. They may have PSD manager plugin in environment/effects. But certainly along with this bug, the incorrect resolution mentioned by the OP and the VFB not rendering anything all appear to only happen in these types of files that are a few years old. Merging into a new scene is the only work around I found.
So that is what the mysterious render effect is, PSD manager?
It can’t be queried for class (returns “undefined”, max itself doesn’t recognise it) and can only be removed.
It’s not us, either: the same exact thing happens with Scanline as main renderer: open the environment dialog → CTD.
It’d be nice if the developer was advised of this, regardless of fixes (which may have to be on the Autodesk side.).
I can confirm deleteEffect 1 fixes all the bugs, thank you 
Glad to hear it is not a VRay issue either, but as you say, the developer of PSD manager should be made aware.
