Possible to port FSR 2.0 / 2.1 / 2.2?

[mhtvsSFrpHdE]

I see ReShade community comments about you can't have TAA because no motion vector
but TFAA did emulate motion vector behavior (far better than other ReShade TAA port without motion vector)

Could this be possible to use with FSR 2?
Lossless Scaling / magpie community also mentioned there are no motion vector, so you can't have FSR 2 series
I know ReShade have no API for upscale,
but just 1920x1080 to 1920x1080, use it as antialiasing method?

[Spacellary]

👀 That'd be amazing but I think we'll need proper motion vectors for that, maybe they add them in the upcoming graphics update.

[mhtvsSFrpHdE]

👀 That'd be amazing but I think we'll need proper motion vectors for that, maybe they add them in the upcoming graphics update.

@Spacellary So qUINT / DRME is still not real motion vector that can compatible with FSR 2 requirement?

[Spacellary]

I asked Alex if DRME or his FFXIV_MOTIONVECTORS could be used to implement FSR2, and he replied:

no

also ffxiv is mainly cpu constrained in most scenarios. if you're struggling in e.g. limsa, it's not because of your gpu most likely

also do note that the REST addon with all bells and whistles does add an additional cpu overhead (the UIONLY version very much less so)

I think most people should stick to the UIONLY version of REST.

But hey, maybe there's a way we haven't found out yet.

[mhtvsSFrpHdE]

I asked Alex if DRME or his FFXIV_MOTIONVECTORS could be used to implement FSR2, and he replied:

no

also ffxiv is mainly cpu constrained in most scenarios. if you're struggling in e.g. limsa, it's not because of your gpu most likely

also do note that the REST addon with all bells and whistles does add an additional cpu overhead (the UIONLY version very much less so)

I think most people should stick to the UIONLY version of REST.

But hey, maybe there's a way we haven't found out yet.

Thank you for the information!
This issue shall closed then.