![]() ![]() Step 1-3 was just them listing the previous fixes that didn't work for them. Here's the fix that Dulana57 found: - Launch ORIGIN, launch STEAM, in origin select the Steam version of Star Wars Battlefront 2, right click and go to Game Properties > Advanced Launch Options. I'm happy to say that everything is all ok now, though it took the better part of a day to get it all down. TROUBLESHOOT FOR MODS If you have Battlefront through Steam, that is why mods don't work. So after dubious searching I stumbled onto the Microsoft Application Compatibility Toolkit, and a post on another forum that set down the steps to get it all working. One way to fix it is to use the task manager under the processes tab and right clicking on the program and choosing Set Affinity, then desleceting all but one core (however you'd have to do this everytime). Then launch the game through FMM as per usual and get back in the action. In the command line arguments insert your path to Frosty Mod manager executable. Apparantly a lot of older games have trouble play on PC's with processors numbering more than one. Launch ORIGIN, launch STEAM, in origin select the Steam version of Star Wars Battlefront 2, right click and go to Game Properties > Advanced Launch Options. Opprinnelig skrevet av JacksonXR75:Step Four was downloading a program from Microsoft that allowed me to force the game to only use a single cpu Core on my multicore processor.
0 Comments
Leave a Reply. |