Transformers:WFC Mouse Input stuck in a fixed range of view/Arch Linux.

Questions about Wine on Linux
Post Reply
LinuxLover471
Newbie
Newbie
Posts: 4
Joined: Mon Apr 07, 2025 5:13 am

Transformers:WFC Mouse Input stuck in a fixed range of view/Arch Linux.

Post by LinuxLover471 »

Hi, I have had a few issues with wine while playing Transformers: War for Cybertron. The cutscenes did not have any sound, but that was fixed in wine 10.5! Thanks.

But I also had another issue, the issue was with the mouse input, the camera input specifically. When I try to move the camera it is stuck to a certain limit, the buttons work good.

In v10.4, the issue had a workaround, in which you would need to transfer xinput1_3.dll to the system32 and syswow64 with the respective versions of the file at the correct locations ( I do know that system32 has 64 bit files and vice-versa). The file now wants an overwrite for this, whereas it did not need any beforehand. I got to know about the xinput1_3.dll issue when I tried to run the game in windows 10, it asked for the dll and also asked for a d3d dll, I don't remember exactly which, but it was related to d3d.

I also tried removing the prefix and creating a new one. But there was no fix.

I am using the wine development version 10.5, downloaded from the official pacman repository. I also have Wine-mono. I am also using DXVK-Sarek-async-10.8 if that helps. I had installed PhysX support from Nvidia's website.

Here is the link to my post in the arch linux forums.

inxi -Fxxxz

Code: Select all

System:
  Kernel: 6.13.8-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required>
    uuid: <superuser required> BIOS: Award v: FI date: 08/09/2010
CPU:
  Info: quad core model: Intel Core2 Quad Q9550 bits: 64 type: MCP
    smt: <unsupported> arch: Penryn rev: A cache: L1: 256 KiB L2: 12 MiB
  Speed (MHz): avg: 2834 min/max: 2000/2834 cores: 1: 2834 2: 2834 3: 2834
    4: 2834 bogomips: 22667
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02
    arch: Kepler-2 pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0fc8
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: HDMI-A-1 model: LG (GoldStar) FHD serial: <filter>
    res: 1920x1080 dpi: 102 size: 480x260mm (18.9x10.24") diag: 546mm (21.5")
    modes: max: 1920x1080 min: 640x480
  API: Vulkan v: 1.4.309 layers: 1 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: N/A device-ID: 10de:0fc8
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Info: Tools: api: vulkaninfo de: kscreen-doctor
    gpu: nvidia-settings,nvidia-smi x11: xprop
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio
    vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:27d8 class-ID: 0403
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b class-ID: 0403
  API: ALSA v: k6.13.8-arch1-1 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Message: No PCI device data found.
  Device-1: Ralink RT5370 Wireless Adapter driver: rt2800usb type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 2-8:5 chip-ID: 148f:5370
    class-ID: 0000 serial: <filter>
  IF: wlp0s29f7u8 state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 71.48 GiB (5.1%)
  ID-1: /dev/sda vendor: A-Data model: SU800 size: 476.94 GiB
    speed: <unknown> tech: SSD serial: <filter> fw-rev: 8B scheme: MBR
  ID-2: /dev/sdb vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
    speed: <unknown> tech: HDD rpm: 7200 serial: <filter> fw-rev: A7C0
    scheme: MBR
Partition:
  ID-1: / size: 68.35 GiB used: 23.6 GiB (34.5%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 29.36 GiB used: 19.88 GiB (67.7%) fs: ext4
    dev: /dev/sda6
Swap:
  ID-1: swap-1 type: partition size: 7.91 GiB used: 256 KiB (0.0%)
    priority: -2 dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 58.0 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 30%
Info:
  Memory: total: 4 GiB available: 3.82 GiB used: 2.53 GiB (66.2%)
  Processes: 185 Power: uptime: 1h 37m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 882 Compilers: clang: 19.1.7 gcc: 14.2.1
    Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.37
Thanks,
LL
LinuxLover471
Newbie
Newbie
Posts: 4
Joined: Mon Apr 07, 2025 5:13 am

Re: Transformers:WFC Mouse Input stuck in a fixed range of view/Arch Linux.

Post by LinuxLover471 »

Also I have installed sdl2-compact (I think that was what it is called) and sdl3 and their lib32 versions.
LinuxLover471
Newbie
Newbie
Posts: 4
Joined: Mon Apr 07, 2025 5:13 am

Re: Transformers:WFC Mouse Input stuck in a fixed range of view/Arch Linux.

Post by LinuxLover471 »

I recently installed TFOC, and it also has the same issue, I also got to know that these games don't utilize Xinput but something else, some sort of raw input? The other games I used, like Doom3 worked flawlessly. Sorry for not editing the post, I cannot before I hit the 3 posts mark to be able to post and edit freely.
LinuxLover471
Newbie
Newbie
Posts: 4
Joined: Mon Apr 07, 2025 5:13 am

Re: Transformers:WFC Mouse Input stuck in a fixed range of view/Arch Linux.

Post by LinuxLover471 »

The issue is fixed, turns out I was using the wrong version for this task, I was using development version and the wine-staging version fixed the issue.
Post Reply