System Information
Operating system: Windows 10
Graphics card: GTX 1080
Blender Version
Broken: 3.0
master.79425ed32676-windows.amd64-release
Worked: 2.93.5
Cuda would map to the first point in a UV because when I use a mapping node and use location I can move it across to parts of my image to an individual pixel on that image.
OptiX and CPU/only works without issue.
https://i.imgur.com/Ea4DNep.png
https://i.imgur.com/NrG5gfU.png
https://i.imgur.com/68OHWHp.png
Can confirm 3.0 not working, can't open this file with 2.93.4 - it says file format not supported. I am not aware of such break in compatibility though @Marcus Stange (Toys0125) is this something that happens on your end too?
@Richard Antalik (ISS) I would believe they added no compatibility patch temporally to prevent 3.0 blend files from breaking unexpectedly. They might add it back in a later patch. I also tested that you can still back port if needed with copy and pasting data blocks between blenders usually with a version number at a time. I did a 3.0->2.95->2.94->2.93->2.90 testing to see if it was bugged in any earlier versions.
Well I can open files saved with 3.0 in older versions, that's why I am wondering. In any case it's not relevant to this issue.
So tried testing with the eariler verisons that in blender builds blender-3.0.0-alpha+cycles-x.b8238733598d-windows.amd64-release also have the issue where it says file not supported. Still can copy and paste into blender without issue. And it does render correctly in blender with cuda. But funny enough that EVEE did not work correctly. https://i.imgur.com/3dZd1lX.png
https://i.imgur.com/ONVvKQE.jpeg
Will test more later.