Yes, at least if you mean this thread: https://forums.ashesofthesingularity.com/486449/ashes-support-faq#videoissues
I did not see anything about re-installing video drivers there, though. Anyway, I have tested a slew of different configurations now, Ashes: Escalation v2.9 (via the Steam Beta option) and v3.0, combined with older Nvidia driver from 2019 and newest Nvidia driver, combined with different graphics presets and graphics interfaces (DX11, DX12, Vulkan), fullscreen or windowed, with or without VSync ... you name it.
Apart from benchmark results in the 1-2 FPS range the only other consistent observation I made is that neither graphics card nor CPU showed any kind of load during the benchmarks. What I expected to happen is that the fans would engage and the notebook would get warm during the benchmark -- not the case. I did the last benchmark runs having the task manager open in the background for confirmation and as I suspected, there was only a light CPU load (~30%) and no visible load whatsoever on either of the two GPUs (dedicated or embedded, the latter should not have been used anyway, of course).
Since I could find some rather recent benchmark results of the 2070 Max-Q (2019 or so) on the internet for Ashes: Classic I then decided to download that from Steam and give it a spin instead of Escalation. And, lo and behold, 70ish FPS on High presets with the current Nividia drivers and DX12 right off the bat. Did not even have to tell Windows explicitly to use the dedicated GPU. And also the fans decided to turn on in hoover mode.
==========================================================================
Oxide Games
Ashes Benchmark Test - ©2015
C:\Users\jensk\OneDrive\Dokumente\My Games\Ashes of the Singularity\Benchmarks\Output_21_04_12_2019.txt
Version 1.50.24210
04/12/2021 20:23
==========================================================================
== Hardware Configuration ================================================
GPU 0: NVIDIA GeForce RTX 2070 with Max-Q Design
CPU: GenuineIntel
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Physical Cores: 6
Logical Cores: 12
Physical Memory: 16263 MB
Allocatable Memory: 134217727 MB
==========================================================================
== Configuration =========================================================
API: DirectX 12
==========================================================================
Quality Preset: High
==========================================================================
Resolution: 1920x1080
Fullscreen: True
Bloom Quality: High
PointLight Quality: High
Glare Quality: Low
Shading Samples: 8 million
Terrain Shading Samples: 8 million
Shadow Quality: Mid
Temporal AA Duration: 0
Temporal AA Time Slice: 0
Multisample Anti-Aliasing: 1x
Texture Rank : 1
== Total Avg Results =================================================
Total Time: 60.000774 ms per frame
Avg Framerate: 72.069893 FPS (13.875421 ms)
Weighted Framerate: 71.762962 FPS (13.934764 ms)
CPU frame rate (estimated if not GPU bound): 72.182152 FPS (13.853840 ms)
Percent GPU Bound: 99.871529 %
Driver throughput (Batches per ms): 5390.119141 Batches
Average Batches per frame: 13214.808594 Batches
Average Particles simulated per frame 397965
==========================================================================
So, I do not really know what to take away from this. Seems like this is not something that cropped up with the 3.0 version, nor does it seem directly driver or configuration related. More like some change that happened sometime in Escalation as opposed to Classic?
I can provide a ton of benchmark results now, if that helps pinning it down. Also happy to do further tests. Would really like to be able to play Ashes: Escalation 
Thanks!
