Magic Resolution consistency/override about t3 HOT 3 OPEN

The Blend operator causes odd behavior due to GetTextureSize being used in a way so that it only cares about one of the input images:

from t3.

It's tempting to try to use context.RequestedResolution (like the new SetRequestedResolution), however I see 2 problems with this approach:

• Result cache system would need to be more complex (dirty-flag per requested resolution or no cache support for updateActions when resolution is different)
• I feel isolated resolution override is a different use case from what SetRequestedResolution offers, and offering the latter as a solution to the former would cause confusing behaviour (resolution override that transcends operator boundaries would have unintended consequences etc)

from t3.

Thanks for the feedback. You're correct in that ideally all ops using [GetTextureSize] should publish this parameter to allow an override. In practice, I have to admit, I'm hesitant to implement everything that would be consistent because I'm afraid that that many operators would suffer from too many parameters. Also there is a small performance overhead by the added parameter.

On the other hand, I recently stumbled over the same issue. So I added [SetRequestedResultion] after our discussion on discord.

from t3.