ButchDiavolo

Ah ok. The game does start, so I just ignore it until it causes issues then Thanks

Heya Tech, thanks for updating the guide so quickly. I had to laugh when I decided to install NMS again the other day. No sooner had I installed and modded it, when an update dropped and most mods stopped working. Typical. Anyway, when running AMUMSS again, it throws out 2 errors (probably related?): and Do those/ that error(s) need correcting or is this intended?

Hi Tech, I just installed NMS again following the guide (haven't started a game yet). I noticed that Gumski Cam (gcam) installation is now different: instead of downloading a preferred file, it is now one file. During the guide patch building, gcam will ask for customisation. And before anyone asks: no, I am not "back". Just installing NMS for some MUCH needed downtime relaxation. Hope you are all doing well.

Due to rather overwhelming issues in the "real world", I will be unable to give support in the STEP forums for the time being. I know this message is not necessary, but I just want to let people know what is going on and why I am not responding to messages and IMs. I will be back when things have settled down again. And yes, that is a threat

I just love how delightfully unclear he always is with his descriptions... I just tend to steer clear of his "enb" stuff.

You can install any mod midgame without problems. Unless the mod author specifically say the mod need a new game, of course. I personally have never had issues with re-running LOOT after installing a mod midgame. I guess it could be possible if the new mod conflicts with another. But that doesn't have anything to do with LOOT.

Ah! Yes sometimes textures or meshes are hardcoded in plugins, I forgot about. Mainly because most texture/mesh mods don't have plugins. And the problem is not spotted, because MO2 can't read the content/ coding in a plugin file. Which makes it very difficult to trouble shoot, because the reference in the plugin remains, even if you hide/ delete the texture/mesh. Fun huh? As far as other mods go, check out ERM- Enhance Rocks and Mountains (mountain meshes) and Tomato's Mountains 4K 8K (textures). ERM combined with Tomato's Slate version is my favorite mountain retexture. It looks so different from the norm. For Architecture, you could check out Riton's overhauls. And check out Yuril's Fyxes, most are tiny fixes but they make a heck of a difference. a MUST have is Yurils Fyx High Hrothgar Step Collisions. You can actually walk/run/skip/ crawl up the 10,000steps now without getting stuck! And my personal favorite Whiterun overhaul: Illustrious Whiterun by winedave. If nothing else, you should at least get his wood addition. His wood textures are amazing. Of course this is just optional. I am sure you can find what you are looking for by yourself. Just some examples of what is out there, but old and new.

I am so glad that was the solution. if you have any other mods that comes with pre-rendered lodgen folders, just delete those as you don't need them. You will be making your own lodgen based on your loadorder. However, DON'T remove folders named DynDOLOD\lod which contain meshes which end with xxxpassthru_lod.nif. Those are the files that Dyndolod needs to create your lodgen. In the mean time, enjoy your Skyrim.

Many lighting effects are actually meshes and textures, as are for example mists etc. As such the lighting effects will interact with the meshes around them, making it look like they are illuminated. If they are not fine tuned however, they will cause mesh flickering. This means, among other things, that one part of a mesh is lit but another part of the same mesh is not. Giving odd effects and actual flickering. A recent development to prevent this flickering, is dividing up the meshes in separate parts, while still remaining one mesh (more magic). This is what Lux does. So by using the Lux meshes, you can use any lighting mod and it will not cause visual oddities. And Lux is fully parallax enabled. That whole Atlantean situation sounds odd. If you hid the textures, it should be impossible to show in the game, as you say. Unless it is saved into the save game somehow. Ah OK. I just went to look at the contents of Atlantean. I see it also includes lodgen files. It could be that the textures that keep appearing are also included in that. Try disabling the "Green tundra landscape LOD" folder and see if it still shows up. In fact, you don't really need those files, because you will be running xlodgen etc. yourself at the end. When you try to disable that LOD folder, it could be that MO gives an error message and you can't hide it. That means the filename would become too long. in that case try hiding the folder under the main lod folder and so on, until you are able to hide them. Then go in-game to check if they are gone then. *crosses fingers* Even if they are still there, you should consider deleting that whole LOD folder, because you don't need it. Some mod creators add those files for people who don't want to use Dyndolod etc. then it is just install and forget. And yes, another option is to ask the Atlantean mod creator for advice. They created it, so they should know what could be causing it. If/ when you find out, please let me (us) know, because the answer could help others. And well, I am just curious now

The "problem" with adding mods to a pure STEP install, is that the patches will most likely no longer work/ conflict. Going beyond STEP, you are basically going to have to deal with problems by yourself. But you can always ask on the forums. About step 4: trusting someone to death is never advisable I am by no means an expert on anything. I just take note of what works and what not. Learning from disasters if you will. So many disasters *sigh* I think I am on Skyrim build 50-something now. And I again have a big problem... As for Lux, I am using Lux in the same way as the STEP guide uses ELFX: just for the meshes (and few textures). The problem with using parallax is that using a mod like ELFX can/ will cause light flickering. Lux is aimed at parallax now AND has "divided" meshes, which will cut down enormously on this flickering. So I use only the meshes. I delete the plugins, because I don't want the "look" of Lux. For lighting itself, I am currently using Skyrim is Luminous (SiL) and Enhanced Dynamic Lighting (which is made to compliment SiL). Both mods are very new, but they look good to me. Well, in the case of Skurkbro, I know he was totally burned out after making his overhaul. He took a looooong break, maybe even still on break. I am sure he just missed a few textures and didn't update them to the new parallax. As I said in the previous post, using old parallax textures on new parallax meshes will cause the spiky thing. This is because the old parallax used different height settings in the textures, so it looks either molten, glistening or spiky. I think all the other landscape mods/ modders are similar. They have to change so many things to make it work with parallax, that they lose sight of what they changed. And then burn out and need a break. And then either forget or lost interest in the mod. *chuckles about the Atlantean becoming spikey* Well... welcome to modding! sometimes mysterious things happen and who knows why? The way I fix problems like that, by using a backup landscape mod. I use Majestic Landscapes combined with Majestic Landscape addons and tweaks. I have installed them in the general "Foundation" section, so they get overwritten by everything, except things that are missing or flawed. Then I hide the flawed textures/ meshes, so that Majestic takes over. That fixes the spikey problem for me. I overcame the obstacle by making sure only the mod I wanted is registering in MO2. If you have a large(ish) mod list, textures and meshes are overwritten by many mods, sometimes even ones you wouldn't expect. So I go by the Data tab in MO2. That shows you everything you need to know really. You then work back across all the mods, until the file name is displayed in white and not red, which means that no other mods alter that file. Another way to get an oversight of what is overwriting what, is double-clicking on the mod you want the file to come from, and going to the conflicts tab. This will also show you the over-writers. If the file you want to see is shown in either the winning or no conflict part, then it should show up. If it is overwritten by another mod(s), you can see which mods are involved. You then trace back all those mods and hide their version, until your preferred version wins. Oh, and a pro-tip: Don't forget to refresh the MO mod-list after hiding or unhiding files! if you don't refresh, it will still show the old situation. And if you go into the game without refreshing MO, it might even load the old situation. So when ever you chance something, always press the F5 key to refresh. I even press F5 now before going in game, even if I haven't changed anything. Wow. Another book there. I hope this helps you get the Skyrim you want. It is a lot of work, but in the end it is worth it. Oh. I don't know what JoJos Bizarre Adventure is. So no, I am not named after that. It is just a name I made up years ago, when I wanted a change from my usual cow-based names (vachnic, LaVache, BodaciousBovine etc.) You can still see those old names floating around the internet. i.e. vachnic is still my name on the Nexus.

Bring a snack and a drink for the reply. And maybe a blanket for a nap in between. About the projected things: "normal" Skyrim uses a single-pass snow shader, so it doesn't need something like the projected files. Most (if not all) parallax mods use multi-pass snow shaders, so they add the projected-files to make sure snow creation goes well, across all used layers. At least, that is my theory. And I am sticking to it, dammit. Maybe Skyrim 202x doesn't use the multi-pass shaders? Btw, snow shaders are apparently different from snow textures. Who knew? And no, diffuse is not the light effect. The light/ glow effect comes from the _em version. I presume em= emit. I looked up normal map, because I wasn't sure what it is. And now my head hurts... Here is the wikipedia explanation of it. In short it apparently deal with "bumpiness". Alpha mapping regulates how see-through a texture is. I just found an entry on texture mapping on Wikipedia. That should explain a bit about the many different ways and uses, and formats of texture files. Basically more than one kind of texture can be plonked on a mesh.

I am ba-hack! *cracks knuckles for the next chapter* The way you are trying to mix the mods is.. how do I say this politely... flawed. But first a warning about Parallax Mesh Patch Collection Main mod! This mod is old and flawed. It WILL cause crashes. You can still use it if you disable/ delete a number of files: (under spoiler). You can use the parallax patches for Enhanced Vanilla Trees, but then also download this fix, or you will get errors in TexGen and Dyndolod. Better still is to just not use it at all. There are other and newer ways to get the same spread of parallax enabled meshes. So, back to combining mods. The way you are doing it will increase the risk of missing something, which will cause visual weirdness. Best is to install the mods you want and sort them in order of preference. Over the years I have come up with a system, that prevents errors. I am not claiming it is thé way to deal with parallax, but it works for me. I haven't had parallax errors in years. I will post my version below. So the Diavolo™ method is as follows: 1. Follow the STEP System Set Up and SkyrimSE guides first! This will give you a sturdy and stable basis to build on. The SE Guide is in a bit of flux after the surprise Bethesda update. It is still accurate for Skyrim version 1.6.640. If you use 1.6.1130 or 1.6.1170, you can still follow the guide, but be extra careful which version of mods you download. Make sure they are for the correct version of Skyrim! Don't run xLODGEN, TexGen and DynDOLOD yet, because we are adding things!! Once you have a stable installation of Skyrim, you can start adding mods to it. Make a new separator and call it something like "Parallax". Place at the end of the LEFT column, but above any output files (i.e. SKSE Output, FNIS Output, etc). This is where you will put all the parallax mods (obviously). You have to place them last on the left, because the mods here will need to overwrite everything. Start downloading and installing parallax mods, including parallax versions of STEP guide mods. (Enhanced Vanilla Trees, Shaders of Solstheim, Simplicity of Snow if you use it, High Hrothgar fixed). Re-install Embers XD this time enabling the "parallax" tick box. Don't move Embers XD to the parallax section though. Embers will get overwritten by a ton of mods, which is ok. Before doing anything else, Download Lux. Run the Fomod and pick any patches you need for your mod list. When done, open the mod and DELETE all the plugin files, leaving just the meshes and textures folder. These files will act as a replacement for the Parallax Mesh Patch Collection. Since Lux is a lightening mod, the meshes will also cut down on light flicker as an added bonus. Place Lux either last in the Lighting & Weather section, or first in the Parallax section. Next you will have to sort the parallax mods on your personal preference, starting with the AIO mods. i.e. if you prefer the look (as a whole) of Pfuscher's 202x over Skurkbro, move Skurkbro ABOVE 202x, so 202x takes precedence. If you prefer Skurkbro, put 202x above Skurkbro. So the top 3 parallax mods are Lux, 202x and Skurbro. Lux should always be first, the other two are sorted to your preference. These 3 mods are the basis for the parallax part. Together they cover pretty much every mesh and texture. Following the top3, first sort your city/ architecture mods to preference, then trees, mountains and landscapes. Just to be sure: the last mod in a "section" should be the one you prefer or plan to use the most resources from. So least favorite will be overwritten by the ones following. Last of all should be Shaders of Skyrim and Simplicity of Snow (if you use it). The two mods use the previously mentioned projecteddiffuse texture to make sure ash and snow look good. Once you are happy with the loadorder, you have to start weeding the mods. I will use Skurkbro and Skyland as an example. You mentioned you prefer Skurkbro's marshland over Skyland's. So you open Skyland in MO2 and go to the conflicts Tab. Here you will see all detected conflicts between files. in this screen you go find all the Skyland marsh textures (and meshes if applicable). When you find them, right mouse click on them and select "Hide". This will remove Skyland's marshes. Open Skurbro and double check that you got all the marshlands from other mods. If another mod overwrites Skurkbro's marsh, go to that mod and repeat the process of hiding the files in that mod. Do this until Skurkbro's marsh wins, aka no losers to other mods, only winners and no conflicts. And you repeat this process until you are happy with the winners (your preferred mods). Go in game and have a good look around in game, checking if everything turned out like you expected. Make a list of mistakes, errors, wrong textures if you find them, then go back to the mods in MO2 and correct those errors. You may have to unhide textures or meshes to get them back. Do this until you are happy with the results. NOW you can run xLodGen, TexGen and DynDOLOD. You will most likely still get at least one error (in duplicate if I remember correctly) in Dyndolod about a missing parallax texture. I can't remember which mesh it is, but the summary will mention it. To fix it, copy the name of the nif and paste it into MO2's data tab. When it is found, open the mesh with Nifskope. When it is shown (purple), click anywhere on the model in the right screen (it will turn green). This will show a list of thingiemabobs (BSTriShape), click the arrow to open further, keep opening until you see BSShaderTextureSet. Find the missing texture mentioned (woodtrimedge_p I think), double click on the name to select it and just delete that, leaving it empty. It will be in that list twice in two separate BSTrishape fold-outs. Remember to save the NIF! Once that is done, you don't have to re-run the LodGens. You are now ready to enjoy the game. Again, this is the way how I do it. You are of course free to mod however you want. I am just sharing it, because I have never had problems with Parallax and maybe it is helpful to you as well.

Then Pandora seems the way to go, right? Perhaps you can ask on Github how you can make DD work fully with Pandora? I just know the basics of how Pandora works. On the github you can ask the developer him/herself.

Hi Brambleshire. It is indeed quite difficult to find good basic information about the whole parallax process. I have a tiny bit of knowledge about it, that I soft of picked up by reading between the lines so to speak. First of all there are 2 kinds of parallax: the "Old" way and the newer Multilayered/ Complex parallax. It is important to check which kind mods use, because they work very different. To explain the difference a bit, let's start with the textures. Lets start with the easy one: almost every modder has their own snow textures. The projecteddiffuse.dds and projectednormal.dds are used specifically for snow. They are included in the mod, to make sure snow is created the way they envisioned it. The "Old" version uses _p.dds texture files to achieve the parallax effect. This is a special dds-file that has the height information on it (= the parallax effect). So for older parallax mods, you will see a ton of _p.dds files. Sometimes they also uses _para.dds files, but you rarely see those. Diffuse is a layer in .dds files. _em.dds is a glow/ light effect like enb light. There are lot of versions of dds files, which all have specific functions The new Multilayer or Complex parallax works through effects of your ENB or Community Shaders. This works by using the fact that .dds-files have several layers (hence multilayered). In this case it uses the _n.dds files by adding height information to one of the layers. So there is no more need for separate _p.dds files. Occasionally you will still see _p or _para.dds files included. No idea why though. In the case of complex parallax, you have to activate the relevant settings in enb.series. (see under spoiler) Without those options activated, you won't get parallax. No idea how that works. I just consider it magic. The other half of parallax is the meshes. The meshes have to be activated for parallax. The textures are like the clothes of the meshes. If they are missing, you usually get a purple mesh (a naked mesh). When you see that, you know a texture is missing. The parallax "tag" on a mesh will tell the mesh to also expect a parallax texture. If a parallax texture is missing, you generally don't notice immediately. You just won't get the effect. That is what I basically understand about how parallax works. But I could be completely wrong of course. As for the spiky texture: this is a case of the added height information being too strong. It means that you do have a parallax texture on a parallax mesh, but the settings are off. This is most likely caused by using an "old style" on a complex style mesh. I looked in my loadorder, but I couldn't find volcanicdirt01. I did find several volcanictundradirt01, so if you mean that, it is included in all parallax texture landscape mods. In MO2 under the Data tab above the right column, you can copy and paste the file name and MO2 will show you if you have it and if you do, if the name is red, it means several mods have this file. The name in red is the version being used by the game. when you hover over the name, you will see which other mods have that file. You can hide the file that is not working in the mod currently used. The game will then use the next mod. Your first question: if we take the example of Skyland, Skyland - A Landscape Texture Overhaul 2k, this mod has textures and a few meshes, but this is not a parallax enabled mod. Skyland Landscapes Parallax is the mod that adds the parallax enabled textures and meshes to the Texture Overhaul. Skyland was originally released in 2016, before complex parallax became available, so the second mod could be seen as a parallax patch. Atlantean on the other hand only has 1 mod, because it combines textures and meshes in one mod. The mods from Skurkbro come in an AIO (all in one), but he also has the separate mods, for people who want just one or two of his mods. Pfuscher's 202X is again an AIO mod, but split in to several parts, because it is too big for Pfuscher to upload it in one mod. So there are many reasons why there can be more than one version of a mod. And ALWAYS check if a parallax mod is old style or complex style. I have to go run some errands, but I will get back to you on how to merge/ blend different mods. I hope this information (wall of text) is helpful to you.

Hmm, I do know a bit about SexLab, but the whole O-series of mods (Ostim, Obody etc), I know nothing about. So I have no clue how those mods set up animations etc. It could well be that the DD (another mod I know nothing about) animations and assets aren't working as expected because you are trying to combine SL and Ostim. In other words, it may have nothing to do with Pandora. From a quick look at the O-series, it appears to be incompatble with SL? They are different frameworks under the hood. You could test this by disabling everything from the O-series and running Pandora again, to check if it works properly then. If it does, then it probably is a compatibility issue. But again, this is just a theory.