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.07k stars 155 forks source link

Problem with GenerateFNISforUsers.exe #525

Open zelurker opened 5 years ago

zelurker commented 5 years ago

The problem

GenerateFNISforUsers seems to be lost in the virtual filesystem : when launching from its default directory, inside the mods directory of modorganizer 2, it outputs error 76 can't find some part of the path ...temporary_logs, the ... being the whole skyrim directory, if fnis directory was mapped correctly for this exe, it would work. The error 76 is from fnis of course. I tried to move the tools directory of fnis directly inside skyrim data directory : same error I tried to move totally outside all of this, e:\games\tools, then it starts, but it doesn't seem to detect any mod, and it produces its output files to the root of e:\ instead of the override directory, it produces an error if the e:\scripts directory does not exist.

The weird part is that loot which I launch also from mo works fine. Actually it worked the 1st time I moved the fnis directory to e:\, then I tried to relaunch it a little later and the error was back, but this time nothing fixes it... ! Launching skyrim or loot or tes5edit seems to work without problem though ! It's a fresh reinstallation of skyrim on a new system, and I decided to try MO2 instead of MO1 this time...

Environment

fnis latest version, 7.4.5. Latest mo version, 2.1.5, windows 10, 64 bits version. Installed in its default directory c:\Program files\Modorganizer I tried to copy its installation to e:\games with exactly the same result. I tried to reinstall the redist packages at the bottom of your page on the nexus, for info the option to repair the installation is gone, it just says that the package is already installed, and bye bye.

Link to Mod Organizer logs

USVFS

Didn't notice anything useful in the log, I tried a debug log but it doesn't seem more useful. Here is the normal, shorter one : https://gist.github.com/zelurker/057878871cedcf77089d6798486089d9#file-usvfs-2018-09-17_07-21-52-log

MO Interface

The relevant part in the log :+1: 09:57:03 [D] Spawning direct process < "E:/Games/GenerateFNIS_for_Users/GenerateFNISforUsers.exe" , "" , "E:/Games/GenerateFNIS_for_Users" > 09:57:03 [D] Waiting for spawned process completion : GenerateFNISforUsers.exe (3628) 09:57:29 [D] Waiting for process completion successfull (it's not the same time as the previous log because the last one was the debug one, but it still has the same issue).

zelurker commented 5 years ago

Found a brutal workaround : install mo1, copy the mods, profiles and downloads directories from mo2 to mo1 (I wanted to create symlinks using mingw because it worked on win7, but no way to do that with my current win10, anyway...). With mo1, I moved again the GenerateFNISforUsers directory back to its original position, inside the mods directory of mo1 this time, and it worked like a charm !

Problem solved, but with mo1, not mo2. If you have some ideas, I'll probably keep the mo2 install around for some time... !

LostDragonist commented 5 years ago

FNIS expects to be installed in the game directory. E:/Games/GenerateFNIS_for_Users/GenerateFNISforUsers.exe is not a valid installation.

You need to install FNIS with MO2 like a mod. Activate that mod. Then go to the data tab in MO2, find the executable, right-click it and add as executable it will now be in your executable list and you can run it.

zelurker commented 5 years ago

Thanks for the reply, but as I said in the quite long description, this was my 1st reflex, I know it's supposed to be installed this way, this is how I always used it. And as I said, if I do that with mo2, and I just redid that to be sure by using the data tab whuich I never used before this time, I get : ERROR(76): Impossible de trouver une partie du chemin d'accès 'E:\Games\The Elder Scrolls V - Skyrim - Legendary Edition\data\tools\GenerateFNIS_for_Users\temporary_logs'. sorry for tehe french part in the message, but it's pretty obvious anyway, some part of the path is missing, I get that as soon as I click on "update fnis behavior"

As I said again, only reliable fix for now : switch to mo1, which works wonderfully well in the same situation... !

2018-09-17 17:00 GMT+02:00 LostDragonist notifications@github.com:

FNIS expects to be installed in the game directory. E:/Games/GenerateFNIS_for_Users/GenerateFNISforUsers.exe is not a valid installation.

You need to install FNIS with MO2 like a mod. Activate that mod. Then go to the data tab in MO2, find the executable, right-click it and add as executable it will now be in your executable list and you can run it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ModOrganizer2/modorganizer/issues/525#issuecomment-422049931, or mute the thread https://github.com/notifications/unsubscribe-auth/ACu5D37N5DT7GVznN064JklfMFLrgru7ks5ub7jwgaJpZM4WrfNa .

LostDragonist commented 5 years ago

There are plenty of people able to use FNIS correctly with MO2. If you want help correcting the issue on your setup, you'll need to post some better logs.

  1. Change the MO2 log level to debug.
  2. Restart MO2.
  3. Try to open FNIS.
  4. Close MO2.
  5. Grab your new mo_interface and usvfs log and post them.
Al12rs commented 5 years ago

You need to delete the fnis temporary logs before you run fnis again. Like if you are using the fnis redirection option for Mo2 and Vortex (which you should be using only if you actually need it ), you should first make sure you are not using one any target location that is being vietualized, so if you target a mod Forder that mod folder needs to be deactivated when running fnis. Absolutely do not use overwrite as target. (Remember that the target location gets wiped when finished runs). If you use that option after you run fnis the overwrite folder will contain only temporary logs that you then can delete.

Al12rs commented 5 years ago

Sorry did not see the answer from LostDragonist, follow his instructions after making sure you are not doing some of the things I warned about.

zelurker commented 5 years ago

Here you go, debug log : https://gist.github.com/zelurker/322da9737261bf73788ec350ff32c2cc#file-usvfs-2018-09-17_18-46-02-log Interface log : https://gist.github.com/zelurker/7e479b7584961434415e331054cce351#file-mo_interface-log

2018-09-17 20:35 GMT+02:00 LostDragonist notifications@github.com:

There are plenty of people able to use FNIS correctly with MO2. If you want help correcting the issue on your setup, you'll need to post some better logs.

  1. Change the MO2 log level to debug.
  2. Restart MO2.
  3. Try to open FNIS.
  4. Close MO2.
  5. Grab your new mo_interface and usvfs log and post them.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ModOrganizer2/modorganizer/issues/525#issuecomment-422123632, or mute the thread https://github.com/notifications/unsubscribe-auth/ACu5D3Vi_JWtCMPlXcRJuFk3hVbNKgVQks5ub-uLgaJpZM4WrfNa .

zelurker commented 5 years ago

Ok, sorry for the delay to answer, I used mo1 for a long while, anyway... Just unchecking the output of fnis (the mod created from its overwrite directory) fixes the problem somehow. This way you loose the saved settings (which options were checked in fnis), so you have to check them again, it's not super convenient, but there might be a way to move just the settings back to the fnis directory to keep them. Anyway, it works... ! (it works out of the box in mo1, nothing to do, anyway...)

AnyOldName3 commented 5 years ago

That's weird (unless you're running FNIS with the redirect output command line option, in which case it's safer to run it when the output directory isn't visible to the VFS).

Either way, there should be a MO plugin integrating FNIS more effectively into the next MO release, so that should ensure no one encounters this kind of issue again.

Taiel-Kadar commented 4 years ago

\my games\R.G. Mechanics\Skyrim - Legendary Edition\data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe Skyrim 32bit: ??.??.?? - Z:\home\taiel\Documents\my games\R.G. Mechanics\Skyrim - Legendary Edition\

Skeleton(hkx) female: Default (99 bones) male: Default (99 bones) Patch: "SKELETON Arm Fix"

Reading FNISBase V7.6 ...

All Anim Lists scanned. Generating Behavior Files....

ERROR(2012): Could not generate: defaultfemale.hkx defaultmale.hkx 0_master.hkx

i have been trying everything, i cant make it work, help pls, im in ubuntu 20.

Al12rs commented 4 years ago

im in ubuntu 20.