Did a new install to join in for veterans week. Because it thinks I’m new it goes to demo before showing me a login, first giving me a control customization option for a console-style controller (there is not one connected, I use HOTAS). If I click “start demo” or hit esc, the screen goes black.

i9 3.6Ghz 8-core
32G, 1T SSD
RTX 2080
Win 10 Pro build 1809

BTW: I added these lines to the config file under [Vendetta]:

Username=my user name
firsttime=0

and thereby bypassed the demo, which fixed my issue, and unexpectedly, after I was satisfied with my fix, before logging off I chose "offline training simulator" expecting it to crash, it did not.

and just if anyone cares, this was the error log after recreating the fail:

Windows 6.02.9200 (platform 2)
Sat Dec 28 15:42:13 2019
archive returned 0
build date Oct 18 2019 19:00:54
ovr_Initialize: -3001
[12/28/19 15:42:13] Found driver: "Windows Sound (WAV) driver". Type 1, Version 10.1. Load @0x10000000
[12/28/19 15:42:13] Instantiate address: 10002540
[12/28/19 15:42:13] Found driver: "DirectX11 GKGL driver". Type 5, Version 146.0. Load @0x03420000
[12/28/19 15:42:13] Instantiate address: 034235A0
[12/28/19 15:42:13] Found driver: "DirectX8.1 GKGL driver". Type 5, Version 142.1. Load @0x03480000
[12/28/19 15:42:13] Instantiate address: 034A3890
[12/28/19 15:42:13] Found driver: "DirectX9 GKGL driver". Type 5, Version 146.0. Load @0x03480000
[12/28/19 15:42:13] Instantiate address: 034CA4B0
[12/28/19 15:42:13] Found driver: "Vulkan GKGL driver". Type 5, Version 146.0. Load @0x036a0000
[12/28/19 15:42:13] Instantiate address: 036A93B0
[12/28/19 15:42:13] Found driver: "OpenGL Reference GKGL driver". Type 5, Version 146.0. Load @0x03770000
[12/28/19 15:42:13] Instantiate address: 03783620
[12/28/19 15:42:13] Found driver: "Vista Sound driver". Type 1, Version 10.0. Load @0x037e0000
[12/28/19 15:42:13] Instantiate address: 037E22A6
[12/28/19 15:42:13] Found driver: "XAudio2 Sound driver". Type 1, Version 10.0. Load @0x03820000
[12/28/19 15:42:13] Instantiate address: 0382181B
Using multithreaded rendering.
Using 8 physics worker threads. and g_do_mp = 1
using other arch.
DoGameMPJobs.
Initializing job system with 8 threads and 32768 jobs per thread.
starting job system.
Starting game job.
[12/28/19 15:42:16] Creating 2048x2048 shadowmap.
Created 2 refraction targets
Loaded sensitivity envelope for touch regions.
Loaded sensitivity envelope for quest controllers.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for left stick.
Loaded 'envelope/joystick.mot' sensitivity envelope for right stick.
Input driver initialized.
HAS_LEAP - calling initLeapMouse
Unhandled objtable entry Fire Wasp kind livery
Unhandled objtable entry Hexology kind livery
VO_API_VERSION = 14
[12/28/19 15:42:29] Flight-Assist mode enabled.
trigger_fsm: trying to resume already running coroutine!
stack traceback:
lua/utils.lua:108: in function 'error'
lua/trigger.lua:44: in function 'SendMessage'
vo/if_demomanager.lua:2532: in function 'NextDemo'
vo/if_demomanager.lua:3287: in function 'Gamepadclosecb'
vo/if_help_gamepad_new.lua:11: in function <vo/if_help_gamepad_new.lua:8>
(tail call): ?
[C]: in function 'yield'
lua/trigger.lua:119: in function 'WaitForSingleMessage'
vo/if_demomanager.lua:3288: in function 'Tutorial01'
vo/if_demomanager.lua:4233: in function <vo/if_demomanager.lua:4196>

Thanks. That's worrisome.

I assume your game controller was plugged in when you ran the game initially? We may have some auto-detection stuff gone awry.

Thanks for the report, this is now fixed as of today's patch.

Sweet.

(P.S. I don't have a game controller.)

(P.S. I don't have a game controller.)

Hmm. You said "I use HOTAS" in your initial report?

If so, that is definitely a game controller. I didn't just mean gamepads.

Basically, the fix for this had to do with various problems relating to game controllers with more than X buttons.