So you just downloaded an old version and Win10 let you install it instead of 12? Cool.
That's not quite the way DirectX works. DirectX is a massive set of instructions required for gaming and multimedia - think 3D graphics, surround sound, controllers and what not - and some of those instruction sets are removed or replaced instead of being updated as new versions come out. So when you install an old DX version you're just adding back those missing components, not downgrading what's already there.
Another interesting thing. I tried the Xbox Shilling and it fails too.
Any kind of software that uses a controller, be it games or Mach3 plugins, rely on Windows to interpret the hardware and provide access to whichever sticks and buttons that controller might have. So if Windows doesn't understand the hardware, which for these old controllers requires DX9, nothing will be able to use it.
Working! But I don't know why. I reinstalled Xbox Controller and the Xbox 360_64Eng and the errors stopped showing up on startup. Then I could edit the Xbox plugging. Closed and reopened and the controller worked.
Nice! Windows can be picky about which order you install things in, as they can rely on each other in more or less logical ways. And most lower level stuff can only be loaded during the startup process of the program or the computer itself. That's why you need to restart Mach3 if a wireless controller goes into standby mode after a while and cuts the connection. So, as always when you're dealing with Windows: If in doubt, reboot :-)
Btw, XBox360_64Eng shouldn't be required for Windows 10. That's a driver that's included in the OS, or automatically downloaded from Windows Update when you plug it in.
Lars
Guest
Show Posts