If you're experiencing the resolution issue on the base install, then it's not patch related. As for the terminal commands, there shouldn't be any output on steps 4 and 5—those just respectively rename and symbolically link the directory.

If you've tried the WS9Wine1.9.21 Engine I'm not sure I have a lot of other suggestions for you, other than messing around in the Screen Options settings to try and find a combination that works for you.

A few standard troubleshooting questions:

• What are your systems specs?
• Desktop or Macbook (what model)?
• What type of video card (Nvidia or ATI)?
• What version of macOS?
• What's your normal screen resolution, and do you use a "Scaled" resolution setting in macOS's Settings>Displays?

Ok so my specs are,

MacBook Pro (13-inch, Mid 2012)
Processor 2.5 GHz Intel Core i5
Memory 4 GB 1600 MHz DDR3
Graphics Intel HD Graphics 4000 1536 MB
OS 10.12.6
Standard Resolution is 1280X800
Not scaled.

I'm also running it on macOS 10.12.6 right now without issue, so at least we can rule that out.

My best guess is that it's related to your video card. Someone in the Steam forums reported having issues with the patch (basic patch is installed in GOG's version) and Intel HD 4000 video compatibility (on windows). But, conversely, someone over on Planet Vampire (thread link) got it working just fine on a Mac using Intel HD 4000—though that was running on Mountain Lion.

Alright, let's try this a different way, as it's very possible you're just encountering one of Mac's many issues with full-screen resolution changes. Let's see if running in windowed mode fixes your issue.

Open up the Wineskin Advanced preferences as you did before—
• Right click the .app
• "Show Package Contents"
• Run Wineskin.app
• Click "Advanced"

Now, find the "EXE Flags" box. In the setup tutorial above I provided an optional example of adding "-console" (without the quotes) there. Well another option is "-window", which allows you to run the game in windowed mode.

• Add "-window" (without the quotes) to the "EXE Flags" text input
• Run the game (the main .app file)

Note: If you have multiple flags in "EXE Flags", they should be separated by a space—e.g. "-console -window"

Alternately, you can perform a "Test Run" using the last button at the bottom of the "Advanced" settings window if you want to view the test logs after closing out the game. Just don't run in test mode for very long—the logging slows the game down and you'll end up with some huge logs if you try to play a full game.

You are a legend!

Adding the "-window" seems to have done the trick, it now opens and runs properly at 800x600.
Still no luck changing the resolution to anything larger, either within the game using Options>Video or via Set Screen Options, but at least now I can actually play the game.

Would it be possible to add the 1280x800 or any other resolution to the EXE Flags box or am I overreaching?

Thanks so much.

Its a little unusual if you're not getting any resolution options in the game settings screen other than 800x600.

I believe you can also set the resolution in the EXE Flags. If I remember correctly it's -width and -height, but it's been a while. Could be -w and -h if my memory's failing me ;)

Anyway, try adding something like "-width 1024 -height 768" (without the quotes) to your EXE Flags. If it doesn't work, try "-w 1024 -h 768".

Any valid resolution your video card supports should work, but your mileage may vary.

As a last resort, I believe VtMB stores resolution options using Windows Registry keys (as opposed to in config files). Wine comes with a registry editor, but I don't know VtMB's key folder location off the top of my head.

Again, there's also the option of trying to use virtual desktop windows to force artificial fullscreen resolutions. There are settings beyond what's available in Wineskin's Screen Options by going directly to Wine's packaged config editor (winecfg), which is available from the nested Wineskin.app by going to Advanced>Tools>Config Utility. That's a whole other topic I'm not going into here though. Wine's config utility allows you to manage everything from artificial desktop resolutions to dll overrides and sound driver changes—it's not something you want to mess around with too much as a novice except as a last resort.

No problem. I'm glad it finally worked. I'm pleasantly surprised the hard-set resolution did the trick with the autodetection seemingly broken. I'll keep that in mind down the road.

Have fun =)

I struggled through installation using this guide and a few others. None of them succeeded on their own for me, and I found PlayOnMac to be the most effective solution. Here's a step-by-step write-up of exactly how I got it working.

Installation known working under the following parameters:

* iMac (Retina 5K, 27-inch, Late 2015)
* Processor 4 GHz Intel Core i7
* Memory 32 GB 1867 MHz DDR3
* Graphics AMD Radeon R9 M395X 4GB
* Mac OS 10.13 High Sierra
* PlayOnMac 4.2.12
* VtMB 1.2 GOG edition with 9.7 Unofficial patch
* Wesp’s 9.8 Final Unofficial VtMB patch

Needed installers
1. GOG version of VtMB (setup_vtmb_1.2_(up_9.7_basic)_(11362).exe and setup_vtmb_1.2_(up_9.7_basic)_(11362).bin)
2. Wesp’s unofficial patch from patches-scrolls dot de

Installation instructions step by step
1. Right click the installer file, select Open With… and choose PlayOnMac.
2. Install the program as normal, but do not launch the game after installation is finished. Instead, select Exit.
3. Create a shortcut inside PlayOnMac, as normal.
4. Highlight your VtMB installation, and click on Configure in PlayOnMac
5. Under the General tab, type -window in the Arguments field.
6. Select the Miscellaneous tab, and click the button labeled “Open program’s directory.”
7. Rename the folder called “Unofficial_Patch” to something like “Unofficial_Patch_GOG” and close the finder window.
8. Click on the button labeled “Run a .exe file in this virtual drive.” Select the Wesp patch you downloaded, and allow it to install, selecting whichever components you want.
9. After installation, do not run the game.
10. Open up the Mac terminal emulator. Navigate to the VtMB folder. In my case, this command looks like: cd Library/PlayOnMac/wineprefix/Vampire__The_Masquerade___Bloodlines_/drive_c/GOG\ Games/VtMB/
11. Issue the following terminal commands:
a. ditto -V Vampire Vampire.bak
b. ditto -V Unofficial_Patch Vampire
c. mv Vampire Vampire_UP
d. ln -s Vampire_UP Vampire
12. Close your terminal emulator.
13. Remove any useless shortcuts on your desktop.
14. Run VtMB from inside PlayOnMac.
15. Select Options from the main menu. Click on the Video tab, and select the resolution you’d like to play. Accept changes, close the game, and relaunch it.
16. Good to go!

I'm glad you got it working and that the most important parts of my guide (updating the patch) worked for you. You didn't seem to have any technical difficulty, though, so I'm surprised you had trouble using Wineskin.

I stopped using PlayOnMac because I had better luck porting most games with Wineskin. PlayOnMac pre-installs commonly used DLL overrides and winetricks that sometimes get in my way, but of course they do it because it's beneficial for most.

I do recommend the PlayOnLinux/PlayOnMac install script library (as well as the PortingKit library), as they're a good resource for people performing standalone ports that already have existing recipes. And, of course, WineHQ's AppDB is the go-to starting point and communication hub, but they're VERY linux-centric, so YMMV.

Anyway, thanks for the update. The more porting options Mac gamers have, the better :)

Update: I linked your post in the topic post as an alternative.

Wineskin kept giving me errors, no matter what I did. Nearly every permutation of option configuration led to "Engine error: Unable to set mode." Even editing the Windows Registry to force the game's resolution to something other than 800 x 600 led to the error. In regular command line based Wine, adding -window to my launch arguments caused the same Engine error.

I was ultimately able to get some success with full screen, but it required hex editing the engine.dll file, and it screwed up the HUD, so my blood bar was floating in the middle of my screen. No edits I tried fix this.

Anyway, thanks for your guide. It definitely provided a lot of the key information about overwriting the mod launcher. I tried to get somewhere with the Linux script, but had no luck. For what it's worth, this process (exactly as stated in my post) failed without Wesp's patch. The GOG patch would just error out for me.

Oh well, either way, it's working, and I didn't resort to my final stand, which was going to be running Ubuntu in a VM and using the Linux mod loader to play.

Thanks for this useful tutorial.
I have a couple of issues. When I first tried to install it, the game run as expected.
At a certain point i realised that the left button of the mouse was not working.
Out of curiosity I tried to set a new button for attack but it didn't work.

Also if I double click on the file I receive a message that asks me if I want to uninstall Vampire and all its components.

It seems that the only way to launch the application is re-installing it every time.
Any suggestions?

To address your comment about uninstallation—if you followed my guide then I have no idea ;)
It's never asked me to uninstall when running the game.

But it's easy to make a mistake during installation. Are you sure you fully followed Step 7 and selected "Vampire.exe" from the dropdown? You may have accidentally selected (or it likely defaulted to) the uninstaller executable instead. If so, you can go back and set the correct EXE path from the advanced wineskin window. If you followed the guide's app title and location, it should be at "/Applications/Vampire the Masquerade - Bloodlines.app/drive_c/GOG Games/VtMB/Vampire.exe"

As to your other question, about the the left mouse button not working. There's a common bug where a new game won't load the character hands and weapons, so clicking to attack does nothing. I've run into this issue primarily when trying to play a Tremere, but I've seen it occur for other clans as well.

The most common solution to the issue is simply to wipe the save and start a new game, but on occasion I haven't been able to get my Tremeres to properly load even after numerous restarts. In such case, you can use console commands to load up your hands and prep your character for interaction (you'll need to enable the in-game console by adding the EXE Flag "-console" via Step 8 of my install guide). You can load up the console by hitting the tilde (~) key.

Console Commands to fix the "no hands" issue

• give item_w_unarmed
• give item_w_fists
• give weapon_physcannon

There are a lot of different potential startup script glitches. People also occasionally report missing their wallet, keyring, clothes, etc. So in case you find any of those missing, their respective console commands are:

• give item_g_wallet
• give item_g_keyring
• give item_a_lt_cloth

I hope some of that helps :)

Thank you so much for your time.
I can play without any problem now although to be honest I still can't understand what caused the hiccup in first place.

Not a problem, but you're welcome. We all gotta help each other out :)

Seems to have installed ok! Many thanks for the well written guide.

I enabled the console with the EXE flag and when the game starts it complains lots of .txt files can't be found from the vdata/system folder e.g. Histories001.txt. Thing is, if I find that folder on C drive, that file doesn't exist.

Anything to worry about here?

Also is there anyway to get the intro videos to work? I know I could probably go watch it on youtube but would prefer a working game.