Delete the ~/.hgl directory and start with winecfg again. It should setup Mono for you during the first configuration and if not at least tell you that it didn’t. This is what WINE does by default under Debian as well as when you’ve installed it from source code.
It might also work afterwards when you run it with msiexec, but I’ve never tried. I know the above works. Done it many times using the vanilla source code (but Debian packages are just fine).
well it neither did nor told me it didn’t i’m afraid.
but yeah i’ll wipe and try again.
for the record, wine-mono is installed system-wide.
if it fails again, I’ll just try to run the msi file from /usr/share/wine/mono myself, maybe that helps (and should be “more stable” than using the POL script)
noticed mono got not auto-installed, so I ran msiexec /i /usr/share/wine/mono/wine-mono-4.7.1.msi
patch installed fine
now I have the problem I don’t actually have a copy of Windows (neither to dual-boot nor to set up in a VM), could you maybe tell me the files the launcher got for you again so I can just download them manually (the url prefix is in the patcher.xml anyway , just need to know what files to get)?
I tried the list you posted above but I suspect it changed since then, because about half of the files you listed result in 404 errors.
what’d be really great (hey devs, looking at you ) would be if we just could get the link to the manifest file.
The file names haven’t changed. I haven’t tried to download the files manually. Guess we’ll have to wait until Omerta or someone else has got the time to tell us how to do this for ourselves. And they’ll be busy with fixing bugs atm.
oh btw to get the info about how the launcher works, I just noticed strings -e l (that’s a small L, not a big i) and strings -e b can search for utf16 (which .net uses for every string because idiots), maybe that’ll help to identify filenames
now the only problem left seems to be the directx error. maybe I should try just putting that specific dll next to the exe without fancy installation stuff that messes up wine? my nvidia drivers support native Direct3D on linux, it just seems to be missing that dll function.
downloading the MS d3dx9_34.dll now allows it to start, but I get a black screen except for some slider-looking thing and no cursor or mouse/keyboard response:
fun fact: the only other mention of my problem google can find is https://archive.is/WYKqR, where 2 people talk about it and nobody has a solution.
wine shows no errors/etc. any idea how to fix that?
EDIT: with debugging enabled, I get
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3:
fixme:d3d_shader:print_glsl_info_log Vertex info
fixme:d3d_shader:print_glsl_info_log -----------
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[0].zw” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[1]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[2]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[3]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[4]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[5]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[6]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[7]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[9]” might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: “vs_out[11]” might be used before being initialized
but that doesn’t seem critical to me, I mean after at least one frame those will be initialized anyway.
ok, just for the lulz I started the singleplayer mode, and it happily greets me with a ton of bink videos. created a char, played the tutorial, exited, to see if the data generated helps in any way. but nope, same problem still
so it seems to be a bug with the MP client only. for the record, the unmodified MP client has exactly the same issue.
but hey, at least I can play SP now until I manage to get MP running
did you ever get it to work? I can get the game fully working, but I can’t get the launcher to launch. I get this error:
System.Runtime.Remoting.RemotingException: Channel London2038_Launcher_Mutexjd:SingeInstanceIPCChannel is not securable while ensureSecurity is specified as true