Playtest 20201213 hangs on launch

[hannesoid]

Issue Summary

The latest Playtest hangs on launch.

Reproduction

Launch the OpenRA-playtest-20201213

Expected behavior

It should launch

Actual behaviour

It stays on the launch screen indefinitely

System

macOS Big Sur 11.1
iMac Pro 10core 32GB, Vega 64 16GB

…any logs you need?

[anvilvapre]

Could you try collecting a mono stack dump.

# Start ITerm
# Start bash shell
bash
# Start game by entering full path to install location
/fullpathto/appimage &
# Echo process id of last started application. Not sure this will be the mono process.
echo $!
# Or
ps -auxw | grep mono # On Linux, on Mac the options are a bit different. 
# Or look it up in the process manager.

# After send a QUIT signal to the process. The process will be interrupted but will keep running.
kill -QUIT <processidnumberofmono>
# It should cause mono to display a stack trace, showing what the OpenRA main game thread is currently doing.
# Repeat kill command a few times to see if the (top) output changes. 
# Share the output. 

And please share the exception and graphics log if they are present.

[hannesoid]

I just figured out it may be using dotnet rather than mono. I cloned the repo and ran it with dotnet 5, then killed the stuck dotnet process. The crash report looks a bit like there may be a recursion, but not sure how to interpret it:

dotnet_2021-01-18-103316_Hanness-iMac-Pro.log

In the logs folder, the only updated log files after running are these:

perf.log
nat.log

[pchote]

Playtest 20201213 requires mono, the switch to .NET 5 happened after it was branched. Was your opening report also built from source, or running the download from the website?

[hannesoid]

ah, thanks for the info. I originally downloaded it from the website though.

Now I just cloned the repo (bleed branch) and ran it from Visual Studio for Mac (with dotnet I guess).
Fyi, this is where it seems to be hanging in Game.cs

[hannesoid]

Is Visual Studio for Mac the recommended way of developing/debugging it? (I just installed this for the first time)

[pchote]

Ok, thats really helpful: that shows that the game is waiting for the UPnP discovery to return, which apparently is never happening. UPnP is disabled by default because it is unstable, and is known to cause problems exacty like this. I guess that you were able to run previous versions of OpenRA, and at some point turned it on in the Advanced settings?

If you open ~/Library/Application Support/OpenRA/settings.yaml with a text editor and change the DiscoverNatDevices: True line to DiscoverNatDevices: False (or just delete the line, or the entire file) it should solve the problem.

[hannesoid]

Ha, perfect, that worked! Thanks so much @anvilvapre and @pchote for helping!
I removed the DiscoverNatDevices: True line from ~/Library/Application Support/OpenRA/settings.yaml.

For the record for non-techy people,

1. open TextEdit app
2. Hit CMD+SHIFT+G to open the folder ~/Library/Application Support/OpenRA
3. open settings.yaml
4. remove the line DiscoverNatDevices: True
5. save the file

[FikriRNurhidayat]

I have the same issue, but I ran the game on Arch Linux btw.
Changing the DiscoverNatDevices: False doesn't work for me, since by default it is not there, and the default value is False.

Version: 20210321-1

[taoeffect]

Hi guys, I'm running into a similar issue trying to run the RA2 mod: OpenRA/ra2#804

I want to try this solution, however, settings.yaml doesn't exist, so I don't know how to modify it... what should it look like, or how do I generate it?

FYI, bleed does run, but I get a hang (with a completely black screen) running release-20210321 (needed by ra2)

EDIT: I opened issue #20639 for this