Thrustmaster 300 loses connection

Hi,

My setup:
-I am running the virutalhere client on my pc.
-I am streaming f1 2019 to my tv with steamlink.
-I have connected my thrustmaster t300 to a raspberrypi 4B with virtualhere.

Occasionally my steering wheel will lose connection to the game. This noticeable by the fact that my input doesn't matter anymore and the game remembers the last input of the wheel. So if I am pressing the gas paddle and I steer right, the game will continue doing this until the wheel connects again after a few seconds (sometimes 1, sometimes 4). This always ends up with me in a wall with my f1 car. ( I have this problem with multiple racing games by the way)

I have this problem for several months. I did not have this problem with my steering wheel directly connected to my pc. The problems occurs sometimes 1 time in a evening of gaming and sometimes up to 6 times...
I do notice that it happens more often when I am talking to someone via steam, skype or discord, so it may be a network thing? But I am clueless about options.

I would like to hear of someone has a solution to this to try.

#2

Hi, could you tell me if everything is connected with a LAN cable? Or are somethings connected via wifi?If possible everything should be connected via lan cable.

#3

Oh yeah should have stated that. Everything is connected with cat5e cables. I personally almost never use wifi for anything.

#4

Sorry another question, is "steamlink" also running on your pi4 (they have a pi app now) or do you have the actual valve steamlink box from a few years ago. I want to know if the same device is doing everything , or you are using two different devices.

#5

I am using two devices. I started with the game and wheel on the valve steamlink. But the steamlink Just couldnt handle it. So I bought a rpi and started using that one for the wheel.
So wheel rpi and game valve steamlink

#6

OK try this

1. ssh to the pi and then do

sudo renice -19 `pidof vhusbdarm`

2. On the pc bring up task manager -> Details->Right click on vhui64.exe and Set Priority High

I think starvation is happening on either IO or cpu but im not sure.

If you force both processes to get the cpu when they need it it might be enough to fix the issue.

#8

That did not work unfortunately. I also tried switching the option to prioritize network traffic off in the steam link. No effect either :(

#9

It does not occur more often when I am calling someone, but when I am racing multiplayer.

#10

Ok i dont know the issue sorry (I assume you've updated the wheel firmware to the latest (31 at this time of writing) and the thrustmaster client drivers are also the latest)

#12

As I have the rpi 4B 1gb RAM. Do you think a rpi with more RAM could fix the problem?

#13

1GB is plenty for virtualhere. Virtualhere only takes about 10MB per connection. And you only have a few (or one connections)

#14

Oh okay. I will try tonight with all new installed drivers and virtualhere. Maybe I'm lucky...

#15

My friend has a rpi 4b with 4gb ram so I just tried. It loses connection like every 3 or 4 seconds, so that only made things worse.
I tried priority high, realtime and normal. And 0, -19 and -20 on the pi. No difference..

#16

Are there settings in the virtualhere client that I could try changing?

#17

No there aren't any specific settings.

I don't think it is virtualhere specifically, i suspect its some latency in the system. Probably the network is delivering one or a few usb packets a bit delayed and that is enough to confuse the wheel for a few seconds until the network stabilizes again but thats just a guess...

#18

I did online races for 3 straight hours yesterday without the wheel losing connection!
It looks like the trick was to reset the settings to default on virtualhere, although I don't know how or why.

#19

OK weird, hopefully it keeps working fine for you then.

#20

Yeah hopefully. Thanks for the help Micheal!

#21

Problem occurd 2 times yesterday. Not even in online mode. I think only difference with saturday was that I booted the game from big picture mode saturday.
Could be that I was just lucky saturday..

Or people were using less internet in the house saturday as it was almost midnight..

#22

Looks like I was lucky that one night. Maybe because it was a lot later than I usually race and less people in the house were using the internet? We share the router with 6 people so maybe that could be something...

#23

I just realised that when the wheel stopped every couple seconds, the virtualhere client was constantly searching for hubs. It didn't after anymore te reset. Maybe you can think about something with that info.

#24

Try turning off auto-find by right clicking USB Hubs->Auto-Find Hubs and UNcheck that. If you cant see your server, you will need to put the ip address of your server directly i the client by right clicking USB Hubs->Specify Hubs

#25

Tried that yesterday. Finished 2 25% races without any problem on a normal time, so it may be helping. Will know sure tomorrow evening.