Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DFGT wheel jerkiness with FFB #3

Open
jackun opened this issue Mar 4, 2014 · 6 comments
Open

DFGT wheel jerkiness with FFB #3

jackun opened this issue Mar 4, 2014 · 6 comments

Comments

@jackun
Copy link
Owner

jackun commented Mar 4, 2014

http://forums.pcsx2.net/Thread-Qemu-USB-Wheel-Storage-mod?pid=358423#pid358423
http://forums.pcsx2.net/Thread-Qemu-USB-Wheel-Storage-mod?pid=355645#pid355645
@lowlyocean lowlyocean mentioned this issue Jan 27, 2017
Closed
@jackun jackun closed this as completed Nov 8, 2019
@jackun jackun reopened this Nov 14, 2019
@JamesLewisLiu
Copy link

What's the right PCSX2 and plugin version should I use?My DFGT cannot work properly with this.
I tried 1.3.0,1.4.0,copules of 1.5.0 git version on PCSX2 and 0.8.0 0.8.1 0.8.2 for plugin but all for them report "rawinput: Could not enqueue report data: 15" and the wheel itself is not in the center and basically not working when launch the game and buttons all mapped wrong.

@jackun
Copy link
Owner Author

jackun commented Jan 10, 2020 •
edited
Loading

Uncheck "Logitech wheel pass-through". (Deemit, it defaults to enabled.)

Do PS2 games support DFGT in its native mode? Plugin itself doesn't change its mode so the HID report format is probably wrong hence messed up inputs. It could work in GTF/DF/DFPro mode probably but isn't necessary.

Enqueue error is because game doesn't read input data as fast as wheel produces it if using pass-through. Might cause stale/laggy input.

@JamesLewisLiu
Copy link

Uncheck "Logitech wheel pass-through". (Deemit, it defaults to enabled.)

Do PS2 games support DFGT in its native mode? Plugin itself doesn't change its mode so the HID report format is probably wrong hence messed up inputs. It could work in GTF/DF/DFPro mode probably but isn't necessary.

Enqueue error is because game doesn't read input data as fast as wheel produces it if using pass-through. Might cause stale/laggy input.

After uncheck the pass-through it works flawlessly,thank you!
I mainly play GT4 so it should support DFGT?Or not?

@jackun
Copy link
Owner Author

jackun commented Jan 10, 2020 •
edited
Loading

IIRC Driving Force Pro is the newest it supports, DFGT launched with GT5 on PS3. 900 degree range is supported anyway so no difference.

@JamesLewisLiu
Copy link

JamesLewisLiu commented Jan 10, 2020 •
edited
Loading

IIRC Driving Force Pro is the newest it supports, DFGT launched with GT5 on PS3. 900 degree range is supported anyway so no difference.

I think I saw some videos on YouTube that someguy did connect it to PS2...That's weird
EDIT:Here is some reference

@jackun
Copy link
Owner Author

jackun commented Jan 10, 2020 •
edited
Loading

Yeah, newer wheels start up as "Driving Force" initially and DFGT, G25, G27 support acting as old wheels. On PC, driver (or LG HUB nowadays) then sends a command that switches it into "native" mode with full supported features (900° range etc.).

I meant, for PCSX2, there's no difference what wheel you use if you can set it to at least 270/900 degrees, mostly :P Games only see the emulated type.

jackun pushed a commit that referenced this issue Sep 28, 2020
@jackun
hw: usb: hcd-ohci: check len and frame_number variables
54ae639 
While servicing the OHCI transfer descriptors(TD), OHCI host
controller derives variables 'start_addr', 'end_addr', 'len'
etc. from values supplied by the host controller driver.
Host controller driver may supply values such that using
above variables leads to out-of-bounds access issues.
Add checks to avoid them.

AddressSanitizer: stack-buffer-overflow on address 0x7ffd53af76a0
  READ of size 2 at 0x7ffd53af76a0 thread T0
  #0 ohci_service_iso_td ../hw/usb/hcd-ohci.c:734
  #1 ohci_service_ed_list ../hw/usb/hcd-ohci.c:1180
  #2 ohci_process_lists ../hw/usb/hcd-ohci.c:1214
  #3 ohci_frame_boundary ../hw/usb/hcd-ohci.c:1257
  #4 timerlist_run_timers ../util/qemu-timer.c:572
  #5 qemu_clock_run_timers ../util/qemu-timer.c:586
  #6 qemu_clock_run_all_timers ../util/qemu-timer.c:672
  #7 main_loop_wait ../util/main-loop.c:527
  #8 qemu_main_loop ../softmmu/vl.c:1676
  #9 main ../softmmu/main.c:50

Reported-by: Gaoning Pan <[email protected]>
Reported-by: Yongkang Jia <[email protected]>
Reported-by: Yi Ren <[email protected]>
Signed-off-by: Prasad J Pandit <[email protected]>
Message-id: [email protected]
Signed-off-by: Gerd Hoffmann <[email protected]>
jackun pushed a commit that referenced this issue Nov 6, 2020
@jackun
hw: usb: hcd-ohci: check len and frame_number variables
a4db3a4 
While servicing the OHCI transfer descriptors(TD), OHCI host
controller derives variables 'start_addr', 'end_addr', 'len'
etc. from values supplied by the host controller driver.
Host controller driver may supply values such that using
above variables leads to out-of-bounds access issues.
Add checks to avoid them.

AddressSanitizer: stack-buffer-overflow on address 0x7ffd53af76a0
  READ of size 2 at 0x7ffd53af76a0 thread T0
  #0 ohci_service_iso_td ../hw/usb/hcd-ohci.c:734
  #1 ohci_service_ed_list ../hw/usb/hcd-ohci.c:1180
  #2 ohci_process_lists ../hw/usb/hcd-ohci.c:1214
  #3 ohci_frame_boundary ../hw/usb/hcd-ohci.c:1257
  #4 timerlist_run_timers ../util/qemu-timer.c:572
  #5 qemu_clock_run_timers ../util/qemu-timer.c:586
  #6 qemu_clock_run_all_timers ../util/qemu-timer.c:672
  #7 main_loop_wait ../util/main-loop.c:527
  #8 qemu_main_loop ../softmmu/vl.c:1676
  #9 main ../softmmu/main.c:50

Reported-by: Gaoning Pan <[email protected]>
Reported-by: Yongkang Jia <[email protected]>
Reported-by: Yi Ren <[email protected]>
Signed-off-by: Prasad J Pandit <[email protected]>
Message-id: [email protected]
Signed-off-by: Gerd Hoffmann <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jackun @JamesLewisLiu