So there is hope. I did a ton of digging into the script errors. The closest I could get is that it’s an issue with Wine’s version of oleaut32.
With Wine’s debug logging, I could see errors to the effect of 0009:warn:ole:ITypeInfo_fnGetIDsOfNames no names found and similar. Also reading bug reports with Wine show that AddTypeLib was unimplemented – https://github.com/wine-mirror/wine/blob/master/dlls/vbscript/vbscript.c#L663
(To be clear, I am a developer, but I have no experience whatsoever with Win32 dev outside of the .Net stack)
So why not override with the native oleaut32 (from winetricks)? Well, VPX just doesn’t start. And I’ve tried a ton of different library override combos. And the terminal output (even at trace level) is useless and/or undecipherable to me.
I also had the VPX source compiling in a VM and was looking at the IDL bindings and the required dependencies but nothing particularly helpful.
So I decided to scrap the Proton Wine (4.11) for the moment and create a new prefix with standard Wine (5.0-rc5). Ran installer, and used winetricks for wsh57, ole32, and oleaut32.. and it works! Well, there’s no sound device for some reason. And the performance is worse than under Proton. But no errors. DnD, my test table because it errors with LightState right when you start it, started and played fine. TOTAN too (no BlendDisableLighting error)
As for what to do now, not entirely sure.. fix sound and get dxvk working with standard Wine 5.0, or maybe see if an actual Proton release based on 5.0 is forthcoming. Again, I’ll update if I figure anything out new, but think I need a break for a little bit.
You need to login in order to like this post: click here
