+1

Ukończony

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

11 lat temu • Ostatnio zmodyfikowane przez 11 lat temu • 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 editor

Głosuj

Odpowiedź

Odpowiedź

Ukończony

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!

|

Odpowiedzi 2
Zacznij od najstarszych
- Zacznij od najnowszych
- Zacznij od najstarszych

Planowane

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 :)

Odpowiedz
|

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

Odpowiedz
|

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

Odpowiedz
|

Odpowiedź

Ukończony

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!

Odpowiedz
|

Customer support service by UserEcho