WTRTI needs to be closed using task manager and relaunched when restarting the game

[someonemax]

Hi,
When closing and relaunching the game, WTRTI will stop working and even right clicking on the tray icon doesn't open the context menu, so you have to close it using task manager, and relaunch it.

[MeSoftHorny]

Hi.
Does this happen every time? Can you please provide the WTRTI.cfg file? I'll check it.

[someonemax]

Yes
The WTRTI is still responsive (context menu opens) when I close the game. But if I relaunch the game, WTRTI freezes and has to be closed using task manager.
BTW Won't you make a new topic on the new forums?

myWTRTI_2023-06-10-00.zip

[MeSoftHorny]

Did a quick check... seems to work fine.
When you open Task Manager, how much CPU/Mem is the WTRTI using?

[MeSoftHorny]

BTW Won't you make a new topic on the new forums?

I don't know... I hate the "game activity" rules on the forums, and a new forum looks awful.
I will probably make a discord channel, for communication purposes.

[someonemax]

Did a quick check... seems to work fine. When you open Task Manager, how much CPU/Mem is the WTRTI using?

[MeSoftHorny]

Is it when it freezes?
Have you tried a fresh install? I mean, start the app in a different folder.

[someonemax]

Yes
Is there a debug feature that I can enable to generate logs for you?

[MeSoftHorny]

Unfortunately no (at least in the release build).
In this case, having a log may not really help.
It looks like there's a deadlock(multi-thread issue), and it's hard to detect without a proper debugging tool.

How long have you been experiencing this issue? Have you tried different versions?

[someonemax]

I will need to test the previous versions to tell you at which version this has started.

But as a potential solution, isn't it possible to check if the program is responsive or not, when a new instance of the program opens, and if it's not, for it to kill it and start the new instance?
i.e. Instead of having to manually close it using task manager, whenever you launch WTRTI, it will check if a previous instance is running, and if it is responsive, and if it's not responsive it will kill it and launch a new instance

[someonemax]

Or just always kill the running instance and run a new instance whenever the user (re)launches WTRTI

[MeSoftHorny]

But as a potential solution, isn't it possible to check if the program is responsive or not, when a new instance of the program opens, and if it's not, for it to kill it and start the new instance?
i.e. Instead of having to manually close it using task manager, whenever you launch WTRTI, it will check if a previous instance is running, and if it is responsive, and if it's not responsive it will kill it and launch a new instance

I'll see what can be done.
Right now I'm curious why this is happening. Because I can't reproduce it on my system.

[someonemax]

I did some more testing to intentionally reproduce it and initially couldn't ... and in hindsight I probably should've mentioned this:

I use a TV for the game and when I lock the PC and leave the system AFK, the TV turns off automatically after some time and Windows will set the monitor as primary display and if I unlock the PC before I manually turn the TV back on, it will move all the windows (game and presumably WTRTI) to the monitor (though it is possible to move the game back to the TV by setting it to full screen then full windowed again).

If I manually turn on the TV before I unlock the PC, this will not happen (and the game will still be on the TV after unlocking the PC). But for some reason game's performance will take a hit so I have to relaunch it and upon relaunch WTRTI is not working.
I just tested it by manually turning off the TV after locking the PC and WTRTI seems to go unresponsive (even the tray icon's context menu doesn't open) even before relaunching the game.

[MeSoftHorny]

I still can't reproduce it.
Please try this version: WTRTI_v2.1.2_x1_windows.zip

[someonemax]

I tested it several times with each version and it seems to be fixed in the new one. Can reproduce it reliably with old version but can't reproduce it with the new version.
Thanks

[MeSoftHorny]

Good. Thanks.

[someonemax]

While WTRTI now works after the whole "Display turning off and on again" thing, the GPU usages will go way up and causes stutters.

Closing WTRTI and relaunching it fixes it.

[MeSoftHorny]

Does this happen when you go into battle/test flight or immediately after turning off the display?
Is the overlay displayed correctly?
Can you please try to open the settings window(WTRTI) and press OK button, does that fix the high GPU usage?

[someonemax]

It happens after I go into test flight or battle.

Before going into battle:

In the battle:

After restarting WTRTI:

As for whether overlay is displayed correctly, if I turn off the display when the system is still unlocked, and turn it back on, the game will be moved to secondary display, but can be moved back to main display by switching display mode to windowed then back to full window, and then WTRTI will be displayed but will be off center (seems like to stay centered around the display that the game was automatically moved to, after turning off the main display)

But if I turn off the display and turn it back on, while the system is locked, then unlock the system, WTRTI overlay will be displayed correctly (As presumably Windows will not move the game to another display, if the main display turns off when the system is locked)

[MeSoftHorny]

Well... But what about the "Settings & OK button"? Have you tried that?

[someonemax]

Sorry, forgot about that one ...

1- Just going into settings and pressing OK doesn't fix it.
2- Going into settings and changing theme under General tab and pressing OK doesn't fix it.
3- Going into settings and into OSD tab, Disabling "Show OSD" then pressing OK doesn't fix it.
4- Going into settings and into OSD tab, Enabling "Hide unavailable indicators" then pressing OK doesn't fix it.
5- Going into settings and into OSD tab, enabling "Show units in OSD" then pressing OK fixes it.
6- Going into settings and into OSD tab, changing Window mode from Borderless to Windowed then pressing OK fixes it.

[MeSoftHorny]

Thanks.
Hmm, intertesing results... I'll take a look as soon as possible.

[MeSoftHorny]

Here, try this version: : WTRTI_v2.1.2_x2_windows.zip

[someonemax]

Yes this fixes it
Thanks

[MeSoftHorny]

The v2.2 is released.

[someonemax]

Seems like this bug is back with v2.2.1: