Hm, that’s really strange - also that NVIDIA would say unsupported as well
Please could you provide your launcher log and most recent console log so we can take a look under the hood? Hoping we may be able to gather further clues.
It is now working again but only on official realm. I could have sworn when I launched it the first time on official after the skull event update that it was not working.
Maybe it turns out to be only a modded realm issue then after all. Sorry for wasting your time if it turns out to be the case.
Although when launching the modded realm the button is still greyed out.
(Even with 0 mods loaded)
Should not the graphic settings be the same across both realms? I am pretty sure when I change a setting in either it carries over to the other.
Not sure if they are still of use but just in case here are the logs when launching official realm:
I’m glad to hear it’s working again in Official realm, though it’s unusual that Modded realm is not, and that no mods are active, hmm.
I’ve pinged your logs to the development team, thanks! Due to the time of day now, and the weekend, this likely won’t be picked up until early next week. I’ll let you know as soon as I hear back, if we’re able to find anything.
In the meantime, if anything else changes on your end, please let me know
I tried disabling anything that could give an overlay on the game, disabling the Steam in game overlay, the Nvidia overlay and Rivatuner / Afterburner.
That does not seem to be the culprit either unfortunately, still not working.
Also on a side note, the frame generation is working as normal in other games (for example in Darktide it works fine). Seems to be only Vermintide 2 and only modded realm where it is not working.
Question about your latest link. I would like to try whatever it is, I just want to make sure I am understanding it correctly.
Is the first step to download the streamline-sdk-v2.11.1 and then run the setup?
@Koffe ah, no - you should just need to enable logging as SL (Streamline) is distributed with the game. However, we did try to enable logging internally - and were unable to get it to log, so this may not be possible.
Unfortunately, we may have hit a bit of a dead-end. If you do manage to get it to log though then please let me know.