Forum Discussion
6 Replies
- KipEnyan3 years agoNew Traveler
This is not, in fact, fixed on latest patch. The above workaround still works, pressing the new + original keybind simultaneously will allow the new keybind to work until the next time game state is reloaded, but after a reload your new bind goes dead again until repeating the process.
- ShotFromGuns3 years agoRising Vanguard@KipEnyan Are you sure you got the same patch as @dkwebb13? I got a 3.3 GB patch on Steam and mine is still busted; but I definitely didn't get a 100 GB patch (side note: jfc EA), nor is one yet available on this platform—which seems to be what dk is talking about.
- KipEnyan3 years agoNew Traveler
There is no 100GB patch, some peoples installs re-verify when this patch went out for whatever reason so it can look like a 100GB+ download. It’s the same patch that released today everywhere on PC.
- ShotFromGuns3 years agoRising Vanguard
Ah, yeah, in that case, it definitely didn't fix it for me, either. (I did get a bunch of CTD's after installing it until I rebooted my entire machine, though. That was great.)
Yeah, I discovered that the fix didn't last. At first it seemed to work perfectly, but after a while I found the same situation that others reported, I had to use the F key again. Still, I'm delighted to be past that stupid blaster stance tutorial and able to continue playing the game. It would be nice if they'd get it completely fixed. However, I'm perfectly willing to settle for the current situation for right now.
I was wondering about that. At first the system said it was a 3 gb download, but then it suddenly jumped to a much larger number. Which really surprised me, because 100 gb is 2/3rds of the total size of the game! I remember thinking when I saw it, "This isn't a patch, it's a replacement!"
About STAR WARS Jedi: Survivor™
Recent Discussions
- 22 hours ago
- 3 days ago
- 6 days ago
- 8 days ago