Swarm Internals/Raw Resolution vs. Resolution/Aspect Ratio/Custom

[brendanhoar]

Expected Behavior

If Aspect Ratio/Custom values are to be ignored, due to Swarm Internals/Raw Resolution overriding them, some sort of indicator should alert the user.

Actual Behavior

Changing values over and over but always getting the exact same width x height output.

Steps to Reproduce

...well, that was a journey:

1. Created a grid, including a Raw Resolution parameter.
2. Later loaded an output file and reused parameters, ensuring Aspect Ratio/Custom was set so that the images resolution would be loaded.
3. Saw the resolution I had for that file replaced the values in Aspect Ratio/Custom.
4. Modified the values in Aspect Ratio/Custom
5. Generated an image.
6. Image generated was same as original image, changes to the values in Aspect Ratio/Custom were ignored.
7. Lose mind.
8. Half an hour of refreshing/restarting/failing later, look more closely at every generation parameter.
9. See that Swarm Internal has a Raw Resolution parameter and that is also set to the same value as the original image.
10. Say "ahhhh, I see..."
11. But also say: that's not really intuitive.

SUGGESTION: Perhaps "Resolution/Aspect Ratio/*" should have an indicator when the "Swarm Internals/Raw Resolution" value is overriding that setting?

Debug Logs

N/A

Other

I'm not sure what outcome you'd prefer @mcmonkey4eva.

As for me, I'd be ok with any of the following solutions singularly or combined as needed:

1. Indicate that the aspect ratio parameters are being overridden by the Raw Resolution parameters when enabled.
2. Use whatever parameter was last changed by the user (maybe not great).
3. Move the two parameters closer together to ease in discovery.
4. Make the use of one parameter immediately mark the other as disabled in the UI.
5. Figure out a way to combine them happily (might not be possible).
6. Something else that is reasonable, lol.

B