Did you update your MSFT C++ redistributables?

i had that same problem and also had to change versions

Originally posted by AlP:

Did you update your MSFT C++ redistributables?

No. If they're redistributables, they should be installed for me with the game, I shouldn't have to just google stuff and install random things to get the game to play. I don't want to have to do work to get my game to launch.

Originally posted by NeuralSimulation:

No. If they're redistributables, they should be installed for me with the game

Well, they are not. At least when you update the game through Steam.

Originally posted by NeuralSimulation:

Originally posted by AlP:

Did you update your MSFT C++ redistributables?

No. If they're redistributables, they should be installed for me with the game, I shouldn't have to just google stuff and install random things to get the game to play. I don't want to have to do work to get my game to launch.

The game is (as far as we can tell) properly marked to install them, but the Steam client doesn't do it correctly, on at least some systems. Blame appears to be on Steam here, or perhaps on Microsoft or maybe even some antivirus.

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.

The playerbase is so low that I dont think you can say most players arent.
I cannot launch the game on 2 PC's. 2 people on my discord also cant launch the game.

also having this issue

Originally posted by roomy rooms:

also having this issue

If you select a previous version, it should work.
Annoying, but what can you do.

Originally posted by ProbablyFishing:

Annoying, but what can you do.

You can update your C++ redistributables like you've already been advised to do. This isn't hard.

Originally posted by rome of oxtrot:

Originally posted by ProbablyFishing:

Annoying, but what can you do.

You can update your C++ redistributables like you've already been advised to do. This isn't hard.

I did. Everyone on my discord did. It did not work.

Did you do a repair install of the 2022 redistributables from add/remove programs? I've seen a few people who need to repair their installation. You may also need to repair Windows (run "sfc /scannow" from an elevated shell). I've definitely seen people who have broken redist installs, either because they got a bad version of the installer at some point or because their Windows installations are unhealthy.

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.

downloading the 2022 redistributable fixed it for me, I realize this is a microsoft thing but I was able to launch & play DF a few months ago so it'd be cool to get some kind of hotfix or downgrade for that

I posted in a different thread a few weeks ago that I did get it to work by running a repair on the MSVC redist through add/remove programs. I was unable to install the latest installer, it claims that it can't run on my machine.

Originally posted by NeuralSimulation:

The latest version of the game won't launch for me. I went to the betas tab in settings, and my selection was "none." I would expect this to mean I'm not testing a beta, but it seems like I was given 50.14test branch anyway, which just immediately closes when I try to open it. (press play.... tries for 2 seconds then fails)

I tried deleting the game and reinstalling, and also disabling all the workshop mods, but neither one did the trick.

Manually selected 50.13 and it loaded fine, but man.... this is bad. If I had just bought the game, or didn't know that I could select a branch to run (as I suspect most users don't), I'd be very angry.

Same issue. Resolved by installing the latest c++ redistributable. It is not pushed by steam, you need to do this yourself manually.