-
-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GTA5: "You need a new application to open this com.epicgames.launcher link." message pops up. (Windows 10) #3643
Comments
I also have this error though rdr2 works fine from steam |
I too was facing this error when i downloaded gta5. Any reasons? |
for rockstar games to work, use the workaround explained in discord https://discord.com/channels/812703221789097985/1210747284086849578 (I should actually move it to a wiki page at some point) |
The link is not working well (Sorry if I am wrong but i am new to discord) |
I guess you first need to join the discord server before opening that link, check https://discord.gg/rHJ2uqdquK |
I added a wiki page to make it easier https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/wiki/Rockstar-Games:-Code-134-Error-(workaround) |
THANK YOU IT WORKED!! |
Rockstar changed something on their side and this is not showing up anymore and the workaround mentioned in the wiki (for the error 134) is also not needed anymore. |
It seems to be more of a Legendary issue than a Heroic issue. Using Legendary through Playnite (or through command line, I also tried) spits out the same error until you install EGL. There's this issue on the Legendary repo but it's a bit old and not well described. When you do install EGL, for me it's like the game is trying to launch twice, with the R* launcher asking for permission both when launching and when the Epic launcher opens. To add something to the OP's description, I'm pretty sure there's nothing about the official Epic launcher messing with the launch process, I never had EGL installed on my current Windows 10 Home installation and still ran into the problem when downloading GTAV on Epic. |
Yeah I did a fresh installation of Win11 about a month ago and ran into this problem yesterday. I don't play GTA V very often, I've never installed Epic on my computer and never will because I prefer this launcher. Let's hope for a fix I guess. |
I wrote a stopgap way to fix this. The problem is when legendary (or EGL) launch the game, that calls Rockstar's Only follow these instructions if you never intend to install EGL or are on linux, which means prefixes are disposable and you probably never used EGL anyway. This change will fix GTA if EGL is not present, but will also break parts of EGL if it is present. I will not help you troubleshoot this if you disregard this warning and run the file anyway Download the attached .reg file Windows: Run the reg file, confirm yes until changes are merged. That's it, you're done. Linux:
Heroic & Legendary devs had the foresight to do this automatically in Heroic on Linux, you don't need to do anything 🙂 (out of curiosity, can someone more knowledgeable than me can tell me why this results in the entire process failing instead of just moving on regardless of whether or not the URI succeeded?) |
Yes, this also seems to be a somewhat recent change on R*'s end, I was able to launch GTAV just fine some time ago (and probably any other game that uses their launcher). Bold move to hardcode a call to EGL after it worked fine for everyone for this long. So until Legendary updates to handle this on its own (or R* reverts the change) there's no official fix in sight, sadly. Thanks for the temporary fix though! |
Thank you both so much! Now GTA launches perfectly fine! But I've just noticed that outside of the game my keyboard is super slow and unresponsive, it takes like 10 seconds to register a key press. My PC isn't slow either, just that my keyboard is ridiculously slow. I don't think I had this issue before, not sure if it's correlated. |
All the registry edit does is define the URI protocol (as nothing 😆) for EGL. Most likely not related, but I'll admit I did not actually go far into game after testing that it worked and launched. I'll test it. Edit: Oh, outside the game? Yeah, definitely unrelated. |
Hello all. I've done some more digging, it seems that all you need is the actual As to why this works like this (just "breaking" the protocol): No idea. We've actually tested implementing this protocol correctly (following Epic Games' docs), and that didn't work. Really no idea on that one Note that this workaround is not necessary on non-Windows OSs, as we already set this registry key on prefix creation: HeroicGamesLauncher/src/backend/storeManagers/legendary/setup.ts Lines 27 to 38 in a579cb4
|
I can't say I know enough to pinpoint exactly why doing this works, but it seems to satisfy whatever criteria the original process is looking for in seeing whether or not the call succeeded or failed. I wrote a similar set of scripts or reg entries to do the same thing for modified EA single player games on Steam (& on Linux) since every last one of them manually invokes the link2ea URI, and I got tired of dealing with their garbage launcher. Same behavior there, so long as an entry for the URI is present, it works. That's why I'm curious about why. If I were a better reverse engineer I'd probably try to debug and trace the behavior. Or maybe URI standards on Windows are documented somewhere? |
That's the weird part actually, the launcher is not looking for anything. I've logged its registry access using ProcMon, it is not looking at that key at all What I assume is happening is that:
That would explain both why it is now working, as well as why Heroic implementing that protocol might've not worked |
While that is definitely possible, I'm more inclined to believe that this is the default behavior in Windows when a URI is called, the same way the default behavior for when it's called but isn't defined is for the entire thing to fail and Windows to complain that there's no program available for it. Why would Rockstar go through the effort to make it so that their launcher aborts the game launch down the line if some specific part fails, but not also abort it at this much easier to reach branch? Software equivalent of an iron door next to a paper window. Granted, you probably have more context to draw from than I, and I may overestimate their sensibility. |
I manually tested Doc-4's fix and it seems to skip EGL entirely. Same effect if you change the registry entry to wherever Legendary is installed (and probably if you set it to anything else, if CommandMC's guess is correct, I haven't checked). You only need to empty out |
@CommandMC I read your reply, asked a question in my head about why you didn't use procmon to trace the query and promptly forgot about it when responding even though you even kind of asked 🤦 |
Thank you. I did try to trace the query, but was unable to find anything yesterday. Alas, I did have my filters set wrong (I filtered the Process Name to contain "GTAV", "Rockstar", or "Epic", the process making the request is "Launcher.exe") |
Ah, the generic thing you didn't filter for, I know the feeling |
Describe the bug
After uninstalling the official Epic Games launcher and installing Heroic on my PC running Windows 10, when I open Grand Theft Auto 5, the launcher with the Rockstar DRM opens without problems, but when it tries to start the game, nothing happens and this message appears.
I have tested the Heroic launcher on a different device that never had an installation of the official Epic Games launcher using Windows 11 and this problem has not occurred. Some trace of the Epic Games launcher installation must be preventing the Heroic/Legendary protocol from being associated correctly.
I have tried changing the com.epicgames.launcher protocool on the registry myself using this .reg file I manually modified, but nothing seems to happen.
Add logs
Steps to reproduce
Expected behavior
I expected a full re-installation of Heroic to fix the broken link association in the registry, but no.
Screenshots
No response
Heroic Version
Latest Stable
System Information
OS: Microsoft Windows 10 Pro 10.0.19045
Additional information
No response
The text was updated successfully, but these errors were encountered: