Greetings all. Wish I could help Frisk or Goonie, but I don't have the Thrustmaster or Heusinkveld products to answer such questions. Sorry.
So my bro-in-law never bothered trying to get the DriveHub working with his Xbox Series X and Fanatec parts... because I didn't have any luck getting mine into "Fanatec" mode and getting the extra switches and knobs working on the Xbox.
I however have the PS5, and using 2.07 Beta 8, F1 2019, and some combination of hooking turning on the PS5, using the buttons on the wheel to try and put the wheel into "Fanatec" mode (as opposed to Fanalogic, where the wheel looks like a Logitech G series wheel to F1 2019), plugging the pedals into the drive hub, and then opening the game... the game saw the wheel in pedals in "Fanatec" mode at least once, so I could setup the up/down switches as additional inputs in F1 2019. I use the right one for fuel mix, and the left for the diff. setting.
Since then, I updated my DriveHub to 2.08 Beta 4, bought F1 2020 on sale this morning for $15 from the PS Store, and tried getting things hooked up and working on the PS5 again in "Fanatec" mode. But try as I might, the system only sees the Fanatec gear as "Fanalogic" (aka Logitech) parts... and it won't let me configure the extra switches like F1 2019 did.
I have no idea if the latest Beta might have impacted things. If I'm using the right "buttons" to put the wheel into Fanatec mode while the pedals aren't connect, and BEFORE I open the game on my PS5 or what. As I understand it, to configure the controller for Fanatec mode, with a F1 style wheel, you hold the two bottom most buttons on the wheel for about 5 seconds. Only FREQUENTLY when I do that... 1) The system takes a screen shot, because that's what the bottom most "left" button does with that wheel, and 2) The entire wheel controller becomes "unresponsive" (aka I can't use the joystick, buttons, or anything with the console. It's like it goes into a different mode, and the system looses "sight" of the wheel... if that makes sense).
Just wondering if anyone else might have seen this issue and have a suggestion on what I need to do to "fix" it. I'm guessing just going back to 2.07 Beta 8 might be a good start, since I don't have the Thrustmaster gear, which seems to be what Podger updated it for. Does that sound best or ?