GSDFan

I managed to put together a inventory_menu.xml file to get Darnui and wmm to work together, no more message that the files aren't correct or old. also been looking into oHUD eHUD solution, but nothing to report.

I am playing with UIO now and I can say I am impressed. You still need to use FOMM for Project Nevada, PN extra options and Flashlight NVSE and maybe a others. You have to install the PN and extra options as extra options needs to see PN to install cyberware and then make a mod out of it. FlashlightNVSE will not see MCM in Mo and needs to be installed with FOMM / Make mod method. MO can now install the rest without the errors we had in the past. DarnUi has to be at the bottom to work and there is a conflict between Darn and the Weapons mod menu inventory_menu.xml file, whick is giving me problems.

UIO looks promising. Project Nevada and PN extra option will need to need installed with FOMM. The extra options will not install the cyberware selection as it will not see PN proper.

I was doing some more testing and I think I found a solution for this problem. I had to add the the fallout folder path to the path environment string and it works without the -laaexe whatever. Edit: I tried to shorten the path to the common directory and I could not run the program, I got the error I have been getting. It has to have the full path to the Fallout folder.

I tried this for my self and it did not work for me.

I have seen this in a couple of posts and since I cannot reproduce it I never figured it out so the following may not work. In the arguments box you most likely have the following “-laaexe .FalloutnvMO.exeâ€. Try adding “-SteamAppId ID 22380†right after it. It should look like this “-laaexe .FalloutnvMO.exe -SteamAppId ID 22380†minus the quotes. Report back if it works. Thanks

This has been added to the wiki.

Are you getting this any other files or just this one? If it is just this one you can extract the archive and create a folder in the mods directory and put the ESP and BSA from SkyUI in there. You can extract above and use 7zip or winrar to repackage and try that. You can also delete the fomod folder and do a manual install from the MO downloads. I doubt the NCC downgrade will help and probably should not be done past the version it was meant to fix. If you do not have the most current version of MO install that and if you do, download the manual archive and overwrite your files. Something may have gone wrong with your current install.

As GrantSP said FOSE appears to be running and I came to the same conclusion when I looked at the log. A couple of things I noticed suggest that the left pane Non-Mo mods are in the wrong order. They should follow the Boss / LOOT ESP load order. You are also missing some lines that I have, which would suggest that you do not have the BSAs from the Anchorage, ThePitt, BrokenSteel. Pointlookput and Zeta checked in the Archives tab.

This week I had some time off from work and I thought I would look into some of the things that have been bugging me about Skyrim problems I have been experiencing lately. The issue I have is when I verify integrity of game cache or I delete Skyrim.ini and SkyrimPrefs.ini from My Games Skyrim, I would get a “Skyrim Launcher has stopped working†message when the game is first run from Steam. This would happen when the Video Detection dialog appears and OK is selected. This had been ongoing for some time and as I only run the launcher when I set up the game I let go and did not worry about it. When monitoring the My GamesSkyrim folder I saw that both files were created as this was happening, but none of the video information was set when I ran the launcher the next time, which ran perfectly fine the second time. I also noted that the Modified date time stamp was different for both files. Skyrim.ini had a date that was a couple of months behind the current date. My only thought here is the date did not get updated because the program was crashing and the video detection was not done and never applied to the ini file. I traced this down to the ENB I had installed. I removed the ENB, deleted both configuration files and the launcher is happy again. The new configuration files have the same date modified time stamp. I installed another ENB thinking somehow my first one was a bad install, but I got the same results. ENB being used is ENBSeries v0.264. Rolling back to an earlier version of ENB did not help. If anyone knows of a solution for the problem I would like to hear it or if others have this problem and it is not just me.

Try running without the ENB installed. If it runs then the ENB is the problem, it has happened to me.

It would appear you have a problem with the download with manager button in Firefox. In Firefox settings, applications tab scroll to nxm in the left pane. In the right pane under action select "Always Ask" and OK out of settings and restart Firefox. Go to a mod on the Nexus with a download with manager button and press it. Click continue with download. You should get a window that has a selection. There will be an entry to select an application, press the "Choose" button and navigate to where you have MO installed. Once there, select "ModOrganizer.exe" and OK out to finish. This will allow you to associate MO with the green download button. The next time you download a mod with the green download (nmm) button select Mod Organizer. Do not select "Remember my choice for nxm links" as this will allow you to select Nexus Mod Manager if you use it for other games that MO does not support. Google translation: Il semble que vous avez un problème avec le téléchargement avec le bouton de gestionnaire dans Firefox.Dans les paramètres de Firefox, les applications onglet défilement pour nXm dans le volet gauche. Dans le volet de droite sous l'action sélectionnez "Toujours demander" et OK sur les paramètres et redémarrer Firefox.Aller à un mod sur le Nexus avec un téléchargement avec bouton de gestionnaire et appuyez dessus. Cliquez poursuivre téléchargement. Vous devriez obtenir une fenêtre qui a une sélection. Il y aura une entrée pour sélectionner une application, appuyez sur le bouton "Choisir" et accédez à l'endroit où vous avez installé MO. Une fois là -bas, sélectionnez "ModOrganizer.exe" et OK sur à la fin.Cela vous permettra d'associer MO avec le bouton vert de téléchargement.La prochaine fois que vous téléchargez un mod avec le bouton download vert (NMM) sélectionner Mod Organizer.Ne pas sélectionner "Enregistrer mon choix pour les liens nxm" que ce qui vous permettra de sélectionner Nexus Mod Manager si vous l'utilisez pour d'autres jeux que MO ne fonctionne pas.

The binary line should point to javaw.exe.

Be careful when you say "Merge" when using MO. MO does not do the merge like TES5Edit. When updating installed mods it depends on how the mods update is packaged. You can install the patch into the main mod or its own mod. One thing to keep in mind if going the two mod route is MO may throw a PMOP error and want you to move the update before the main mod.

Merge is your friend when updating mods.

Which OBSE mod / plugin are you trying to install? As a side note the OBSE extender works differently in Oblivion than the other extenders in the other games. It cannot be launched directly from MO and will not activate when the game is launched from MO. As far as I know it will only activate when the game is launched from Steam. The fix is to go into MO settings, the wrench and screwdriver icon, and select the workaround tab. Under load Mechanism you need to change it to “Script Extender†and click OK out of the setup and shut down MO. This will create an OBSE plugins folder in the vanilla data folder with a couple of MO filed inside.This setting will make the MO virtual directory one big OBSE mod. From now on you have to mod in MO and launch the game from Steam to see the changes mods make. I hope this has shed some light on this for you.

Tannin has posted a new build 1.2.12 addresses the 202 error, but states: Reading the Nexus forum it looks like there are other issues that have been introduced. We may want to sit tight for a while.

Double click the BFF mod and a information window will appear. In it will be a lot of tabs across the top. Click on Optional ESPs and take a screen shot. Do the same for the conflicts and file tree tab.

A picture of the file tree tab would help.

take a look at these posts NMM updated to 0.52.2 causing MO errors - Mod Organizer Support - S.T.E.P. Download With Manager Error - Mod Organizer Support - S.T.E.P.

I downloaded the above mods without error. One thing I did recently was I changed my "Favourite download location" in my Nexus profile from generic USA to the server closest to my location, which is a premium server.

MY DVD is non-Steam version, I uninstalled FO3GOTY and shut shut down steam to avoid any conflicts. When MO started I had a choice to select the Regular or GOTY version. The game ran without Steam and accessed the DVD for authentication check. Launching FOSE from MO or the game directory did not start Steam. So setting the load Mechanism to script Extender and running fose_loader.exe did not work? What did it do? Sorry for being a pest about this, just trying to expand the knowledge base.

Hi again, I found my DVD based Fallout 3 and nuked my Steam version, installed FO3 and updated to version 1.7. FOSE will not run on the retail DVD version without the upgrade. Three reinstalls and upgrades later I had a working updated game. Sorry to say FOSE worked from MO. I we can’t run FOSE from MO then let’s try a workaround. In MO settings Workarounds tab and set the “Load Mechanism†from Mod Organizer to Script extender, click OK out of settings and restart MO. When MO closes this will create a folder fose plugins in the vanilla data directory with two files in the plugins folder. They are hook.dll and mo_path.txt. I mention these in case you change back to the original setting and they do not get cleaned up after a MO restart. This essentially treats your whole MO setup as a FOSE mod. In my testing I ran FOSE from MO and from the game directory, fose_loader.exe, and it saw the plugin I had installed, which was “DALCO FOSE Check†in each case. When I set local saves in the profile it also operated as expected. Try this and see if it works for you.

Doing it that way you are going in circles. Always run LOOT from MO before using WRYE. Don’t use WRYE for anything other than creating your bashed patch. Do make note of any mod ESPs that are orange and write them down when in WRYE. Exit WRYE and start TesEdit, right click on the mods and select none. In the top edit field enter the first ESP name that was orange and put a check in the box next to it in the lower list and click OK. When the finished message appears, right click on the last ESP and select sort masters. When that finishes close out to TesEdit, make sure that only the ESP you sorted is checked and OK all the way out. Also if you add, remove or otherwise change the load order of ESPs you may have to do this all over again. No need to erase anything unless you feel that a mod did not install properly. Just disable all of them and use the STEP guide from the beginning and move mods in the left pane in the order that STEP provides and activate as you go.

All mods are installed in a pool you can draw from, so they are available to all profiles when activated. You would need to install XP32 twice, one for male and one for female, deactivating the one not needed.