404
- -Page not found :(
-The requested page could not be found.
-diff --git a/build/404.html b/build/404.html deleted file mode 100644 index 5fa13cc..0000000 --- a/build/404.html +++ /dev/null @@ -1,352 +0,0 @@ - - -
- - - - -Page not found :(
-The requested page could not be found.
-- Site was offline for ~2 days for maintenance, as I was moving the entire infrastructure to the new Server, which is located somewhere in the frosty north, and has plenty of hardware to handle the things I throw at it. For those on IPv6, the site should already be 100% online again, while for those on IPv4-only, it may take a day or so to update. During the move/maintenance I learned a couple things: -
- -- And I’m also left with one question: What the heck do I do with 8 Zen3 cores that are practically sitting idle?! -
- -- Update: The mail server is now also available with IPv4 again, as people still pretend that IPv6 doesn’t exist. Notably affected are: Amazon, Microsoft, Google/YouTube, the FFmpeg mailing list, the Debian mailing list, Slack, and some others that I forgot the names of. Shame on every single one of the listed for not supporting IPv6 in 2021. -
- -- It’s been a day since the reveal of FidelityFX Super Resolution, and it appears to be a DLSS killer. But on closer inspection, it seems that AMD made a mistake in at least one of the examples, and forgot to show the FSR footage, instead only showing the native footage. Let’s go into the details on AMDs FidelityFX Super Resolution a bit. -
- -- If you watched the AMD presentation only once, you would most likely not have spotted this – I’ve even had to watch it three times to spot it. There’s three demos in the presentation, but only one of them has this issue: -
- -- Going by AMDs patent registrations, FidelityFX Super Resolution is entirely Spatial, but in the second demo it has information that would be completely hidden without Temporal information. It is able to perfectly represent textures and surfaces, despite it lacking the information to do so. This can’t even be explained away by VP9, HEVC or H264 compression artifacts, as those are vastly different from what we end up seeing here. -
- -- My conclusion is that AMDs marketing team made an honest mistake here. They seem to have forgotten to show the layers or even add them after testing the overlay. It is still impressive in the other demos for a Spatial upscaler. If AMD wishes to clarify this, please contact me at info(at)xaymar(dot)com. -
- -- Update: Other sources in contact with AMD have confirmed that this is a Spatial upscaler, therefore the second demo should be physically impossible. -
- -- It depends on which version of DLSS. If you compare FidelityFX Super Resolution to DLSS 1.0 and 1.1, I’d take FidelityFX Ultra Quality over DLSS 1.0 and 1.1 any day. The temporal issues in DLSS 1.0 and 1.1 are horrible to look at, and make games unplayable because of heavy ghosting issues and similar. But if you compare it to DLSS 2.0 and 2.1, FidelityFX Super Resolution doesn’t hold up anymore. DLSS 2.0 and 2.1 look almost identical to the native resolution, while running up to 400% faster. -
- -- AMD definitely has a strong contender, and if they can figure out how to add a Temporal compontent to the upscaler, they will be competing with DLSS 2.0 instead of DLSS 1.0. As an example of a great upscaler, Unreal Engine 5 recently unveiled Temporal Super Resolution which gives a slight improvement in performance, while losing nearly no quality. -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -- -
- -