The author states that it must be sorted as the 6th plugin, which in SSE puts it between Dragonborn and USSEP. Question: I have recently installed Sexlab Light SE. Currently running LOOT 0.10.3 Build 0fc788b. After each crash, I have downloaded the next-to-last version (installer version) from GitHub and installed that, which runs fine. I have upgraded 3 times in the past couple of months, hoping each time that a runnable build has been published, and each time LOOT has crashed on launch with no error message. Because I'm lazy and your Installer versions have always worked in the past.
#Boss load order fallout new vegas windows 7
System is Windows 7 圆4 Home Premium/i5-3570K/16GB/GTX970 and I downloaded/installed the Installer version. Previous versions run fine from either shortcut. It will not run, whether from its own desktop shortcut or from NMM's 'Supported Tools' dropdown.
Issue- the latest version of LOOT (0.11.0) crashes reliably on launch.
Yes, all in one post! I'm such a multi-tasker, right? I'd like to report an issue and ask a question. Sorry you had to reinstall your OS, that's a pain to do. If I remember correctly Wrinly did mention he had routines that make it such that this shouldn't be needed. If those are not in sync that might cause the masterlist to be out of sync. It holds all sorts of files used by Git to manage what is happening with the files from the server. Also in the folder reserved for the specific game's masterlist is a small hidden folder named. You can check this under settings in LOOT but most users don't check that, at least I don't believe so. So if the effected game is still reading the v0.7 or the v0.8 masterlist then those are very old. However, for other games there is a v0.10 masterlist, and a v0.7, and a v0.8, masterlist when Wrinkly changed the syntax. Well oddly enough for Skyrim SE this doesn't apply because there is only a v0.10 folder. Wish I would have suggested that sooner, but I didn't notice you were going to reinstall Windows. If you still have an issue with a specific game, while still in the C:\Users\\AppData\Local\ LOOT delete the game's masterlist folder, test LOOT I'm not sure I caught his message that he was going to do that. I'm giving an example because I feel bad that Beermotor reinstalled his OS. However, anyone reading this don't blindly do this. I don't have any userlist.yaml files so I wouldn't loose anything. I just do it because it's what I have done for a while now when I have issues. I can't remember but he may have even frowned upon this the last time I brought it up. There are a few things that Wrinkly mentioned shouldn't be needed. I've got a lot of reading to do before I start. I've learned over the years that one mass commits at everyone's peril.Īlso mad props for the fantastic and thorough documentation. Most of Sharlikran's first paragraph won't apply to you, because you don't have write access to the official repositories.Īlso, try to keep your commits/PRs focused, so you're not making unrelated changes in the same commit, for example, because that makes reviewing and making changes simpler. Travis will catch syntax errors when you make a PR, and your changes can't affect anyone else until they're accepted, so it's low-risk. The review process is an excellent way to get and give feedback, and the worst I'll do is ask you to make changes or (rarely) explain why I think your submission isn't appropriate for inclusion in the masterlist. My advice would be to use the existing masterlist entries as examples (the reference goes into more detail than you'll probably need), and don't be afraid to send pull requests early and often.
0 kommentar(er)
