(04-03-2019, 09:14 AM)twotonkatrucks Wrote: [ -> ]What do you mean by crashes? It won't load games at all? If that's the case, you may have a different problem. The games run fine, it's just that Dolphin hogs up memory when I do (eventually, you may run out of memory and "crash" the program).
.framework files are different from .dylib. What you want to replace libvulkan.dylib with (and rename) is libMoltenVK.dylib, which is included with the Vulkan SDK.
EDIT: also, the latest Dolphin come with v 1.1.101.0. You want to replace it with an older Vulkan distro, namely v 1.1.92.1.
ok, thanks... re: the first issue, yes, it crashes for me, doesn't even run. Once a game is loaded, a crash window appears with buttons for ignore, restart, etc... I'll delete all traces of Dolphin and start from scratch and see what happens. Thanks.
Ok, it works. I used vulkansdk-macos-1.1.92.1. However, if I try to add enhancements, like 2x native resolution and 2x anti-aliasing, a bunch of msgs appear:
failed to compile EFB readback pipelines
failed to initialize renderer classes
Fifo shutting down while active
Failed to initialize video backend
If I set the settings to default, it all works so far. Thanks.
EDIT: Trying to setup a wired DS4 controller is ridiculous. It literally takes like 10 seconds to register a button press when I try to assign it in the settings.
(04-05-2019, 12:23 PM)pleasejust Wrote: [ -> ]EDIT: Trying to setup a wired DS4 controller is ridiculous. It literally takes like 10 seconds to register a button press when I try to assign it in the settings.
Actually, I'm getting the dreaded "beach ball" now. It crashes Dolphin when I try to assign it via detecting button press on DS4 (I'm trying this wirelessly). I have to "manually assign it by right clicking and choosing from the list. Maybe this is another bug?
Okay so I figured out that the DS4 controller configureation DOES work for me. But, as pleasejust says, I have to hold down what4ever button for a while before it registers. otherwise I just get the spinning beach ball forever.
Is this behavior by design? Seems a bit weird and unnecessarily cumbersome.