I've updated my lod / vfx mod again earlier. Includes more vfx improvements, and also a lot of lod additions. Such as: geralt's armor, scabbards, monsters with hair / fur, animals, etc. Not sure If something similar is already done with that batch lod mod on nexus, though. So may not be compatible, if people are using that.
Also, I've finally been hit with that main char face lod bug that people have been reporting (I couldn't reproduce until now).
It's definitely a game related glitch, because it only happened to me after a certain point in the game (just before starting "The Last Wish" quest. It then cached the bugged lod faces, and it's now bugged also in saves before that, of which were working perfectly until that point.
Seeing as I can reproduce it now, I can work around it. I've had to change up how I do the lod for the main char faces (Geralt is still fine). They don't quite have the cutscene faces in-game anymore, but it's still higher quality than vanilla. But, they work fine, no disturbing, droopy face glitching.
I suspect the Triss lod mod on Nexus doesn't cause the glitch, because it was created before 1.10. It's doing it a bit of a hacky way, in removing things, instead of increasing the range. But I tried doing it that way with current version as a test, and it didn't help.
This has gotten pretty substantial in scope over time. As of the current version, I've hand-done over 600 model lod & VFX files, thus far.
If anyone wants the latest, here it is;
modLodAndFX_1.52 <- Lod, and VFX changes
modVisualFX_1.52 <- VFX changes only
Also, I've finally been hit with that main char face lod bug that people have been reporting (I couldn't reproduce until now).
It's definitely a game related glitch, because it only happened to me after a certain point in the game (just before starting "The Last Wish" quest. It then cached the bugged lod faces, and it's now bugged also in saves before that, of which were working perfectly until that point.
Seeing as I can reproduce it now, I can work around it. I've had to change up how I do the lod for the main char faces (Geralt is still fine). They don't quite have the cutscene faces in-game anymore, but it's still higher quality than vanilla. But, they work fine, no disturbing, droopy face glitching.
I suspect the Triss lod mod on Nexus doesn't cause the glitch, because it was created before 1.10. It's doing it a bit of a hacky way, in removing things, instead of increasing the range. But I tried doing it that way with current version as a test, and it didn't help.
This has gotten pretty substantial in scope over time. As of the current version, I've hand-done over 600 model lod & VFX files, thus far.
If anyone wants the latest, here it is;
modLodAndFX_1.52 <- Lod, and VFX changes
modVisualFX_1.52 <- VFX changes only
Last edited:
^Can you also release a fx version only as well like you did before? Just in case we have conflicts with the big lod mod on nexus.
Or, actually how much lod does your mod cover? Is it worth using over the big lod mod on nexus?
Or, actually how much lod does your mod cover? Is it worth using over the big lod mod on nexus?
I'll check that out tomorrow, thanks for reporting. I'm pretty sure I know what's causing it. Once that bug crops up, the altered lod values for faces, and facial hair become ridiculously precarious.
I'm actually getting bloody disturbed looking at these gnarly glitches so much lol.
I'll upload a VFX only version once I've sorted some of the lod stuff.
I'm actually getting bloody disturbed looking at these gnarly glitches so much lol.
I'll upload a VFX only version once I've sorted some of the lod stuff.
You tried it with a new save or an old one? Because with the files i've edited the faces are working fine before and after that quest ( an old save patch 1.07)It's definitely a game related glitch, because it only happened to me after a certain point in the game (just before starting "The Last Wish" quest. It then cached the bugged lod faces, and it's now bugged also in saves before that, of which were working perfectly until that point.
It only seems to happen once you reach a certain point in the MQ after 1.10. Loading save files past that point that are before 1.10, may not show it. But you could try loading that file, then saving it in another slot, to see if it's present.You tried it with a new save or an old one? Because with the files i've edited the faces are working fine before and after that quest ( an old save patch 1.07)
The problem seems to be related to the rigging / skeleton. I can't fathom wtf causes it the freak out though. I really can't see any reason for rigging changes once you pass a point in the game.
---------- Updated at 09:20 PM ----------
Updated the links from the quoted post. All faces should be sorted now. I made them the highest quality I could, without triggering that annoying ( terrifying lol ) glitch. I swapped out aspects / features for hq eyes, skin, hair, body etc, but I couldn't extend the range of the lod 0 (cutscene) faces, or it would just go berzerk. Still looks nicer than default, though.
I upped the VFX only version as well.
I've updated my lod / vfx mod again earlier. Includes more vfx improvements, and also a lot of lod additions. Such as: geralt's armor, scabbards, monsters with hair / fur, animals, etc. Not sure If something similar is already done with that batch lod mod on nexus, though. So may not be compatible, if people are using that.
Also, I've finally been hit with that main char face lod bug that people have been reporting (I couldn't reproduce until now).
It's definitely a game related glitch, because it only happened to me after a certain point in the game (just before starting "The Last Wish" quest. It then cached the bugged lod faces, and it's now bugged also in saves before that, of which were working perfectly until that point.
Seeing as I can reproduce it now, I can work around it. I've had to change up how I do the lod for the main char faces (Geralt is still fine). They don't quite have the cutscene faces in-game anymore, but it's still higher quality than vanilla. But, they work fine, no disturbing, droopy face glitching.
I suspect the Triss lod mod on Nexus doesn't cause the glitch, because it was created before 1.10. It's doing it a bit of a hacky way, in removing things, instead of increasing the range. But I tried doing it that way with current version as a test, and it didn't help.
This has gotten pretty substantial in scope over time. As of the current version, I've hand-done over 600 model lod & VFX files, thus far.
If anyone wants the latest, here it is;
modLodAndFX_1.52 <- Lod, and VFX changes
modVisualFX_1.52 <- VFX changes only
Last edited:
Asmodean, what lods does your mod cover? I want to know if I should use it with different mods. The large increased Lod mod also comes in individual packs: characters, environment, architecture. Holgar96 also just released a lod mod for all characters in the game.
Well, the faces aren't fixed. I double checked them all before uploading, but now it's after happening again. >.> After progressing further on Yen's got that bug again. I'll have to relook yet again.
#Edit: Now I know why I didn't notice it. Whatever I did, the bug only appears from a distance now, whenever you get closer to them, it switches to normal. I might be on to something.
@RasAlgethi24 if you extract the mod using quickbms you can see all of the files I am modifying.
#Edit: Now I know why I didn't notice it. Whatever I did, the bug only appears from a distance now, whenever you get closer to them, it switches to normal. I might be on to something.
@RasAlgethi24 if you extract the mod using quickbms you can see all of the files I am modifying.
Last edited:
You could use all of them, like i do, and set their priority as you wish.Asmodean, what lods does your mod cover? I want to know if I should use it with different mods. The large increased Lod mod also comes in individual packs: characters, environment, architecture. Holgar96 also just released a lod mod for all characters in the game.
Right, found out how to finally prevent that issue. It seems you're ok to change mostly everything except the renderLODs, and the glitch doesn't occur. At first I thought it was only lod values with a default of 0, but then the bug occured when you were further away from the characters.
So, for anyone wondering - you can edit the material calls (the hq mats used, instead of the lq lod ones) but you can't try altering the renderLOD ranges at all. That's definitely what's causing all of these problems.
I'll have a fix up in a bit.
---------- Updated at 03:05 AM ----------
Updated the link in this post.
Man, it has become quite the chore to mod this game.
So, for anyone wondering - you can edit the material calls (the hq mats used, instead of the lq lod ones) but you can't try altering the renderLOD ranges at all. That's definitely what's causing all of these problems.
I'll have a fix up in a bit.
---------- Updated at 03:05 AM ----------
Updated the link in this post.
Man, it has become quite the chore to mod this game.
Last edited:
Just tried your latest lodandfx version and I can confirm I am no longer getting the face bug! Great work. So much better than vanilla.
I have like 400+conflicts though between your mod and increased lod but I guess it should be ok as long as I set their alphabetical priorities correctly.
I have like 400+conflicts though between your mod and increased lod but I guess it should be ok as long as I set their alphabetical priorities correctly.
Last edited:
Ta for the confirmation. Yeah, typically speaking asset conflicts (as in, not script ones) are fine, as long as you've got them loading in the order you want them to. Just load to big batch lod mod first, then load mine after it.Just tried your latest lodandfx version and I can confirm I am no longer getting the face bug! Great work. So much better than vanilla.
I have like 400+conflicts though between your mod and increased lod but I guess it should be ok as long as I set their alphabetical priorities correctly.
To confirm I have your mod named as "modYlodandfx" and the large lod mod as "modzzzlodall". Your mod should take priority over that one right?Ta for the confirmation. Yeah, typically speaking asset conflicts (as in, not script ones) are fine, as long as you've got them loading in the order you want them to. Just load to big batch lod mod first, then load mine after it.
Yeah. Apparently it's ascending load order, so A has a higher priority than B for example, and so on. I haven't really looked in-depth into the load order stuff though, because I've got no conflicting stuff. As I've done most of it myself lol.To confirm I have your mod named as "modYlodandfx" and the large lod mod as "modzzzlodall". Your mod should take priority over that one right?
If the name-based load order actually works as intended, then you should be able to clearly see what order the mods are loading, if you view the contents of the mods folder by: details, and sort them by name. The mod folders will be sorted in the same order they should load.
Sounds great Asmodean. Going to test the update once I'm home.
For the load order: There are basically two ways of doing it:
Either you abuse the alphanumerical load order scheme as stated above, or you are using the mods.settings file:
For those who are interested, it works like this:
The mods.settings is an optional file responsible for simple mod settings (on/off, mod priorities). Should be placed in:
C:\Users\[user_name]\Documents\The Witcher 3\mods.settings
For each mod you need an entry which is structured like this:
ascending descending order.
Or simpler: the higher the file in the list, the more will you see of it.
Personally I am using a mods.settings file, as it gives me full control over what mods - even parts - are loaded.
For those of you who are form the TES/Fallout community - think of it as an ordinary (but optional) load order.
This file can easily be used for a mod managing tool - which I am currently working on for my launcher by the way - to ensure you are gettign the files you want.
Simple example: You are using a LOD mod for characters, modLODCharacters for example and a texture replacer for Triss, modAwesomeTriss for example. The retexturing mod also edits the LOD files, so there are no inconsistencies when moving further away from Triss in game. but right now the mods would be loaded like this:
But in this case the LOD mod would overwrite the files provided by the retexture mod. This would result in having the retextured Triss close up, but vanilla Triss from further away.
Now we use the mods.settings file:
Now we just told the game to use the Triss mod with highest priority, which means it's loaded LAST (not to be confused here, the lower the number, the higher the priority, the later the file gets loaded. The result? We have awesome character LOD for all characters, but still can use Triss' retexture and actually see it in game. Remembering this and using Script Merger can basically make any mod compatible - logic conflicts of course excluded.
For the load order: There are basically two ways of doing it:
Either you abuse the alphanumerical load order scheme as stated above, or you are using the mods.settings file:
For those who are interested, it works like this:
The mods.settings is an optional file responsible for simple mod settings (on/off, mod priorities). Should be placed in:
C:\Users\[user_name]\Documents\The Witcher 3\mods.settings
For each mod you need an entry which is structured like this:
Mods which do not appear in the mods.settings file are enabled by default and are loaded in alphanumerical[modName1] ← name of the mod in square brackets
Enabled=1 ← 0 or 1, 1 means the mod is enabled and 0 turns it off
Priority=100 ← from 0 to 9999, lower number means higher priority, eg.: 5 before 8
[modName2] ← the same for all mods installed
Enabled=1
Priority=100
Or simpler: the higher the file in the list, the more will you see of it.
Personally I am using a mods.settings file, as it gives me full control over what mods - even parts - are loaded.
For those of you who are form the TES/Fallout community - think of it as an ordinary (but optional) load order.
This file can easily be used for a mod managing tool - which I am currently working on for my launcher by the way - to ensure you are gettign the files you want.
Simple example: You are using a LOD mod for characters, modLODCharacters for example and a texture replacer for Triss, modAwesomeTriss for example. The retexturing mod also edits the LOD files, so there are no inconsistencies when moving further away from Triss in game. but right now the mods would be loaded like this:
- modAwesomeTriss
- modLODCharacters
But in this case the LOD mod would overwrite the files provided by the retexture mod. This would result in having the retextured Triss close up, but vanilla Triss from further away.
Now we use the mods.settings file:
[modAwesomeTriss]
Enabled=1
Priority=1
[modLODCharacters]
Enabled=1
Priority=100
Now we just told the game to use the Triss mod with highest priority, which means it's loaded LAST (not to be confused here, the lower the number, the higher the priority, the later the file gets loaded. The result? We have awesome character LOD for all characters, but still can use Triss' retexture and actually see it in game. Remembering this and using Script Merger can basically make any mod compatible - logic conflicts of course excluded.
Last edited:
^Regarding the alphanumerical priority, lower means higher priority or lower priority? If I have two files:
modzzzlod
modlodandfx
Which takes priority? I thought zzzlod gets lowest priority.
2nd questions, if I make a mod.settings file do I have to include every mod in my mod folder or can I just include the mods I want to set priority for?
modzzzlod
modlodandfx
Which takes priority? I thought zzzlod gets lowest priority.
2nd questions, if I make a mod.settings file do I have to include every mod in my mod folder or can I just include the mods I want to set priority for?
In this case modzzzlod has a lowest priority. I know because I did some tests with other textures mods and the one with "lower" alphabet letter was the one who worked.
I do not use mod.settings but I believe you only need to include conflicting mods.
I do not use mod.settings but I believe you only need to include conflicting mods.
@RasAlgethi24:
@PeLLeT_RSD is right. The mods get loaded in ascending alphabetical order.
You don't have to include all mods in the mods.settings file. Only the ones you want to load in an explicit order.
Quoting myself here:
@PeLLeT_RSD is right. The mods get loaded in ascending alphabetical order.
You don't have to include all mods in the mods.settings file. Only the ones you want to load in an explicit order.
Quoting myself here:
Mods which do not appear in the mods.settings file are enabled by default and are loaded in alphanumerical descending order.
Last edited: