Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
On my system, the redistributable updater ran when it was supposed to (at least, it logged as having run, although it did no work because, as a developer, i had already installed the update it before Steam had a chance to do so, but there's still a log in the system that Steam attempted to run the installer), so I'm starting to think it might be a problem with damaged Windows or damaged Steam client installs or something. This might also explain why most people aren't having a problem.
I cannot launch the game on 2 PC's. 2 people on my discord also cant launch the game.
Annoying, but what can you do.
Fundamentally I think this is a Microsoft problem. I've seen extensive discussions of this exact same problem for another app (not a game, but instead a line of business application) where the developer even provided an installer to install the redistributable and it still didn't work reliably. The reason why most apps aren't running into this problem is likely simply that relatively few developers are publishing apps built with MSVC 17.10 yet. We'll probably start to see more of this in January when the 17.6 LTSC channel hits end of support and everyone on that channel upgrades to 17.10. The 17.4 LTSC channel expired in July, but I bet a lot of people on 17.4 likely upgraded to 17.8 at that time instead of 17.10 because 17.10 was barely a month old at that time, and people using LTSC channels almost never move to the newest channel when the channel they're on hits end of support, instead going to the second newest because the developer will had have some time to evaluate the impact of the transition.
It was probably a mistake for Bay12 to have moved to 17.10 when they didn't need to, but Tarn isn't a software developer and doesn't have anyone on his team who understands Microsoft licensing or best practices for software development or publishing for the Microsoft ecosystem, so he has never gotten good advice on how to do this and thus made the unwise choice to upgrade his build system without properly evaluating what effect that would have on the resulting product. I advised him, some time ago, to switch to using LTSC 17.6 or LTSC 17.8 for release builds, but I suspect he either didn't receive that advice or hasn't had a chance to act on it.
Same issue. Resolved by installing the latest c++ redistributable. It is not pushed by steam, you need to do this yourself manually.