ติดตั้ง 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 (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
Looks like it's one of those weirdo bugs lurking inside the EGS code (Chantelise and Recettear share a lot of code and assets) that only hits very specific setups...
I also have this problem (just got the demo, because I love the IDEA of the game but I wanted to see if it wasn't just a sugary coating); nothing I do seems to fix the problem (reinstall, computer restart, game cache revision, changing binds, can't really unplug the keyboard on a laptop). I haven't contacted Steam Support yet; and I heard that while this seems to be a EGS-related bug, contacting them would be nearly impossible because they only speak Japanese and because it's not even a coherent development team, just more of... Think something along the lines of Four Leaf Studios from Katawa Shoujo. I was looking for something more like a quick-fix to the problem rather than a coherent bug removing update. Any help?
However, he has admitted that he is not convinced it is an EGS problem, but rather a hardware problem (on my, your and another user's end). That being said, I find that unlikely, as I have completely switched out input hardware (deleted old drivers etc) and the problem persists- yet ONLY with EGS games in my reasonably large library.
Long story short, no I don't have a quick fix for you. However, I am still working on resolving the issue, and will let you know if I can figure anything out.
Hey Mashpit,
I am still in contact with Andrew Dice from Carpe Fulgur, and I relayed that you are having similar issues. More specifically, you are having identical issues to another person who contacted me about the scrolling problem (they're on a laptop too). The problem that Dice and I are having is that he has not been able to replicated the problem short of taping down the bound "up" key.
If you don't mind, could you try and explain as precisely as possible what you may have installed or altered since your time on Recettear (without giving away sensitive info obviously) so that I can relay it to him? I noticed you have over 15 hours logged, so you had to have played it "normally" for some time before things went wonky.
If you don't want to post about that, its fine, but Dice is asking for anything that may help him/CF narrow down what is happening.
Also, I plan on formatting the laptop in the next month or so for personal reasons. After the wipe, I'll reinstall the game and see if the problem persists.
Dxdiag: http://puu.sh/5Pbph.txt
I can also include hardware information about my desktop (a platform that is guaranteed to be compatible with the game), but I believe Mr. Dice already has that information...
Although by this point (coming up on 4 months now), I am grasping at straws. So far I have stumped /r/Recettear, /r/techsupport, /r/pcmasterrace, this Steam forum, and Steam support.
I devised a hotfix, I think. Hold on while I experiment with it.
I'm not sure WHAT in the steps did the trick, but here's how I got it:
1. Install (re-install?) Vjoy, a joystick emulator.
2. Set up the buttons (Right, Left, Up, Down, Z, X, C, V, W is what I used, as per default)
3. Enable Vjoy, and turn on key blocking.
4. Open Recettear's key configuration tool, and set the gamepad controls (even if they're the same)
5. Open Recettear.
6 (optional). Turn off Vjoy.
Now it even works when I turn Vjoy off.
I'm pretty sure it had something to do with one of the registry changes Vjoy makes when you install it, then..?
Andrew Dice might want to contact Ben Baker for a look at the code.
Get back on me on whether this works for you as well; I think I might've just solved a problem that nobody's been able to address since 2010.