安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题


That's right. But it isn't.
My hotas is shown (both parts), so is my mouse (don't ask)..
...but not my pedals.
I have had a little look into this issue and it would appear the crux of it is that when setting which options are available for setting Yaw/Pitch etc the expected bind needs to start with the word "Joystick" but not include the word "Button". It would make sense that the Saitek pedals could be listed as something else if they are at all detected by the game.
This is a bit of a long shot too considering how long ago you posted but I have just uploaded a version of compiled binaries from my source mod of Helium Rain with some logging enabled which may be useful in discovering what the game detects them as, if they are indeed detected at all.
Within the .zip file I have included both the windows and linux binary files. The game will print the binds to the Game.log files in the save folder (well, at least it does on windows for sure). Before doing this it may be useful to navigate to the Helium Rain savefolder %appdata%/local/heliumrain/saved/savedgames (windows location, dunno about linux).
To trigger the file being written with the available binds, launch the game with the appropriate binary included in the zip file, start or load a game so that you are in a ship in space. Then navigate to the settings menu, go to the Gamepad / Joystick section and click any of the Joystick options, like yaw/pitch/roll etc. This action should then generate all the game binds that Helium Rain has picked up on and print them to the Game.log file as generic events.
Example output within the file on my system looks like this:
2025-11-18T01:12:40.855 GAME_LOADED
2025-11-18T01:12:42.213 GENERIC_EVENT,"AnyKey"
2025-11-18T01:12:42.213 GENERIC_EVENT,"MouseX"
2025-11-18T01:12:42.213 GENERIC_EVENT,"MouseY"
and on and on it goes. Everything listed after the "GENERIC_EVENT" is a possible game bind. It seems to list a lot of devices that aren't plugged in like oculus etc but in testing with my TM16000 the relevant TM16000 binds only appear while it is plugged in. If the file is successfully created on your end please upload it or copy the relevant key events as a steam reply.
https://www.mediafire.com/file/v3lhxotxdqda3yh/HeliumRainFanPatch.1.44DebugKeyLogging.zip
When I get a chance, I will look into it more closely and give some feedback.
For now, my entire Hotas is at a friend's place, so I cannot speak for when that might be though.
Either way, thank you for the effort.