From 9344a29f0e937809fabccb341a9e24b3c5f8d2f0 Mon Sep 17 00:00:00 2001 From: Stuart Carnie Date: Fri, 20 Dec 2024 06:38:42 -0700 Subject: [PATCH] Rendering: MoltenVK hack is no longer required, as bug was fixed. Original issue: https://github.com/godotengine/godot/pull/51679#issuecomment-976900929 And related fix in SPIRV-Cross: https://github.com/KhronosGroup/SPIRV-Cross/issues/2046 --- servers/rendering/renderer_rd/effects/fsr.cpp | 7 ------- 1 file changed, 7 deletions(-) diff --git a/servers/rendering/renderer_rd/effects/fsr.cpp b/servers/rendering/renderer_rd/effects/fsr.cpp index 5599a5a162d..d8ceb64c3f8 100644 --- a/servers/rendering/renderer_rd/effects/fsr.cpp +++ b/servers/rendering/renderer_rd/effects/fsr.cpp @@ -36,18 +36,11 @@ using namespace RendererRD; FSR::FSR() { Vector FSR_upscale_modes; - -#if defined(MACOS_ENABLED) || defined(IOS_ENABLED) - // MoltenVK does not support some of the operations used by the normal mode of FSR. Fallback works just fine though. - FSR_upscale_modes.push_back("\n#define MODE_FSR_UPSCALE_FALLBACK\n"); -#else - // Everyone else can use normal mode when available. if (RD::get_singleton()->has_feature(RD::SUPPORTS_FSR_HALF_FLOAT)) { FSR_upscale_modes.push_back("\n#define MODE_FSR_UPSCALE_NORMAL\n"); } else { FSR_upscale_modes.push_back("\n#define MODE_FSR_UPSCALE_FALLBACK\n"); } -#endif fsr_shader.initialize(FSR_upscale_modes);