Jump to content

Lexy's: Legacy of The Dragonborn Special Edition


Recommended Posts

Hi Lexy. I ran the skyrim launcher and the game to set up things during the beginning of the guide but I made the mistake of not running it through MO2. Now when I run it through MO2 it says the directory name is invalid. I checked the path to the executable and that is correct.

 

I do not have it installed where my steam is installed I have it installed in my e: drive while steam is in my C: drive. Could that be in any way relevant?

Link to comment

AHA! Not sure what I did but after playing around with MO2 and my steam account was finally able to launch the game choosing the normal skyrim logo on MO2. Now FNIS gives no errors :)

 

Also the issue with Wrye Bash was resolved... somehow. No idea why. It looked like wrye bash unchecked a lot of mods off on it's own. So when I clicked build patch it reported no issues.

Edited by Ostegun
Link to comment

So I'm running a Ryzen 1800x and it's on a fast SSD, plus all the optional modw. It was indeed my first LOD run as this was a completely fresh install. I haven't crashed at all in game or seen anything out of the ordinary yet, but I've only spent a few hours playing so far. Is there anything I should look out for in game that would be a tell-tale sign something went wrong? And if so should I just delete the LODgen files and re run it? Would this mean I would have to rerun the dyndolod stuff as well?

You wouldn't see anything in game, most likely. LODGen basically redoes the terrain and the textures for distant LOD, so the distant textures may not match the ones from your mod list, but that would be about the extent of it. I'd clear it all out and re-run LOD... make sure you are running it through MO2 and that ALL instructions are followed. And yes, DynDOLOD would need to be rerun as well.

 

After updating DynDOLOD, I suddenly get Error Code 5 while generating, which means an access error.

I never had these types of errors before the update, having run the client several times without a hitch.

I already tried disabling my AntiVirus to no avail.

I had it at different points in the process, the latest with Markarth (see below), before also for example with Sovngard files.

Any ideas?

Error 5 is an Access Denied error, and has been very prevalent since Sheson updated to 2.48+. I've managed to get around it entirely by running DynDOLOD as an Admin. You aren't the only one seeing this by any means, as you may have gathered.

 

I updated the Loot app. How can I redo the Loot Group Section ?  the old Loot Group persists.

Under the options, there is the ability to Delete User Rules. This is an alternative to reinstalling, but all the LOOT rules will still need to be redone.

 

AHA! Not sure what I did but after playing around with MO2 and my steam account was finally able to launch the game choosing the normal skyrim logo on MO2. Now FNIS gives no errors :)

 

Also the issue with Wrye Bash was resolved... somehow. No idea why. It looked like wrye bash unchecked a lot of mods off on it's own. So when I clicked build patch it reported no issues.

WB is expected to uncheck mods - those are the ones that it is merging into the Bashed Patch. I mention this only because it seems you didn't understand that (and there have been a few questions about this on Discord lately). The only time the dialog box asking to deactivate mods comes up is when a mod that is mergeable is still active in the list.

Link to comment

Looking through my SSELODGen log, I noticed that no LOD data was generated for LabyrinthianMazeWorld. The relevant snippet said this:

 

[LabyrinthianMazeWorld] Generating LOD
[LabyrinthianMazeWorld] Gathering CELL and LAND records.
[LabyrinthianMazeWorld] Land height: -2048, Water height: -2048, Scanned: 16 CELL records, Found: 0 LAND records for area [2147483647,2147483647] to [-2147483648,-2147483648]
[LabyrinthianMazeWorld] LODsettings: Level 4 to 8 stride 8 from -4,-4 to 0,0
[LabyrinthianMazeWorld] no useful LAND data for terrain LOD generation found
 
Is this normal?
Link to comment

 

Error 5 is an Access Denied error, and has been very prevalent since Sheson updated to 2.48+. I've managed to get around it entirely by running DynDOLOD as an Admin. You aren't the only one seeing this by any means, as you may have gathered.

Well, how do I get around it? I can't access the game now after trying at least 8 times to rebuild the files.

It crashes at different points in the process.

Could it have to do with the recently redone merges? Could it be because I stick with Verdosebrom instead of Verdant?

I only wish to be able to play again. Pretty much kicking myself for updating so quickly instead of waiting for a few more updates to the build.

Link to comment

Some questions regarding Wyre Bash:

 

(1) Which mergeable esps (in Wyre Bash) should be marked as NoMerge ?   In the discussions, XPMSE.esp was adviced to tag as such.

 

(2)  When creating the Bash Patch, are mergeable ESL files merged effectively ?

Edited by madskyrim
Link to comment

Well, how do I get around it? I can't access the game now after trying at least 8 times to rebuild the files.

It crashes at different points in the process.

Could it have to do with the recently redone merges? Could it be because I stick with Verdosebrom instead of Verdant?

I only wish to be able to play again. Pretty much kicking myself for updating so quickly instead of waiting for a few more updates to the build.

Did you try running it as Admin as Shadriss suggested? If it's still not working, revert back to version 2.47 with resources from 2.45.

Link to comment

Well, how do I get around it? I can't access the game now after trying at least 8 times to rebuild the files.

It crashes at different points in the process.

Could it have to do with the recently redone merges? Could it be because I stick with Verdosebrom instead of Verdant?

I only wish to be able to play again. Pretty much kicking myself for updating so quickly instead of waiting for a few more updates to the build.

As I suggested, try setting DynDOLOD to run as an Administrator. It's not ideal, but if it works...

 

This will have nothing to do with the merges, and I plan on keeping Veydesbroom as well when I update in a week or so. As to the 'waiting a few more updates', that may put you into perpetual stasis - this guide updates AT LEAST weekly, so if you are waiting for a more 'solid' build, you'll be waiting a long time.

 

Some questions regarding Wyre Bash:

 

(1) Which mergeable esps (in Wyre Bash) should be marked as NoMerge ?   In the discussions, XPMSE.esp was adviced to tag as such.

 

(2)  When creating the Bash Patch, are mergeable ESL files merged effectively ?

1) None. Lexy has a list of bash tag changes, none of which are NoMerge. The XPMSE suggestion was based on that particular user's issue, one where XPMSE was (somehow) being merged into the Bash when it shouldn't have been.

 

2) Well, given that I've had no problems with the Bashed Patch since ESLs started creeping into the load order, I'm going to say yes. Personal experience, of course, but if there were prevalent problems, I doubt Lexy would leave them unaddressed in the guide.

Link to comment

Thank you High King!

 

Almost done ! been learning a lot but it's my first time using Mator smash. In the guide it says select from update to Bashed Patch, 0.esp. But I Only have from update to dragonborn.

 

Are we supposed to check some boxes in the previous pop up window before clicking okay?

 

Instructions:

 

  1. Run Smash inside Mod Organizer 2, Select 'Skyrim SE' and click ok.
  2. In the popup window select ok. SHOULD I CLICK ON SOME OF THE BOXES?
  3. Highlight everything from Update.esm down to Bashed Patch, 0.esp. HERE IS MY ISSUE
  4. Right click and select Add to patch.
  5. In the popup window call both fields Smash Patch.
  6. Highlight everything from Update.esm down to Bashed Patch, 0.esp.
  7. Right click, select Smash Settings, navigate to Smash and click Smash.all except for the following plugins:
Link to comment

Hello everybody!

First, thanks for this great guide, I love it! So detailed in every aspect!

I carefully followed it, installed everything except the ENB stuff (never liked ENBs).

So far its working great, but there is one thing I can not solve: Images in Books are replaced with some funny rainbow pic! :D

Now this isnt gamebreaking, but maybe somebody has an idea what I did wrong?

 

Screen-Shot0.png

 

Link to comment

As I suggested, try setting DynDOLOD to run as an Administrator. It's not ideal, but if it works...

 

This will have nothing to do with the merges, and I plan on keeping Veydesbroom as well when I update in a week or so. As to the 'waiting a few more updates', that may put you into perpetual stasis - this guide updates AT LEAST weekly, so if you are waiting for a more 'solid' build, you'll be waiting a long time.

After setting DnyDOLOD as Admin in the system, it took me another three tries to have it run through to the end.

It's so weird, cause I had never had any of these issues before.

 

Regarding the playing part: So far I had no trouble continuing my save files after the updates of the last couple months or so. Everything ran smoothly with virtually no CTDs. I only noticed a few glitches with the Dragonborn library, though I doubt that has anything to do with the updates (things not added through sorting, using quest items in the sorting process etc.)

Link to comment

Hello everybody, one question to all out there: I have been opening all the .esp needed to convert 44 in WryeBash prior to use CK because I wanted to check if any has an none esm as a master, using "list master" functionality, but so far and at the end of the guide now, I've not needed to esmify any. Am I missing something here? Or the instructions are there just in case?, thank for the help, people :)

Anyone can lead me on this please?, thank you :) Edited by Electronauta
Link to comment
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.