Hi @sunhuge welcome to the Proton issue tracker on Github. And thanks for opening a issue for your game.

Could you say what game you're having issues with? Because right now, your issue is not very helpful.

Steps to make a better issue report:

1. Search the Proton issue tracker for your game.
2. See if there is already a issue open for your game, if so, add your findings to that issue, by commenting on that issue.
3. If there is no issue yet opened for your game, edit the title of your issue from "Bug with Proton" to "name of game (appid)"
4. The name of the game is the name you find on the Steam store for the game.
5. Please copy/paste the name from the Steam store, so it's correct.
6. Then look at the appid number, you can find this on the Steam store page for the game, its the last number. For example, for the game Sid Meier's Pirates! the appid is 3920
   App 3920 on the Steam Store
7. Go to your Steam Client -> Help -> System Information.
8. Copy and paste the System Information into a gist. Copy into a gist here
9. Attach a link to the gist into your issue.

I have the same problem trying to play "Totally Accurate Battle Simulator". I tried mucking around with command line options like "-screen-fullscreen 0" and "-show-screen-selector" and explicit "-screen-height" and "-screen-width".

Client information:

https://gist.github.com/windo/49282ee679ff459a4377539fe9d7c275

Seems that issue appears at specific hardware. I have a PC with GeForce GT 1030 and a laptop with GeForce GT 740M. Nvidia driver versions are the same. PC has no problems with Unity renderer but a laptop fails with the problem described above.
Trying to avoid the problem using flag PROTON_USE_WINED3D=1 allows me to run the game but it can't render an image. Screen is black and console is spammed by messages:
Attempting to bind Texture ID 15 as UAV, the texture wasn't created with the UAV usage flag set!
I'm wondering what sources (wine, proton) can I inspect trying to fix one of those two issues?

@yuanbi 's solution worked for me for "Pathfinder: Wrath of the Righteous", but shouldn't be necessary.

FWIW, the error I got was the resolution I was already using (!), so a simple check of the current resolution before attempting to apply a new one and only doing it if it's different might sidestep the problem

Possibly NOT using the kernel parameter nvidia_drm.modeset=1 may also fix this

Just to add to this, for the game "Encased", @yuanbi 's tip worked to get past the initial screens, but the game itself wouldn't complete loading up a savefile, it would just hang and play the background music