Lexy's: Legacy of The Dragonborn Special Edition

[sm0kem]

Enai is on mod update spree again 

[Gilgamesh2k5]

Oh, wait, Gilg...I think from what you've typed out there: do you have a shortcut to the executable, and you're double-clicking that to run the application? Because that's not how you do it.

 

You're supposed to add it as an executable in MO2, which you seem to have done, then select it from the dropdown in MO2, and click Run.

No the shortcut I use is one that you create within MO2. Look under the dropdown list for executables. There is a create shortcut button. It places a shortcut for whichever executable you want wherever you choose. It is a shortcut to the executable within MO2.

[BuddyKidd]

BuddyKidd, how do you get around it? just remove the d3d11.dll file when using CK?

Yes

[shandrakor]

No the shortcut I use is one that you create within MO2. Look under the dropdown list for executables. There is a create shortcut button. It places a shortcut for whichever executable you want wherever you choose. It is a shortcut to the executable within MO2.

Welp, there went my hope for a silly fix.

 

Personally, I have MO2 outside the Steam folder entirely, but it shouldn't make a difference. And you don't seem to be running from Program Files, so that's not the issue. Maybe Mod OrganiZer is mad at you for spelling it with an S? ;)

 

Um, I've got Start In left blank, but that shouldn't be an issue either.

 

You're able to run your other MO2 executables, right? The game will launch, for example?

[Decopauge123]

DarkladyLexy, your  DynDOLOD - Dynamic Distant LOD Generation  Ultra Trees setup directions tell us to delete all files in "<DynDOLOD 2.36 Beta 8 Path>\Edit Scripts\DynDOLOD\cache" except "becauseofreasons.txt", a 1-byte file that has no content.

 

The 1st step of Sheson's directions for generating 3d Tree Static Object LOD is to either (1) delete DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_[GAMEMODE]_skyrim-tamriel_trees.txt or (2) just delete all files in ..\DynDOLOD\Edit Scripts\DynDOLOD\cache\.

[sm0kem]

I believe that file is there to preserve the folder. Some zipping utils will remove empty folders.

[Gilgamesh2k5]

Welp, there went my hope for a silly fix.

 

Personally, I have MO2 outside the Steam folder entirely, but it shouldn't make a difference. And you don't seem to be running from Program Files, so that's not the issue. Maybe Mod OrganiZer is mad at you for spelling it with an S? ;)

 

Um, I've got Start In left blank, but that shouldn't be an issue either.

 

You're able to run your other MO2 executables, right? The game will launch, for example?

yep, all other executables run

[Tzefira]

yep, all other executables run

One more shot in the dark...run MO2 as administrator, then run from the drop-down?

[GrantSP]

MO2 should NOT be installed into the Steam or the Game folder. This is a documented issue that has been discussed with the devs and the best option is to install MO2 somewhere away from those folders.

 

Also there are no justifiable reasons to run MO2, or for that matter any game tool, as administrator. If you are having issues with permissions the fault lies in your Windows system,or the way your Windows account is set up, and that should be fixed. Whenever a tool is run as admin the properties on it are now going to be at odds with any other tool that tries and accesses that file that doesn't have admin rights.

[Decopauge123]

DarkladyLexy, your  DynDOLOD - Dynamic Distant LOD Generation  Ultra Trees setup directions tell us to delete all files in "<DynDOLOD 2.36 Beta 8 Path>\Edit Scripts\DynDOLOD\cache" except "becauseofreasons.txt", a 1-byte file that has no content.

 

The 1st step of Sheson's directions for generating 3d Tree Static Object LOD is to either (1) delete DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_[GAMEMODE]_skyrim-tamriel_trees.txt or (2) just delete all files in ..\DynDOLOD\Edit Scripts\DynDOLOD\cache\.

I believe that file is there to preserve the folder. Some zipping utils will remove empty folders.

I've never heard of zipping utilities doing that, but then I haven't been everywhere or read everything.   This would only matter if you run TEXGEN to generate the desired textures, and before you run DynDOLOD, run a zipping utility that actually does remove empty folders on the "<DynDOLOD 2.36 Beta 8 Path>\Edit Scripts\DynDOLOD\cache" directory.

 

If you follow directions for generating TEXGEN and then DynDOLOD output, the "<DynDOLOD 2.36 Beta 8 Path>\Edit Scripts\DynDOLOD\cache" directory will be empty for less then 10 minutes:

(1) an average TEXGEN run is (for me) about 5 minutes, and

(2) the time from the end of the TEXGEN run to the start of the DYNDOLOD run should be less then 5 minutes [unless you take a break before running DynDLOD].

[Decopauge123]

MO2 should NOT be installed into the Steam or the Game folder. This is a documented issue that has been discussed with the devs and the best option is to install MO2 somewhere away from those folders.

 

Also there are no justifiable reasons to run MO2, or for that matter any game tool, as administrator. If you are having issues with permissions the fault lies in your Windows system,or the way your Windows account is set up, and that should be fixed. Whenever a tool is run as admin the properties on it are now going to be at odds with any other tool that tries and accesses that file that doesn't have admin rights.

... or any application in general.  Running an application (any application) with administrator privileges can be risky even if it is required.  That's why people who work as system administrators for a living should have two accounts: one for working as a system administrator, and one for doing everything else that doesn't require SysAdmin privileges.  A mistake in the personal account can only affect only the personal account.  A mistake in the SysAdmin account can destroy the entire system.

[Tzefira]

MO2 should NOT be installed into the Steam or the Game folder. This is a documented issue that has been discussed with the devs and the best option is to install MO2 somewhere away from those folders.

 

Also there are no justifiable reasons to run MO2, or for that matter any game tool, as administrator. If you are having issues with permissions the fault lies in your Windows system,or the way your Windows account is set up, and that should be fixed. Whenever a tool is run as admin the properties on it are now going to be at odds with any other tool that tries and accesses that file that doesn't have admin rights.

I was suggesting running as administrator as a troubleshooting tool, as I have no idea whether or not Gilgamesh has a permissions issue. I'm not telling them to run it that way permanently. I rescind the suggestion.

 

As fr where MO is installed -- I had gone by GamerPoets and that's wrong, good to know. Can MO be safely moved somehow or would I have to do an entire re-install from scratch?

Edited March 26, 2018 by Tzefira

[Decopauge123]

I was suggesting running as administrator as a troubleshooting tool, as I have no idea whether or not Gilgamesh has a permissions issue. I'm not telling them to run it that way permanently. I rescind the suggestion.

 

As fr where MO is installed -- I had gone by GamerPoets and that's wrong, good to know. Can MO be safely moved somehow or would I have to do an entire re-install from scratch?

If you are running MO2 as a portable application (which you are, because Merge Plugins requires it  ), you should be able to move your MO2 directory.  However, I've never tried to move and reuse an entire MO2 directory.   Maybe Google doing it, or search the MO2 support forum, for answers to your question.  As a precaution, before you try any such move, consider making a zip of your key MO2 directories and put the archive on a different drive.

[GrantSP]

It's alright @Tzefira, I wasn't having a shot at you, just a friendly reminder to all. STEP appreciates everyone that comes and lends a hand with modding.

[Tzefira]

If you are running MO2 as a portable application (which you are, because Merge Plugins requires it  ), you should be able to move your MO2 directory.  However, I've never tried to move and reuse an entire MO2 directory.   Maybe Google doing it, or search the MO2 support forum, for answers to your question.  As a precaution, before you try any such move, consider making a zip of your key MO2 directories and put the archive on a different drive.

A quick googlin' says it's relatively painless matter of copy and paste MO folder, delete .ini, but we'll find out tomorrow 

 

It's alright @Tzefira, I wasn't having a shot at you, just a friendly reminder to all. STEP appreciates everyone that comes and lends a hand with modding.

 

And I appreciate STEP, I keep learning every time I check in. You folks rock