-
-
Notifications
You must be signed in to change notification settings - Fork 80
HunterPie with Mod Organizer 2 #160
Description
Mod Organizer 2 released support for MHW a little over a month ago, and someone asked on the guide I wrote how to get HunterPie working with Mod Organizer 2. I did a quick test launching HunterPie first then running MHW through MO2 and was able to get some functions to work such as this overlay here. But due to how MO2 virtualizes the nativePC folder with usvfs, HunterPie kept warning me that Stacker's Loader and the CRC Bypass were needed for some functions of HunterPie Native (they were installed in MO2). This is because by default, the virtual file system created with MO2 is not visible to other applications.
I'd like to do some testing with MO2 to see if I can make those HunterPie Native functions work properly. That said, I'm not too familiar with HunterPie so I'm not sure what those functions actually are. So I have a couple questions:
- What would be a good way to test that the HunterPie Native functionality is working as intended? If there's a feature such as an overlay that I could try and load at the main menu or in game, I could use that to see if HunterPIe is actually able to use the virtual nativePC folder.
- Mod Organizer 2 allows the user to manually specify libraries to load when the game is launched. I believe these libraries would then be able to see the virtual nativePC folder created by MO2. Which library (or libraries) would be responsible for the detection of the nativePC folder and utilizing it?
If it helps to know what's working and what isn't, here's a log from starting the game in a "friends" session and walking around for 30 seconds in Astera with no libraries injected. Note that in game I received a message saying HunterPie Native was loaded, but the GUI of HunterPie.exe warned me that Stacker's Loader and the CRC Bypass were needed for some functionality and was pointing me to download them..
NoLibraries.log
Here's a log doing the same thing but with injecting "HunterPie.Core.dll, HunterPie.Native.dll, and HunterPie.UI.dll". Same messages appeared in game and in HunterPIe.exe. In both tests it looks like like HunterPie was able to connect with HunterPie.Native.dll
UINativeCoreInjected.log