RSLHelper unable to find Raid.exe process

[Drauku]

Operating system

Windows 10

Systemlanguage

English (EN)

Current Game-Version

5.60.2

RSL Helper Version

v3.2 Release-4 Build-2

Bug description

I have been experiencing this bug for many months, and the only fix I have found so far is a system reboot.

Whenever I close the game, the Raid.exe process does not actually quit. I'm able to reload the game, but then there are multiple Raid.exe processes in task manager. It cannot be force closed, even via cmd line taskkill or using Process Hacker. The only fix is an OS reboot.

The issue this causes is RSLHelper apparently cannot differentiate between the old and new processes, and therefore can never attach to the new Raid process.

Note the two Raid.exe processes in the attached image, the current/new process 31728 is using RAM, the 27816 process is not, and is the dead/remnant old Raid.exe process: .

Steps to reproduce

• Start Raid using RSLHelper.
• Close Raid and RSLHelper.
• Start Raid again using the RSLHelper app. This does load a new Raid instance as expected, however, the RSLHelper client now is stuck on "Wait for a new Raid Window" despite having opened the new window itself.

Relevant log output

No response

[OpaWattebausch]

That is not an issue of the helper than. If you can not kill the raid.exe, it's a local problem on your pc.

[Drauku]

The issue I'm reporting is that RSLHelper cannot differentiate between the stale raid.exe process and the new raid.exe process that was started by the helper itself. I wouldn't know how to program for that, but I know it's possible since Plarium Play and the HH Gaming Artifact Extractor are both able to find the new process.

[Drauku]

Is this issue not something others have encountered? I've been seeing this behavior for many months, on three different Windows 10 desktops as well.

[OpaWattebausch]

No, you are the first and only one. Is your helper located in the standard path? If not: Did you set the path to plariumplay.exe in the settings?

[Drauku]

Standard path? Probably not, this is my installation path: C:\Games\RSL\RSLHelper

Yes, my PlariumPlay.exe location is properly configured in settings. RSL Helper successfully loads Raid when I open it.

Are errors like this image possibly related? Note the rather large number in the CalcTime: filed, bottom right. This happens fairly regularly as well, and I'm unable to close RSLHelper. I have to end the process in order to reload it.

[OpaWattebausch]

Reinstall the vc++ redist package and don't forget the restart of pc after that.

[Sanych]

Попробуйте заново прописать путь к ярлыку Raid.exe в настройках RSL и поставить галочку на разрешение автоматического запуска

[Drauku]

Ever since updating beyond v3.2 release 2 build 4, RSLHelper has not crashed with the "undefined operation" error as shown in my last post, just above.

I went ahead and reinstalled all vc++ redist packages from 2005-2019 just to make sure I did not leave one missing.

Per Sanych's suggestion, I went ahead and re-registered the PlariumPlay path, but loading Raid was never an issue.

I realize there is nothing that can be done about removing the remnant raid.exe process, that is a Plarium issue. I was just pointing out that other programs which also connect to raid processes do not run into this conflict with remnant processes. I do not know what they do differently, but it is possible for RSLHelper to continue working even without raid.exe exiting cleanly.

[github-actions[bot]]

This issue is stale because it has been open for 5 days with no activity. It will be closed in 2 days if there is no further response.

[github-actions[bot]]

This staled issue was closed because it has been inactive for a total of 7 days.