-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F4SE - some plugins breaking #32
Comments
You are using a custom Proton with Fallout 4, right? I'll do the necessary modifications for #33 so you can test if stock Proton is the problem. |
Custom Proton support was added in 2.5.0. You can update your current installation by removing it in Lutris without removing game files and installing the new version on top of the previous directory. Custom proton versions should be specified using the arguments setting in Lutris. In order to see all options available use the following command: $HOME/.local/share/modorganizer2/proton-launcher.sh --help |
Hotfix added in 2.5.1 |
Actually this was with stock proton - I will have to see if proton-GE fixes this, I'll try it with 2.5.1 - I was actually later on using modified versions of the run and download scripts because I personally wanted to remove the restart-pulse option and add the no-esync option (Fallout4 is known to work better if you disable esync) - but it would be beneficial to instead be able to set parameters in lutris anyway. |
I will add options to override the pulse restart and include no-esync as default for Fallout 4. |
Those options appear to also have been reverted in 2.6.2 - since they didn't get applied on my side ? Either way -by hacking the script locally and applying the search path fix patch myself, I was able to get it to run ProtonGE instead, but right now this doesn't work at all. Using ProtonGE ModOrganizer2 immediately crashes on startup, so I can't test if that fixes the plugin issue. Debug logs: DEBUG 2020-05-12 09:21:29,463 [application.launch:379]:Launching MO2FO4 (linux) (140251018754432)
Proton: Upgrading prefix from 5.0-1 to 5.8-GE-1-MF (/home/metalpoetza/.steam/steam/steamapps/compatdata/377160/) |
I checked the release and the master branch and everything is in order. It is likely a cache issue with Lutris once again. For some reason Lutris caches downloads using the file id in the installer instead of using the download URL. Because of that you always have to clean the cache when updating. You can selectively uncache the dependencies that changed running these commands from inside your cache directory: cd mod-organizer-2
rm -rf dialog find_library_for_appid gamesinfo nxm_broker nxm_mime_handler proton_launcher wine_launcher |
These logs show that GE suffers from the same problem Wine-staging does. Now to completely isolate the issue I need you to manually install the plugin and run FO4 directly from Steam. If it works I'll need you to do the following:
PROTON_DUMP_DEBUG_COMMANDS=1 steam
Then send me the logs from Lutris:
With these two I'll be able to point out all differences in how Steam starts the application and how my script is starting it. |
Okay, so for now, it's not possible to use GE builds with mo2, that's good to know anyway. Either way, turns out the same problem affects proton and proton-GE when run from within Steam. But it doesn't affect pure wine when using a windows version of steam inside wine (that's how I was using it with Vortex due to a different issue). So you can close the ticket on your side - it's a proton bug not a bug in your launcher. |
I would like to keep this open because more people may come across the same problem. Also, if some tweak is found that can fix this issue I would like to implement it. |
Not sure if it will help, but I found the plug-in source code here: https://github.com/reg2k/fo4-autoswitch Given other F4SE plug-ins work fine, I'm guessing something this one does is at least partly responsible for the issue. Maybe someone will recognize it. Edit: Also, for anyone wanting the functionality of this plug-in on Linux, I've come across AntiMircoX that allows you to use mouse, keyboard, and gamepad simultaneously by mapping gamepad inputs directly to mouse/keyboard inputs. You have to set up the mapping you want and then turn off the controller support in-game for it to work. There are some downsides, mainly that in-game prompts will use the keyboard button instead of the controller and you lose all the context sensitivity of the in-game controller support. |
Pretty late but there is another option around the auto switch mod, buffout 4 https://www.nexusmods.com/fallout4/mods/47359 |
Installing the auto gamepad switch plugin for F4SE causes it to hang on startuped, Fallout4.exe launches but immediately becomes defunct.
This plugin works fine with Vortex. This appears to be a memory issue introduced with the ModOrganizer support or, potentially, with stock Proton. Let me know if I can send any particular logs - but I looked at them and there are no errors, it just shows the DLL loading and then nothing more.
I can't say how many F4SE plugin mods are affected but I can confirm at least this one is: https://www.nexusmods.com/fallout4/mods/23136?tab=files
The text was updated successfully, but these errors were encountered: