{"id":15014,"date":"2025-08-22T16:36:27","date_gmt":"2025-08-22T23:36:27","guid":{"rendered":"https:\/\/mattfife.com\/?p=15014"},"modified":"2025-09-15T10:47:36","modified_gmt":"2025-09-15T17:47:36","slug":"whoops","status":"publish","type":"post","link":"https:\/\/mattfife.com\/?p=15014","title":{"rendered":"AMD accidently releases FSR"},"content":{"rendered":"\n<p>AMD recently published a\u00a0<a href=\"https:\/\/gpuopen.com\/learn\/amd-fsr4-gpuopen-release\/\" target=\"_blank\" rel=\"noreferrer noopener\">new version<\/a>\u00a0of its FidelitySDK with FSR 4 upscaling and FSR 3.1.5 frame generation support. Unfortunately, they accidentally published the full FSR 4 source code on GitHub. Before AMD took it down, some <a href=\"https:\/\/www.tomshardware.com\/pc-components\/gpus\/amd-accidentally-marks-fsr-4-open-source-source-code-reveals-potential-support-for-older-radeon-gpus#xenforo-comments-3885121\" data-type=\"link\" data-id=\"https:\/\/www.tomshardware.com\/pc-components\/gpus\/amd-accidentally-marks-fsr-4-open-source-source-code-reveals-potential-support-for-older-radeon-gpus#xenforo-comments-3885121\">media outlets<\/a> and X users managed to record screenshots of the files, including\u00a0<a href=\"https:\/\/videocardz.com\/newz\/amd-releases-fidelityfx-sdk-2-0\" target=\"_blank\" rel=\"noreferrer noopener\">Videocardz<\/a>. <\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-twitter\"><blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\"><p lang=\"en\" dir=\"ltr\">AMD accidentally posted FSR4&#39;s Source Code and then tried to delete it all LOL<br><br>The repo<a href=\"https:\/\/t.co\/FOpsWIn5sf\">https:\/\/t.co\/FOpsWIn5sf<\/a><br><br>Commit history<a href=\"https:\/\/t.co\/nIMoDMt0LF\">https:\/\/t.co\/nIMoDMt0LF<\/a><\/p>&mdash; CaptainMcShotgun (@CaptMcShotty) <a href=\"https:\/\/twitter.com\/CaptMcShotty\/status\/1958209363652321604?ref_src=twsrc%5Etfw\">August 20, 2025<\/a><\/blockquote><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/div>\n<\/div><\/figure>\n\n\n\n<p>Update: PCGamer is reporting that AMD is <a href=\"https:\/\/www.pcgamer.com\/hardware\/graphics-cards\/amds-fsr-4-open-source-whoopsie-daisy-may-be-harder-to-take-back-than-initially-thought-thanks-to-the-inclusion-of-a-difficult-to-revoke-mit-license\/\" data-type=\"link\" data-id=\"https:\/\/www.pcgamer.com\/hardware\/graphics-cards\/amds-fsr-4-open-source-whoopsie-daisy-may-be-harder-to-take-back-than-initially-thought-thanks-to-the-inclusion-of-a-difficult-to-revoke-mit-license\/\">having more trouble putting the genie back in the bottle<\/a> than first thought because they accidently included the MIT license.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AMD recently published a\u00a0new version\u00a0of its FidelitySDK with FSR 4 upscaling and FSR 3.1.5 frame generation support. Unfortunately, they accidentally published the full FSR 4 source code on GitHub. Before AMD took it down, some media outlets and X users managed to record screenshots of the files, including\u00a0Videocardz. Update: PCGamer is reporting that AMD is having more trouble putting the genie back in the bottle than first thought because they accidently included the MIT license.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[28,9],"tags":[],"class_list":["post-15014","post","type-post","status-publish","format-standard","hentry","category-ai","category-cool"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/s4WECr-whoops","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/15014","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=15014"}],"version-history":[{"count":4,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/15014\/revisions"}],"predecessor-version":[{"id":15216,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/15014\/revisions\/15216"}],"wp:attachment":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=15014"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=15014"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=15014"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}