Forum Discussion
Sorry, should have clarified, I have 2005, 2008, 2010, 2012, 2013, 2017 installed, and in the cases you highlighted, I have x86 and x64 with the same versions, just not the exact same that you have.
For a given C++ release, is it best practice to install the latest from that particular year? E.g., if some other game installs a version of 2013, is it safe to install the latest of 2013 and assume that game will work with it? Or does the particular version matter? I have no idea how VC++ guarantees their APIs match from year-to-year and version-to-version.
- 7 years ago
Yea, still not working for me. I've had random failure in a variety of games that are unexplainable. Just Cause 3, Dark Souls III, both are unplayable on my rig and installing them actually screws up other games. I've long suspected VC++ issues, but have no idea which versions to keep, which to update, and which to remove.
- 7 years agoWell i learned about it cause of the trouble installing apex legends.. Before i couldnt get Warface to run fullscreen (played window for over a year), fortnite would crash to desktop without error, ring of elysium would crash anytime.. Now i can run just about any game without crash
- 7 years ago
Just wanted to let you know that I did try your recommendation, it unfortunately doesn't seem to have fixed anything in regards to Apex, but maybe other things will run more smoothly for me.
Here's what my C++ packages looked like before I started:
Notice there are several copies of 2013 (one of the duplicate x64's was japanese...?)
I tried to emulate your setup for what Apex cared about, and disregarding the 2008 stuff, I copied yours exactly, and this is what it looks like now:
Still a no-go, but at least it's cleaned up a little!