https://bugs.winehq.org/show_bug.cgi?id=48373
Bug ID: 48373 Summary: WriteProcessMemory? - Project Reality fails linking Launcher and Game Executable Product: Wine Version: 5.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: consolelogger@rhyta.com Distribution: ---
When running Project Reality, past the game menu and the loading in, an error shows up where it says: "Failed linking to the Launcher"
https://old.reddit.com/r/ProjectReality/comments/eg3xfu/lets_try_to_get_pr_w...
We have the luxury of being able to ask the devs about what might be going on there:
"If he joined a server, the Launcher has succeeded in opening the process and writing to it. These sort of issues are usually an anti virus not liking this kind of cross-process communication. In your case wine is probably incapable of WriteProcessMemory [...] Wine has both ReadProcessMemory and WriteProcessMemory, not sure what exactly the issue is but it shouldn't be that unless an odd bug has been hit [...] I suspect that or PR is triggering an unandlhed edge case or the failure reason is actually another one."
I was hoping to post a report with logs here, but couldn't find out what arguments are needed on WINEDEBUG= to have instances of ReadProcessMemory and WriteProcessMemory and adjacant "stuff" show up in the logs. How would I go about optaining a log that contains info helpful for solving this? I will do so as soon as I can and am happy to do testing and further research. Cheers.