+INFO: 7th positionIssue status: Acknowledged (so Frontier previously has confirmed it)
Today this issue is 9th position at Top Voted of this status (next status should be: Fixed)
Request for more than 32 buttons (Virpil throttle)
Need a link to it.
Issue Tracker
issues.frontierstore.net
Have to say I am a bit disappointed now.
Had the hope that it will be fixed with Odyssey release.
Had the hope that it will be fixed with Odyssey release.
Have MS fixed the 'default' HID stack in Win10 yet? IIRC, this is the issue, not DirectX, at least not any more.
The very same setup just works in other titles, some of them older than ED. While I will admit that MS likely did not make it easy, it's very clear that other devs have figured it out. So, I still don't get why this is even an issue in a sim made more than a decade after 2001.
The way to avoid it is to avoid using the Win10 HID drivers/stack. I'm not sure why FDev haven't taken this option, but MS really need to fix the defaults. At its core, it's an OS issue, which means that it is the OS dev who needs to fix it - not have 3rd party devs provide a workaround.
Despite what the nix crowd might wish to believe, most of us don't really have a choice with our OS. I do have a choice with what games I play and continue to spend money on, and devs have a choice in what they support. If others are willing to make this work for my money...........
I spent a lot of money on my Virpil gear, to not be able to use it fully, or have to kludge together "fixes" and work arounds to make it work, only to have to undo those workarounds to play games from devs that have figured it out. You can say MS needs to fix it all you want, you are not even wrong to do so, but the reality is that other devs have already fixed their games to deal with it. So the question is, why hasn't Fdev?
Are you against Fdev fixing this for us? Or is this just finger pointing for the sake of it?
Like I said, I've no idea why FDev haven't 'fixed' it. As far as finger pointing goes, I think the pot is calling the kettle black here - and only one is pointing where the blame truly lies. I'm all for holding devs to account for their failures, but get the right devs.
I do have the right devs, you do as well. But the reality is, if other devs can adapt their code to work on the Win10, so can Fdev. MS is not getting a pass here, but; Do I have more of a chance to get MS to change their code to work with Fdevs code, than I do of getting Fdev to change theirs to work with MS code, when so many other sim devs have already adapted?
Based on the current state of Odyssey, I fear there will be no fix for that before the next year.
FDev will have to spend every second to fix Odyssey before the console launch.
FDev will have to spend every second to fix Odyssey before the console launch.
Unfortunately i fear the same which makes me sad.
I still hope that this will be implemented for the launch of the consoles.
Yes, but it's also ignored (not started) by the devs