Issue with FNA (not XNA) on "older" NVIDIA GPU?

[OneOfMany07]

I tried to play Hacknet which apparently uses FNA by default. I kept getting a blank, no sync screen (amber monitor light, instead of blue for normal use). I could alt-tab away fine, but couldn't find any obvious errors.

Then I found a post about using XNA mode for "older" NVIDIA GPU's and I've got a 1080 ti from around 2017. That XNA is the original, likely now worse, way the game talked to the GPU. I tried to find a list of known working or broken devices for FNA, but couldn't. Switching did let me load the game.

Is my failure something that you'd like to debug or fix? I'm not the game developer, but know a good amount about computers and programming (very basic GPU stuff, and a range of languages). And figured you'd want your most recent framework to work everywhere if possible.

Windows 10 19045 build with latest drivers and updates that I can find. Intel i7-4790k CPU, 32GB RAM, NVIDIA FE GTX 1080 ti, plenty of storage. I'd had things overclocked a bit before, but now even my RAM is running below rated speeds (1066 not 1333).

After uninstalling the game there was only a "debug.log" that gets a line like these when I run it...

[0210/015528:ERROR:gpu_process_transport_factory.cc(642)] Lost UI shared context.
[0210/015826:ERROR:gpu_process_transport_factory.cc(642)] Lost UI shared context.
[0210/164243:ERROR:gpu_process_transport_factory.cc(642)] Lost UI shared context.

There is a text console that shows when I run the game, but the last lines didn't have anything catastrophic. And I saw something about NVIDIA near the top so it seemed to be detecting my hardware.

HyperV platform is turned on, so that enables an NVIDIA container service. It lets me run WSL2 (Windows Subsystem for Linux).

I know my monitor triggers a warning about duplicating it's signal on the HDCP page, but I haven't found content that won't play before. It lets you daisychain multiple monitors down a single computer connection for certain resolutions, and I can't turn that off in the screen. It also only supports the higher 75hz refresh on DisplayPort, so I can't just switch to HDMI (that wouldn't notice the daisychain issue).

[flibitijibibo]

I think the FNA version Hacknet uses is pretty old so we won't be much help here. I think it might be from 2016(!) so manually updating FNA and the fnalibs might not work if it depends on undefined behavior somewhere. If updating doesn't cause an immediate crash then you should be able to get good details in the console!