Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
As for the "hard-coded" button - it's not hard-coded. The "interact" action (Keybinding section Space/Actions) is used when interacting with the Spatial Bypass in space and the "OK" action (Keybinding section "Menus/Actions" ) is used when choosing the location to jump to in the map screen. You likely only changed "interact" from F to something else but left "OK" at F. I just tested this with "interact" bound to "Ä" and "OK" to "Ü" and I could open the bypass with "Ä" and then press "Ü" to choose the jump target on the map (and both keys displayed correctly)
Regarding the keybind issue, under the Menu/Action keybind I have OK set to Space/F. Interact is set to just Space. Using Space to interact with the spatial bypass unit from the ship works fine, but using Space to set the target destination of travel in the menu that pops up doesn't work, despite that being the displayed keybind. Only F works in the menu to initiate fast travel.
I see - I believe that this is a keybinding conflict then - SPACE is used as a modifier for "info boxes" to scroll with mouse wheel while SPACE is pressed. Because the target location on map is hovered the info box will show and when pressing SPACE the input whill be consumed as "scroll modifier" and thus not work for the "OK" action anymore
Maybe the Devs could add a little bonus text to the Conversation, if this edge case happens. HIVE's dry humor and "... oh great, i was RIGHT. We will die." or something like this^^
Calling this an edge case seems strange to me because I created my first "rift gate" thing in the nebula to the home base and took it after rescuing the emissary. Why? because it seemed like the proper and almost intended time to start making the fast travel points. Only to get sucked into the rift the moment I came out back at base. I wasted 40 minutes try to fight my way through before realizing there were FOUR parts and I was only at the 1/2 way point to this annoying thing. said screw this reloaded a save before I ever took the fast travel deciding that crap was the complete opposite of fast. Mainly because I'm level 18 with level 18 gear facing off against level 21 and 22 adversaries.
Now I come across this post more-or-less saying that this is actually a forced rift for the story and it wasn't because I took the fast-travel home? Seriously!? Ugh. I might as well abort my slow trek back the normal way and reload the auto save...assuming it hasn't been overridden yet.
[edit]
Well isn't THAT swell. My rift auto save was there but it was for the very START of the rift. Instead of being ready to start the third part when I got annoyed an quit I'm instead at the very beginning. Only one experience with rifts and they are definitely the one and only fault I have with this game. I was loving it all the way up to this point.
You should have multiple auto-saves and one that is dated before you started the Rift.