I am trying to run Diablo II resurrected using lutris (which was installed from sbopkg) and have had
some success but have run into a problem with vulkan. Now slackware 15 64 bit multilib has vulkan-1.2.176.1 along with it's 32 bit compatibility package but i have only managed to build slackware
current's vulkan-sdk-1.3.204-x86_64-1.txz and not it's 32 bit compatibility package. Now my question
is how would i do that in this case. And yes the current 1.3.204 does get diablo II res. to work but
i would like to see if the compatibility package would help in this case and also for other games as
well. It seems only recently that the lutris logs started mentioning the need for a more recent
version of vulkan (1.3) and it seems to be effective in this case, granted said game tends
to break compatibility with lutris sometimes (possibly because it is patched frequently) but there
you have it.

Not sure how exactly would 32bit "compatibility package" help you run 64bit exclusive software, on 64bit wine, hosted on 64bit system.
And how is this Slackware problem anyway?

Edit:
To be precise, the game having frequent patches and breaking ABI is not something anyone here can fix.
And this game, lutris, nvidia, or multilib, are not part of Slackware install.

If this is a request to bump vulkan version in -current, then you should note something like that in the title.
If something does not compile, attach the compiler output.

my suggestion for you is to use a rolling-release container to keep up with the speed of changes in lutris/wine/vulkan/diablo.
Take a look at this https://github.com/Kron4ek/Conty
This is an arch-linux container packed with wine, steam, lutris and a whole lot of other stuff to game and develop. you can add other stuff easily and rebuild it from time to time with a command (or download updates from the creator).
You just need to download the file conty.sh, make it executable and run in terminal something like "./conty.sh wine Diablo2.exe" or "./conty.sh lutris"

2 members found this post helpful.

Lot of times "64-bit" windows programs still require some 32-bit support.

And if you're using multilib (generally recommended, unless you're using the conty solution recommended by giomat), Alien Bob has a great description of how to build and install 32-bit packages: http://www.slackware.com/~alien/multilib/ (See "compiling 32-bit programs.)

yeah i know about alien bob's multilib howto and have run into an error which is not unheard of when you are trying to compile a current package on slackware15 multilib. See the attached file. I wouldn't know why the 32 bit version doesn't compile. I have the complete output but the file is too big to upload.

Attached Files

vulkan-error.txt (2.1 KB, 9 views)

This one's pure 64, a friend of mine has bought it so I've seen it.
I don't have windows or a sufficient GPU to run it.

Regarding building the compat32 vulkan lib on multilib, 99% you're missing some compat32 component.
Make sure also there's no nvidia driver in the way, when you compile it.

As advised above, you can avoid all of the mess by using Conty.sh: https://github.com/Kron4ek/Conty

It's a container (just a fancy word for large, static binary) with everything you need built in, including multi-lib. There is nothing else you need... just download and run. It works on a straight 64 bit system.
There are extra preliminary steps to take before compiling things when you have multi-lib. Installing multi-lib is not something I'd recommend to someone who doesn't understand compiler messages.

hmm never tried conty.sh, some day maybe i will. In any case i managed to install slackware current for testing and it seems to work fine with lutris and i also
managed to get dlss to work on it (which solved most if not all graphics issues for the d2 res.) as for problems compiling in multilib i have been doing it for years and usually i don't have many
problems i can not solve by searching it out on the internet or inquiring here. Honestly most distros do update vulkan pretty regularly so i don't see what the problem is as i did
get vulkan 1.3 to compile as 64bit. @ elcore so what you are recommending is i uninstall nvidia and then try to compile 32 bit vulkan and if so will that work after i uninstall nvidia or are you advocating a system that has never had nvidia on it?
Also doesn't the nvidia driver come with its own vulkan 1.3 api as well so vulkan 1.3 software IS indeed needed to make full use of the nvidia drivers. Another fact i
did not include is that i am using 530.41.03 which is pretty much the latest for now but i have tried the so called stable drivers with the same result.

No, what I'm saying is, nvidia casually replaced system libs many times in the past, and compiling packages on such a system has not been tested by the distributor.
And because nobody can fix the errors you may or may not encounter with these replacement libs, neglecting to mention you are hosting the nvidia blob on your build system just wastes everyone's time.
Maybe you could build packages in a VM, then install built packages on bare metal, and only then install the blob on top of that, if needed.
BTW, the latest blob for 32bit systems was 390.157 last time I checked. If 530.41.03 contains any newer 32bit compatibility bits, I'd be surprised.

I thought that behavior changed around the time of the pre-Slackware 15 development cycle, about 2019?

@ elcore it's funny that vulkan 1.3 would compile in 64 bit on slackware15 but not in 32 bit though. i suppose i could try an nvidia free root if not to see if this works and also to get the
32 bit package although i suspect it will still not work. Perhaps it has something to do with the bash version mismatch between version 15 and current. I have had to use the current slackbuild
and packages to get this to work as well as it has.

I have built vulkan-1.3.231 from a modified current vulkan-sdk slackbuild

I think I've added
-DROBIN_HOOD_HASHING_INSTALL_DIR="$TMP/robin-hood-hashing-$ROBIN_HOOD_VERSION/build/install/usr" \
to the cmake invocation in Vulkan-ValidationLayers-sdk

@ mickski56 are you sure that is all you did, i just looked and it is the same as my current slackbuild ?
I also um commented line 359:
# zcat $CWD/VulkanTools-sdk.gcc12.diff.gz | patch -p1 --verbose || exit 1
or did you keep it ?

I must be the odd one out! There seem to be more people who would rather spend weekends getting it working rather than actually playing the games.