Campaign choose mission only shows 3 missions
Product: Star Wars Battlefront II Platform:PC What is your issue related to? General Summarize your bug I played the first 3 missions in the 10 hour preview, bought the deluxe game, played the res...
Forum Discussion
Bit of a nightmare. I'm 8 missions in to the campaign, went back to replay an earlier mission to test out some screen settings (Endor) and only after that did I realise I could actually only see the first three missions! Now of course when I go to continue the campaign it wants to start from Endor - not where I'm actually at - Under Covered Skies.
No way do I want to replay through five entire missions in sequence again to get myself back to where I was. ☹️
Please get this one sorted asap!
@Bruvva wrote:Bit of a nightmare. I'm 8 missions in to the campaign, went back to replay an earlier mission to test out some screen settings (Endor) and only after that did I realise I could actually only see the first three missions! Now of course when I go to continue the campaign it wants to start from Endor - not where I'm actually at - Under Covered Skies.
No way do I want to replay through five entire missions in sequence again to get myself back to where I was. ☹️
Please get this one sorted asap!
Ouch.
I feel for you. I wanted to go back to get all the collectibles and was in a similar situation.
As the fix has not yet been released (this is an easy fix I'm sure), I "got around this" by setting difficulty to its easiest setting and skipping all cut-scenes (space bar on PC). This let me get back thru in about half the time (and get a bunch of crystals for finding the collectibles!)
The problem (bug...) has to be related to the game starter screen, that shows me the TRIAL version... BUT I have redeemed the product code, and have the full game. Picture attached.
EA_DavidCommunity Admin
@DarthFDG Thanks for the workaround, hopefully it helps folks chasing the achievements or who just want to blaze through again.
@EA_David has this been recorded to the bug list for resolution? Sounds like it should be a relatively easy fix for inclusion in a patch.
Cheers
