It's an interesting idea with lots of potential for better configuration management.
I understand that the mod is an automated profile selector based on hardware configuration but I dream of having better tools beyond "profile sync" to manage my 6800+ mods under configuration. Here is my short wish list:
- Section definition from MO2 separator. All mods starting from the identified separator up to the next one. Simpler than declaring individual mods. I already use separators as identifiers for a batch file to swap in and out mods from my almost saturated 2tb SSD drive.
- Prereq/Coreq mod. Profile/section activation condition set from the identified mod (single mod or mod list) MO2 state enabled/disabled. That should simplify carrying states for all my test landscape/grass/season/patches and other texture combinations.
- Import sections. Import mod entries from external files at the target separator placeholder when the profile is activated and conditions met. Mod entries from a small profile, MO2 CSV, an export (TBD).
Section definition from MO2 separator. All mods starting from the identified separator up to the next one. Simpler than declaring individual mods. I already use separators as identifiers for a batch file to swap in and out mods from my almost saturated 2tb SSD drive.
I will add it with next update. This is amazing idea.
Prereq/Coreq mod. Profile/section activation condition set from the identified mod (single mod or mod list) MO2 state enabled/disabled. That should simplify carrying states for all my test landscape/grass/season/patches and other texture combinations.
Sure. For section, it will be doable, but for profile I need to convert this plugin to c++ (which I will do anyway at some point), since python MO2 API lacks in profile management. I am using a trick to switch profiles, and this trick works only during MO2 startup.
Import sections. Import mod entries from external files at the target separator placeholder when the profile is activated and conditions met. Mod entries from a small profile, MO2 CSV, an export (TBD).
👍🏻
If you have a discord, send me a DM, my nickname is the same as here on nexus, so that I can ask you while implementing these features. I need to make sure I understood them correctly.
Section activation by mod should be good enough and really useful.
While we are at it, this is part of my extended wish list:
- Mod list validator. Using keywords in a mod MO2 "Notes", validate list consistency. Keywords are "COREQ( {list of mods} } where {list of mods} is all mods that should also be enabled when the this mod is enabled, "PREREQ( {list of mods} ) where {list of mods} is all mods that should be enabled BEFORE this mod (install order), "EXCREQ( {list of mods} ) where {list of mods} is all mods that should be disabled when this mod is enabled. {list of mods} could be mod names or NexusIDs. An export/import function would produce a mod dependency file that could be distributed and exchanged. I'm already use this notation (with manual validation) to maintain obscure dependency between some mods and their patches way below in the install order.
I have a discord account (same nickname) but I'm not there often. Notify me when ready, we could exchange further.
I was trying to think how I'd utilize this, but then I realized it would be great for easily adding mods that you want to a Wabbajack list. Since I discovered Wabbajack a few years back I had been installing all my additional mods by hand, which gets pretty damn tedious when you're installing hundreds of mods by hand. I inevitably FUBAR the list and have to start over. I discovered MO2 Splitter a few months back, which allows you to export and import a selection of mods to/from your list, but it doesn't handle separators well (it just dumps them in with the imported mods, leaving you to organize it yourself) and the validation is up to you. I started making main category folders and then subfolders for specific categories (like City Overhauls -> Solitude Overhaul -> all Solitude mods here) to make the import process less tedious.
Having something like CommanderDominator described would make importing large overhauls and collections a breeze! Making the config file would be a bit tedious for huge imports like Armors, Clothing, Utilities where I have 40+ mods per category, and would take some scripting on my part, so my wish is "point it at a directory and have it write a config with those plugin names". I see that you mentioned you plan on writing a configuration wizard of sorts, so I'll just have to do it myself until then :)
Today I learned that my monitor is actually 43:18, as 21:9 is a marketing approximation. You may want to add this to the examples because (other than not reading the vram correctly) that's why I had problems with my profile matching.
There is an issue in __init__.py where you're getting the VRAM. In systems with two GPUs (in my case an older system from the final days of SLI), the result will come back as "11260\n11260", which is not an integer and stops the plugin from continuing.
If a manual workaround is needed by anyone, you can change the line from "GPU.vram = GPU.get_vram_in_gb()" to "GPU.vram = 11260" (or however much VRAM you have).
Ideally get_vram_in_gb() can be modified to pull just the VRAM for the active GPU or the first GPU or whatever feels most appropriate. It's probably a pretty rare situation these days.
* oneshot option. filter/condition only fires once on 1st startup and never fires again, until some file is deleted (should happen after wabbajack updates modlist because it clears some files). like if data/sectionname.lock exists - don't fire anymore on startup. has to be per section to make sense, but can be global as well as an option. this can be used to provide initial configuration, but skip triggering every mo2 launch so user-made adjustments are respected.
* detect controller/gamepad as one of conditions in future updates? would be cool to toggle some mods if controller is connected. I can see potential issues like if user wakes up controller after mo2 started though... previous oneshot option might help here.
* trigger other MO2 plugin. Like trigger your affinity plugin =) also can benefit from oneshot option. maybe not arbitrary plugins should be triggered, but just your affinity would be cool to.
* cpu vector flag detection. like trigger avx1/avx2/avx512 .dll (pre-installed as mod ofc) for FSMP if cpu supports it. note about avx512 - it only really works on amd cpus for fsmp, intel is problematic, more info on mod page. so probably wise to support explicit amd_avx512 filter to filter out intel cpus with hybrid cores.
* GPU vendor detection. Filter by amd/nvidia/intel, so GPU specific mods can be toggled.
* screen refresh rate detection. to toggle display tweaks configs for 60/120/144 hz screens.
* log file deleter, or just generic file deleter, probably in overwrite only for safety. get rid of pesky logs that keep re-appearing in overwrite. or clear up enb cache or cs cache if switching between enb/cs profiles.
I followed the installation and set the config.ini file—everything is simple and well explained, but when I launch the game, mods aren't being enabled/disabled (screenshot below). config.ini:
This means mod name in the INI is not the same as name in the MO2. Make sure you do not have additional spaces etc. If this still does not work, send me your Profile Assistant INI and modlist.txt file from your current profile directory.
You can also try this version, it will write to log all mods that should be enabled/disabled but were not found on the mo2 list.
Nevermind, I misunderstood how the plugin works. I thought it would enable/disable mods upon launching the game, but in fact it happens upon starting MO2.
So how does it work on a multi monitors setup? Does it detect the main display's aspect-ratio? Or does it look for the values from skyrimprefs.ini perhaps?
Thank you, but I think it is pretty easy to configure. If some part is not clear, ask me. Btw I do not know French, I did this mod for my friend, so examples with language filter are using his native language.
I can also configure it for you, if you will tell me what result you want.
33 comments
I understand that the mod is an automated profile selector based on hardware configuration but I dream of having better tools beyond "profile sync" to manage my 6800+ mods under configuration. Here is my short wish list:
- Section definition from MO2 separator. All mods starting from the identified separator up to the next one. Simpler than declaring individual mods. I already use separators as identifiers for a batch file to swap in and out mods from my almost saturated 2tb SSD drive.
- Prereq/Coreq mod. Profile/section activation condition set from the identified mod (single mod or mod list) MO2 state enabled/disabled. That should simplify carrying states for all my test landscape/grass/season/patches and other texture combinations.
- Import sections. Import mod entries from external files at the target separator placeholder when the profile is activated and conditions met. Mod entries from a small profile, MO2 CSV, an export (TBD).
If you have a discord, send me a DM, my nickname is the same as here on nexus, so that I can ask you while implementing these features. I need to make sure I understood them correctly.
Section activation by mod should be good enough and really useful.
While we are at it, this is part of my extended wish list:
- Mod list validator. Using keywords in a mod MO2 "Notes", validate list consistency. Keywords are "COREQ( {list of mods} } where {list of mods} is all mods that should also be enabled when the this mod is enabled, "PREREQ( {list of mods} ) where {list of mods} is all mods that should be enabled BEFORE this mod (install order), "EXCREQ( {list of mods} ) where {list of mods} is all mods that should be disabled when this mod is enabled. {list of mods} could be mod names or NexusIDs. An export/import function would produce a mod dependency file that could be distributed and exchanged.
I'm already use this notation (with manual validation) to maintain obscure dependency between some mods and their patches way below in the install order.
I have a discord account (same nickname) but I'm not there often. Notify me when ready, we could exchange further.
Going on Discord.
Having something like CommanderDominator described would make importing large overhauls and collections a breeze! Making the config file would be a bit tedious for huge imports like Armors, Clothing, Utilities where I have 40+ mods per category, and would take some scripting on my part, so my wish is "point it at a directory and have it write a config with those plugin names". I see that you mentioned you plan on writing a configuration wizard of sorts, so I'll just have to do it myself until then :)
[2025-05-11 14:07:08,967] [I] [assistant.py:76] Profile Assistant: initialized. Vram: 4 GB. Aspect ratio: 43:18. System language: en.
If a manual workaround is needed by anyone, you can change the line from "GPU.vram = GPU.get_vram_in_gb()" to "GPU.vram = 11260" (or however much VRAM you have).
Ideally get_vram_in_gb() can be modified to pull just the VRAM for the active GPU or the first GPU or whatever feels most appropriate. It's probably a pretty rare situation these days.
* oneshot option.
filter/condition only fires once on 1st startup and never fires again, until some file is deleted (should happen after wabbajack updates modlist because it clears some files). like if data/sectionname.lock exists - don't fire anymore on startup. has to be per section to make sense, but can be global as well as an option.
this can be used to provide initial configuration, but skip triggering every mo2 launch so user-made adjustments are respected.
* detect controller/gamepad as one of conditions in future updates?
would be cool to toggle some mods if controller is connected.
I can see potential issues like if user wakes up controller after mo2 started though... previous oneshot option might help here.
* trigger other MO2 plugin.
Like trigger your affinity plugin =) also can benefit from oneshot option. maybe not arbitrary plugins should be triggered, but just your affinity would be cool to.
* cpu vector flag detection.
like trigger avx1/avx2/avx512 .dll (pre-installed as mod ofc) for FSMP if cpu supports it.
note about avx512 - it only really works on amd cpus for fsmp, intel is problematic, more info on mod page.
so probably wise to support explicit amd_avx512 filter to filter out intel cpus with hybrid cores.
* GPU vendor detection.
Filter by amd/nvidia/intel, so GPU specific mods can be toggled.
* screen refresh rate detection.
to toggle display tweaks configs for 60/120/144 hz screens.
* log file deleter, or just generic file deleter, probably in overwrite only for safety.
get rid of pesky logs that keep re-appearing in overwrite.
or clear up enb cache or cs cache if switching between enb/cs profiles.
will a settings loader be made for NPC Underwear Distribution Engine (NUDE) ?
Mo2 2.5.2
CHIM
config.ini:
Settings=21:9,16:9
DebugMode=True
[21:9]
EnableMods=WidescreenMods
DisableMods=
AspectRatio=21:9
[16:9]
EnableMods=
DisableMods=WidescreenMods
AspectRatio=16:9
[WidescreenMods]
Mod=[21x9] Edge UI - Modern Skyrim Interface
ProfileAssistant.log:
[2024-11-06 22:09:25,674] [D] [assistant.py:54] Profile Assistant: initialized. Time: 0.0s.
[2024-11-06 22:09:25,674] [I] [assistant.py:76] Profile Assistant: initialized. Vram: 15 GB. Aspect ratio: 16:9. System language: fr.
[2024-11-06 22:09:25,674] [D] [configuration.py:210]Config file found: C:\Mod Organizer 2\plugins\ProfileAssistant\config.ini.
[2024-11-06 22:09:25,674] [D] [configuration.py:245]Profile Assistant: Mod list for WidescreenMods: ['[21x9] Edge UI - Modern Skyrim Interface']
[2024-11-06 22:09:25,674] [D] [assistant.py:81] Profile Assistant: found configuration: [21:9] [None;None) 7:3 None None/['WidescreenMods']/[].
[2024-11-06 22:09:25,674] [D] [assistant.py:81] Profile Assistant: found configuration: [16:9] [None;None) 16:9 None None/[]/['WidescreenMods'].
[2024-11-06 22:09:25,676] [D] [configuration.py:91] Profile Assistant: Checking Vram: 15 GB.
[2024-11-06 22:09:25,676] [D] [assistant.py:263] Profile Assistant: Configuration 16:9 passed tests.
[2024-11-06 22:09:25,676] [D] [configuration.py:176]Profile Assistant: Enabled mods: []. Disabled mods: ['[21x9] Edge UI - Modern Skyrim Interface'].
[2024-11-06 22:09:25,676] [I] [configuration.py:177]Profile Assistant: Settings 16:9 activated. Enabled mods: 0, Disabled mods: 1.
[2024-11-06 22:09:25,682] [D] [assistant.py:86] Profile Assistant: applying configuration. Time: 0.008s.
Upon launching the game, '[21x9] Edge UI - Modern Skyrim Interface' isn't disabled:
Any idea?
You can also try this version, it will write to log all mods that should be enabled/disabled but were not found on the mo2 list.
So how does it work on a multi monitors setup? Does it detect the main display's aspect-ratio? Or does it look for the values from skyrimprefs.ini perhaps?
Thanks
I kind of understood the function but I really need an explanation through a video.
A bit complex for configuration though, is it possible to have it in french please ? :)
Btw I do not know French, I did this mod for my friend, so examples with language filter are using his native language.
I can also configure it for you, if you will tell me what result you want.