Jump to content

AliasNick

Supporter
  • Posts

    13
  • Joined

  • Last visited

Nexus Mods Profile

About AliasNick

Profile Fields

  • Discord ID
    abstrusity
  • Country
    Canada
  • Currently Playing
    Skyrim SE
  • Favourite Game
    Skyrim SE

AliasNick's Achievements

Rookie

Rookie (2/14)

  • Reacting Well
  • Conversation Starter
  • First Post
  • Collaborator
  • Week One Done

Recent Badges

0

Reputation

  1. I have the same problem and it's driving me in-f***ing-sane because of its sporadic/random nature. My original testing sessions - Launching through MO2 with nothing but the cleaned ESMs and skse scripts. - Upon main menu loading done / console 'coc riverwood' / move around / scroll to 3rd person / move around while moving the mouse / console 'qqq' (exquisitely satisfying in these troubleshooting times) - Repeat 3 times without changing anything --- I have tried A LOT of A/B testing scenarios like all the other poor souls in this thread. I will elaborate on them here in this very reply eventually. One thing is for sure, shaders are, so far, not the issue. Or if it is, it is combined to some other behaviour. This is also why I'm writing this post without elaborating on my previous attempts, as I think I found yet another clue which was not thoroughly explored in previous replies. *Tests will be inserted here later.* --- Test #428372 - From system file read access issues to faulty INIs Context: Since my MO2 mod folder is entirely backed up in MS OneDrive. The last reply by @Glanzer made it clear that my problem was related to this. Or so I thought, unfortunately I was able to replicate the problem with OneDrive sync paused and my antivirus turned off. I flipped a table or two then closed MO2. I copied the skse scripts manually in my install folder located in another drive (away from OneDrive) and launched my game from the skse loader directly. After 3 numerous attempt, it, f***ing, worked. I was not ready to declare it a win. Obviously I will have to use MO2 in the end. This is when I remembered that I use profile-specific saves and INI settings. Since MO2 was out of the equation, it led me back to my INIs. I backed up my old, forgotten but working ~/Documents/*.ini and replaced them with my INI from MO2. AUTOMATICALLY I was able to replicate the issue. 3 times with profile INIs, the bug was there. I restored my old INIs and it was working without an issue again. Ladies & gentlemen, an age-old, issue-inducing modding plague causing these kind of issues? While proudly using BethINI?! And that no bulls*** guides will see its "fixes" appear in my files unless I know the author is well-known and/or knowledgeable on the subject. I would not have been surprised of this situation if the ProfileRedirector mod was on due to the fact that it caches INIs and might break stuff, but since it wasn't, the testing is aiming in that direction, INI issues. Even though I'm not 100% sure yet, more like 90% sure. I will be reviewing each lines of my defective "oh-so-perfect-BethINI-generated-INIs" against my old, trash but working ones. Like I said, I will keep you all informed here. Never give up. Update: - I backed up both my working and not working INIs. - I recreated my with BethINI from scratch. Using these settings. Every changed setting I would save INIs and run Skyrim to test. - Tested out those fresh INIs both outside and inside MO2. (profiles vs documents) Everything worked. - Tested loading the game with read-only INIs, nothing triggered. - Reviewed every line to see any changes between the newly crafted and the broken ones. - Copying the lines from the broken INIs that were not in the new ones did nothing to break the game. It's just working. And I'm kind of pissed that I cannot replicate the issue, because I still haven't found what is causing it! I have but speculations to make after all this. Need further testing. Here is what changed from last time: - I did not generate nor use a SkyrimCustom.ini anymore. - My files are not read-only, even though I tested those and it made no change. I will edit this again if something come up. If someone wants to take the torch from here, please do so!
  2. Solid upgrade. Makes navigating and searching the website way faster. Still few minor design related inconsistencies I would call, but I'll let you guys apply the forthcoming design updates before pinpointing them. Good job!
  3. Thank you hothtrooper44, your mods are amazing!
  4. Thank you Arthmoor for your time and passion that you shared with this community. Truly appreciated!
  5. Thank you Enai for not only your mods, but your hard work and time toward this community. As mentioned by other people below, your mods earned a special place in my load order, never to be removed. I cannot play without those anymore. Best regards to you. P.S. I'd like to thank the Nexus for making this modding experience possible and for those great kind of blog post.
  6. In response to post #54732143. #54732223, #54732768, #54732823 are all replies on the same post. Fair point (actually made me laugh). The fact they want to mod their game their own way is fine and pretty much shows they wanted things to change in the first place I admit. But the Nexus website is the central point that everyone uses, not just them. The website was outdated, thus, a new experience was needed. The new design is the way forward. We may not like 100% of what it is (including myself). Compromises must be made and constructive conversations are essential for the benefit of all users. Throwing demotivational bullshit at the devs is anti-productive imo.
  7. People don't like change. And it shows right here. (And are simply mean too, I can't believe what I just read in the comments. It's not even constructive.) Keep up the good work. This newest design/UI *is* the way to go. It's refreshing, easier to navigate and feels like a modern platform. Love the news for Vortex. I can't wait to see how it'll be like! (:
  8. MO can manage files that are outside of its virtual folder. And by looking at your load order the older files are overwriting USLEEP. Unless you disabled them in MO indeed. But more importantly, you should really build yourself a TES5Merged Patch and a BashedPatch. These are crucial elements in any load order. Lots of tutorials online on these two.
  9. Hello. The first thing I see in there is that you have those: Unofficial Skyrim Patch.esp Unofficial Dawnguard Patch.esp Unofficial Hearthfire Patch.esp Unofficial Dragonborn Patch.esp They are not required since you already have Unofficial Skyrim Legendary Edition Patch.esp The legendary patch, aka USLEEP, should be the only one loaded from that series. In other words the individual ones are deprecated and should not be used. --- Second, and even worse imo, you don't seem to have any TES5Merged Patch nor any BashedPatch in that load order. For such an exhaustive modlist, they both become mandatory.
  10. +1 Would definitely want this in my load order!
×
×
  • Create New...