https://bugs.winehq.org/show_bug.cgi?id=53470
Bug ID: 53470
Summary: Action Mogura: directional pad doesn't work correctly
in game
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: joshas(a)gmail.com
Distribution: ---
Created attachment 72831
--> https://bugs.winehq.org/attachment.cgi?id=72831
Log from game running
Configure game to use directional pad of XBox360 controller instead of analog
stick. While directional pad input works correctly in launcher configurator, in
game directional controls do nothing. Action buttons are working correctly
though.
On Windows 10 after enabling D-PAD everything works as expected.
Game is built using "Multimedia Fusion 2" tool.
Game is freeware, link on archive.org:
https://archive.org/download/actionmogura_v1.3/actionmogura_g_14_4_9.zip
sha1sum
1940e2b3b5bebdaae2e2e58c39644343c5184e1c actionmogura_g_14_4_9.zip
As game launcher is partially in Japanese, here are the instructions how to
configure controls to use directional pad:
- Run game launcher `action_mogura.exe`.
- Press "Key Config" button.
- In top right dropdown select second option to select gamepad instead of
keyboard.
- In second dropdown (top left) select "joypad1"
- Check the checkbox "POV入力を使用する" (use POV input, i.e. use D-PAD)
- Select action buttons
- Click "OK" and "RUN" to start the game and check if DPAD works. Going to menu
is enough to see if up/down controls are working.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53469
Bug ID: 53469
Summary: RuneScape 3 : Game Crashes with page fault
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: allan4229(a)gmail.com
Distribution: ---
Created attachment 72830
--> https://bugs.winehq.org/attachment.cgi?id=72830
backtrace provided by wine itself
After installing the game, the game will randomly crash with page fault, as per
the attached file.
Some valuable mentions :
- I'm using i3wm, so, for some testings I've added some workspace assignments
to avoid "BadWindow" error.
- Sometimes the page fault occurs at the address 0xFFFFFFFFFFFFFFFF instead of
0x0000000000000000 . Depending on the wine version being used.
- For some versions of wine, I got the error "corrupted double-linked list".
- For some versions of wine, I got the error "double free" related do malloc (I
don't remember exactly the error message, but the default one when you try to
call free() twice).
- Wine custom version lutris-7.2-2-x86_64 lasts longer in-game before crashing.
- I'm pretty sure it has something to do with the graphics, because :
1. It lasts longer before crashing if you set graphics to min value
2. It crashes when attempting to increase the graphic settings in-game
- It STILL crashes on min graphics
- I got "malloc(): unsorted double linked list corrupted" after 20 mins
in-game, for example.
Related to "Compatibility Mode":
- "BadWindow" error still occurs in compatibility mode even when trying to set
a global regex. After checking by monitoring windows' names I had noticed that
it tries to open an unnamed window that may be the cause.
- Even when the "BadWindow" error does not occur in Compatibility mode I got
only black-screen/crash in-game.
System :
- Wine staging 7.14 (winehq mirror -
https://dl.winehq.org/wine-builds/debian/dists/)
- Lutris to enable DXVK, VKD3D and D3D extras.
- Debian testing
- Kernel 5.18.0-9.1-liquorix-amd64
- amdgpu (POLARIS 10)
- Program https://content.runescape.com/downloads/windows/RuneScape-Setup.exe
```sh
sha1sum RuneScape-Setup.exe
bee061914639601d7e602f9653f883bdac7da3a1 RuneScape-Setup.exe
```
PS : if you're wondering why using it instead of the native client... well...
dxvk gets up to 5x more FPS (twice as dx native) and the latency is a lot
better (at the native client it feels like 400ms of input lag). That's why.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.