1. Feedback
  2. Idées
+1
Terminé

Screen position should optionally be per-fragment rather than per-vertex

robert briscoe il y a 11 ans • mis à jour par Freya Holmér (Developer) il y a 10 ans • 2

Admin Edit: Renaming the title.

Original title: "Screen Position Node Broken?"

Original post below:

So I just started experimenting with screen projected textures using the screen pos node, and although it looks ok in SF, it acts really crazy in the editorImage 87

Solution

Solution
Terminé
Freya Holmér (Developer) il y a 10 ans
It's not really broken, but it's interpolating per-vertex rather than calculating per-fragment, which will look bad on low-poly objects. There should be a per-fragment option. I'm renaming this thread and switching it to a feature request rather than a bug :)

Edit: There is now a checkbox for per-pixel screen coordinates as of Beta 0.16!
Prévu
Freya Holmér (Developer) il y a 11 ans

It's not really broken, but it's interpolating per-vertex rather than calculating per-fragment, which will look bad on low-poly objects. There should be a per-fragment option. I'm renaming this thread and switching it to a feature request rather than a bug :)

robert briscoe il y a 11 ans

Quick Question: Is the refract shader also interpolated per-vertex? because i'm getting a lot of the similar issues with refraction also:




Freya Holmér (Developer) il y a 11 ans

Yep! Refraction is done in screen space, so it's using the same screen position data as the screen position node :)

Solution
Terminé
Freya Holmér (Developer) il y a 10 ans
It's not really broken, but it's interpolating per-vertex rather than calculating per-fragment, which will look bad on low-poly objects. There should be a per-fragment option. I'm renaming this thread and switching it to a feature request rather than a bug :)

Edit: There is now a checkbox for per-pixel screen coordinates as of Beta 0.16!

Service d'assistance aux clients par UserEcho