Hi juj!
Sorry that’s what I was referring to by “debug output from the game”. I used the wrong term there, my mistake!
When using sg.AntiAliasingQuality = 2, the logwindow says
[2017.10.07-06.58.55:357][820]Warning: Processing the console input parameters the leading '=' is ignored (only needed for ini files).
[2017.10.07-06.58.55:357][820]sg.AntiAliasingQuality = "2"
When using sg.AntiAliasingQuality = 1, the logwindow says the same thing
[2017.10.07-06.59.29:740][883]Warning: Processing the console input parameters the leading '=' is ignored (only needed for ini files).
[2017.10.07-06.59.29:740][883]sg.AntiAliasingQuality = "1"
While in the hung/frozen state, the game uses the same amount of CPU as before (Firefox is reporting 4-5%) and same amount of RAM.
Following your suggestion of just trying to blindly open the console and set the AntiAliasingQuality back to 2 or 3 actually does fix the game. It works again. However setting it back to 1 or 0 freezes it again.
[2017.10.07-07.00.54:104][945]Warning: Processing the console input parameters the leading '=' is ignored (only needed for ini files).
[2017.10.07-07.00.54:104][945]sg.AntiAliasingQuality = "3"
So the game itself is still running, the screen just stops updating but it can still accept and process input.