-
Posts
4,289 -
Joined
-
Last visited
-
Days Won
27
Everything posted by GrantSP
-
That's truly bad news, sorry about that. On the bright side though now you have a reason to go SSD!
-
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
Excellent. I'll add backup software to the list of known culprits in this thread. -
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
That would be a fair assumption. -
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
Are you sure you don't have some AV package or firewall or any other software that has access rights to your system that was updated at the same time? Clearly since the MO code hasn't changed since you installed it, and it was working, there must be other software that is at play here. Sadly I'm at a loss as to what that might be as all the steps outlined so far would resolve this. -
Updating from version 1.1.18 for USLEEP
GrantSP replied to TboneTones's question in Mod Organizer Support
Okay I can replicate this with that mod so there is at least something odd with the way Nexus, MO or that page's settings that is messing with the UI in MO. Whenever the 'Meta.ini' is generated for this mod the line is missing that stores the endorsement state. Now to fix it is very easy. For every mod that is giving you this odd behaviour open the 'Meta.ini' and add this line to force MO to recognise it as endorsed: endorsed=1If you don't want to endorse it change it to: endorsed=0If you want to avoid endorsing change it to: endorsed=3Now the actual problem here is MO is by default viewing the "Endorsement state is unknown" value whenever this line is missing but unfortunately we can't change that via the UI. If you want to revert MO to see that condition you change this line to be: endorsed=2 -
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
Some process is interfering with MO. Since it used to work for you there must have been an update or driver change that has affected this process. Whilst I agree with you that changing a monitor shouldn't make such a drastic difference, we are talking about Windows, so who knows? Let's at least eliminate all our options on our end. Grab a new download from Nexus of MO and install it in a completely different location. Set it up as you would for which ever game, Skyrim, Fallout, whatever and check that it launches the default executables. Add in the SKSE and try with that. Repeat for the other tools. If it works for this new install we have established a working base to add the existing MO install onto it. -
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
Could check in your 'Settings' -- 'General' -- Log Level = Debug If it is set to anything else please change it to Debug and provide a new log. If it is already set at debug then something on your system is stopping MO from attaching the "hook" process and thus the error. -
Failed to spawn... Access is denied
GrantSP replied to RoboticPlayer's question in Mod Organizer Support
Post your logs here and let's see what is, or isn't being hooked. Best idea is to delete everything in the 'logs' folder first to remove anything not necessary for our examination. Read the STEP Citizenship Guidelines found at the link at the bottom right of every page to see how to use spoiler tags. -
Updating from version 1.1.18 for USLEEP
GrantSP replied to TboneTones's question in Mod Organizer Support
Could you please invoke the context menu on one of those mods that are not allowing you to endorse and select "Open in explorer". Open the 'Meta.ini' file with Notepad and paste the contents here inside spoiler tags. If you're not sure how to do that check the STEP Citizenship Guidelines link found at the bottom right of every page, that will also explain to you why you can't edit posts. Generally speaking ANY issue with Nexus, as called from MO is due to: a change in how Nexus handles things such as the cookies that store that information (not likely in this case)MO has a copy of incorrect data in its 'webcache' folder which can be fixed by deleting the contents of that folder (possibly the case in this instance)the user is not logged in as the same user that downloaded the file originally (not likely)the file is not from Nexus (?)the internet connection is flaky and commands are not being processed in time for a response (?) -
That looks much better to me. Well done.
-
I think the red is too jarring a colour, it clashes with the more subtle greens of the rest of the UI. A vibrant yellow would still serve as a highlight but not be overly distracting. IMHO.
-
Do I have to have vanilla Skyrim to get started?
GrantSP replied to Tharmagon's question in General Skyrim LE Support
Because of the advanced feature set MO uses, it is recommended to use it on a "clean, vanilla" installation, ie. no mods installed directly into the game's data folder. -
This doesn't appear to be a specific MO issue, rather something peculiar to your machine. There is nothing different about the way MO populates the UI with selection boxes, the same code is used for all mods installed so if it works for one mod it will work for all. I have just installed the mod you specified and it works as you would expect. I would suggest looking for anything that may be interfering with your mouse driver, perhaps some form of graphic overlay or another process that is intercepting certain mouse clicks.
-
Updating from version 1.1.18 for USLEEP
GrantSP replied to TboneTones's question in Mod Organizer Support
Check the FAQ, about 15 questions down the list. -
Updating from version 1.1.18 for USLEEP
GrantSP replied to TboneTones's question in Mod Organizer Support
Yes, remove the old install once you have moved everything across. Why? When you download files from Nexus the 'nxm' handler from the previous install will probably install them into the old location. To be sure, once you have the new one installed click the globe icon to initiate a Nexus page, this should force the new MO to be used for all future downloads. Running "NXMHandler.exe" from within the MO folder will also do this. MO will automatically use the folders if you move everything into the defaults, but it never hurts to check. ;) -
Updating from version 1.1.18 for USLEEP
GrantSP replied to TboneTones's question in Mod Organizer Support
MO does not need to be installed anywhere specific to work, it is preferable to install it away from any UAC folders such as "Program Files" or "Program Files (x86)". Make a folder anywhere and install MO.Copy over the 'downloads', 'mods' & 'profile' folders from your external driveVerify that the settings are pointing to those foldersPlay -
That notice in the MO guide is incorrect and has been edited. There is no proper way to install the "full" LOOT by simply adding a single file to MO's LOOT folder. The 'Sort' function uses exactly the same code as LOOT does, at the time of release for MO, and it only lacks some features such as the 'report window' and the ability to edit metadata. The actual sorting function is identical. STEP recommends installing the full LOOT package to be used via MO because those features are vital to setting up correct load orders with the extensive list of mods used in our guides.
-
I'm going to go out on limb here and say you are completely fine with using those images. Both are already using logos/iconography from the game so any cause for complaint will come from the developers, not those artists. However the use of artwork from the game has always been an acceptable use of those assets when used for game related work.
-
That last edition looks... fantastic. The previous ones were just too bright and green for me, maybe the addition of the 101 did it? What artwork are you referring to? If it is the 101 and the radioactive logos surely they are free to use by anyone? I will definitely use this on my Fallout installs.
-
FWE Alternative start, don't start.
GrantSP replied to varrgas's topic in Fallout 3 - Clear & Present Danger
It's a little vague as to what is actually wrong here, sorry. From what I glean from this is you are not being presented with the alternate start option, is that correct? If so the answer is not in the script within FWE. Simply put if there was an error in that script it would have been found many years ago as that mod is quite old and used in many installations. You will need to recheck that you have followed through with the installation of each mod in it's correct spot as outlined in the guide. Then check any patches that you have created. -
Okay just tried with your selections and it installs fine. Checked through your post about the missing texture and that specific one is installing fine with my copy so all I can think of is yours is broken or something else is interfering with the extraction process. It looks like you have Steam and MO installed away from UAC folders so that's good. If you have any AV or firewall software try adding MO to their exclusion lists or disable them temporarily to see if it succeeds this time. Aside from that I'm out of ideas. If the bulk of the install succeeds you may be able to add in the missing textures using explorer or some other file manager. The download is just a RAR file with a fomod folder inside, the files are pretty easy to find.
-
Can you give me the options you chose in the FOMOD dialogue? I'll see if I can replicate it on my end. I used the selections from the F&L guide.
-
Well the logs show nothing. Was that all there was? Seems very short, not even any mention of the installation attempt. This is my log after doing an install: [spoiler=MO log after installing FCO]11:55:46 [W] QSslSocket: cannot resolve TLSv1_1_client_method 11:55:46 [W] QSslSocket: cannot resolve TLSv1_2_client_method 11:55:46 [W] QSslSocket: cannot resolve TLSv1_1_server_method 11:55:46 [W] QSslSocket: cannot resolve TLSv1_2_server_method 11:55:46 [W] QSslSocket: cannot resolve SSL_select_next_proto 11:55:46 [W] QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb 11:55:46 [W] QSslSocket: cannot resolve SSL_get0_next_proto_negotiated 11:55:46 [D] ssl support: 1 11:55:46 [D] Working directory: D:\Games\ModOrganizer\FNV 11:55:46 [D] MO at: D:\Games\ModOrganizer\FNV 11:55:46 [D] initializing core 11:55:46 [D] initialize plugins 11:55:46 [D] looking for plugins in D:\Games\ModOrganizer\FNV\plugins 11:55:46 [D] loaded plugin "bsaExtractor.dll" 11:55:46 [D] loaded plugin "checkFNIS.dll" 11:55:46 [D] loaded plugin "diagnoseBasic.dll" 11:55:46 [D] loaded plugin "gameFallout3.dll" 11:55:46 [D] loaded plugin "gameFalloutNV.dll" 11:55:46 [D] loaded plugin "gameOblivion.dll" 11:55:46 [D] loaded plugin "gameSkyrim.dll" 11:55:47 [D] loaded plugin "iniEditor.dll" 11:55:47 [D] loaded plugin "installerBAIN.dll" 11:55:47 [D] loaded plugin "installerBundle.dll" 11:55:47 [D] loaded plugin "installerFomod.dll" 11:55:47 [D] loaded plugin "installerManual.dll" 11:55:47 [D] loaded plugin "installerNCC.dll" 11:55:47 [D] loaded plugin "installerQuick.dll" 11:55:47 [D] loaded plugin "NMMImport.dll" 11:55:47 [D] loaded plugin "previewBase.dll" 11:55:47 [D] loaded plugin "pyCfg.py" 11:55:47 [D] loaded plugin "proxyPython.dll" 11:55:48 [D] downloads after refresh: 303 11:55:48 [D] game path: D:\steam\steamapps\common\Fallout New Vegas 11:55:48 [D] managing game at D:\steam\steamapps\common\Fallout New Vegas 11:55:48 [D] setting up configured executables 11:55:48 [D] configured profile: F&LNV 11:55:48 [D] validating login cookies 11:55:48 [D] initializing tutorials 11:55:48 [D] loaded language en-GB 11:55:49 [D] interface Ethernet seems to be up (address: fe80::a8ca:cab8:8c46:c789%6) 11:55:50 [D] displaying main window 11:55:50 [D] retrieving credentials 11:55:51 [D] user is not premium 11:55:51 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\modlist.txt saved 11:55:58 [D] nexus category id 109 not mapped 11:55:58 [D] simple expression matched, using name only 11:55:58 [D] passed mod id: 54460, guessed id: -1 11:55:58 [D] using mod name "Fallout Character Overhaul" (id 54460) -> Fallout Character Overhaul 3.0-54460-3-0.rar 11:56:06 [D] running D:\Games\ModOrganizer\FNV\NCC\NexusClientCLI.exe -g FalloutNV -p "D:\Games\ModOrganizer\FNV\profiles\F&LNV" -gd "D:\steam\steamapps\common\Fallout New Vegas" -d "D:\Games\ModOrganizer\FNV\overwrite" -se "5.0.3" -i "E:\Games\ModOrganizer\FNV\downloads\Fallout Character Overhaul 3.0-54460-3-0.rar" "D:\Games\ModOrganizer\FNV\mods\Fallout Character Overhaul 2" 11:56:13 [D] brought window to front 11:56:52 [D] Installation successful 11:56:52 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\modlist.txt saved 11:56:56 [D] save D:/Games/ModOrganizer/FNV/webcache/cookies.dat 11:56:56 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\initweaks.ini saved 11:56:56 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\plugins.txt saved 11:56:56 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\loadorder.txt saved 11:56:56 [D] D:\Games\ModOrganizer\FNV\profiles\F&LNV\lockedorder.txt saved 11:56:56 [D] setting file times on esps 11:56:56 [D] save D:/Games/ModOrganizer/FNV/webcache/nexus_cookies.dat If you did try and nothing happened, install a fresh MO somewhere else and point the "downloads" folder to where you now have it and then install FCO into a fresh profile in this new MO.
-
Strange display errors and mod recognition with new computer
GrantSP replied to mpotto's question in Mod Organizer with STEP
Welcome to STEP @mpotto I'm not really sure what "display issues" you are describing, the columns just need to be resized by grabbing the separator bar between each of them, just as you would in any modern UI. The fonts on some of the UI elements do look a little odd but they can be changed by either choosing another style in the "Settings" or even by using Windows settings for your overall appearance. There was a report just the other day about Windows text scaling feature causing issue with some elements. Do you have that enabled? Your screenshot also shows a lot of mods are directly installed into Skyrim's Data folder, as they are marked as "Non-MO". STEP strongly advises ALL mods used to be installed via MO to avoid any conflict mismanagement. You will need to unsubscribe from those Steam mods and install them manually using MO. -
Clear the 'logs' folder to remove any detritus that is currently in there and then go through the steps to install FCO again. Paste the contents here either in spoiler tags or via PasteBin.com or similar.

