113 note(s)
Updated my fix post on reddit to share the good news!
Thank goodness for Zhen and everyone who made this possible! A permanent fix for a patch this quick is amazing!
I just used MM v0.50 and I think I'm going to cry. It's so beautiful.
EDIT: Seriously, my GTX 970 will be arriving in the mail any day now, I got the Witcher 3 for free, Black Emporium is out tomorrow and a new fast, sleek, and sexy Manager. It's like freaking Christmas right now!
Thank you Zhentar and all the other amazing modders for get ModManager up and running! Had no issues at all merging all my mods (including the MoreLootFlex and Increased Capacity mods that were always causing issues) HUZZAH!
EDIT: Do we need to remove the original patch folder or rename it? Merging went flawlessly, but the mods aren't working. So I'll try removing the vanilla patch see if that works
u shouldn't have to remove anything, the new mod manager will create an automatic folder in ur update folder and it *should* work fine with ur mods let me know if u have any further issues
*snip*
EDIT: Do we need to remove the original patch folder or rename it? Merging went flawlessly, but the mods aren't working. So I'll try removing the vanilla patch see if that works
Yea, as tklivory pointed out, its the older mods that never made into daimods (and unfortunately I don't know how to do that). So some are working, some are not.
I'm half way there! lol. So, its an issue on my end I guess you could say. So excellent job and Kudos! 
Yea, old mods won't work unless u notify the modder who made those mods to update their files or u can do it ur selves via DAImodding tool .
The mod manager wont recognize some of the old mods be it texture or config mods there are just old code that doesn't "mesh" well with the new code that the new patches have.
Althou Personally I haven't tested the DAi MODDING TOOL to see if it actually works with the new patch.... so if u guys would be kind enough to do so let me know if there are any issues and I will notify Dan to fix it.
In short Zhenthar is the guy who fixes the mod manager and Dan is the one who fixes the DAIModdingTool
Thank you for your update tklivory I will let Dan know of the issue and hopefully he will have it fixed soon
Anyone updated to patch 7 that has tried if the tool SRWE works correctly yet?
(Just got around to computer so i might have missed info about it tho..)
Anyone updated to patch 7 that has tried if the tool SRWE works correctly yet?
(Just got around to computer so i might have missed info about it tho..)
Anyone updated to patch 7 that has tried if the tool SRWE works correctly yet?
(Just got around to computer so i might have missed info about it tho..)
The SRWE hasn't been working since patch 6 I believe .. so whoever made that tool needs to be notified of the issue with the new patches... there is nothing we can do here the coders will only be focusing on DAIModdingtool and Modmanager.. anything beyond that is not our problem
The SRWE hasn't been working since patch 6 I believe .. so whoever made that tool needs to be notified of the issue with the new patches... there is nothing we can do here the coders will only be focusing on DAIModdingtool and Modmanager.. anything beyond that is not our problem
Ah yeah, this is the reason why iam still rolled back safe on patch 5
Its a tool i prefer alot - Was thinking it maybe magicly was working again... Why i asked the ppl here that actually patched ^^
That its not related to the mods or our tools for em i know
Sadly, the problem persists. You can change the size of the window, but the resolution remains native.
Yeah, figured it would persist, but didnt wanna let go of the hope!
Guess ill give WBG a tryout then!
Hello! New to the group, so apologies if this is out of line or in the wrong spot. Or if there's a fix already, I have done some digging but come up with nothing.
As patch 7 killed my mods, I was overjoyed to see the v0.50 update to the Mod Manager, and downloaded it immediately. But I've run into a major snag: the patch merges beautifully, the mods work as before... but anytime I try to do anything Jaws of Hakkon related (visit the Frostback Basin, for example) the game crashes to desktop.
It's definitely something to do with the mods, as removing the new handy-dandy Patch_ModManagerMerge folder fixes the crashing. I'm only using a handful of texture mods (those Skyhold pyjamas, ugh) and they're the newer .daimod filetype.
I'm running v0.50 in administrator mode, and I'm not getting any kind of error message in the Mod Manager itself... any ideas?
I was gonna try out modding some hair but I cannot get DAI Modding Tool to finish searching for assets. It gets to almost the very end and crashes:
"DAI Modding Tool has stopped working...""
It seems to be happening when it is scanning the official patch
I took JOH out of the update folder.
I copied the ini from the old tool.
Has anyone successfully run a new scan since P7? I assume everyone would be using the old caches which guess is fine as long as you're not modding something the latest patch changes. Or maybe it wouldn't... I don't know.
THANK YOU SO MUCH!!!! 
My game is working perfect with newest patch and all my mods
Hello! New to the group, so apologies if this is out of line or in the wrong spot. Or if there's a fix already, I have done some digging but come up with nothing.
As patch 7 killed my mods, I was overjoyed to see the v0.50 update to the Mod Manager, and downloaded it immediately. But I've run into a major snag: the patch merges beautifully, the mods work as before... but anytime I try to do anything Jaws of Hakkon related (visit the Frostback Basin, for example) the game crashes to desktop.
It's definitely something to do with the mods, as removing the new handy-dandy Patch_ModManagerMerge folder fixes the crashing. I'm only using a handful of texture mods (those Skyhold pyjamas, ugh) and they're the newer .daimod filetype.
I'm running v0.50 in administrator mode, and I'm not getting any kind of error message in the Mod Manager itself... any ideas?
Okay, I think I figured this out...
Look in your Patch_ModManagerMerge folder and there should be a “DataWin32” folder. Move those files to “Patch_ModManagerMerge/Data/Win32” and the DLC should work. That stopped the crash for me, at least
yes please if u dont mind, the more ideas the merrier
I have been saying elsewhere that I need someone to make me a Samuel L. Jackson in Pulp Fiction hair mod, for....reasons.
Hello! New to the group, so apologies if this is out of line or in the wrong spot. Or if there's a fix already, I have done some digging but come up with nothing.
As patch 7 killed my mods, I was overjoyed to see the v0.50 update to the Mod Manager, and downloaded it immediately. But I've run into a major snag: the patch merges beautifully, the mods work as before... but anytime I try to do anything Jaws of Hakkon related (visit the Frostback Basin, for example) the game crashes to desktop.
It's definitely something to do with the mods, as removing the new handy-dandy Patch_ModManagerMerge folder fixes the crashing. I'm only using a handful of texture mods (those Skyhold pyjamas, ugh) and they're the newer .daimod filetype.
I'm running v0.50 in administrator mode, and I'm not getting any kind of error message in the Mod Manager itself... any ideas?
Try this, I think it will fix the problem:
The new Mod Manager takes the problematic files that were killing the previous ModManager and puts them into a folder called ‘DataWin32′ in the newly made Patch folder. To restore those DLC files, follow these steps:
Screenshot: 
I was gonna try out modding some hair but I cannot get DAI Modding Tool to finish searching for assets. It gets to almost the very end and crashes:
"DAI Modding Tool has stopped working...""
It seems to be happening when it is scanning the official patch
I took JOH out of the update folder.
I copied the ini from the old tool.
Has anyone successfully run a new scan since P7? I assume everyone would be using the old caches which guess is fine as long as you're not modding something the latest patch changes. Or maybe it wouldn't... I don't know.
Nope, the Modding Tool is broken, and Dan is aware of the issue and it working on it. Until it is fixed, I'd recommend just having Patch 6 handy and using it until the Modding Tool fixed.
Just like with previous releases, I would imagine that something is encrypted and trying to read it is crashing the Modding Tool.
Quick update:
Black Emporium is out. People are reporting that it is breaking mods, as in: CTD when trying to go to the Emporium when the mod is installed, or the mods simply don't work.
The package.mft file in the BE folder is encrypted, as are the files, just like the Jaws of Hakkon DLC.
Will update after some further testing.
Mod manager fix is here !!!! Thnax to zhentar!!!! here is the link http://www.mediafire.../ModManager.zip
Great news, Adela!
So I was able to get the Black Emporium and mods working without issues (SO FAR). I had to do a bit of chicanery to do it, though.
When I first attempted to play DAI with mods after merging them with the fresh new ModManager V.50, it CTD - wouldn't even open the game, actually. Figuring I had corrupted files, I removed the mods completely, put my copy of P7 files into the Update folder, and did a full Repair, which took a while.
After that, I put the patched folder in as 'Patch' and did NOT leave the vanilla folder in. I also incremented the version of the package.mft in the modded Patch folder by one. After that, I was able to see my mods, use the Black Emporium and the mirror, and craft, all without issue. However, I didn't get to play a lot.
I think repairing the files might be key before using mods with the BE installed.
One thing I DID note was that the modded hair did NOT show up in the BE CC. However, I only had a female Qunari of the four origins with hair mods who have gotten to Skyhold, so I can't verify with any elves or female humans. Can someone else verify this?
After repairing my game and using the newest version of the ModManager, everything merged fine. Game started fine, mods worked. Until I tried entering the BE, it continues to freeze and I have to Ctrl+Alt+Delete out of the game. I removed all outdated mods, so next step will be merging them one and a time to see if its one specific mod or just mods in general that are causing the freezing issue
Someone on Tumblr verified that the female elf hair mods don't show up in the Black Emporium either. So, that means (to me at least) that the BE CC must not use the Lod 0 layers like the opening CC does, which is... weird, but hey, at least it's a known issue.
And I'm probably going to hate myself in the morning for this, but I made a place for people to report issues about DAI mod stuff, just to centralize it. We'll see if it works, anyway. It can be found here, if anyone is interested. Very barebones at the moment, but it might be a good way to learn about issues and put word out about new mods without exposing the modders here or at the DAI Tools forum to too many trolls like we've seen.
So I was able to get the Black Emporium and mods working without issues (SO FAR). I had to do a bit of chicanery to do it, though.
When I first attempted to play DAI with mods after merging them with the fresh new ModManager V.50, it CTD - wouldn't even open the game, actually. Figuring I had corrupted files, I removed the mods completely, put my copy of P7 files into the Update folder, and did a full Repair, which took a while.
After that, I put the patched folder in as 'Patch' and did NOT leave the vanilla folder in. I also incremented the version of the package.mft in the modded Patch folder by one. After that, I was able to see my mods, use the Black Emporium and the mirror, and craft, all without issue. However, I didn't get to play a lot.
I think repairing the files might be key before using mods with the BE installed.
One thing I DID note was that the modded hair did NOT show up in the BE CC. However, I only had a female Qunari of the four origins with hair mods who have gotten to Skyhold, so I can't verify with any elves or female humans. Can someone else verify this?
So back to using the former use merged patch as official patch? That's manageable I guess but I'm leery of changing the patch version number as it will tie the save game to that number.
If it gets fixed the standard modded patch number will be 9 (If you upped it, it must have been to 10 yes?)
Retour en haut