Open the 7zip file and drag the two files into Frosty.
Frosty is design to read from .rar files not .7z which is why you get that error message. Just open the .7z with 8zaip and drag the files into the mod manager and you should have not problems.
For all of u, to get every mod correctly u must download FrostyModManager 1.0.6.2 and the DapathFix in this link below: https://github.com/Dyvinia/DatapathFixPlugin. They are 2 archives in "Realeases", one .zip and other 107.zip u must take the first one, the second one is for new games like Need For Speed Unbound, that uses FrostyModManager 1.0.7. When u have it, go to FrostyModManager folder > Plungins and copy DataPathFix folder and the Datapathfix.dll (when u download it)
Open FrostyModManager as always and load the mods u want. Launch the game and enjoy it! It works for me in this game and in Mirror's Edge Catalyst! Hope this help anyone. *This is because the EA Connect app, when they change it, it makes troubles for sync the mods and load everything alright. For games that are olds, like: MEA, Mirror's Edge, etc*
I have not played in 2 years or 3. And I can not get any of the mods to work. And all of a sudden frosty is now launching the game with steam after downloading and using the frosty fix.
i have no idea what im doing wrong but i get this message when i drag the rar file into frosty:
Object reference not set to an instance of an object.
at FrostyModManager.Compression.SevenZipDecompressor.OpenArchive(String filename) at FrostyModManager.MainWindow.<>c__DisplayClass26_0.<InstallMods>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 FrostyModManager.MainWindow.<InstallMods>d__26.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
Maybe try a different Frosty release ,sometimes helps. New versions can introduce bugs. The game ,plus a lot of the mods here are a few years old. Sometimes sticking with the old can be better especially if you had it working ok in the past.
P.s; That could be a windows permison issue. I keep my game plus mods plus Frosty tool away from any places related to protected windows folders (like program files). I also exclude said folder from antivirus scanners. Also read comment down below about changing it to zip ,might help too.
I get that with several mods lately. I noticed that this seems to happen because of .7z files not properly being handled/recognized by the frosty mod manager. You have to extract the files and them compress them into a .zip file instead. The frosty mod manager should recognize/handle it now.
FYI: People often make the mistake of extracting the files into a folder then placing that folder into a zip DON'T DO THAT.
EX) CCO.7z-->Extract to CCO folder-->Compress CCO folder to CCO.ZIP THIS IS A MISTAKE Why? Because you're multi-layering the file now. You're basically creating a file path CCO\CCO\<the actual files you need>. The mod manager (and a lot of other programs) will likely not recognize this because it's looking for the direct files located inside the zip the first time it's opened (I.E. CCO\<the actual files you need>).
Instead you should go into the extracted folder and select all the files inside it and compress them into a ZIP folder and try using that with the Frosty Mod Manager.
EX) CCO.7z-->Extract to CCO folder-->Open CCO folder-->select CCO.archive and CCO.fbmod-->Compress to CCO.zip
Really nice. Ever think of making any similar complexions for male Ryder? The female ones are great, but since they change the skin tones a bit, it's really difficult to get the twins to look similar.
Give Feedback
58 comments
Frosty is design to read from .rar files not .7z which is why you get that error message. Just open the .7z with 8zaip and drag the files into the mod manager and you should have not problems.
https://github.com/Dyvinia/DatapathFixPlugin.
They are 2 archives in "Realeases", one .zip and other 107.zip u must take the first one, the second one is for new games like Need For Speed Unbound, that uses FrostyModManager 1.0.7.
When u have it, go to FrostyModManager folder > Plungins and copy DataPathFix folder and the Datapathfix.dll (when u download it)
Open FrostyModManager as always and load the mods u want. Launch the game and enjoy it! It works for me in this game and in Mirror's Edge Catalyst!
Hope this help anyone.
*This is because the EA Connect app, when they change it, it makes troubles for sync the mods and load everything alright. For games that are olds, like: MEA, Mirror's Edge, etc*
I have not played in 2 years or 3. And I can not get any of the mods to work. And all of a sudden
frosty is now launching the game with steam after downloading and using the frosty fix.
But none of the mods show up in the game.
Any help would be appreciated.
Object reference not set to an instance of an object.
at FrostyModManager.Compression.SevenZipDecompressor.OpenArchive(String filename)
at FrostyModManager.MainWindow.<>c__DisplayClass26_0.<InstallMods>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 FrostyModManager.MainWindow.<InstallMods>d__26.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
New versions can introduce bugs.
The game ,plus a lot of the mods here are a few years old.
Sometimes sticking with the old can be better especially if you had it working ok in the past.
P.s;
That could be a windows permison issue.
I keep my game plus mods plus Frosty tool away from any places related to protected windows folders (like program files).
I also exclude said folder from antivirus scanners.
Also read comment down below about changing it to zip ,might help too.
FYI: People often make the mistake of extracting the files into a folder then placing that folder into a zip DON'T DO THAT.
EX) CCO.7z-->Extract to CCO folder-->Compress CCO folder to CCO.ZIP THIS IS A MISTAKE
Why? Because you're multi-layering the file now. You're basically creating a file path CCO\CCO\<the actual files you need>. The mod manager (and a lot of other programs) will likely not recognize this because it's looking for the direct files located inside the zip the first time it's opened (I.E. CCO\<the actual files you need>).
Instead you should go into the extracted folder and select all the files inside it and compress them into a ZIP folder and try using that with the Frosty Mod Manager.
EX) CCO.7z-->Extract to CCO folder-->Open CCO folder-->select CCO.archive and CCO.fbmod-->Compress to CCO.zip