Don't know if this is the right place to post this, but when running ResPatch.exe, there's no way to select hidden folders, even after setting the winecfg to show dot files. How do you get around this?

Don't know if this is the right place to post this, but when running ResPatch.exe, there's no way to select hidden folders, even after setting the winecfg to show dot files. How do you get around this?

I did not encounter this issue as I did not need to navigate to any hidden folders. A possible solution would be creating a symbolic link (e.g. ln -s .steam Steam) you'll have to test it to confirm.

@kisak-valve
Regression: Proton 4.2-3 breaks this game, after the bik videos are rendered (in 4.2-3 the videos properly scale, fixing one of the issues I mentioned in the op) the menu is a garbled mess (does not correctly render)

Forcing proton to use the 3.16 series (3.16-9 beta or older) fixes the issue making the game playable again (but the issue with BIK scaling returns)

After messing around a bit more I found that installing the unofficial patch, launching the game on the 3.16 series, setting the resolution to your screen's native resolution, and the restarting the game with 4.2-3 the game will now work normally on 4.2-3. So there's effectively a workaround for this problem. But it still points to a potentially serious regression in Proton 4.2-3.

@kisak-valve
steam-2600.log
Current system info: https://gist.github.com/Rabcor/1cc205282a7aadd53bab8b98668b512b
Screenshot: https://imgur.com/QpZBhQJ.png

Note: In this test I have the unofficial patch installed, but configured the resolution to it's default 800x600 again, This results in 1/4 of the menu being rendered as seen in the screenshot. Without the unofficial patch installed the entire screen would be the garbled mess instead of just 3/4 of it.

Note 2: If I took a screenshot with Steam (F12) it displayed the entire main menu as if nothing was wrong in the resulting screenshot.

Edit(Note3): Also I know Laptops with hybrid graphics can be problematic on linux. mine's set up with PRIME, e.g. it just uses the dedicated graphics card as if it were a desktop. (Only way to get vulkan running)

I can confirm this issue is still present in Proton 4.11-9. After the introductory videos, you can't see the game's main menu. It's just a black screen. Works in Proton 3.16.

Here's my log:
steam-2600.log

After adding that to the game's launch options, I received this error, and the game would crash/close:

I am getting crashes on quicksave. Does anyone else experience this?

5.4.13-arch1-1 kernel
4.11-12 proton
latest unofficial patch installed
"-game Unofficial_Patch" launch options

I am getting crashes on quicksave. Does anyone else experience this?

5.4.13-arch1-1 kernel
4.11-12 proton
latest unofficial patch installed
"-game Unofficial_Patch" launch options

Hello! I've found a workaround to this issue for now. Figured I'd comment here since this is the only instance of the issue that my google skills can find.

For some reason the built-in quicksave function does crash under wine (at least in my experience) but saving regularly works fine. So you can just bind a shortcut key to the regular save system like this:

• Add the -console switch to whatever you're using the launch the game.
• Load into a save.
• Open up the console and type bind "F9" "save quick QuickSave"
• Voila. F9 will now quicksave without crashiness.

The quick parameter is the save's ID. If a matching ID is provided later, the save will overwrite the previous. This means with one bind, you'll have one quicksave slot that will always be overwritten. Alternatively you could do something like this if you wanted:
bind "F9" "save quicka QuickSave 1"
bind "F10" "save quickb QuickSave 2"
bind "F11" "save quickc QuickSave 3"

Be sure to successfully quit after binding your key, as for some reason if you experience a crash it won't save. Once you've got the bind going, you can disable the console if you wish.

Hope this helps.

Compatibility Report

• Name of the game with compatibility issues: Vampire: The Masquerade - Bloodlines
• Steam AppID of the game: https://steamdb.info/app/2600/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.59
• Kernel version: 5.5.5
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 5.0-3

LOG:
steam-2600.log

Symptoms

Black screen on launch

Reproduction

Vanilla, no patches

Using the "PROTON_FORCE_LARGE_ADDRESS_AWARE=1" launch option produces the infamous "Unable to run, less that 15mb memory available" bug (https://www.pcgamingwiki.com/wiki/Vampire:_The_Masquerade_-_Bloodlines#Unable_to_run.2C_less_that_15mb_memory_available).

LOG with "PROTON_FORCE_LARGE_ADDRESS_AWARE=1":
steam-2600.log

Hi, I am confirmig what @shoober420 found, it can get fixed by using Unofficial Patch or Proton 3.16.
What I found next is that for some reason I cannot select other dialogue option than first. Tried on Steam vanilla and UP, both acting same. Console or remapping shows that keys 1 to 4 as captured correctly but game just ignores all others except 1. Has anyone encountered this? Thanks.

Hi, I am confirmig what @shoober420 found, it can get fixed by using Unofficial Patch or Proton 3.16.
What I found next is that for some reason I cannot select other dialogue option than first. Tried on Steam vanilla and UP, both acting same. Console or remapping shows that keys 1 to 4 as captured correctly but game just ignores all others except 1. Has anyone encountered this? Thanks.

Yes, I can confirm this issue. It works fine under wine-staging but I'm getting this bug under Proton. I don't think this is an issue with key mapping as changing key binding in game console using command bind "2" "anotherkey" doesn't solve this bug.

Compatibility Report

• Name of the game with compatibility issues: Vampire: The Masquerade - Bloodlines
• Steam AppID of the game: 2600

System Information

• GPU: nvidia GTX 770
• Driver/LLVM version: nouveau
• Kernel version: 5.8.11
• Link to full system information report as Gist:
• Proton version: 3.16-9

I confirm:

• [ ] that I haven't found an existing compatibility report for this game.
• [ x ] that I have checked whether there are updates for my system available.

Symptoms

I have installed the unofficial patch.

I played the first mission at the Santa Monica beach. It plays but there are some bugs and setup was involved thanks to the tips in this thread.

Bugs:

• movies during intro are not fullscreen: resolved in proton 4.x

• freezes sometimes during loading screen

• quicksave crashes: see workaround: https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-583835458

• unable to use other proton versions than 3.16-9.
  4.2-9 weird graphical glitches where it can't display main menu but sometimes it works. 4.11-2 fails to launch. 5.0-1 untested.

• have to stop program after exit

Reproduction

Setup instructions:

1. set launch options: PROTON_USE_WINED3D= %command%
   nouveau does not support dxvk, so use wine's DX9 support.
2. Force the use of a specific Steam Play compatibility tool: Proton 3.16-9
   This is needed otherwise with Proton 5 you get the 15 MB memory error as seen in https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-562370128
3. Launch game to create a prefix directory then exit game.
4. Install unofficial patch as @Rabcor had mentioned.

To install unofficial patch you need to download it, and run the following command:
WINEPREFIX=/path/to/steamapps/compatdata/2600/pfx wine vampirepatch.exe

However, this did not quite work because the pfx created by steam is 64-bit while the vampirepatch.exe is 32-bit. To resolve this I had to create a 32-bit prefix as described here:
https://old.reddit.com/r/linux_gaming/comments/99e0kc/steam_playguide_create_custom_32bit_prefix_to/?utm_source=BD&utm_medium=Search&utm_name=Bing&utm_content=PSR1

Here is a dump of commands where I save the Steam directory from the prefix, create a new 32-bit prefix using wine-staging, create a syswow64 directory, and move Steam back.

cd .steam/steam/steamapps/compatdata/2600/
cp -r pfx/drive_c/Program\ Files\ \(x86\)/Steam .
rm -rf pfx
WINEPREFIX=$PWD/pfx WINEARCH=win32 winecfg
mkdir pfx/drive_c/windows/syswow64
cp -r Steam pfx/drive_c/Program\ Files/
WINEPREFIX=$PWD/pfx wine ~/vampirepatch.exe

With this in place, VTMB can finally run the unofficial patch. Select ~/.steam/steam/steamapps/common/Vampire The Masquerade - Bloodlines when prompted by the unofficial patch for the installer. This should be under the Z:/ or root directory in wine.

1. Configure launch options again to use the unofficial patch: PROTON_USE_WINED3D= %command% -game Unofficial_Patch

2. Resolve the quicksave crash as mentioned in the bugs section above.

@CrotchetyKitty

* Open up the console and type `bind "F9" "save quick QuickSave"`

This worked. Edit: nm it did manage to crash once. I'll have to test more.

bind "F9" "save quicka QuickSave 1"
bind "F10" "save quickb QuickSave 2"
bind "F11" "save quickc QuickSave 3"

Using save slots like this caused me to freeze.

I'm on Gnome, using the unofficial patch, a few problems remain:

• If I use the -window launch option, the game window hangs in a black screen indefinitely;
• If I use the -window -noborder launch options, the game window hangs just as before and the border is still there;
• If I use the -fullscreen launch option, the game freezes the whole computer and I need to push the reset button.

I only managed to run the game using the -window launch option, killing the game process, removing the launch option and then launching the game; it makes the game start windowed with a border. It seems that the -noborder launch option has no effect whatsoever, that makes the game unplayable on Gnome, since it has those fat window decorations, which pushes the game window past the display boundaries.

Alright, using the virtual desktop prevents the game from freezing the computer while trying to launch with the -fullscreen launch option.

Edit: I can confirm previous reports of the game freezing at random on loading screens, I'm not sure why.

• Add the -console switch to whatever you're using the launch the game.
• Load into a save.
• Open up the console and type bind "F9" "save quick QuickSave"
• Voila. F9 will now quicksave without crashiness.

Still the game freezes for me in 1 from 3 quicksaves + freezes on loading screens make the game almost unplayable for me (I wasn't able to play more than 10 minutes straight without the game become frozen).
I'm just wondering what the game is doing during the save to froze.

Have there been any updates guys? I tried to play it and it crashes or freezes at a quick save still for me at least on the steam deck

Tried to play with unof patch - doesn't work with proton version <6, with 6 and up ot launches, and can be kinda played from desktop mode, but the controls are limited, and if launched from game mode it doesn't understand any controls except right stick camera and right trigger lmb, also can't use virtual keyboard in game.

Tested this again with both GE Proton 7-50 and the latest Proton Experimental, and the game is still non-playable in Gaming Mode due to the controller bug. Only right stick movement and right trigger work. I'm using the latest game update and 11.3 Unofficial Patch.

Replying to https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-1457487359

I found a solution on reddit that helped. Proton 6.21-GE2 worked for me.

Replying to https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-1457523538

While I appreciate the workaround, downgrade still isn't a solution per se. The issue remains in Proton's newest versions.

Replying to https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-1457814707

I fully agree with you, in fact GE isn't even official, I wrote it so it at least people here can play the game.

I've done some more testing and, interestingly enough, on the Steam Deck the problem might be related to how the window of the game is drawn.

I'm using Proton 6.21-GE2 and it enables contoller support in game mode, but only when at native resolution (1280x800). Putting the resolution (in game or via the settings in Steam) to 960x600 makes breaks the controller support (in the same way that newer Proton versions are broken) that this particular version of Proton solves.

I've also tried with the environmental variables of "-full" and "-window" which yield the same results - changing the resolution in both windowed and fullscreen breaks controller support.

Replying to [#1804 (comment)](https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-1457487359)

I found a solution on reddit that helped. Proton 6.21-GE2 worked for me.

No sound on steam deck.

Hello @syberpunk, based on [#1804 (comment)](https://github.com/ValveSoftware/Proton/issues/1804#issuecomment-590131659), can you test how the game behaves with the launch options set to PROTON_FORCE_LARGE_ADDRESS_AWARE=0 %command%? That runtime option was enabled by default a fairly long while ago.

Hi @kisak-valve , this does not work with the proton 8 version I declared in my report.

@syberphunk Unfortunately this seems to be a game bug, as I can reproduce this issue on my Linux machines and on my Windows machines. It seems to happen when the RAM is higher then 3.5GB or so. While it appears regressive, it is the intended behavior here due to Proton improving on its WINE implementation. The older Proton version will still be able to play the game, and in my testing it works up to Proton 4.11-13.

@syberphunk Unfortunately this seems to be a game bug, as I can reproduce this issue on my Linux machines and on my Windows machines. It seems to happen when the RAM is higher then 3.5GB or so. While it appears regressive, it is the intended behavior here due to Proton improving on its WINE implementation. The older Proton version will still be able to play the game, and in my testing it works up to Proton 4.11-13.

This needs to be handled better, and with better instruction to the user.

The scenario of this which I highlighted in the issue I raised, is that a customer can buy this on the Steam Deck for £15 still, and will have no messaging or instruction that they:

1. Can play it on the Steam Deck (the 'verified' status is inaccurate)
2. Need to change their proton version so that it does play on the Steam Deck

There's also some part of me that frankly says I shouldn't have to jump around proton versions to get games working, while that's currently possible and capable, while this is a game that's available for sale and listed for purchase to Valve's ecosystem it makes sense to have either the latest Proton handle this gracefully, or to have better messaging. A recent Proton handling this gracefully at least reduces confusion and reduces effort on the user's part, making for an easy sale for Valve.

@kisak-valve I have noticed a regression in 8.0, and another regression in 9.0 as i was testing the game (not sure if the regression from 8.0 carried over to 9.0)

I tried running proton version 4.2-9 again, it behaved fairly similar as in the op, so I had a thought to see if i could replicate the 15mb memory error on it by using PROTON_FORCE_LARGE_ADDRESS_AWARE=1; and I could, using this option made the error happen.

The regression I noticed however is that on newer versions, setting PROTON_FORCE_LARGE_ADDRESS_AWARE=0 does not resolve the issue implying to me quite strongly that disabling Large Address Aware this way does not work at all.

PROTON_FORCE_LARGE_ADDRESS_AWARE=0 on 5.0-10; 5.13-6;7.0-6 allows you to play the game normally
PROTON_FORCE_LARGE_ADDRESS_AWARE=0 on 6.3-8 allows you to launch the game but the main menu is just a black screen (this seems like it was fixed by 7.0)
PROTON_FORCE_LARGE_ADDRESS_AWARE=0 on 8.0-5 and Experimental, it prevents the error, but the game will not play (just opens a small black window on launch and then doesn't do anything more.)
PROTON_FORCE_LARGE_ADDRESS_AWARE=0 on 9.0(Beta) does not prevent the error, e.g. this setting is broken on 9.0 beta. Proton-Ge-Custom is also affected.

So the two regressions are that on 8.0, the game will not launch properly, and on 9.0 the game will not launch at all even if you set the flag that should allow you to launch it.

On another fun note, using the Proton 4.11, using the PROTON_USE_D9VK flag allows you to play the game without the unofficial patch.

All of my testing was on an AMD Radeon 680M iGPU from a Ryzen 6900HX cpu on endeavourOS(arch) with mesa 24.0.4

@Rabcor Can you try STEAM_COMPAT_CONFIG=noforcelgadd %command% for a launch option? That should work and allow you to play on newer Proton versions. Let me know if you still have problems.

STEAM_COMPAT_CONFIG=noforcelgadd

This works!

So I just spent maybe 4 hours pulling my hair with the latest VTMBup115rc11.2 patch version.
Turns out it plops a d3d9.dll next to the exe. Renamed it and the game runs again..
Also on recent Proton versions, since I'm running two dGPUs, this is the only game that still needs DXVK_FILTER_DEVICE_NAME, or the main menu will go haywire with flickering.

Hope this helps someone, somewhere.

Is anyone able to play Bloodlines at the moment, using the unofficial patch 11.5? Using older Proton versions, I just get a black screen. On newer versions, it crashes right away. Using Experimental, I get a gray screen saying "loading..." for a second, then it crashes.

Just found out, patch 11.5 works fine on Proton 9 without any flags on Bazzite. For some reason it does not run on Fedora Silverblue using Steam from Flathub.