That could have been it. Many thanks!

Thanks. It probably was it, but I've found an even neater solution: swift public var cgImage: CGImage? { guard let image = CIImage(mtlTexture: self, options: nil) else { print("CIImage not created") return nil } let flipped = image.transformed(by: CGAffineTransform(scaleX: 1, y: -1)) return CIContext().createCGImage(flipped, from: flipped.extent, format: CIFormat.RGBA8, colorSpace: CGColorSpace(name: CGColorSpace.linearSRGB)!) }

Thanks. I'll see about feedback assistant tomorrow, but I'm not sure if I will be able to create a concise project that reproduces that. What I am utterly confused about is that this code works perfectly fine on Intel and fails on M1. I tried adding Blit synchronize for the texture, thinking that maybe this was the cause, but it didn't do anything. Interestingly, I found out that only for the green channel I get the 0.0f values, for everything else I seem to be getting "nothing" (meaning that when I add or multiply the sample result for r, b or a, it also always comes back as black, while green behaves as if it actually is 0.0f). And the result is always the same, no matter which coordinates I sample. I'd rather not go to 2D array texture unless there's no other solution. Like you said, it would require changes not only in the shader, but also upstream, that I'd rather avoid.

All right, so this is what happened: After setting the texture in the compute encoder and ending the encoding, but before committing the command buffer, I was flagging the texture as purgeable. For some reason Intel did not purge the texture before rendering, while M1 did.

I would like to add, that the same IPC code also works fine with FxPlug 3. It only breaks down inside FxPlug 4, where the plugin is ran as a separate service.

Switching from MPSImageScale to MPSImageLanczosScale solved this error. Does it mean that MPSImageScale is an abstract base class? Why can it be instantiated then and it's not mentioned in the docs?