Forum Discussion
SO THIS WORKED
Seem to have a pretty solid solution to my issues. It appears that Borderless Windowed mode fixed most of my issues. Could then play for the rest of the night on multiplayer ground maps without issue, not one crash for a solid 5 or 6 maps played both ways. So that is pretty good result. Many thanks to my friend who suggested this solution. Also tried the Singleplayer campaign, and this no longer resulted in a crash on entering a sequence when you play as the droid, which was another superb result. I finally got a crash on the earlier part of the Endor chapter of the Singleplayer, but after a night of playing almost bug free I'll put that down to the law of averages.
The night was not without issue, early on for example it took so long to find a populated server, we were constantly joining an empty server, Matchmaking needs a serious overhaul, and there is still the issue of the massive discrepancy between buffed and unbuffed weapons and abilities. If one team is all buffed up to the max and the other is not? It just results in a whitewash every time, which is no fun for anybody.
So much happier, rather be complaining about Loot Crate issues and Matchmaking system problems than constant CTDs, but EA/DICE still need to sort this stuff out.
Hi,
Changed Borderless Windowed mode as TALON1138 suggested and it seams to help. Whole user interface works way more smoothly and I dont get those screen freeze/screen flashing stuff anymore when entering or exiting from match back to main menu.So far I have played battle scenario trainings and no crashing.
Attached log shows that game still takes all the memory and gives those CPU load peaks when new macth or when main menu is loaded after victory, but game doesn´t crash to those situations anymore as max CPU load peaks are "anymore" like 80% as they use to be ~100% in fullscreen mode.
Next I will try to continue playing in singleplayer campaing and let see what happens.
About STAR WARS™ Battlefront™ II
Recent Discussions
- 34 minutes ago
- 2 days ago
- 3 days ago
- 3 days ago