Last updated: 9 August 2026
Device Support Policy
Which devices get a DNR profile, and why we ask manufacturers to send us the hardware before we build one.
Your membership gets you every profile we have built, for every device we support. If a device is not on that list, we have not built for it, and we cannot promise we will.
The reason is simple: we do not write a profile for hardware we do not own.
The current list lives on the compatible devices page and is kept up to date as new hardware is added.
If your device is not there, it has no DNR support today and we are not promising it in future. That is not us being difficult, it is us not wanting to leave you waiting on something that may never come.
The most useful thing you can do is tell the manufacturer you want it. Demand reaching them is what starts the conversation, and it carries far more weight coming from the people buying their hardware than from us.
If a manufacturer wants their customers to get DNR content, we ask them to send us the device. Not on loan, and not to borrow. There are three reasons, and none of them are about the money.
It pays for the work
A profile is not a config file. It is written, tested, then maintained through every revision and every plugin update after that. The value of the device offsets those hours and the integration work in the DNR SimHub plugin.
It is the only way to test properly
DNR profiles are built in JavaScript, not assembled from presets, and every theme has to be checked against the real device. Button behaviour especially cannot be guessed at. No manufacturer would ship hardware untested, and we will not ship software untested for exactly the same reason.
Nobody wants to owe anybody a wheel
Hardware used hard breaks. High force feedback, constant handling, months of testing across multiple sims. If the device is ours, a failure is our problem and nobody is left arguing about who owes what.
Then we cannot build the profile. That is the honest answer.
We do look at exceptions. Whether one is possible depends on the device, how long the integration would take and how complicated the profile would be, and the decision is ours. It is worth asking, but please do not read this paragraph as a yes.