Hey, I know it's been forever since this game/mod came out but I just hit this bug and am looking for a fix. I think it's coming from the "Data Trail" quest. I tried downloading the .fbproject and editing it myself but I've never used Frosty Editor before so am having a little trouble. Any tips/help would be appreciated!
Love the concept of this mod, but I think it may need to be looked at once again. My game version is 1.10 and I tried to use this to get rid of the annoyingly persistent (!) in the journal using this mod, but it still remains. I did notice that there were a few other quests that also 'popped' being read, to include "Cold Hard Cache", "Kadera's Ransom", "Beer Run", and "Data Trail" to name a few, but its possible that these simple were not read by me in the completed category prior to installing the mod, since they were recently completed by me in the game. If you need more data, please let me know. More than willing to help test out solutions.
My persistent (!) started soon after arriving on Voeld. I've been through every mission in the list, completed or not, and waited on each one to let it pop and nothing makes the (!) disappear.
Shame. I was really hoping this would sort it out for me.
P.S. After playing NG+, I kept an eye on my Journal making sure that it was cleared the whole time. "Task: Data Trail" on EOS is the mission that bugged me out this time. Seeing as how I was now bugged there was no way to see which mission on Voeld bugged last time.
Please let me know if it worked for you or not. It is probably possible to expand the mod to cover all potentially bugged quests and do away with the problem once and for all.
If you have a problematic save game or a good idea about which quest is causing the problem for you, drop a post and we´ll see what we can do about it. =)
at System.Security.Cryptography.HashAlgorithm.ComputeHash(Byte[] buffer) at FrostySdk.Utils.GenerateSha1(Byte[] buffer) at Frosty.ModSupport.FrostyModExecutor.<>c__DisplayClass17_0.<Run>b__0() 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.ModSupport.FrostyModExecutor.<Run>d__17.MoveNext() --- 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 FrostyModManager.MainWindow.<launchButton_Click>d__12.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)
Hmm... That is peculiar. I´m unable to reproduce this error. I just downloaded my mod from here in order to test it. Installs and works fine for me.
Does it crash when you load FMM with this in the Mods directory, when you try to activate this or when you hit launch?
Might be a conflict with other mods. I´d try running this solo once, saving and then restoring the other mods you are using without this one activated. Also make sure you have MassEffectSDK.dll in your version of FMM and nothing inappropriate in its ini-file. Could be worth it trying a fresh install of FMM.
If none of these suggestions help, leave me another post and I´ll look into it with fresh eyes =)
FMM crashes after I hit Launch button. MasseffectSDK.dll present in FMM folder. I deactivated all other mods - and nothing changed. I created empty profile, activated your mod - FMM still crashes.
I downloaded zip archive only with .fbmod file inside. Is it right? There is no .archive file?
Did it work for you as intended? I mean no errors installing and the marker was cleared? I´m going to do my best to develop this until it handles all the Journal notification problems. (Luckily the other sections can be manually cleared or aren't bugged.)
If you get an error, try the new package I just updated.
Lol sorry I'm actually saving this mod for when I play Andromeda again, I'm trying to complete other games currently and I'll get to MEA in a long while. I bet it does work tho :)
18 comments
My persistent (!) started soon after arriving on Voeld. I've been through every mission in the list, completed or not, and waited on each one to let it pop and nothing makes the (!) disappear.
Shame. I was really hoping this would sort it out for me.
P.S. After playing NG+, I kept an eye on my Journal making sure that it was cleared the whole time. "Task: Data Trail" on EOS is the mission that bugged me out this time. Seeing as how I was now bugged there was no way to see which mission on Voeld bugged last time.
Like I promised earlier, I keep adding bugged quests as I find them.
This new version contains five more problematic ones, now eight altogether.
Enjoy =)
Jandof
P.S. If you think there are more than these out there, just post your suspicions here and I'll look into them.
If you have a problematic save game or a good idea about which quest is causing the problem for you, drop a post and we´ll see what we can do about it. =)
Jandof
Value cannot be null.
Parameter name: buffer
at System.Security.Cryptography.HashAlgorithm.ComputeHash(Byte[] buffer)
at FrostySdk.Utils.GenerateSha1(Byte[] buffer)
at Frosty.ModSupport.FrostyModExecutor.<>c__DisplayClass17_0.<Run>b__0()
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.ModSupport.FrostyModExecutor.<Run>d__17.MoveNext()
--- 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 FrostyModManager.MainWindow.<launchButton_Click>d__12.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)
FMM version: 1.0.3.1
I just downloaded my mod from here in order to test it. Installs and works fine for me.
Does it crash when you load FMM with this in the Mods directory, when you try to activate this or when you hit launch?
Might be a conflict with other mods. I´d try running this solo once, saving and then restoring the other mods you are using without this one activated.
Also make sure you have MassEffectSDK.dll in your version of FMM and nothing inappropriate in its ini-file.
Could be worth it trying a fresh install of FMM.
If none of these suggestions help, leave me another post and I´ll look into it with fresh eyes =)
Jandof
MasseffectSDK.dll present in FMM folder.
I deactivated all other mods - and nothing changed.
I created empty profile, activated your mod - FMM still crashes.
I downloaded zip archive only with .fbmod file inside. Is it right? There is no .archive file?
I may have messed up the packaging. Strange thing though I couldn't get the error even when I reinstalled it.
Anyway, I prepared another package. Should show up there now. Give it a go and let me know if it works better. =)
Jandof
But blasted icon not gettin away.
I pass through all quest notes - done and current. Some of them are blinked.
But icon still here.
Did it work for you as intended? I mean no errors installing and the marker was cleared?
I´m going to do my best to develop this until it handles all the Journal notification problems.
(Luckily the other sections can be manually cleared or aren't bugged.)
If you get an error, try the new package I just updated.
Jandof