From ed9b4cfb76c5d9113488d26cb61ddd676e4265ba Mon Sep 17 00:00:00 2001 From: Joshua Goins Date: Mon, 1 Apr 2024 14:56:45 -0400 Subject: [PATCH] Don't try to update Wine/DXVK if we're using a custom version In the event that GitHub is down, the game is actually unplayable as the launcher doesn't allow you to skip updating these components (for now.) To prevent this, you can use a custom wine you have installed but the launcher was still erroneously updating it. Now it won't try to update DXVK/Wine if you don't request it to, although I'm not sure about tying DXVK to the wine option right now. --- launcher/src/assetupdater.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/launcher/src/assetupdater.cpp b/launcher/src/assetupdater.cpp index b2d8dfd..bb63d2b 100644 --- a/launcher/src/assetupdater.cpp +++ b/launcher/src/assetupdater.cpp @@ -38,11 +38,12 @@ QCoro::Task AssetUpdater::update() Utility::createPathIfNeeded(m_wineDir); Utility::createPathIfNeeded(m_dxvkDir); - if (!co_await checkRemoteCompatibilityToolVersion()) { + if (m_profile.wineType() == Profile::WineType::BuiltIn && !co_await checkRemoteCompatibilityToolVersion()) { co_return false; } - if (!co_await checkRemoteDxvkVersion()) { + // TODO: should DXVK be tied to this setting...? + if (m_profile.wineType() == Profile::WineType::BuiltIn && !co_await checkRemoteDxvkVersion()) { co_return false; }