search

ShikyoKira / Project-New-Reign---Nemesis-Main

Animation Behavior Patching Tool
GNU General Public License v3.0
465 stars 183 forks source link

Nemesis refuses to open. #211

Open Zyaph opened 4 years ago

Zyaph commented 4 years ago

So I was finally convinced to swap from FNIS to Nemesis a few days ago, but for some reason the program refuses to launch. I've tried running via MO2 application dropdown, directly from the mod folder itself, and installing it to the normal Skyrim SE folder, to no avail. After opening the program, I get a CMD prompt pop up for half a second and then it disappears, and nothing else happens. Nemesis DOES show on my task manager as a background process. https://puu.sh/FxHFQ/7f0f34d771.png

Steps taken to try and resolve the issue:

  1. Double checked that FNIS was completely uninstalled via MO2 and all files deleted on PC.
  2. Double checked that I am using the correct Nemesis version (SSE)
  3. Reinstalled Nemesis multiple times, and trying out old versions of Nemesis.
  4. Updated and reinstalled MO2, and updated Windows.
  5. Restarted MO2 and PC multiple times
  6. Let Nemesis "run" for a few hours to see if it's just shy
  7. Added Nemesis to exception list in Windows Firewall as well as Kaspersky
  8. Tried launching with non-essential programs turned off

And... nothing. My cursor gets the loading wheel for 2-3 seconds every time, i see the CMD screen for a second, and then nothing happens.

I'm at an absolute loss about what to do from here. I see other people with the same problem on Youtube, Reddit, Nexus forums, but I never see a solution that works for me. I have also seen this previous thread but the solution here does not apply/work for me: https://github.com/ShikyoKira/Project-New-Reign---Nemesis-Main/issues/84

If anyone has any idea please let me know!

ShikyoKira commented 4 years ago

make sure u have the c++ redistributable 2019

Zyaph commented 4 years ago

make sure u have the c++ redistributable 2019

I believe I did, but I reinstalled it just in case, and no change :(

ShikyoKira commented 4 years ago

can you run it outside of MO2?

Zyaph commented 4 years ago

can you run it outside of MO2?

Unfortunately not, that's what's making this so confusing. I just tried again outside of MO2 and it just hangs in the background processes like in my original screenshot link.

ShikyoKira commented 4 years ago

can you try it in another machine?

Voeille commented 4 years ago

I had a similar issue, and I found out I couldn’t run any programs that relied on Qt5, and I think it started happening after one of the windows updates. I tried reinstalling C++ redistributable, rebooting, nothing helped. And recently, after another windows update, all Qt5 programs magically started working again, without even me rebooting yet to finish the update. I suppose something must’ve gone wrong with the previous update and it broke some stuff needed for Qt5 to run on windows.

Zyaph commented 4 years ago

can you try it in another machine?

Sorry it's taken so long to reply, been pretty busy with work with everything going on. Unfortunately I don't have another PC on hand to test it, but I had a friend test it for me using the same installation steps and it ran fine for them. I have also found out something that may be related which I will mention below...

I had a similar issue, and I found out I couldn’t run any programs that relied on Qt5, and I think it started happening after one of the windows updates. I tried reinstalling C++ redistributable, rebooting, nothing helped. And recently, after another windows update, all Qt5 programs magically started working again, without even me rebooting yet to finish the update. I suppose something must’ve gone wrong with the previous update and it broke some stuff needed for Qt5 to run on windows.

That is extremely helpful to know. I actually JUST found out that the Origin client (EA game client), which now uses Qt5, is having the EXACT same issue for me, and what seems to be many many other people. So, going on assumptions, the only thing I can think of to try next is to do a rollback to when Qt5 programs worked (and I have no idea when it broke), or to do a reinstall of Windows.

I'll do some research to see if there are other solutions, but if anyone can think of anything let me know. I'm sure it would be a big help to others who cant run Nemesis and have no clue as to why.

Voeille commented 4 years ago

That is extremely helpful to know. I actually JUST found out that the Origin client (EA game client), which now uses Qt5, is having the EXACT same issue for me, and what seems to be many many other people. So, going on assumptions, the only thing I can think of to try next is to do a rollback to when Qt5 programs worked (and I have no idea when it broke), or to do a reinstall of Windows.

I wanted to do a rollback but it was too long since the last update and me noticing the Qt5 issue, and I didn't really fancy a reinstall, so I decided to wait for another update to make sure it really is related, and it was. I'd recommend the same for you. The update that stopped the issue for me is KB4549951; hopefully it won't break again when I reboot.

Zyaph commented 4 years ago

I wanted to do a rollback but it was too long since the last update and me noticing the Qt5 issue, and I didn't really fancy a reinstall, so I decided to wait for another update to make sure it really is related, and it was. I'd recommend the same for you. The update that stopped the issue for me is KB4549951; hopefully it won't break again when I reboot.

Just checked and I'm still on KB4537572. Thanks for the head's up, I'll put off reinstalling Windows until I get to that update at the very least, while searching for more options. I swear I'm always the last person to get updates available haha.

ShikyoKira commented 4 years ago

@Voeille this is really a big finding. I'll put this in the FAQ since I'm sure as more people use Nemesis, we will receive more similar reports.

@Zyaph be sure to come back and close this issue if the update indeed fixes your problem ;)

Jumu3668 commented 4 years ago

I found an alternative solution for myself that seemed to work. You need to make sure that you have ONLY the binary filled in in MO2 Executables for Nemesis that points to the exe. I accidentally put in the path to my skyrim data folder in my "Start In" argument which caused it to not open when launched.

cuzfinal commented 4 years ago

I have another way. new a folder named Nemesis_Engine in Skyrim Special Edition/Data, then fill 'Start In' width _D:\Steam\steamapps\common\Skyrim Special Edition\Data\NemesisEngine, it works for me.

Voeille commented 4 years ago

It's me again, possibly with another discovery. The problem returned to me (with all Qt5-dependent programs), and it seemed to follow a consistent pattern — it breaks after a reboot, fixes itself when another windows update installs, and then breaks again after the next reboot. As I mentioned before, reinstalling vcredist didn't help, and yet I thought it must be the source of the problem as nothing else seemed to be related. I looked up where the vcredist DLLs are installed, and I found 3 files in C:\Windows\SysWOW64: vcruntime140.dll, vcruntime140_clr0400.dll, vcruntime140d.dll. I decided I might as well make a backup and try to delete them and see what happens (you need to fiddle with permissions to be able to change anything in that folder). It let me delete two of them (the remaining one, vcruntime140.dll, was in use). I tried to run the program, and it was perfectly fine! Then I put them back into SysWOW64, tried to run a few Qt5 apps again, and... it was still fine. It doesn't make any sense to me, but it seems like any change there fixes the issue. Or perhaps it was related to folder permissions, and changing that helped? I have no idea, but at least I found something that works, and I'm not limited to use Nemesis and other Qt5 programs only when my windows updates, which was quite annoying.

joyjoy244 commented 4 years ago

v0.84-beta in SSE, I got stuck with the ''qt5 error message'', I installed nemesis in the game folder and mod organizer and it works, i forget to install the zip in MO so thats why nemesis dont want to start i think; I have 27k annimations the progress bar is red asf but my last save is working normally.

MKDhiyanesh commented 3 years ago

Try pasting MSVCP140.dll and VCRUNTIME140.dll in Nemisis_Engine folder. It solved the problem for me.

DokuseiSan commented 3 years ago

.net script framework also needs to be installed: https://dotnet.microsoft.com/download

If you already installed it, do repair and reboot your pc and try to launch nemesis again

scarecrow42300 commented 3 years ago

My Nemesis client also refuses to open in MO2 and in the directory after I have resetted my OS, (my newly purchased PC was experiencing deadlocks so I had to reset my OS) my first problem was the usual vcruntime140.dll and msvcp140.dll but after putting them to my SysWOW64 and System32 folder the Nemesis client then proceeded to give me an error

"The application was unable to start correctly (0xc000007b). Click OK to close the application."

I tried reinstalling Nemesis, Reinstalling VCredist, Fiddling around the SysWOW64 and System32 folder, and I also tried putting the dll files into the Nemesis_Engine folder as per the suggestion of MKDhiyanesh. I also tried DokuseiSan's suggestion it also didn't work. I also tried updating my Windows 10 but alas it still won't launch

Mind you before the OS Reset Nemesis was working just fine, then after the OS Reset it just wont launch.

Hope you guys can find a solution, thanks. Capture

scarecrow42300 commented 3 years ago

I have fixed my problem now

It seems that some of the dll files were misplaced

download both the 32 bit and 64 bit version of msvcp140 and vcruntime140

now put the 32 bit dlls on SysWOW64 and put the 64 bit dlls on System32.

thedeanius commented 3 years ago

I have fixed my problem now

It seems that some of the dll files were misplaced

download both the 32 bit and 64 bit version of msvcp140 and vcruntime140

now put the 32 bit dlls on SysWOW64 and put the 64 bit dlls on System32.

This was it- sortof... the key is you have to install the 32bit version of vc++ redistributable as well as the 64bit. I didnt need to move any dlls after installing the 32bit version tho. it just worked

Aceymac commented 3 years ago

so my solution to this problem was having both the 64 and the 86 vc++ installed and it just opened again and ive been trying to get it working for 2 days now. Just letting people know try to install different versions of c++ just to test if it fixes it

barjumper commented 2 years ago

hello all, spent half a day today trying to get nemesis up and running. Downloaded Nemesis file from https://www.nexusmods.com/skyrimspecialedition/mods/60033?tab=description. Additionally I downloaded the mod Nemesis PCAE from https://www.nexusmods.com/skyrimspecialedition/mods/31667?tab=files.

Installed Microsoft Visuals x84 (as described on the nexus page for Nemesis).

Saved the Nemesis folder in the MO2 folder under mods. The folder Nemesis_Engine must be moved to the main data game directory. I have the engine folder under Skyrim Special Edition < Data < Tools (where Fins should be). I hope this helps one or the other, good luck

Translated with www.DeepL.com/Translator (free version)

barjumper commented 2 years ago

next i had the problem that nemesis error 2006 showed up during updating. As a solution I can say the mod Nemesis activate in Mo2 as it was downloaded. ORDER SHOULD LOOK LIKE THIS ( SCRIPTS; MESHES; NEMESIS_ENGINE) copy the scripts into the folder SteamLibrary\steamapps\common\Skyrim Special Edition\Data\tools\Nemesis_Engine.

copy the meshes into the folder SteamLibrary\steamapps\common\Skyrim Special Edition\Data\tools\Nemesis_Engine\cached_behaviors.

All hxk files need their Nemesis_...xml counter part in the same folder in which they are located. Here the files from the mesh folder must be distributed so that it is completely empty afterwards.

Translated with www.DeepL.com/Translator (free version)

barjumper commented 2 years ago

next nemesis gave me error 6002 i solved it trough downloading windows net framework 3.5 and by turning of my anti virus complet