poltmoto.blogg.se

Upon adding the Steamworks API and setting up the default "Generic Gamepad" Steam Input on my app page, the only way I can use a gamepad anymore is through the Steam build, or if I build an exe and don't have the steam_appid.txt file in my build folder. I'm having the opposite problem of people above. But once I stop and start the game again in Unity, it stops working again. The only other thing I've noticed is if I completely close Unity and kill the Steam process (Since my game never properly stops, even after closing Unity), then open both of them, then I can use my gamepad once. Kind of a ridiculous workaround, considering how allegedly 'easy' it is to fix for some people. Looks like I can regain gamepad control in Unity Editor if I just close Steam while I'm working. Fallback handler could not load library /Users/***/Contents/Frameworks/MonoEmbedRuntime/osx/InControlNativeįallback handler could not load library /Users/***/Contents/Frameworks/MonoEmbedRuntime/osx/libInControlNative.dylibįallback handler could not load library /Users/***/Contents/Frameworks/MonoEmbedRuntime/osx/libInControlNative.soįallback handler could not load library /Users/***/Contents/Frameworks/MonoEmbedRuntime/osx/libInControlNative.bundleįallback handler could not load library /Users/***/Contents/Frameworks/MonoEmbedRuntime/osx/libInControlNative