ติดตั้ง 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 (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
On some distros, like Arch, libcurl.so.4 is built against gnutls, which prevents native Steam from running the game. To fix this, you need to convince the game to use libcurl.so.3 instead, else the game will crash with the error:
The update-safe way to do this without modifying the game files would be to go to the game properties and set "General>Set Launch Options..." to
//Update: Thanks to sarcastic cat for further explanation.
https://imgur.com/a/vIbFL
That's the same issue as you posted previously, actually. Try setting up the launch options as noted in some posts in page 2 and it should hopefully fix the save problem
I'm having a bug with the controller support.
I think it's just using the first gamepad it finds, which unfortunately for me is a problem because for some reason in Linux my mouse shows up as a gamepad and is always first in the list. So when I get into the game it's acting as if I'm always pressing down-and-right on the d-pad.
Here's the console output dealing with the gamepads:
I know it's a weird scenario, so maybe there could just be an option in the config file to manually override the gamepad "slot" that it uses?
I actually ran into this same issue with Risk of Rain in Linux (which is also using GameMaker: Studio) and they completely ignored my bug reports. I still can't play it to this day
I can't do anything about it myself, but this will looked into next week! My apologies for the inconvenience.
You can "fix" it by rm-ing /dev/input/js0 and symlinking /dev/input/js1 (or actual gamepad device) to it. For a more permanent solution you can try https://github.com/denilsonsa/udev-joystick-blacklist
(Please excuse the very unprofessional debug messages. EDIT: and the lack of formatting, thanks Steam)
If you are familiar with Game Maker Studio you'll notice that it's basically a copy and paste from the documentation, which is the recommended practice.
What this does, though, is that it only picks one device to act as gamepad. At least that's what should be happening. The reports here are that mouse AND gamepad are being recognized at the same time, which shouldn't be possible as the gamepad_device variable can only hold one value (0 for mouse, or 1 for gamepad). That's why this is a bit confusing.
I could of course try to force it to be 1 by default, or 2 or whatever number the user wants, but would that even fix this issue?
Nope, but that would probably break gamepad for everyone else.
The real problem is that on Linux some mouses (and probably other devices) are presented both as mouse and as gamepad, e.g. as two different devices. So gamemaker (and your code) will rightfully think that it's a gamepad. I can't really think of any way of fixing it from gamemaker/momodora side, except whitelist or blacklist of devices.
That's really a linux bug, rather than GM/Momodora.
We could make it optional just for those players who have this issue in the first place. It will require manual editing of a file on their end. For everyone else, the game will pick the first gamepad it finds normally (as it is now).