viry2

If you still need the file, I can send it to you, just PM me. can you pm it to me, please? c:

You can check if you have conflicting mods, or the same mods installed with frosty and daimm, seems to me that it might be the case here.

I had this error myself, but it only happened when I tried to import mods in an archive, which wouldn't work 100% of the times, so maybe you can try to unzip the archive and import the contents of it with Frosty. But if you already did, I'm not sure what causes the problem then. Being unable to launch Frosty sounds weird, if you reinstalled it multiple times already. If we're talking about the error mentioned above, it usually crashes Frosty, but I can still start it again. Maybe you need to delete Frosty's data from AppData folder or Program Data. It usually keeps a lot of stuff inside that can interfere, so you can google how to find AppData folder (it's usually hidden) and search for Frosty related files there and delete them, to get a clean installation and try again. I'm not sure that it'll help, but that's the only solution that comes to mind.

After a few hours of attempting to get MM and Frosty working together, I've finally succeeded. First of all, make sure that both Frosty and DAI executable are running with administrator rights. If they aren't, find the respective .exe files, NOT the shortcuts, right click them, choose Properties, in the window that has just popped out, open Compatibility tab, find and check the 'Run this program as an admintrator' box. Then, make sure that your DAI isn't in the 'Read only' state. To check, right click the game folder, open Properties, and in the General tab tick 'Read only' box (tbh I'm not sure that it helped the deal, but still did it just in case). Now, follow the first tutorial in this thread, but I'll add a couple of details from my own experience. Install your mods with Mod Manager, move your original Patch folder somwhere else, change the name of Patch_ModManagerMerge to Patch, delete the ModManager line from the package.mft in the folder that you've just renamed. You don't have to change the patch version number, at least I didn't have to, it worked fine with the Version 15. Now, open FrostyMM (remember that it should be running with administrator rights), add your desired mods, and MAKE SURE that they aren't the same mods that you've already installed with ModManager, otherwise it will result in problems, like freezes and crashes or not starting the game at all. For example, I've installed Solas complexion mod with both MM and Frosty and didn' notice it. Game started, I loaded my save at Skyhold and it worked just fine, but when I started running around to check if evefything's working fine, I walked into the room where Solas usually is, and as soon as I entered the room game just froze and I had to close it with Task Manager. When I removed this mod from the MM patch, it all loaded just fine. When you've imported, applied and arranged your mods, hit Launch. It may take some time and may seem like the process is stuck, when the bar will be filled a little more than the middle, but eventually mod applying window will close and DAI should start running in a few seconds (it usually takes 5-10 seconds on my system). And you don't have to use v1.0.4.2 Frosty, I use v1.0.5.2 and it works. Don't forget to delete your ModData folder before every Launch of the game. But for me it wasn't necessary, it loads normally even with ModData folder. Hope it helps.