FINAL FANTASY XVI PC Demo | RX 6800 XT & 5800X3D | 4K FSR 3 & Frame Generation | No Commentary
HTML-код
- Опубликовано: 11 сен 2024
- FINAL FANTASY XVI PC Demo | RX 6800 XT & 5800X3D | 4K FSR 3 & Frame Generation | No Commentary
Witness the FINAL FANTASY XVI PC demo in stunning 4K resolution with AMD FSR 3 Super Resolution, Upscaling set to Quality Mode, and Frame Generation enabled. Running on an RX 6800 XT and 5800X3D at the highest settings, this video demonstrates the game’s performance at 4K, recorded at 30fps due to hardware limitations. Experience the enhanced visuals and performance boost provided by these settings.
👉 Upgrade your gaming rig with the AMD Ryzen 7 5800X3D processor for peak performance: amzn.to/3AKoys5
(As an Amazon Associate, I earn from qualifying purchases at no additional cost to you.)
#4k #ffxvi #rx6800xt Support the Channel with Super Thanks! ❤️💲
Enjoying the content? Show some extra love by using the Thanks button! Just click the three dots next to the Share button below the video, and select Thanks. Your support helps us keep the channel going and is deeply appreciated! Plus, your comment will be highlighted to stand out in the comment section. Thank you for being awesome! 😊
Looks decently smooth and comparable to 3070 performance. Did it stutter for you overall, and what was performance like during the final Eikon battle?
the game run poorly without frame gen and upscaling, i try it at 4K dlaa no frame gen no upscale, only got around 60-70 and it often drop to 45
I can't get frame generation to work. (Rx 6600)
Whenever I turn it on, a window pops up stating it was successfully activated but then the game closes up.
Thanks for your comment! While frame generation seems to be working fine on my setup (I have an RX 6800 XT with a 5800X3D), I've noticed that other users are experiencing similar problems to what you're describing. It might be a broader issue affecting certain systems or setups.
I recommend checking out the Steam discussion page for the demo here steamcommunity.com/app/2515020/discussions/. Other users might have found a workaround or fix, and it's also a good place to stay updated if the devs release any patches or updates to address the issue. Hopefully, a solution comes out soon!