something worked wrong with render settings for me

Hi Mahmoud, would you mind sending me your .blend file so I could troubleshoot?

That link says "Access Denied" (at least for me).

Hi @Mahmoud ,

The link is working now, thank you.

I can't find anything wrong with your file, but it doesn't seem to be working in 4.1, for some reason.

When you open your file in 4.0 (and ignore the warning that it was written in a newer binary), it works fine. Both images get the correct Resolution.

It's getting late here now, so I haven't looked into whether it's a bug in 4.1, or if perhaps something just works differently, but I'll investigate a bit tomorrow.

I managed to get it opened in 4.1 under windows, but the issue persists. I'll have a look in a few days when I am back in the office. See what I can find.

Hi Mahmoud and Paul,

I'm not sure if this was not clear, but, the problem is with Blender 4.1. (I suspect it's a bug.)

Use Blender 4.0 and all is fine.

(And it has nothing to do with your computer or Operating System Mahmoud, I am using Linux.)

Okay guys,

I think I've found something:

In Blender 4.1, use the arrow keys to switch the Inputs in the File Output Node:

Then Render again. 

Yeah, you are right.

The hack works perfectly in Blender 4.0, but in 4.1, the File Output Node uses the Resolution of the first Input.

So, when switching the Inputs as I said, the second Input gets Scaled down to 96 by 96, but the Image is still 512 by 512...

Basically, the hack only works in 4.0 (or before, probably, haven't tested that).

You can make a Full Copy of your Scene and change the Resolution of one of the Scenes, but you'd have to do that each time....That's why Paul came up with this hack...unfortunately, and I think this might actually be a side effect of an optimization, this doesn't work in 4.1...

We could submit a Bug Report and see how they'll react,...???

Oh, that's a great idea Dwayne!

OOOF This update has rendered my explanations and research obsolete! Ok, I'm going to try and see what the workaround for this is. It's pretty important! I was blown away when I discovered this hack of rendering out different sized files at the click of a button. File Output should technically do the work of two separate outputs - that' the whole point of multiple inputs. Will look further into this.

I'll have to make a note on that lesson, or an addition ASAP to warn about this issue. I'll work on an efficient work-around and add it to the course. So far, Dwayne's solution is the most efficient

Yup. Try as I might, the file output node won't recognize the scale function downstream. I've tried this in 4.2 alpha as well. For now, the solution is as Dwayne mentioned above, and use two file outputs. I still feel like I am missing something really small.

Hey Paul,

Not sure if this can be helpful, but 4.2 has an Extension (Addon) :

Probably won't lead to an easier workflow than Dwayne's two File Output Nodes, but mentioning it anyways (I'm aware, that you might have known this already...).

Hmmm I will have a play around with this! It could have its uses, but yeah, setting up two cameras for two separate renders might be adding in redundant things when the compositing solutions proves simpler. I've submitted a bug report and see if I get any replies.

UPDATE: I submitted a bug report. Developers will be taking a look. This is likely what is happening. A developer is taking a look.