1. Feedback
  2. Ideas
+1
Completed

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

robert briscoe 10 years ago • updated by Freya Holmér (Developer) 10 years ago • 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

Answer

Answer
Completed
Freya Holmér (Developer) 10 years ago
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!
Planned
Freya Holmér (Developer) 10 years ago

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 10 years ago

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) 10 years ago

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

Answer
Completed
Freya Holmér (Developer) 10 years ago
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!

Customer support service by UserEcho