Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- start/restart the PC without controller connected
- start the game
- connect the controller
This is likely the same problem people with (Xbox & Steam) controllers are seeing in Jedi: Survivor. I was seeing the same thing in Fallen Order.
Long story short: add the EA application "EADesktop.exe" as a non-steam game (Games -> Add a non-steam game to my library), start the EA desktop app through that entry, then start Jedi: Fallen Order from the EA desktop app.
Long story slightly longer: the problem with both Jedi games (and possibly everything else launched through the EA desktop launcher) is that something is broken in the way Steam inserts its controller stack between the input devices and the actual game. The result being that Steam interprets the controller not as being in the "Game" mode but in "Desktop" mode. And in Desktop mode, the default binding for left stick click is to bring up the on-screen keyboard.
There may be other ways of taking Steam out of the equation if you have an Xbox controller -- possibly it suffices to disable "Steam Input for Xbox controllers" in the global "Steam settings -> controller" interface. I don't know, because I don't have an Xbox controller, but a Steam controller. However, the fix of launching the EA desktop app through steam should also fix the Steam overlay and FPS counter, which weren't working for me either.