Re: F1 23 vr and t300

Edit: First two steps provided resolution.

3I UEFI is available. https://www.msi.com/Motherboard/B450-TOMAHAWK-MAX/support

AMD Chipset driver v6  https://www.amd.com/en/support/chipsets/amd-socket-am4/b450

Remove MSI Center if installed.

Nvidia driver is not latest  https://www.nvidia.co.uk/download/driverResults.aspx/218133/en-uk

T300 FFB driver is not registered? https://support.thrustmaster.com/en/product/t300servobase-en/ (Installing the software a second time removes it, try the Thrustmaster CP)

---

Device Name: Thrustmaster T300RS Racing Wheel
Attached: 1
Controller ID: 0x2
Vendor/Product ID: 0x044F, 0xB66E
FF Driver: %SystemRoot%\system32\tmpid.dll
FF Driver Date:
FF Driver Version:
FF Driver Size: 0 bytes

---

Lots of non-standard equipment (BT mouse, USB keyboard, iCUE RGB, USB audio, etc.) before we even get to the Quest 2 https://www.meta.com/gb/quest/setup/

I do suggest trying to troubleshoot the 2D game first in a 'divide and conquer' approach.

Remove the Quest, play 2D game - do you still have the framedrop? Keep removing.

Try standard keyboard and mouse. Old thread, but might be insightful https://www.reddit.com/r/razer/comments/kpp3hu/ysk_how_to_disable_razer_game_manager_service_as/

WER does have a lot of Razer errors.

Uninstall the RGB control software.

Try onboard audio instead of USB https://www.msi.com/Motherboard/B450-TOMAHAWK-MAX/support#driver but check updates https://www.uaudio.com/volt/start

Disconnect the second display.

I also suggest connecting T300 to USB 2.0 (under PS/2) and probably your keyboard. They are both USB 1.1 devices.

If we can get the 2D game working and it's literally only when the Quest is connected then I could try connecting my Quest but I don't have the T300 so a direct comparison is impossible.