Frosty mod file have been updated with the latest Frosty Editor (1.0.5.3). This means you'll find only a .frostymod file now, no archive! --------------------------------- ! Update ! (2019 12 09) Frosty mod file have been updated with the latest Frosty Editor (1.0.5.7).
Please read before commenting! I’m always happy to help but I don’t like repeating myself.
Your mod doesn’t work!!! What should I do? Do you happen to use Frosty & DAIMM together? If yes, there’s your answer. Skip to the next section.
Did you try to load ONLY my mod and see if it works? If not, do it now. If it works now it means it’s conflicting with another mod you have.
Always make sure you use the correct version of Frosty MM!!
General information about using Frosty & DAIMM together First of all, you should understand that Frosty and the old tools were not meant to be used together in the first place. You can’t predict which mods will conflict and cause trouble in your game so you’ll have to experiment what setup (ie what combination of daimods & frosty mods) works for you yourself.
Once you decide to mod your game with both it's your responsibility. You can’t blame the mod authors if something doesn’t work; in this case it’s not their fault but your setup’s.
If you don’t like the hassle either stick to Frosty or DAIMM.
If you’d still like to try please follow this tutorial. This is the correct way to do it!!
Frosty can handle .daimods!!! Lot of people seem to forget about this but you don’t have to convert every single mod to .frostymod!
Some mods SHOULD BE left in .daimods in fact. (For example eyebrow textures will become weird blurry messes if you convert them to Frosty.)
Mesh edits (ie all the old hair mods), gameplay changes (like “War Table – No Waiting”) & ebx edits (ie skill edits, color changes etc etc) are perfectly fine* left in .daimod and loaded directly into Frosty MM. *Some exceptions might occur, but it's rare in my experience.
Texture mods & configurable mods are the only exceptions. Texture mods can be hit and miss. They can sometimes work too but most of the time they probably will be glitching out. Configurable mods just crash Frosty.
You can find more information about this topic on my blog.
It doesn't seem to work in the Hinterlands (unsure about Val Royeaux, I know some mods behave weirdly there too), but I've had no problems otherwise, and I love the tattoo. It's easy enough to just disable it in the Hinterlands and reenable it afterwards.
I'm sorry but without specifics I can't help. Are you using the latest Frosty MM? Frosty alone or with the DAIMM? What's your mod setup? Did you try to load my mod alone on a clean game?
Sorry, I ended up super busy yesterday so I didn't experiment much more. It worked throughout the prologue and works in Haven, I'm using the latest Frosty and DAIMM. I haven't tried loading your mod alone yet but will do that next time I have time to play. What I did find is that all my other mods work, but as soon as I enable this one outside Haven, cutscenes stop working (the meeting with Mother Giselle and Bull's recruitment). Weirdly, Scout Harding's initial cutscenes worked fine. In the Hinterlands it became completely invisible during exploration, like I had no tattoo at all. The cutscenes would work normally up until it was my character's turn to speak, at which point the dialogue wheel would fail to show up. By pressing the skip button repeatedly at Mother Giselle, I got the first dialogue option to show up, but my character's face was blotchy all over in the color of her tattoo (dark red), like the texture had just been smeared on her face. After that, my character's dialogue and Giselle's were unvoiced, though subtitles still worked. Also, my character's position in the cutscene kept jumping back and forth. I had to force quit the game to exit the scene. Trying a second time got the same result, which is when I remembered the complexion glitch and wondered if something similar might be at play. Disabling the tattoo immediately got everything working. I left it off for the rest of the Hinterlands and into Val Royeaux and recruiting Sera, Vivienne, and Blackwall. I enabled it again at Haven before going to the Storm Coast for Iron Bull, but as soon as the cutscene started with him, I had the same error of the dialogue wheel not showing up. In this case, the camera never cut to my character, so I don't know if her face was all blotchy. Cutscenes for the prologue and in Haven work perfectly, but exploration areas, at least the Hinterlands and Storm Coast, just seem to have bizarre glitching.
Also, I have no other mods altering my character's face and head other than a Frosty hair mesh and a Frosty hair texture mod. No complexions or eye textures. I'm using Enhanced Inquisitor Colors but not Enhanced Inquisitor Sliders, so my complexions are completely vanilla.
It's a beautiful tattoo, and since no one else has reported these problems I'm entirely willing to believe it's something unfortunate going on with my computer, but if I can get it working I would love to continue to use it.
Thank you for the detailed explanation. I don't know what daimods you're using but I suggest you go through them first because something (or multiple things) are clearly conflicting with Frosty.
You should understand that Frosty and the old tools were not meant to be used together in the first place so once you decide to mod your game with both it's your responsibility to figure out what mods do and don't work together. The more daimods you use, the higher the probability that something will conflict and cause problems in your game.
And most importantly the first thing you should do before reporting a bug is to test the "offending" mod solely on a clean game how it's meant to be used in the first place. Thank you.
I reinstalled Inquisition to test this again and it worked perfectly fine.
I'm sorry, but I have the same problem. I tried removing ALL other mods except this one, but to no avail. And it happens everywhere (most often in Val Royeaux and Caer Bronach), except maybe for Skyhold, the Black Emporium and probably Haven, too (I don't remember now).
30 comments
---------------------------------
! Update ! (2019 12 09)
Frosty mod file have been updated with the latest Frosty Editor (1.0.5.7).
IMPORTANT
Your mod doesn’t work!!! What should I do?
Do you happen to use Frosty & DAIMM together? If yes, there’s your answer. Skip to the next section.
Did you try to load ONLY my mod and see if it works? If not, do it now. If it works now it means it’s conflicting with another mod you have.
Always make sure you use the correct version of Frosty MM!!
General information about using Frosty & DAIMM together
First of all, you should understand that Frosty and the old tools were not meant to be used together in the first place.
You can’t predict which mods will conflict and cause trouble in your game so you’ll have to experiment what setup (ie what combination of daimods & frosty mods) works for you yourself.
Once you decide to mod your game with both it's your responsibility. You can’t blame the mod authors if something doesn’t work; in this case it’s not their fault but your setup’s.
If you don’t like the hassle either stick to Frosty or DAIMM.
If you’d still like to try please follow this tutorial. This is the correct way to do it!!
Frosty can handle .daimods!!!
Lot of people seem to forget about this but you don’t have to convert every single mod to .frostymod!
Some mods SHOULD BE left in .daimods in fact. (For example eyebrow textures will become weird blurry messes if you convert them to Frosty.)
Mesh edits (ie all the old hair mods), gameplay changes (like “War Table – No Waiting”) & ebx edits (ie skill edits, color changes etc etc) are perfectly fine* left in .daimod and loaded directly into Frosty MM.
*Some exceptions might occur, but it's rare in my experience.
Texture mods & configurable mods are the only exceptions.
Texture mods can be hit and miss. They can sometimes work too but most of the time they probably will be glitching out.
Configurable mods just crash Frosty.
You can find more information about this topic on my blog.
Are you using the latest Frosty MM? Frosty alone or with the DAIMM? What's your mod setup? Did you try to load my mod alone on a clean game?
Also, I have no other mods altering my character's face and head other than a Frosty hair mesh and a Frosty hair texture mod. No complexions or eye textures. I'm using Enhanced Inquisitor Colors but not Enhanced Inquisitor Sliders, so my complexions are completely vanilla.
It's a beautiful tattoo, and since no one else has reported these problems I'm entirely willing to believe it's something unfortunate going on with my computer, but if I can get it working I would love to continue to use it.
I don't know what daimods you're using but I suggest you go through them first because something (or multiple things) are clearly conflicting with Frosty.
You should understand that Frosty and the old tools were not meant to be used together in the first place so once you decide to mod your game with both it's your responsibility to figure out what mods do and don't work together. The more daimods you use, the higher the probability that something will conflict and cause problems in your game.
And most importantly the first thing you should do before reporting a bug is to test the "offending" mod solely on a clean game how it's meant to be used in the first place. Thank you.
I reinstalled Inquisition to test this again and it worked perfectly fine.
Upd: Chargen Bundle seems to fix it!
I love how it looks on my Carta assassin. Hope you like the image