I can get this to open with Lutris on my Steam Deck, apply mods to Mass Effect Andromeda, and even get a bit of code for Launch Options to get the mods running. I'm using Proton 9.0-4 to launch the game because of EA nonsense. None of the mods actually show up, and I'm wondering what to do considering I'm seemingly applying mods using Frosty.
I do know that you have not read fully mod description, bc there is a full instruction on how to report issues (and you didn't follow them). Read it, and also you will find tips about dataPath arg
I read, but am deeply bad at Linux and don't understand half the verbage used. Deeply appreciate you for making this and replying, will do more research before asking anything else.
Okay, this seems to be a renderer issue. I fixed it with the following steps:
- Runner: sys-wine-10.0 - DXVK: off
That got it to load a visible window and successfully scan for Dragon Age: Inquisition. Unfortunately, when I click 'Select' to open the mod manager proper, I get another black screen (about the size of an error box, maybe?) and the whole thing just hangs.
Nobara Linux, RTX 4070. I have triple- and quadruple-checked that it has access to all user files in Flatseal.
The newer wine seems to have issues with .net 48 :/ I've heard that running Frosty through proton tricks (or maybe adding it as a non steam game) with proton 9 (must be 9, not 10) helps.
Edit:
Personally I'm running Frosty in a bottle, using kron4ek wine 10.12 staging, dxvk 2.7, and wine-mono 10.1. And it works fine
So, as before, we already found that the issue with your case is that the custom winmm.dll (that should be placed next to BF2 exe file) provided by Frosty is not loaded by the game. I have no idea why this happens, probably bc of some unusual setup, distro, packages etc. BUT
In the newest version of Frosty I've included improved winmm.dll. Before installing "empty" mods pls remove old winmm.dll from BF2 folder, run empty install, and give it a try. Now, even if winmm proxy won't be able to load org winmm, it should leave a proper log behind it. If not, then it means game doesn't even sees the winmm.dll, and there's nothing I can do about it :/.
And when it comes to arguments, use either: WINEDLLOVERRIDES="winmm=n,b" %command% -dataPath "ModData/Default" or WINEDLLOVERRIDES="winmm=n,b" game-performance mangohud obs-gamecapture %command% -dataPath "ModData/Default"
WINEDLLOVERRIDES="winmm=n,b" is environmental variable, you want it to be at the beginning of the command, not in the middle.
Alas, game still not loading and there's no log file.
About my setup I can say that I use CachyOS and tried proton versions from 7.0 to 10, Experimental, GE and proton-cachyos. Doubt that that the issue but I have CoW disabled on btrfs file system for Games folder, but who knows. Applied betterInitfs and did not.
Auto-scan find the game in this path:
Z:\home\reient\Games\Steam\steamapps\common\STAR WARS Battlefront II
But actually - "Games" is symlink to:
/storage/ssd1/Games
And I tried to add the game manually with actual path - didn't change anything (path still in the Z: drive though)
Thanks for the info about positioning of WINEDLLOVERRIDES line, kinda forgot about it.
And is this OK that after removing launch arguments, ModData folder, winmm and crypthook from game folder - game still doesn't open until some one file redownloaded after files verification? IIRC, five years ago when I played with mods on Windows through EGS version - there was possibility to run game without installed mods. But by that time there was some workaround for EGS version until FMM added official support, so don't know all technical stuff
FIRST Why the game doesn't launch after mod installation, even without params. I did quite a lot of testing on such setup - BF2 from Epic installed and run via Heroic. * Without any mods installed, with winmm.dll proxy disabled - launches fine. * With empty mod list installed (click Install mods in Frosty, without any mods installed), without launch args, with winmm.dll proxy disabled - launches fine. * With BF2 Expanded - Instant Action installed, but without launch args, with winmm.dll proxy disabled - again launches fine. * With BF2 Expanded - Instant Action installed, without launch args, with winmm.dll proxy disabled, BUT with BetterInitFs tool run - DOESN'T launch.
For some stupid reason BetterInitFs modifies base game files, and without winmm.dll proxy the game cannot load any modified files.
So my guess is you were running BetterInitFs, which breaks base game files. Unfortunately it's a third party plugin, so I can't do much about it, but I advise NOT to use it until you can fix your setup to launch successfully with empty mod list installation (no mods selected in Frosty, Install mods button clicked, game run with -dataPath launch arg).
SECOND I have literally no idea why your game refuses to load winmm.dll proxy. My only sugestion is to launch protontricks, there choose game, and choose "Run explorer.exe". It should open wine file explorer. There try to locate your game exe, and check if winmm.dll is visible. It doesn't matter that your Linux file explorer can see the dll, if wine/proton for some reason cannot. Maybe there are issues with file permissions and wine/proton cannot read custom winmm.dll? You can compare permissions of winmm.dll and game exe file.
Also do not switch Proton versions like crazy, especially going as far back as Proton 7.0. With each change, Proton makes changes to your prefix. And it can break a lot of stuff, especially when you are downgrading. Remember that Proton/wine etc where not build with modding in mind. Imo at this point it would be good to delete the whole prefix and start over with newest Proton from Steam or GE.
Yeah, I know that switching wine/proton can cause issues, but when I switched - I did this backwards, meaning I was downgrading down to 7.0 -and each time EA App, directx and redistributables were reinstalling - so I presume there's a fail-safe for that case. But when I switched from 7.0 to up-to-date proton - nothing was reinstalled, so yes, I actually already deleted the whole prefix and started over to prevent any issues.
Okay, I've opened game folder in explorer.exe and winmm and crypthook are visible from here. The only difference in permissions is that winmm and crypthook didn't have "Allow executing file as program" checked - I'm not that tech-savy but my logical guess is that this irrelevant for anything not .exe, .msi etc. But just in case I checked those boxes, cause all files, including GFSDK_ShadowLib_Util.win64.dll for example, have them.
Then I tried to launch game without applying BetterInitFs - the only reason I applied it earlier because it was written in description, but I guess it is not necessary if not using major modpacks? Anyhow, tried to launch with full launch args - no avail. Then tried to "install mods" again (and again) as recommended in troubleshooting - no avail.
Removed -dataPath from args, not touching WINEDLLOVERRIDES - game starts as usual. Then I checked some files in ModData folder and subfolders and some didn't have "Allow executing file as program" either, so through search I applied it to all files - but again, no avail.
Retried with Hard Links OFF - no avail.
Seems like we out of options - so thanks for trying to help. The only possible way I see is to try to install EGS version from Heroic - but even if it would work - I don't want to play it from here.
so due to steam having to preload Battlefront 2 through EA app although I launched the game via steam it still opens up the EA app then everything closes an the game dosent launch is there any way to get past this or does it make the steam version unplayable @6maniman303
If the game refuses to launch with datapath arg, but works without it, then there's no issue with ea app. Most probable causes are: 1. Winmm.dll is not loaded. 2. symlinks generated by Frosty are broken 3. One of the mod you installed is corrupted, or doesn't work under Linux
So I used protontricks to use the linux mod manager which was just much easier for me to get access to Battlefront 2 and I installed the latest version of expandd which didnt work as I mentioned do you think I should try an earlier version of the more or should I change something else?
I’m having the same problem, where the EA App launches and then closes when I try to launch SWBF2. I have a winmm-proxy.log so I’m assuming that’s the winmm log, and it seems to be loading things just fine. It’s 3 lines long and it ends with executing my SWBF2 exe.
My modded Mass Effect Andromeda also works fine, so I don’t think the issue is my Frosty or EA App. Can you explain how to check the symlinks? When I look in the file explorer, my SWBF2 moddata/default/data folder looks the exact same in my SWBF2 as in my MEA, but one works and the other doesn’t.
I run Frosty via Lutris and then I boot the game like normal, from Steam.
Is there any reason I shouldn’t copy the entire Data folder from MEA and paste it over the SWBF2 one? That’ll be an easy way to make sure the Data folder isn’t the problem.
DarthRevan - do NOT copy anything from MEA to SWBF2. Data folder contains meshes, textures, gameplay logic of the game. If you will copy MEA data folder to SWBF2, then you will copy all the Data (meshes, textures) to BF2, which will crash horribly due to missing stuff.
Please try to first remove all mods in Frosty, then close it, in Steam check file integrity of SWBF2, then open open Frosty, do NOT add mods, click Install button, and try to run game with dataPath arg. This way you will check if the game can run with modding setup, but without mods. If it will work, then it means some mods just don't work
SilverModder - which expanded mod? Bc InstantAction is already tested by me and another person to work fine, and Kyber version requires Kyber, which doesn't support Linux, so it is expected it won't work
Yes I was using instant action not kyber first I started with the most recent version of expanded, then I tried Expanded instant action vanilla which also did not work should I try installing Ea option on the mod manager since it will always preload EA or do you suggest I try something else. Also one more thing Id like to mention my BF2 is installed on my SD card not the actual deck do you think that could be the problem?
If you own and launch the game through Steam, then don't use EA setup option from Frosty.
99% of Frostbite games on Steam preload EA App. But Steam is smart and it's passing launch arguments to EA App, which later passes them to the game itself.
The game being on the sd card might be an issue, especially if in Frosty Mod Manager the game is added though wine D: drive, or other drive that's not Z:. But tbh I have not tested Frosty with secondary physical drives (like sd card)
I just reinstalled the game on the deck and tried to load 0 mods into the game and use that launch option it didnt work so Im gonna tell you every step I did 1 by 1 let me know if I missed an important step because im running out of ideas so first I downloaded and extract linux FMM and I launched with protontricks with the SWBF2 prefix then I scanned and got access to SWBF2 I created a profile named it with no spaces and have tried 2 separate versions of the expanded, the most recent and vanilla both did not work I did apply Betterinitfs after I installed the mod then I would apply the launch prefix given by the mod and either use proton experimental or the most recent proton I also did not extract the expanded mods after I downloaded them. then after launching my game it would soft crash before Id even get to the title screen. So did i miss anything important? also I know you said expanded worked for you but which version also what proton did you use or recommend to launch the game and could you try again and see if your game still launches with the mod and I did not use kyber expanded I used instant action.
I have also found that doing this process breaks the game even though I validated the files and took out the launch option so I have to delete and reinstall it everytime it fails.
I'm sorry you have these issues, you've provided many informations, but none of them are really useful to me :/ there's the whole section in description how to report issues. And from my experience when people are following these instructions we usually are able to figure out the root cause. But when people just decide not to read the description, we can guess and guess forever
How do you use it in lutris.. how do you put the launch command on lutris? I got a problem launching it from steam with the latest proton GE, it's won't stop create large shader cache.
Could anyone comment on if this is still working for Battlefront 2? I've spent hours at this point trying to get my game to run with mods (EA App), but the furthest I've gotten is running Frosty Mod Manager with PortProton, applying mods, using the -dataPath "ModData/Default" (also tried the symlink option listed in the description); yet still hasn't worked.
Side Note: I also tried CLI, but ended up getting a "system exception" error & couldn't figure out how to fix it (everything I've read says it means that an unknown error occurred). Really trying to get back into Battlefront, but at this point it's looking like I'll have to buy a whole drive just to dual boot Windows (solely for a singular game).
Well, I've tested the newest version with Battlefront 2 from Epic (via Heroic) on my Steam Deck. I was able to install Battlefront Expanded Instant Action mod and boot the game into title screen, and look at new characters.
1. Make sure winmm is loaded. You can check it by looking for winmm.log and crypthook.log next to the game exe file. If logs are there, and they don't contain any errors - this part should be good. 2. Check your symlinks. Check if they exist in your linux file manager first, usually in ModData/Default (you should have symlink in ModData/Default/Data to Win32). Then in the program you use to run the game run wine explorer to verify this symlink is visible for wine, too. If you're running the game through native steam, you can use protontricks to launch explorer, if it's Heroic, you can use winetricks built into game settings page at wine tab, and lastsly in bottles you van find explorer in legacy tools. 3. For sure use the newest version of Frosty, WITHOUT replacing dlls with random stuff from the internet, as it's usually not compatible.
EDIT: Also please provide what exactly do you mean by "it doesn't work", bc game can "not work" in different ways for different reasons. Also it would be nice to know what's your setup (from which store you own game, which programs do you use to run it, is it a flatpak program)
Thank you so much for responding. My apologies for not being more clear! I should have been, but I wasn't really expecting such a detailed response.
I own the game on EA App.
EA App runs on Lutris; through the app (opened via Lutris), I launch Battlefront 2.
winmm & crypthook are both DLL files in my Battlefront 2 directory. I'm not 100% sure how to fix this, or if it even needs to be fixed (could it be that I'm running Linux Mint causes these files to be .dll)?
Executor.log & sdk.log are both in the frosty folder; these are the only .log files in the folder.
Use Hard Links is ON.
Game launches through EA App without command line arguments; when adding -dataPath "ModData/Default", the game does not launch. Making an "EAModData" folder with the instructions in the description also do not work.
Only attempting to install one mod; https://www.nexusmods.com/starwarsbattlefront22017/mods/1230 (Star Card Loadouts; not installing GameModeInfo).
I am using the latest file provided (the one uploaded today, June 9th. My initial report was made using the previous version, the "m" version).
Referring to "it doesn't work", when I launch the game, EA App will close; then reopen shortly after, with Battlefront 2 never launching.
I really appreciate you taking the time out of your day to help me solve this issue; the only solution I can come up with on my own is to buy a new drive to install Windows onto, & launch into that whenever I want to play Battlefront 2. Please let me know if I need to provide any more information, and I understand if you have other things going on that you need to prioritize; I am just some random bloke on the internet after all.
1) is Lutris installed as flatpak? Or from distro repository, or app image? 2) winmm and crypthook should have dll extension, it's a windows library extension. 3) in Lutris, in prefix where you run EA App, open Wine Cfg, and check libraries tab. You should have winmm (without .dll) there, if not add it. 4) please upload and link the content of executor and sdk log files.
Imo what happens is winmm.dll is not loaded by the game, which is required for the game to be able to read mod files. So please make sure to check and resolve point 3.
After that you will need to make symbolic link to ModData/Default (you called it EAModData, good enough), and place it next to the game exe.
Then open EA App, go to game properties, add -dataPath EAModData to launch args.
Then still in EA App, click "open game folder". It should show ugly folder window, showing game folder, from WINE perspective (very important). Make sure the EAModData is shown in this window, next to game exe.
At first I suggest to click Install button in Frosty without any mods, to create clean file structure. Then you run game, test if the setup is ok, and only after that start adding mods.
1) Lutris appears to be installed as a flatpak (downloaded from Software Manager); going to try reinstalling as a system package to see if that clears it up, as I know flatpaks can have some issues with certain things due to their sandbox environment. I will update when I retry Frosty through my new Lutris install. I checked the winecfg of EA App, winmm was missing. I added it, as well as doing another fully fresh install of your Frosty manager, while also following each step you listed (symlink to ModData, launch args, made sure EAModData was visible in "Show Game Folder" while also placing it next to starwarsbattlefrontii.exe). When launching the game, it does as it did before; EA App closes (for a noticeably longer period than it did before), before then re-opening; with Battlefront 2 never launching.
I really appreciate your help in all of this; the longer time between EA App closing & re-opening makes me believe it's a problem with Lutris being a flatpak. Again, thank you so much!
EDIT (1): I'm so sorry to not have mentioned this sooner, as this could be a problem with the install (I apologize for any frustration I'm causing by not bringing up important info sooner); my game is not located on the wine :z drive (a message appears when launching the mod manager, as well as in both log files). I could not initially get the game to install on the :z drive, as it said I only have 15 gigs of space available (I have 500+ gigabytes available on my computer); now, after re-installing Lutris from the .deb file provided on their website, I am able to install the game to the :z drive; as I'm typing this the game is installing.
Again, I really appreciate you taking the time out of your day to help a stranger out with a problem, especially one that's due to their own error. I will follow up with my update below this.
YOU DID IT!!!!!! Game is now running with mods; your instructions got my game running w/ mods on Linux, which I thought wouldn't happen. Thank you so, SO much for taking the time out of your day to give me such thorough responses, as well as updating the guide on the description; these together got my game working. I think it was a culmination of problems; mainly being that Lutris was the flatpak version, causing it to not have full access to my drive (explaining why the Z: drive had limited space on EA App). Installing the .deb version of Lutris allowed me to install the game on my Z: drive (as well as your tip to make sure EA App had winmm).
Again, thank you so much. I owe it to you! Absolutely wonderful being able to run this game with mods, brings me back a lot of fun memories from a few years ago. good luck on your future endeavors, you deserve the best :)
Unfortunately you are right. Vanilla Frosty had two issues: 1) It was using all available threads, which could be unstable (as Frosty is spaghetti code), I've reduced it to half. 2) Frosty had serious memory handling issue. Basically during mod installation, it was loading all uncompressed mod data into memory at once, which was fast to access and use, bc RAM is fast. But if Frosty would exceed total RAM available it would hard crash. And it wasn't an arbitrary big amount of mods. Trying to install only the mod collection you gave me on my Steam Deck would make Frosty crash. So I had to reimplement this part, to make data load into memory only when it's needed, and after it would be used, it would be purged from memory. It adds time, but is much safer, and allows wider amount of users to use Frosty. Both of these fixes make Frosty much more stable and safer, but unfortunately at the cost of mod installation time :/ Maybe someday I will sit again to it, to find a middle ground.
187 comments
EDIT: Used this video to set up Frosty
Another chance is, you added mods to Frosty... but you haven't applied them before installation xd
- Runner: sys-wine-10.0
- DXVK: off
That got it to load a visible window and successfully scan for Dragon Age: Inquisition. Unfortunately, when I click 'Select' to open the mod manager proper, I get another black screen (about the size of an error box, maybe?) and the whole thing just hangs.
Nobara Linux, RTX 4070. I have triple- and quadruple-checked that it has access to all user files in Flatseal.
Edit:
Personally I'm running Frosty in a bottle, using kron4ek wine 10.12 staging, dxvk 2.7, and wine-mono 10.1. And it works fine
For the time being, my launch args are:
But I also tried to launch just with provided by FMM:
And without WINEDLLOVERRIDE because I tried to add winmm and even crypthook
(though it pointless I guess) to libraries through winecfg:
Would much appreciate the help.
In the newest version of Frosty I've included improved winmm.dll. Before installing "empty" mods pls remove old winmm.dll from BF2 folder, run empty install, and give it a try. Now, even if winmm proxy won't be able to load org winmm, it should leave a proper log behind it. If not, then it means game doesn't even sees the winmm.dll, and there's nothing I can do about it :/.
And when it comes to arguments, use either:
WINEDLLOVERRIDES="winmm=n,b" %command% -dataPath "ModData/Default"
or
WINEDLLOVERRIDES="winmm=n,b" game-performance mangohud obs-gamecapture %command% -dataPath "ModData/Default"
WINEDLLOVERRIDES="winmm=n,b" is environmental variable, you want it to be at the beginning of the command, not in the middle.
About my setup I can say that I use CachyOS and tried proton versions from 7.0 to 10, Experimental, GE and proton-cachyos.
Doubt that that the issue but I have CoW disabled on btrfs file system for Games folder, but who knows.
Applied betterInitfs and did not.
Auto-scan find the game in this path:
- Z:\home\reient\Games\Steam\steamapps\common\STAR WARS Battlefront II
But actually - "Games" is symlink to:
- /storage/ssd1/Games
And I tried to add the game manually with actual path - didn't change anything (path still in the Z: drive though)Thanks for the info about positioning of WINEDLLOVERRIDES line, kinda forgot about it.
And is this OK that after removing launch arguments, ModData folder, winmm and crypthook from game folder - game still doesn't open until some one file redownloaded after files verification?
IIRC, five years ago when I played with mods on Windows through EGS version - there was possibility to run game without installed mods. But by that time there was some workaround for EGS version until FMM added official support, so don't know all technical stuff
FIRST
Why the game doesn't launch after mod installation, even without params.
I did quite a lot of testing on such setup - BF2 from Epic installed and run via Heroic.
* Without any mods installed, with winmm.dll proxy disabled - launches fine.
* With empty mod list installed (click Install mods in Frosty, without any mods installed), without launch args, with winmm.dll proxy disabled - launches fine.
* With BF2 Expanded - Instant Action installed, but without launch args, with winmm.dll proxy disabled - again launches fine.
* With BF2 Expanded - Instant Action installed, without launch args, with winmm.dll proxy disabled, BUT with BetterInitFs tool run - DOESN'T launch.
For some stupid reason BetterInitFs modifies base game files, and without winmm.dll proxy the game cannot load any modified files.
So my guess is you were running BetterInitFs, which breaks base game files. Unfortunately it's a third party plugin, so I can't do much about it, but I advise NOT to use it until you can fix your setup to launch successfully with empty mod list installation (no mods selected in Frosty, Install mods button clicked, game run with -dataPath launch arg).
SECOND
I have literally no idea why your game refuses to load winmm.dll proxy. My only sugestion is to launch protontricks, there choose game, and choose "Run explorer.exe". It should open wine file explorer. There try to locate your game exe, and check if winmm.dll is visible. It doesn't matter that your Linux file explorer can see the dll, if wine/proton for some reason cannot. Maybe there are issues with file permissions and wine/proton cannot read custom winmm.dll? You can compare permissions of winmm.dll and game exe file.
Also do not switch Proton versions like crazy, especially going as far back as Proton 7.0. With each change, Proton makes changes to your prefix. And it can break a lot of stuff, especially when you are downgrading. Remember that Proton/wine etc where not build with modding in mind. Imo at this point it would be good to delete the whole prefix and start over with newest Proton from Steam or GE.
Okay, I've opened game folder in explorer.exe and winmm and crypthook are visible from here. The only difference in permissions is that winmm and crypthook didn't have "Allow executing file as program" checked - I'm not that tech-savy but my logical guess is that this irrelevant for anything not .exe, .msi etc. But just in case I checked those boxes, cause all files, including GFSDK_ShadowLib_Util.win64.dll for example, have them.
Then I tried to launch game without applying BetterInitFs - the only reason I applied it earlier because it was written in description, but I guess it is not necessary if not using major modpacks?
Anyhow, tried to launch with full launch args - no avail. Then tried to "install mods" again (and again) as recommended in troubleshooting - no avail.
Removed -dataPath from args, not touching WINEDLLOVERRIDES - game starts as usual. Then I checked some files in ModData folder and subfolders and some didn't have "Allow executing file as program" either, so through search I applied it to all files - but again, no avail.
Retried with Hard Links OFF - no avail.
Seems like we out of options - so thanks for trying to help. The only possible way I see is to try to install EGS version from Heroic - but even if it would work - I don't want to play it from here.
1. Winmm.dll is not loaded.
2. symlinks generated by Frosty are broken
3. One of the mod you installed is corrupted, or doesn't work under Linux
My modded Mass Effect Andromeda also works fine, so I don’t think the issue is my Frosty or EA App. Can you explain how to check the symlinks? When I look in the file explorer, my SWBF2 moddata/default/data folder looks the exact same in my SWBF2 as in my MEA, but one works and the other doesn’t.
I run Frosty via Lutris and then I boot the game like normal, from Steam.
Is there any reason I shouldn’t copy the entire Data folder from MEA and paste it over the SWBF2 one? That’ll be an easy way to make sure the Data folder isn’t the problem.
@6maniman303
Please try to first remove all mods in Frosty, then close it, in Steam check file integrity of SWBF2, then open open Frosty, do NOT add mods, click Install button, and try to run game with dataPath arg. This way you will check if the game can run with modding setup, but without mods. If it will work, then it means some mods just don't work
99% of Frostbite games on Steam preload EA App. But Steam is smart and it's passing launch arguments to EA App, which later passes them to the game itself.
The game being on the sd card might be an issue, especially if in Frosty Mod Manager the game is added though wine D: drive, or other drive that's not Z:. But tbh I have not tested Frosty with secondary physical drives (like sd card)
every step I did 1 by 1 let me know if I missed an important step
because im running out of ideas so first I downloaded and extract linux
FMM and I launched with protontricks with the SWBF2 prefix then I
scanned and got access to SWBF2 I created a profile named it with no
spaces and have tried 2 separate versions of the expanded, the most
recent and vanilla both did not work I did apply Betterinitfs after I
installed the mod then I would apply the launch prefix given by the mod
and either use proton experimental or the most recent proton I also did
not extract the expanded mods after I downloaded them. then after
launching my game it would soft crash before Id even get to the title
screen. So did i miss anything important? also I know you said expanded
worked for you but which version also what proton did you use or
recommend to launch the game and could you try again and see if your game
still launches with the mod and I did not use kyber expanded I used
instant action.
I got a problem launching it from steam with the latest proton GE, it's won't stop create large shader cache.
Side Note: I also tried CLI, but ended up getting a "system exception" error & couldn't figure out how to fix it (everything I've read says it means that an unknown error occurred). Really trying to get back into Battlefront, but at this point it's looking like I'll have to buy a whole drive just to dual boot Windows (solely for a singular game).
1. Make sure winmm is loaded. You can check it by looking for winmm.log and crypthook.log next to the game exe file. If logs are there, and they don't contain any errors - this part should be good.
2. Check your symlinks. Check if they exist in your linux file manager first, usually in ModData/Default (you should have symlink in ModData/Default/Data to Win32). Then in the program you use to run the game run wine explorer to verify this symlink is visible for wine, too. If you're running the game through native steam, you can use protontricks to launch explorer, if it's Heroic, you can use winetricks built into game settings page at wine tab, and lastsly in bottles you van find explorer in legacy tools.
3. For sure use the newest version of Frosty, WITHOUT replacing dlls with random stuff from the internet, as it's usually not compatible.
EDIT:
Also please provide what exactly do you mean by "it doesn't work", bc game can "not work" in different ways for different reasons. Also it would be nice to know what's your setup (from which store you own game, which programs do you use to run it, is it a flatpak program)
Thank you so much for responding. My apologies for not being more clear! I should have been, but I wasn't really expecting such a
detailed response.
- I own the game on EA App.
- EA App runs on Lutris; through the app (opened via Lutris), I launch Battlefront 2.
- winmm & crypthook are both DLL files in my Battlefront 2 directory. I'm
- Executor.log & sdk.log are both in the frosty folder; these are the only .log files in the folder.
- Use Hard Links is ON.
- Game launches through EA App without command line arguments; when adding
- Only attempting to install one mod; https://www.nexusmods.com/starwarsbattlefront22017/mods/1230 (Star Card Loadouts; not installing GameModeInfo).
- I am using the latest file provided (the one uploaded today, June 9th. My
- Referring to "it doesn't work", when I launch the game, EA App will close; then
I really appreciate you taking the time out of your day to help me solvenot 100% sure how to fix this, or if it even needs to be fixed (could it be that I'm running Linux Mint causes these files to be .dll)?
-dataPath "ModData/Default", the game does not launch. Making an "EAModData" folder with the instructions in the description also do not work.
initial report was made using the previous version, the "m" version).
reopen shortly after, with Battlefront 2 never launching.
this issue; the only solution I can come up with on my own is to buy a
new drive to install Windows onto, & launch into that whenever I
want to play Battlefront 2. Please let me know if I need to provide any
more information, and I understand if you have other things going on
that you need to prioritize; I am just some random bloke on the internet
after all.
thank you!
2) winmm and crypthook should have dll extension, it's a windows library extension.
3) in Lutris, in prefix where you run EA App, open Wine Cfg, and check libraries tab. You should have winmm (without .dll) there, if not add it.
4) please upload and link the content of executor and sdk log files.
Imo what happens is winmm.dll is not loaded by the game, which is required for the game to be able to read mod files. So please make sure to check and resolve point 3.
After that you will need to make symbolic link to ModData/Default (you called it EAModData, good enough), and place it next to the game exe.
Then open EA App, go to game properties, add -dataPath EAModData to launch args.
Then still in EA App, click "open game folder". It should show ugly folder window, showing game folder, from WINE perspective (very important). Make sure the EAModData is shown in this window, next to game exe.
At first I suggest to click Install button in Frosty without any mods, to create clean file structure. Then you run game, test if the setup is ok, and only after that start adding mods.
4) https://www.dropbox.com/scl/fi/ydjrjggo72ziectm78mbv/sdk.log?rlkey=0nvay1c1njba0p9mpu8bvcjpj&st=c79muckn&dl=0 & https://www.dropbox.com/scl/fi/gab2cov7efcf6nk2dfm2v/executor.log?rlkey=aa42medt7zihbvxvq2w5o8au8&st=iwu7glgt&dl=0
I really appreciate your help in all of this; the longer time between EA App closing & re-opening makes me believe it's a problem with Lutris being a flatpak. Again, thank you so much!
EDIT (1): I'm so sorry to not have mentioned this sooner, as this could be a problem with the install (I apologize for any frustration I'm causing by not bringing up important info sooner); my game is not located on the wine :z drive (a message appears when launching the mod manager, as well as in both log files). I could not initially get the game to install on the :z drive, as it said I only have 15 gigs of space available (I have 500+ gigabytes available on my computer); now, after re-installing Lutris from the .deb file provided on their website, I am able to install the game to the :z drive; as I'm typing this the game is installing.
Again, I really appreciate you taking the time out of your day to help a stranger out with a problem, especially one that's due to their own error. I will follow up with my update below this.
Again, thank you so much. I owe it to you! Absolutely wonderful being able to run this game with mods, brings me back a lot of fun memories from a few years ago. good luck on your future endeavors, you deserve the best :)
1) It was using all available threads, which could be unstable (as Frosty is spaghetti code), I've reduced it to half.
2) Frosty had serious memory handling issue. Basically during mod installation, it was loading all uncompressed mod data into memory at once, which was fast to access and use, bc RAM is fast. But if Frosty would exceed total RAM available it would hard crash. And it wasn't an arbitrary big amount of mods. Trying to install only the mod collection you gave me on my Steam Deck would make Frosty crash. So I had to reimplement this part, to make data load into memory only when it's needed, and after it would be used, it would be purged from memory. It adds time, but is much safer, and allows wider amount of users to use Frosty.
Both of these fixes make Frosty much more stable and safer, but unfortunately at the cost of mod installation time :/
Maybe someday I will sit again to it, to find a middle ground.