yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2026-08-09 11:15:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update index.md

Browse source
This commit is contained in:
Matías Locatti 2023-10-19 02:20:31 -03:00 committed by GitHub
parent c003129152
commit 551707bfb2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
site/content/entry/yuzu-progress-report-sep-2023/index.md
View file

@ -315,7 +315,7 @@ Games don’t report their motion vector data to the console, since they were ne
There are ways to implement this, we could add one frame of delay and extrapolate data.
The downside here is that 33ms of delay for 30 FPS games would be utterly disgusting.
We could guess motion from previous frames, but this could have a very high performance cost and produce very erratic results, old frames can't read the future.
We could guess motion from previous frames, but this could have a very high performance cost and can potentially produce erratic results, old frames can't read the future.
Or we could dip our toes into AI, which has given us unsatisfactory results in the past.
As you can see, while coding a generic way to extract motion vector data might be possible, it’s a huge endeavour, so expect it to be a very low priority at the moment.
We have bigger fires to put out first, after all.