Thanks for sharing, dude. This is why I hate dialogue wheels. I really hope they return to the Origins style dialogue for DA4, but I doubt they will :/
I mean I guess they meant to simplify it and make the dialogue UI look more sleek, but it comes off as lazy. DAI is the worst in Bioware's game catalogue when it comes to not being clear what the dialogue options contain.
Hi there! I just downloaded this mod and when I tried to run it for the first time, it spat out an 'Unhandled exception has occurred' message at me then crashed Frosty. I'm not sure what to do to fix it, since I'm new to using mods. I added it to my Frosty the same as any of my other mods and have had no problems with the others. So I'm hoping you might know what I'm doing wrong.
This is the dialogue box that popped up: (this site won't let me put a screen up so here's the text instead.) Thanks!
?Object reference not set to an instance of an object. at Frosty.ModSupport.FrostyModExecutor.ProcessModResources(IResourceContainer fmod) at Frosty.ModSupport.FrostyModExecutor.Run(FileSystem inFs, CancellationToken cancelToken, ILogger inLogger, String rootPath, String modPackName, String additionalArgs, String[] modPaths) at FrostyModManager.MainWindow.<>c__DisplayClass13_0.<launchButton_Click>b__0(FrostyTaskWindow task) at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Frosty.Core.Windows.FrostyTaskWindow.<FrostyTaskWindow_Loaded>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
it seems this mod requires the bioware localization plugin, download the main file from the link, unzip it, and place the BiowareLocalizationPlugin.dll it produces into the Plug-ins folder of your frosty mod manager folder. that should resolve the error.
For some reason this (and some other mods) are simply not working for me in game.
I have Frosty Mod Manager 1.0.6.0 (BETA 5) Im running the game via that and EA desktop app. Only SOME of the mods on my "Applied mods" list activate in the game.
When trying to launch the game via FrostyFix v5.2.1 it simply directs me to EA desktop app. If I then try launch the game from there (EA desktop app) it tries to launch the game, but then just shows that the game is running (in background) but im unable to access it. The process is open in task manager, but its not visible anywhere.
It has become quite finnicky with the new EA Desktop App. You have to enable Platform Launching and choose the correct Platform (in your case EA Desktop). It is in the options menu under Launch Options in Frosty Mod Manager. You will also have to make sure Frosty Mod Manager is launched with admin privileges.
Thanks to Discord I got the game running. I was using 1.0.6.0 (BETA 5) version of the mod manager instead of the stable release. Somehow the website frostytoolsuite.com directs straight to the beta version download, instead of the stable....
Does this mod play nicely with the multi romance and bi mods ?
I noticed when using Apomorph's mod that some of the romance options were not available. (When romancing Cassandra as a female qunari mage, some of the romance dialogue options would not appear).
It doesn't look like they do. I've tried the 'Bi Cassandra' one and I didn't get it to work. I'm sorry. If I knew how to make a patch properly with Frosty, then I'd try, but I don't want to tinker too much with other modder's mods.
33 comments
This is the dialogue box that popped up: (this site won't let me put a screen up so here's the text instead.) Thanks!
EDIT: Also concerned that it doesn't allow the added dialogue options from DWO to come through. Any idea?
I have Frosty Mod Manager 1.0.6.0 (BETA 5)
Im running the game via that and EA desktop app.
Only SOME of the mods on my "Applied mods" list activate in the game.
When trying to launch the game via FrostyFix v5.2.1 it simply directs me to EA desktop app.
If I then try launch the game from there (EA desktop app) it tries to launch the game, but then just shows that the game is running (in background) but im unable to access it.
The process is open in task manager, but its not visible anywhere.
Any ideas?
You have to enable Platform Launching and choose the correct Platform (in your case EA Desktop).
It is in the options menu under Launch Options in Frosty Mod Manager.
You will also have to make sure Frosty Mod Manager is launched with admin privileges.
Hope it works.
I was using 1.0.6.0 (BETA 5) version of the mod manager instead of the stable release.
Somehow the website frostytoolsuite.com directs straight to the beta version download, instead of the stable....
Now this mod is working as it should.
I noticed when using Apomorph's mod that some of the romance options were not available.
(When romancing Cassandra as a female qunari mage, some of the romance dialogue options would not appear).