Share on other sites

So far I've only tested on Win 7. I'll see if I can connect my two game controller devices to my one and only Win10 PC. -- not easy. it's only got one USB port so I need to free up a USB hub from somewhere ... :-(

Share this post

Link to post

Share on other sites

Strange, with all my joysticks and HIDs I've never had a problem with Win10 doesn't recognize or changes them

It's just this one function. The callback is supposed to be repeated called by Windows until either I say enough or it says there's no more. Once I've invoked this procedure it's out of my control, theonly code in my program is when it calls me. The logging shows it simply doesn't call me after the first device.

I've posted this as a question on MSDN but i'm not hopeful for an answer that way.

It looks like I'll have to test for Win10 and not include this improvement (on the very system in which it is most needed!). Such a shame.

I'll continue to look for a solution. Maybe sleeping on it will give me some bright idea.

Share this post

Link to post

Share on other sites

The work-around is to enumerate All devices, not just Attached devices. Somehow they've broken the "attached" device checking in Win10, as it works fine in Win7. I've modified my code to cope, and have already uploaded 4.963f to the Download Llinks subforum. Please use that. I'd like to see the log still please, but only with the "LogExtras=x200000 parameter set if there's still a problem.

Don't use anything later than 4.963 on Win10 at all, until I release 4.964. I've had to revert back to the older joystick scanning. The new one, which looks so good on Win7, is simply using broken facilities on Win10. Maybe I'll try again in 6 months or a year in the hope that MS will fix it.