UserWarning: MPS: 'nearest' mode upsampling is supported natively starting from macOS 13.0.
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Your question
We're running on probably unsupported hardware. AMD RX 6900 XT on a Mac 5,1 with macOS 12. We got errors launching running without any parameters: 'RuntimeError: "upsample_nearest2d_channels_last" not implemented for 'Half'' but can get around it if we started with --force-fp32.
The issue however is when rendering we end up with a glitched image result.

While generating this we see in the logs:
/Users/rmp/projects/ComfyUI/venv/lib/python3.8/site-packages/torch/nn/functional.py:4001: UserWarning: MPS: 'nearest' mode upsampling is supported natively starting from macOS 13.0. Falling back on CPU. This may have performance implications. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/native/mps/operations/UpSample.mm:255.)
return torch._C._nn.upsample_nearest2d(input, output_size, scale_factors)
100%|
Requested to load AutoencoderKL
Loading 1 new model
/Users/rmp/projects/ComfyUI/venv/lib/python3.8/site-packages/torch/nn/functional.py:4001: UserWarning: MPS: passing scale factor to upsample ops is supported natively starting from macOS 13.0. Falling back on CPU. This may have performance implications. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/native/mps/operations/UpSample.mm:246.)
return torch._C._nn.upsample_nearest2d(input, output_size, scale_factors)
Prompt executed in 31.60 seconds
Is this error what would produce the image result or should it still work with the fallback to CPU?
We have been using Automatic 1111 running without problems utilising the GPU in this environment and would love to move to Comfy. Any ideas or pointers greatly appreciated
### Logs
_No response_
### Other
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.