same here. a "true gamer" wouldnt call 20-30 fps as "fine fps" but considering I am boasting an intel Laptop GPU currently (havent found out how to actually switch to the AMD one in this Laptop), I would call it fair enough. I honestly havent tested a lot but no tweaks, and nothing needed. just flip the config as you like, dont forget steam controller config if you like using a controller, and then start the game.

same here. a "true gamer" wouldnt call 20-30 fps as "fine fps" but considering I am boasting an intel Laptop GPU currently (havent found out how to actually switch to the AMD one in this Laptop), I would call it fair enough. I honestly havent tested a lot but no tweaks, and nothing needed. just flip the config as you like, dont forget steam controller config if you like using a controller, and then start the game.

I use a 580 now its fps is stable on it. barely any fps drops if they were one synthesis it was 60 fps 45 to 50 fps on ubuntu in my system most likely.

System Information

• GPU: GTX 970
• Driver/LLVM version: Nvidia 440.26
• Kernel version: 5.3.2
• System Info
• Proton version: 4.11-7
• Proton log: steam-527270.zip

Assessment

Been playing this for about 26 hours now, there are several issues, though not game breaking ones.

The game requests more than one back buffer, there is no setting to change this behavior.

8628.884:0033:0035:fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.
Please configure the application to use double buffering (1 back buffer) if possible.

The game tries to use an unimplemented usage flag, it will spam the log with this.

8631.139:0033:003a:fixme:d3d:resource_check_usage Unhandled usage flags 0x40.

After a while, OpenGL will run out of memory and cause several shaders to fail, resulting in black textures several places.

8848.362:0033:0037:err:d3d:wined3d_debug_callback 0x1f1500: "GL_OUT_OF_MEMORY error generated. Failed to allocate CPU address space mapping for texture (consider building 64-bit app).".
8848.362:0033:0037:err:d3d:wined3d_debug_callback 0x1f1500: "GL_INVALID_OPERATION error generated. The source or destination texture is not complete.".
9120.507:0033:0037:err:d3d:wined3d_debug_callback 0x1f1500: "GL_INVALID_VALUE error generated. Size and/or offset out of range.".
9120.507:0033:0037:err:d3d:wined3d_debug_callback 0x1f1500: "GL_INVALID_OPERATION error generated.".

As the state gets worse, incomplete frame buffer attachments are spewed out in the log. The UI starts to degrade at this point.

9133.358:0033:0037:fixme:d3d:wined3d_context_gl_check_fbo_status FBO status GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT (0x8cd6).
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_DEPTH_ATTACHMENT: 2d texture 113, 0x0, 0 samples, format 0x88f0.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_STENCIL_ATTACHMENT: 2d texture 113, 0x0, 0 samples, format 0x88f0.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT0: 2d texture 112, 2560x1440, 0 samples, format 0x8c43.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT1: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT2: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT3: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT4: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT5: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT6: NONE.
9133.358:0033:0037:fixme:d3d:context_dump_fbo_attachment GL_COLOR_ATTACHMENT7: NONE.
9133.358:0033:0037:err:d3d:wined3d_debug_callback 0x1f1500: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.".

Despite all this, the game does its best to cope, though there are noticeable degradation over time. Overall there are definitely some issues that need to be fixed.

The integrated web browser in the Steam overlay causes the game to crash, it doesn't happen every time, but quite frequently.

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
11725.738:0033:0037:trace:seh:raise_exception code=80000101 flags=1 addr=0xf7f1b999 ip=f7f1b999 tid=0037
11725.738:0033:0037:trace:seh:raise_exception eax=00000000 ebx=00000002 ecx=0e17e9bc edx=00000000 esi=00000008 edi=00000000
11725.738:0033:0037:trace:seh:raise_exception ebp=0e17e9bc esp=0e17e990 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000246
11725.738:0033:0037:trace:seh:call_stack_handlers calling handler at 0x7bcd1e80 code=80000101 flags=1
wine: Assertion failed at address 0xf7f1b999 (thread 0037), starting debugger...

Log: steam-527270.log