search

FarbstoffRSL / RSL-Helper

Der Farbstoff RSL-Helper
234 stars 180 forks source link

Improvement: RSL Helper freezes while waiting for Raid window #67

Closed rbeurskens closed 3 years ago

rbeurskens commented 3 years ago

When the helper start when Raid is not running but Plarium play is, it will wait for the game to launch. However, it does so in a matter it is blocking the UI thread, so it can't be interacted with/moved (aka. freezes) and only shows a mouse wait cursor when hovering over it. When clicking on the window, Windows detects this and prompts to wait or kill the process. (I think this is caused by an active wait construction or lock on the UI thread. Maybe a spin/sleep would work better) image image

rbeurskens commented 3 years ago

This also happens when Plarium Play is not running: image If I choose "wait to respond" and I launch Raid, it unfreezes, however, the following message shows up. blocking startup until I click it away: image

BlackHawk3000 commented 3 years ago

Possibly due to a Plarium update

Dwza commented 3 years ago

Did you set the path to your plarium client?

rbeurskens commented 3 years ago

First time I didn't set the path and it found Raid by itself (it said on startup it was found on default path). later I set the path. It didn't seem to make difference. I had to terminate Raid a few times as it froze while downloading additional resources during the load screen for starting a battle. For some reason the helper launcher kept detecting a 'Raid.exe' process even though it was not running (also Plarium play - I didn't see any sign of either in the task manager) I guess it indeed could have influence that I did not play Raid on that machine for a while and it just had a large update.

Dwza commented 3 years ago

detecting the raid exe probably just checking the location, not to run state. just a guess, im not sure :) have to ask this. so is it working now?

rbeurskens commented 3 years ago

I haven't had any problems with the detection recently but not (yet) tested it explicitly. Apart from that, the loader window can't be interacted with in any form and is covering all other windows as long as it is open. (Which means you can't move/minimize/resize it, see/click on any content in the screen area it covers, even blocking the active window showing its content etc.)

Dwza commented 3 years ago

I haven't had any problems with the detection recently but not (yet) tested it explicitly. Apart from that, the loader window can't be interacted with in any form and is covering all other windows as long as it is open. (Which means you can't move/minimize/resize it, see/click on any content in the screen area it covers, even blocking the active window showing its content etc.)

@rbeurskens is this a new issue?

rbeurskens commented 3 years ago

Well, It was implicitly included in this original description. But indeed detecting/locating the Raid process/executable is only one of the things the launcher is doing, so it would be a separate issue. So yes, it would be a separate issue describing just this and nothing else. (it's not blocking, but just annoying) Originally I thought it was only blocking while waiting/searching for Raid, but it seems the launcher UI is irresponsive during the whole time its window is open.