search

ModOrganizer2 / modorganizer

Mod manager for various PC games. Discord Server: https://discord.gg/ewUVAqyrQX if you would like to be more involved
http://www.nexusmods.com/skyrimspecialedition/mods/6194
GNU General Public License v3.0
2.16k stars 160 forks source link

directory_iterator Issue when trying to open Nemesis (Skyrim SE) with MO2 #1569

Open kennedyxp opened 3 years ago

kennedyxp commented 3 years ago

I am trying to install Nemesis on Skyrim Special Edition, but after installed correctly and added his executable in Mod Organizer 2, as the image shows: https://i.imgur.com/9SqDPeS.png

I am getting this error: https://i.imgur.com/nXMegvD.png

I have tried uninstalling and installing MO2 several times, i already ran the program with administrator privileges, watched tutorials on how to install Nemesis, and even added Mod Organizer 2 folder to my anti-virus exclusion list, but the problem persists.

Sorry the bad english.

LostDragonist commented 3 years ago

image

Guess it has something to do with Mactype. That program does some bad stuff that messes with MO.

kennedyxp commented 3 years ago

image

Guess it has something to do with Mactype. That program does some bad stuff that messes with MO.

I disabled MacType for Mod Organizer 2 and the problem unfortunately persists...

Edit: What intrigues me the most is that Nemesis opens and works perfectly in Mod Organizer 1 that I use for Skyrim Legendary Edition, but in MO2 for Skyrim Special Edition it does not.

Edit 2: I apparently fixed it by adding not only "ModOrganizer.exe" on MacType.ini exclusion list, but "skse64_loader.exe", "Explorer++.exe" and "Nemesis Unlimited Behavior Engine.exe" too. Now Nemesis opens and works without any problem. For those who don't know, in MacType folder located in Program Files, there are a MacType.ini file that you can include .exes that are known to have problems running with MacType. Sorry for the issue report, but at least, that should help users who have MacType installed.

Edit 3: It is recommendable to add "hkxcmd.exe" to MacType exclude list too, or even disable MacType temporarily until you finished using Nemesis to Update Engine and Generate Behavior Files.

Flying--Dutchman commented 2 years ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine...

Crosspost to the issue at nemesis: https://github.com/ShikyoKira/Project-New-Reign---Nemesis-Main/issues/642

Spartan322 commented 2 years ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine...

Crosspost to the issue at nemesis: ShikyoKira/Project-New-Reign---Nemesis-Main#642

Posting here to help Linux folks who see this issue since Nemesis is archived and these two issues are what pops up when searching on this problem:

To correct this issue you can symlink Nemesis_Engine in the <MO2 Path>/Skyrim Special Edition/mods/Project New Reign - Nemesis Unlimited Behavior Engine to your <Steam Path>/steamapps/Skyrim Special Edition/Data (so it becomes <Steam Path>/steamapps/Skyrim Special Edition/Data/Nemesis_Engine) path and run the executable from the MO2 mods path in MO2, it may popup lacking configuration (which the Nemesis window might be on top of, just move the window out of the way if that happens) but otherwise it seems everything works fine.

TheguynamedT commented 2 years ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine... Crosspost to the issue at nemesis: ShikyoKira/Project-New-Reign---Nemesis-Main#642

Posting here to help Linux folks who see this issue since Nemesis is archived and these two issues are what pops up when searching on this problem:

To correct this issue you can symlink Nemesis_Engine in the <MO2 Path>/Skyrim Special Edition/mods/Project New Reign - Nemesis Unlimited Behavior Engine to your <Steam Path>/steamapps/Skyrim Special Edition/Data (so it becomes <Steam Path>/steamapps/Skyrim Special Edition/Data/Nemesis_Engine) path and run the executable from the MO2 mods path in MO2, it may popup lacking configuration (which the Nemesis window might be on top of, just move the window out of the way if that happens) but otherwise it seems everything works fine.

I made a github account just to say this; Thanks, you legend

v1ld commented 2 years ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine... Crosspost to the issue at nemesis: ShikyoKira/Project-New-Reign---Nemesis-Main#642

Posting here to help Linux folks who see this issue since Nemesis is archived and these two issues are what pops up when searching on this problem:

To correct this issue you can symlink Nemesis_Engine in the <MO2 Path>/Skyrim Special Edition/mods/Project New Reign - Nemesis Unlimited Behavior Engine to your <Steam Path>/steamapps/Skyrim Special Edition/Data (so it becomes <Steam Path>/steamapps/Skyrim Special Edition/Data/Nemesis_Engine) path and run the executable from the MO2 mods path in MO2, it may popup lacking configuration (which the Nemesis window might be on top of, just move the window out of the way if that happens) but otherwise it seems everything works fine.

Thanks, @Spartan322, you utter legend!

This symlink workaround lets Nemesis run from MO2 on the Steam Deck too, for future Google visitors.

guchierrez commented 1 year ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine... Crosspost to the issue at nemesis: ShikyoKira/Project-New-Reign---Nemesis-Main#642

Posting here to help Linux folks who see this issue since Nemesis is archived and these two issues are what pops up when searching on this problem:

To correct this issue you can symlink Nemesis_Engine in the <MO2 Path>/Skyrim Special Edition/mods/Project New Reign - Nemesis Unlimited Behavior Engine to your <Steam Path>/steamapps/Skyrim Special Edition/Data (so it becomes <Steam Path>/steamapps/Skyrim Special Edition/Data/Nemesis_Engine) path and run the executable from the MO2 mods path in MO2, it may popup lacking configuration (which the Nemesis window might be on top of, just move the window out of the way if that happens) but otherwise it seems everything works fine.

This did it for me, but the game crashes when I click update engine...

Sparklingsliver commented 1 year ago

Facing the same issue with on Linux with wine. Only Title and Binary are set. Latest MO2 version. Cannot give a logfile, since thats not working on wine... Crosspost to the issue at nemesis: ShikyoKira/Project-New-Reign---Nemesis-Main#642

Posting here to help Linux folks who see this issue since Nemesis is archived and these two issues are what pops up when searching on this problem:

To correct this issue you can symlink Nemesis_Engine in the <MO2 Path>/Skyrim Special Edition/mods/Project New Reign - Nemesis Unlimited Behavior Engine to your <Steam Path>/steamapps/Skyrim Special Edition/Data (so it becomes <Steam Path>/steamapps/Skyrim Special Edition/Data/Nemesis_Engine) path and run the executable from the MO2 mods path in MO2, it may popup lacking configuration (which the Nemesis window might be on top of, just move the window out of the way if that happens) but otherwise it seems everything works fine.

I am new to Linux and I tried to symlink in konsole but it said no such file or directory. I am not sure what exact folder/path I need to use? Can you explain it to me? I just used the command ln -s 'mo2 path' 'data path'

jwrichards1982 commented 1 year ago

symlink worked once. Subsequent uses, breaks. Not the same error, but MO2 doesn't build the VFS. It starts to when I close MO2, it keeps building and the Nemesis window opens, then when trying to rebuild the animations, Nemesis stops responding, eventually closed by OOM reaper

spacecowboyx commented 9 months ago

Does this work with BodySlide? I find that running BodySlide from mo2 added as a non steam game works but running mo2 from Skyrim itself with rockerbacons fork it doesn't work or detect the files.

MartinF99 commented 3 months ago

Another workaround is creating a "Nemesis_Engine" folder in your SkyrimSE data directory

DmPekhterev commented 1 month ago

Другим решением является создание папки «Nemesis_Engine» в каталоге данных SkyrimSE.

Buddy! I kiss your navel! Creating this folder helped launch Nemesis in the "mac-os-crossover-mod organizer". Best!

shenawy29 commented 1 month ago

Bit of a necro, but if anyone comes across this and is using Lutris like I am, I managed to fix it by installing Nemesis manually, changing the Wine Runner of Mod Organizer 2 to wine-ge-8-26-x86-64 (default), and also disabling DXVK. Then I can run Nemesis from MO2 as usual, with the Start In command set.