Dead Launch Exec

J

John R Denman

Registered
Launching rF2 from Steam or direct initiates the Steam on-line (Synchronizer) Background Message Box and changes Button Status from Play to Stop for just under 5 seconds, than returns to play.

After a few tries went into Steam Beta Select to step back to "stable" version. Ran the previous version for a session just fine. Returned to Steam Beta Select to step forward to V1128.

Ran the Integrity Check. No issues.
Back versioned, ran a session, than reverted to 1128. Still dead.
Not sure where to look for core dumps anymore, scanned through several folders, nothing revealing.
 
Repeated the step back step forward thing again. This time I get an rf2 System Error Message that VCRUNTIME140_1.dll was not found.
Can't find the file.
Where is this file supposed to be located and how can I get it?
 
John R Denman said:
Repeated the step back step forward thing again. This time I get an rf2 System Error Message that VCRUNTIME140_1.dll was not found.
Can't find the file.
Where is this file supposed to be located and how can I get it?
Click to expand...

Reinstalled (repaired) the 4 runtimes in the support/runtimes folder?
 
John R Denman said:
Can't say for sure, there are four files there.
VCREDIST : 64/86: 2012/2013 .exe's dated 2018. Nothing else.
Click to expand...

No, he means have you run each of those files and installed/repaired for each one. The existence of those files doesn't mean anything.

I suspect the runtime error isn't any of those 4, as it happens.
 
I had this exact problem with the release candidate and the advice from @ruffy_911 fixed it, albeit by installing the latest Visual Studio 2015, 2017, 2019, and 2022 which is what the Microsoft site currently provides. But why does this happen only with the release candidate? Why isn't this installed as part of the game?
 
Edvvc said:
I had this exact problem with the release candidate and the advice from @ruffy_911 fixed it, albeit by installing the latest Visual Studio 2015, 2017, 2019, and 2022 which is what the Microsoft site currently provides. But why does this happen only with the release candidate? Why isn't this installed as part of the game?
Click to expand...
Unsure, but since most users have not reported this issue, it is a problem localized to some users and thus more difficult to diagnose. I've switched this past week 3 times between the two options, (testing the new sound vs old & verifying the shifting issue was corrected) haven't had any similar issues.
 
You must log in or register to reply here.
Back
Top