WYCorp Posted October 29, 2018 Share Posted October 29, 2018 (edited) Tired playing moded BFII for the first time since before the last hotfix patch and the game will not launch via frosty anymore. Tried latest v1.0.4.4 and previous version of frosty, deleted moddata folder, updated mods, activated and deactivated various mods . . . nothing works anymore. Edited October 29, 2018 by WYCorp Link to comment Share on other sites More sharing options...
keraj37 Posted October 29, 2018 Share Posted October 29, 2018 So looks like Dice has banned modding BF2. Link to comment Share on other sites More sharing options...
imogeneA91 Posted October 30, 2018 Share Posted October 30, 2018 (edited) I found out what the potential issue is - at least what my issue was. Everyone kept saying that the symbolic error was due to permissions, but it wasn't. Firstly, try running command prompt. If it loads for a split second then cancels, then that's your issue. Apparently Windows 10 likes to screw up command prompts at times whenever you do a PC update. Mine was refusing to load and FMM needs command prompt to be working to be able to create ModData and the subsequent folders and files. If that's the same issue for you, just google a fix. The only way I could get it to work was creating a new Admin User profile and then running FMM. Now it works like a dream. Posting this here as I've had the issue for 4 or so months, and everyone on the Frostyeditor Discord has been replying condescendingly with 'ITS A PERMISSION ISSUE FOKKIN NOOB LOL CHECK THE SOLUTIONS TAB'. Yeah, nah, definitely wasn't a permissions issue. Edited October 30, 2018 by imogeneA91 Link to comment Share on other sites More sharing options...
keraj37 Posted October 30, 2018 Share Posted October 30, 2018 I found solution too. For me problem was that FMM was placed inside my download folder - moving it to root C:\ solved the issue - this time in 100%. Link to comment Share on other sites More sharing options...
jthrongard Posted April 13, 2019 Share Posted April 13, 2019 I found solution too. For me problem was that FMM was placed inside my download folder - moving it to root C:\ solved the issue - this time in 100%.You wonderful person! This fixed it for me completely. Windows and it's damn permissions/folder structure bugs. Link to comment Share on other sites More sharing options...
Steinerliner Posted April 13, 2019 Share Posted April 13, 2019 I had to restore the ModData folder for Battlefront 2 and it locates the folder...Except the game won't start. Link to comment Share on other sites More sharing options...
DANNYonPC Posted November 14, 2019 Share Posted November 14, 2019 For all those still with an issue - solution: Go to you SW:BF2 folder and create in it manually 'ModData' folder and in it 'Data' folder (and any folder that the exception message string will tell you in case there are more). This should fix it.For some reason Frosty Mod Manager didn't have permission or something was wrong with the path to create it by its own. Nop didnt work for me :( Link to comment Share on other sites More sharing options...
captaincubecraft123 Posted May 8, 2020 Share Posted May 8, 2020 There is an easy solution to the problem. Nothing of the things above worked for me, BUT! You must change the folder, where your Battlefront 2 is installed. If it's installed on a HDD it's simply not gonna work. So make sure it is installed on a SSD, only through installing it to an SSD it will work. Have a nice day. Link to comment Share on other sites More sharing options...
hotroxbod Posted June 13, 2020 Share Posted June 13, 2020 the game and frosty both have to be installed on a primary drive, i had both on an external SSD and it kept giving me errors. after sleeping on it and coming back refreshed i reread the error and figured out that you cant do a symbolic link to an external drive. after reinstalling both on my C drive it worked just fine. Link to comment Share on other sites More sharing options...
Redshirt49 Posted June 19, 2020 Share Posted June 19, 2020 (edited) Any update on this? Still can't get it to work. Running as admin, creating folders manually, moving installation folders around...nothing will stop this error. EDIT : Apparently there is an issue with exFAT hard drives. I'll move the game to NTFS and see if it fixes the problem. UPDATE : Yeah, the exFAT formatted harddrive was the problem. Make sure the game and frosty are on NTFS file format hard drives. Edited June 19, 2020 by Redshirt49 Link to comment Share on other sites More sharing options...
Recommended Posts