Does it happen in other games? Or just DCS? I am going to try IL-2
Does it happen in other games? Or just DCS? I am going to try IL-2
DOnly the rhino causes this issue, I have used many other joysticks and it doesnt freeze dcs
DThis is my motherboard
HI have only DCS so I can't comment on other games. I believe not all AMD based motherboards exhibit this issue. For example, this problem shows up on my X570 motherboard but never on my son's B550. The quickest way to find out if it's USB related is to try walmis' little Python program -> 🧰support. It keeps sending "Interrupt OUT" commands to VPForce's endpoint. If the endpoint ever not responds in time, you'll see this pops out on the screen.
YThe AMD USB controller, specifically the x570chipset, has been an issue with VR as well. It has been common to recommend a PCIE USB card for people having connectivity issues.
Just some additional information to keep in mind
Just some additional information to keep in mind
Dthanks @yeoldgrog
MAargh, I have a ROG Crosshair VIII extreme. I'm using all M2 slots on the board so PCIE-2 is out of order
Does anybody have a idea how to add a stable usb controller?
Does anybody have a idea how to add a stable usb controller?
DI run the python script and it works, until it crashes in DCS
Dand by crash, I mean the screen just dissapears
Dhowever with the configurator program
D
Dis this the same issue @walmis ?
DI had to unplug USB to get DCS to respond again
HDid your X570 motherboard already exhibit the USB disconnect issue with the VPForce controller? Not all X570 boards present this problem unless you're unlucky like me. I think there is chip to chip variation with AMD's B550/X570 chipsets. I wouldn't recommend using an external USB hub since the hub most likely has a switchplexer chip instead of a totally different USB controller chip. Most PCIe USB cards only uses PCIe 3.0 slot. Do you not have this slot available?
MI've had weekly usb dropouts with my SFX100 system and it now occurs to me this could be the problem. I am now trying to start up Walmis his script to scan the usb ports but i'm a total noob with Python and Powershell. Nope all PCIE slots are out. It's a config problem with this board. You can only choose PCIE-1+M1+M2 or PCIE-1+2 and some variations . But my startup disk is M1 and thats just the one wich can't be missed.
HDon't bother running Walmis' Python script if you don't have VPforce controller. The script first looks for VPforce controller and bombards the controller with USB packets unless you know how to modify for your SFX100.
MÀh, that saves me a lot of hassle 
No I'm not that skilled @ this moment to mod a script to the sfx system.
No I'm not that skilled @ this moment to mod a script to the sfx system.
WHey, I'm thinking of mailiing a board to you with a different MCU. Maybe it's got something to do with USB controller hardware on the MCU itself. And I can't reproduce this locally 
HDo you mean a different MCU unit from the same vendor/model as what I have or different MCU by a completely different vendor? I haven't had any issues once I used a PCIe USB card to talk to the VPforce controller I have.
WYeah, I have used different stm32f103 compatible chips, so maybe there are some nuances that don't play nice with AMD USB chipsets 
WOne more thing to try is to increase the USB interrupt priority (in the firmware)
HI just don't want you to waste money sending me another VPforce controller if the problem is to do with AMD's chipset.
WBut I'm interested in narrowing it down, whether the issue is some specific MCU + AMD combination
HI'm not familiar with the specific MCU on my VPforce controller board. Do you happen to know if this MCU has a register setting to increase the differential driving strength (usually in the form of increasing current)? Sometimes driving hard can increase signal to interference/noise ratio. If there is, you can build a custom firmware for me to test out for the sake of curiosity.
Deven if the setting for driving strength is turned off completely, the crash still occurs
DI'm not sold on that it's an issue with the forces applied
Si'm getting this error too, i saw above maybe the
report_id is incorrect? what should it be? Asking because i also have a X570 and every FFB program i am trying crashes in some way.
Wtry report_id=106
Wuhh this sucks
Wneed to find a workaround
Ssame deal
Sis a PCI USB card in my future? 
Slet me try restarting.. it may be stuck from a crashed airforce player
Syep. 106 is firing away
Soh wait it stopped
Wweird that it's 0ms
Wit should run at ~1 ms
Smost of them were
Wdoes the USB reconnect or drop out?
Sno, theres no usb disconnect sound or anything. your configurator still talks to it fine. but can't run hidtest anymore, instant error.
Whmm, maybe the endpoint is in NAKed state... for some reason
Sgotta run for a little bit, have a meeting to connect to
Wroger that, perhaps if you have time we could make a remote desktop session, could try a few things
HWith Wireshark capture, I found that the problem was that the ACK from Endpoint responding to Host's Interrupt OUT got stuck in Host's buffer inside AMD's USB controller. This ACK was never subsequently properly processed and fed back to the host program in the PC. For programs like DCS, it does not allow for any non response from Endpoint, therefore USB hangs causing DCS itself to freeze until USB gets reset. VPforce configurator, on the other hand, doesn't seem to care whether it gets ACK or not so it continues to chug along. The fact that the ACK finally showed up after either we unplugged the USB cable or Walmis' hidtest program cleared itself after HIDException means that the ACK was properly sent by Endpoint (VPforce controller) but, for some reason, was never processed by the USB Host controller inside AMD's chipset.
WI think I might be able to workaround this, @smitty981 ran some tests using a test firmware, and I found out the HID OUT endpoint gets stuck in NAK mode, so I will try to reset it back to active mode
HGood eyes! I didn't bother to look at the content in the ACK sent by Endpoint. The bad ACK has "IRP USBD_STATUS: USBD_STATUS_CANCELED (0xc0010000)" instead of "IRP USBD_STATUS: USBD_STATUS_SUCCESS (0x00000000)". This changes the whole dynamic. I wonder if it's possible to increase the driving strength of AMD's host USB differential driver...
WI doubt that the signalling causes this, it's running at 12mbits, I have 33ohm series resistors on the board, so should be nice and clean
HThen I have trouble understanding why there's never an USB issue when the 20V supply is shut off...
Whmm, perhaps because there's no motor communication = less interrupt load
Wmight be some race condition, that's amplified with AMD board 
