Jump to content

ousnius

Premium Member
  • Posts

    249
  • Joined

  • Last visited

Nexus Mods Profile

2 Followers

About ousnius

Profile Fields

  • Country
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ousnius's Achievements

Rising Star

Rising Star (9/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Told you people would be nice, I'm glad you pulled it through. :) Love you too. <3
  2. For anyone coming from Google, RaceMenu SE was officially released now: https://www.nexusmods.com/skyrimspecialedition/mods/19080
  3. As BodySlide was updated, the shaders and more were improved, so what it looks like now is roughly what the skin texture should be. In FO4, the skin textures are generally a little darker. But yes, there's nothing wrong about that here. You could increase the brightness in Outfit Studio, but that's not recommended, because then the bright outfits will become even more bright than they should be.
  4. Once you accept it and know how to work with it, rules of Vortex are the best for both worlds.
  5. It might be "dumb", but I can't think of a single ENB preset without an enbseries.ini file. So it should work rather well.
  6. Interesting, I didn't know of that. Well, you can still deploy your profile and then edit the .ini files in your documents\my games folder. Since Vortex uses hardlinks, they will be the same file. When you want to edit the other profile's inis, deploy that profile again instead. They're profile specific in that they're swapped out once you swap your profile inside Vortex, which is really all that matters. As for Windows users, your documents folder is already user-based.
  7. The same holds true for Vortex. It uses LOOT as a base to get a mostly working order for you automatically, and then you can go in and apply your own rules and priority numbers to affect or override what LOOT is doing. It's not a drag and drop like in NMM or MO, but it nevertheless allow for the same (actually even more) amount of customization. It's different and takes getting used to of course.
  8. The counter argument is that you don't need to know where they will go, other than adding rules or merging a few you know have conflicts that LOOT doesn't detect. But yes, Vortex needs more visual indicators.
  9. Yeah, it is doing similar things for me. Which mod, does the version number follow semantic standards? (1.2.4 etc.) Is the file vs mod page version/main file correct? Did you install it from the Nexus or manually via archive?
  10. There's an exception for that with certain tools like xEdit or Photoshop, because they actually rename files back and forth instead of straight up replacing the old file you're saving over, which breaks up the hard link. However, Vortex will see this and merge it back into its own folder or ask to do so.
  11. You can turn off auto-sorting of plugins in Vortex, and run your batch scripts after you installed all mods. The plugins.txt and loadorder.txt files still exist.
  12. Interesting, I didn't know of that. Well, you can still deploy your profile and then edit the .ini files in your documents\my games folder. Since Vortex uses hardlinks, they will be the same file. When you want to edit the other profile's inis, deploy that profile again instead.
  13. Why do you need to move your plugin order around to test your mods? You said you need it at specific positions to test, but what's the technical reason for that? You can temporarily force a global priority to the plugin, if you need it to be at the end always for testing purposes. I'm not sure why would need to test intentionally breaking your mod by putting it above conflicting other plugins. What I do agree on is the visual representation of both the mod and plugin order. The result of what all your rules and priorities come down to isn't clear enough to me yet.
×
×
  • Create New...