i just double-checked 4.4 and it seems to work there, so it is only a 4.5dev5-issue.
should these still be reported, or are bug reports only created for release candidates?

cc @stuartcarnie

i just double-checked 4.4 and it seems to work there, so it is only a 4.5dev5-issue.
should these still be reported, or are bug reports only created for release candidates?

Yes, we encourage reporting issues for development snapshots too 🙂

Some follow-up comments

• I can't reproduce it in the editor when clicking the Preview checkbox
• If I run the project from the editor, it reproduces the issue
• If I run the project directly, it does not reproduce the issue

How do you ensure that Preview in the editor renders the materials / shaders?

How do you ensure that Preview in the editor renders the materials / shaders?

in my setup (linked MRP) i have the shader in front of the camera as a plane. like you would do post effects the "old" way:

this setup with MetalFX enabled and scale set to 0.5 already makes the shader purple in the viewport on my machine.
this is why it appears when the camera is selected and "preview" enabled.

i assume it is getting wrong uv coordinates from the SCREEN_UV parameter, causing it to read outside of the available texture.
but only when DOF is enabled at the same time.

Some follow-up comments

• I can't reproduce it in the editor when clicking the Preview checkbox
• If I run the project from the editor, it reproduces the issue
• If I run the project directly, it does not reproduce the issue

on my machine it happens on all 3 instnaces, even when i run it directly from the project list:

• as far as i can tell, the screenreading shader runs before the DOF.
• as in the editor screenshot above, the issue only happens inside the plane using the shader.

• this makes me assume that the pink is introduced by the screenreading shader.
• but the built-in SCREEN_UV seems to provide correct uv coordinates, as i just tried out (uvs are over 0.5 halfway of the screen):

• also, the texture is not pink yet inside the screen texture read (because this would trigger the r>.9 condition):

• but it is pink when it is beeing blended with the opaque objects? since tranparency lets opaque objects be visible in all of the screen:

• my best guess is that the issue appears somewhere in the auto-generated shader code, or maybe in a step that combines opaque + transparent obejcts

just noticed that it is also only on mobile renderer, forward+ works

just noticed that it is also only on mobile renderer,

Ahh, that is what I am observing too!

When I start the editor with the mobile renderer, the panel is also now showing purple:

Ahh, temporal should not be available in mobile as the renderer doesn't provide motion vectors. I'll need to disable it (which I thought I did already). This is the same reason why FSR2 is unavailable.

This is fixed via #106731, which disables MetalFX Temporal upscaling for the mobile renderer, just like FSR2. Once #100283 merges, we can revisit adding support.