Sorry for the delayed response.

It's been well over a year since I played VtMB now, but if I recall correctly, all the necessary histories info is stored in histories000.txt. That's where I've always made my manual class edits. It's possible the load scripts are just checking for additional files.

Having said that, you'd be better off asking about it in a modding thread, as those guys understand the file structure better than myself. I just specialize in making broken things run ;)

The intro videos seem to be hit and miss between systems and video cards. Wine has come a long way since I did this writeup, so you might have better luck with a newer engine.

Newer Wine Tech Notes (Rant)

The official Wineskin (by doh123) has kinda fallen out of support, but over on GitHub, Gcenx has been maintaining an updated version of doh123's code known as "Unofficial Wineskin Winery"—the binaries are available under the Release section of his WineskinServer project. A lot of people seem to be happy with it, but I haven't tried it yet myself.

See Gcenx's comments here and here later in this thread for a correction to my earlier version of this post.

Then there's PortingKit (probably the most popular option these days). VitorMM, who maintains the PortingKit project, has made a lot of improvements to Wineskin—which acts as the base for for PortingKit—and has merged in Gcenx's code with support for wine engines up to at least 4.3 (you can get newer engines when you create new custom wrappers in PortingKit).

Unless you want to get into the code, I'd recommend just keeping PortingKit up-to-date and creating custom wrappers there.

Edit:

To be more specific, if you want to upgrade your existing installation with a new Wine engine, you can create a new custom wrapper from the "File" > "New Custom Port" menu in PortingKit. Name it something obvious like "TEST.app". Select the engine you want and allow it to download the engine. Then, when it asks for an installer executable just cancel out and delete the partial wrapper that was created. Then, on your existing VtMB app:

• Right-click the app file
• Select "Show Package Contents"
• Run Wineskin.app
• Select "Advanced"
• Select the "Tools" tab
• Click "Change Engine Used"
• Select the new engine—e.g. "WS9Wine4.3-2"
• Click OK—After a few seconds you'll be back in the "Tools" window
• Click "Test Run" to see if it's running OK
• You can repeat the process to test as many engines as you like or return to your original engine.

Hi all,

I've been getting this "Oops no new executables found" error and I can't seem to make its source.

I've tried everything and everything seems alright on my end. Followed all steps and everything was going alright until the actual installation bit.

Any thoughts on this?

Many thanks!

That error means Wineskin didn't notice any executables created by the installer. So I'm just going to throw the general checklist questions your way—feel free to just answer the last one that applies before things went wrong ;)

Did the GOG installer open successfully?

Did the installation complete successfully?

Are the game files present in the wrapper? (How to check below)
• Right click "Vampire the Masquerade - Bloodlines.app"
• Select "Show package contents"
• Navigate to "drive_c"->"GOG Games"->"VtMB"
• Look for "Vampire.exe"

If "Vampire.exe" exists, you can manually set that path via "Wineskin.app" within the wrapper.
• Click "Advanced" (same as you did for installation)
• Click "Browse" on the "Windows EXE" line and find and select "Vampire.exe"

If "Vampire.exe" does not exist, or more generally the "GOG Games" or "VtMB" folders are not present, then the installation failed. Usually, though, it will notify you in the installer if something went wrong.

Hi Xixas, I've been having the same problem as trishacontreiras.
When I first attempted to install the game I used "setup_vampire_the_masquerade_-_bloodlines_1.2_(up_10.2)_(28160).exe" from the GOG website. The same error trishacontreiras describes popped up, but so did the GOG installer. I completed installation and the files you mention are present. However trying to install the patch makes the same pop-up appear, but there is no actual installation going on. I was using "VTMBup103rc2.exe" from the latest unofficial patch post. I'd be grateful for any help.

So the "no new executables found" error popped up before (or at the same time as) the installer ran? Ergo, the GOG installer doesn't complete before the error is received? If that's the case, I'd have to guess that a subprocess is started (forked) and then the parent process terminates.

In turn, if a forked process is used, you'd just have to dismiss the initial error, allow the installer to complete, and then manually assign "Vampire.exe" on the "Windows EXE" line.

If the patch ran without crash/fatal error, I wouldn't assume that no actual installation is occurring. As I mentioned in Step 4 of "Updating to the Plus Patch", it's normal to receive the no new executables error on the patch installation. The patch updates files, but the same executables (notably Vampire.exe) exist both before and after applying the patch (therefore there are no new executables from Wineskin's perspective).

Unfortunately, as I haven't played in a while, I haven't tried applying the latest patch. Wesp (the UP creator and maintainer) is still active in this forum—and I'm always happy to be corrected if I'm wrong!—but I would assume the patch still installs in effectively the same way.

I apologize, as I feel like this is one of my less useful posts overall—more a stream of consciousness, really ;)

What I'm trying to say is that things are not always what they appear at a cursory glance, and Wineskin's messaging doesn't always adequately designate the actual state of affairs—you always have to dig into the files and verify changes (or a lack thereof), and always check your created/modified times.

Anyway, I'm happy to dive into the issue further if either of you can provide more specific details.

Thanks for the reply xixas. It's as you say, the error popped up before the installer ran, so I had to manually assign vampire.exe.
However after I changed the 'Unofficial_Patch' folder name to something else and attempted to install the patch I couldn't see any differences in the VtMB folder. Is a new folder named 'Unofficial_Patch' supposed to be made when I install the patch? The problem might be the updated patch so I'll see if I can get the old one and I'll tell you if it works.

Got the same results from using the 9.7 patch.

Yeah, the patch should add a new directory called "Unofficial_Patch" if it installed correctly. Since you both reported the same issue in short order it's less likely that it's as simple as installing to the wrong directory—all the same, doesn't hurt to look around for a rogue "Unofficial_Patch" floating around ;)

I'm traveling, so I can't just grab the latest GOG VtMB version at the moment, but looking at the changelog there aren't any major changes listed since UP 9.7.

For the sake of completeness, what version of MacOS are you running and which Wine Engine did you choose?

I've had issues with a number of my ported games since updating to 10.14, but most of them worked out with a bit of tweaking.

Hmm, that reminds me... just in case—from the wineskin advanced page, click the "Set Screen Options" button at the bottom and ensure "Auto Detect GPU Info for Direct3D" is UNCHECKED. That option keeps a number of things from working correctly on Mojave.

If we can't this working, it might be worthwhile to look into creating a new wrapper with the latest version of PortingKit (as I mentioned a few comments back in my response to neonbible). It's based on Wineskin Winery on the backend—its just got a bunch of extra tools up front. Notably, though, Vitor's been patching Wineskin issues for MacOS 10.14 compatability. They don't have a pre-built port for VtMB, but you can create a custom wrapper from the menu and proceed similarly... once the initial wrapper/game installation's done it's just like a standard wineskin wrapper.

Occurs to me I really ought to get around to documenting all this somewhere!
If we can get ya up and running I'll add any applicable notes to the original post.

I'd love to jump in here with my experience with this.

Ive been replaying VTM:B again on my 2017 MacBook Pro. I used a piece of free software called The Porting Kit to make the wine wrapper. It plays FLAWLESSLY.

Porting Kit also has a mod and patches install function so updating to the newest unofficial patch was a breeze. I cannot recommend this software enough! portingkit.com/en/

Didn't I just suggest this—twice? ;)

Always glad to see people supporting Paul and Vitor though. Those guys have done some great work!

Edit:

When I get a chance I'll grab up to date versions of everything and give it a once over in PortingKit. This thread still gets a good number of views, but it's a couple years old and two major MacOS versions out of date.
If it's still helping people it's worthy of an update.

Sorry... I totally over looked it. Anyway. I can vouch for the game working Flawlessly on a relativly new MBP running OSX 10.14.3.

Does Porting Kit create standalone self contained apps? So if I backup the app file I can load it on any Mac?

Yeah. It's basically an updated version of Wineskin Winery with a different creation UI.
The final app file works just like any other Wineskin app.

Yep—assuming, of course, that the target machine is reasonably within spec of the original machine.
In other words, yes, the app files are portable.

I usually compress them to *.dmg files for storage and quick reinstallation. Of course, every time they update MacOS new problems may be introduced with older apps, so sometimes I have to extract them, update the settings a bit and then re-store them.

I think I should clear up the miss conception here “Unofficial Wineskin” is not a fork of Vitor’s project I was working Wineskin before that code was added to GitHub, that was in response to my work I posted to PortingTeam forums.

PortingKit is more like say Lutris but outputs Wineskin Wrappers, but can also be used to make custom wrappers within a cleaner UI. Wineskin Winery is basic but that’s part of its charm.

If your going to be updating your guide you may want to instead use PortingKit it will work for anyone running macOS 10.8 through 10.14 as of March 27th Vitor now integrated Unofficial’s master wrapper that solves a whole host of issues.

You won’t need to disable gpu detection or swap to macdriver as gpu detection works and macdriver is the default.