GSDFan

Going by the picture the mods path would be C:\Games\Steam\SteamApps\common\Skyrim Special Edition\Mod Organizer\mods. It is your base directory plus mods. The mods directory can also be anything you set. C:\MOmods, C:\FO4Mods and so on. You can change the download and mods locations, but don't mess with the rest, I believe those will give you trouble if changed.

I was hoping to see a problem with one of the paths, but the only thing I could suggest now is to change the "Mods" path with the actual folder path.

Can you provide a screen shot of the paths tab under settings for us?

Going back to the first post: When MO2 is first installed and portable is not selected it will create a folder in Username\AppData\Local\ModOrganizer where it stores all of its settings. Your current install is most likely looking here at startup. Try this, shut down MO. Go into AppData\Local\ModOrganizer and rename the ModOrganizer folder to something else, this will simulate a fresh install. Start MO2 and then select the portable mode and select your game and go on from there.

Just to be clear it should look like this: --game="Skyrim Special Edition"

As you have found out the recognized executables can not be renamed, they can only be made into a new item with a new name. Also they can not be reordered for the drop down menu, they will return to default order above any added executables.

Search for Nvidia profile inspector version 2.13. At some point the profile inspector split from the main application, my version is 1.9.7.8.

Ok, I have found that G-Sync needs to be turned off for Fallout 4 and I guess Skyrim also. These games do not benefit from the G-Sync technology. They need a rock steady 60FPS to function properly. The following should help. Go into the Nvidia control panel and set the “Monitor technology†to “Fixed refresh†and under “Preferred refresh rate (Monitor name)â€, set that to “Application-controlled†and set “Vertical Sync†to “Onâ€. Those items can also be changed in Nvidia inspector under the 2- Sync and refresh section. In this section, I have the “Frame Rate Limiter†set to off, but it can be set to around the 61.8 or 62.8 if needed.The “G-Sync – application Mode’ needs to be set to “Offâ€.The “Monitor technology†is “GSYNC – Application stateâ€, set it to “Fixed Refresh Rate.The “Preferred refresh rate (Monitor name)†correlates to “Prefered Refresh Rateâ€, yes that is how it is spelled, set that to “Use the 3D application settingâ€.You also need to change “Vertical Sync†to “Force ONâ€.Change “Vertical Sync Tear Control†to “Standardâ€.Also disable any Vsync and FPS limiters in ENB if you have it installed or any place for that matter. These settings took care of my large stuttering in Fallout 4.

That guide uses Natural and Atmospheric Commonwealth - A Complete Realistic Weathers Storms Sounds Lighting and Visual overhaul. That is a function of this mod and can be disabled in the holotape. Disable the functional sunglasses effect. By the way I believe if you put on sunglasses the same thing happens. Quoth from the mods front page: "♦ Life-like Night vision goggles and headgears: green or black and white, and functional sunglasses when sun hit too hard. All craftable at the chembench. NVGs can be upgraded to life detection or recon sight from an armor bench."

Are you by chance running a GSync monitor?

If you use MO, MO needs to be run is portable mode.

Well AAR8 being a BHOF, I am glad that not all conversations on the web take on the form of SMS language.

You should check with Windows task manager, you will probably see an executable that was launched through MO was not closed after the crash. FOSE can't hook into the game if it is still in memory and thus the error message. In any case MO should be Restarted. This should be done for any executable that crashes from MO.

For the auto recognized items after you edit the name / other info you have to click the modify button and a new item will be created. The auto recognized item can not be ordered, usually the greyed items. In the edit executables dialog items can be moved via drag and drop, these are the dark black items.

Just so there is no confusion the argument should look like this, --game="Skyrim Special Edition", otherwise it will not work.

I have reset the ini files, set ultra through the launcher and BethINI program. Still looking low res. I will be playing with ENB settings next.

No, just low res all the time. Tweaks did not help.

To the best of my knowledge, the save game for profiles is broken in MO2. It only reads from the MY Games saves folder.

As far as F4SE I do not know why that would do that. Think of the left pane as a pool of mods to draw from. All profiles have access to them. Mods are not profile specific unless you install it a second time and rename it to reflect the profile, "Mod Bob profile2 player 1".

Order your DCL files the way they should be and then Shift click Fallout4.esm and the last DLC, right click and select "Lock Load Order". They will still become unchecked when running LOOT, but then all you have to do now is right click in the right pane and select "Enable all", assuming your load order does not have any ESPs that you have unchecked for other reasons, and deselect a plugin and enable it again. The DLC files will pop back into order. As for them becoming unchecked when installing mods I can only guess at this. Maybe something is protecting the files in the active profile, like an antivirus program. I assume you have run the game from Steam or the launcher at least once.

My close up graphics look low quality. Anyone know any settings to make them look better? When I start the game they look fine, but as I move around the newly loaded textures start loading low quality. This is most noticeable on the Sanctuary bridge. I even tried a new bridge texture and it did the same thing.

Remember this? Well, the reason I do this is because if I put bFullScreen at 0 the screen is huge. Are all of these related to each other? As for the walking jerky with stop/lags this fixed it for me. Note the I have a GSYNC monitor. If you have an Nvidia based system use nvidia Inspectors profile inspector to set the following: Frame rate limiter = 60Fps or 62.8 if your monitor has a high refresh rate.GSYNC-ApplicationMode = off, if you have a GSYNC monitor.GSYNC- Application State = Fixed Refresh Rate. This is the same setting as "Monitor technology" in the NVidia control panel.Vertical Sync should be set to "Use the games 3D application setting" in control panel also.Make sure that Vsync is set to on, iPresentInterval=1, in the game ini files only and not in the enblocal.ini file.In the case for these type of games you want to be at 60fps and not have the video technology trying to adjust for the frame rate for you. I hope this helps some.

My new addition to the pack. About 6 months old, 26 pounds and a Shepherd mix. Very good with her big sister Leah.

@Greg, that is where I was going next. toonfandun, if you type NXM in the search box on the MO support page you will get a lot of results. You Can Now Open NXM Files Using Multiple Programs should do the trick for you. Post 11 gives detailed instructions. You may need to also reset the association in Firefox also. In firefox settings find "Applications" and set it to "Always Ask". Then try downloading again. I would leave it on this setting.

First of all please provide MO version and the program that is registered as the default browser in Windows. I believe that the links you speak of from MO is purely your system. MO send them to the system default browser just like if you had a internet shortcut on the desktop and click that. You can try the following though: Shutdown MO. Open the ModOrganizer directory. Look for the "webcache" directory. Rename the webcache directory to something else. (webcache_Old).\ Restart MO and Test There is a program in MO that handles this also. Not knowing your default browser is kind of a hindrance here. Try the following: Shutdown MO. Open the ModOrganizer directory. look for nnxmhandlers.ini and rename it to something Else. Start MO and click the globe icon. Start MO and test. If that did not work then we will need to look at running the application that makes the nnxmhandlers.ini. There is one last thing you can do and consider this as a last ditch effort as it will set MO to a first run situation. You can rename the "ModOrganizer.ini" in the MO directory, as always MO must be shutdown first. Restart MO and follow the automated guide as before and test.