Open GoogleCodeExporter opened 9 years ago
Does the lox box give you any info about why it is disconnecting? Does it do
this after you just connect or after giving any user input? I need more info to
determine the problem cause.
Original comment by kytechne...@gmail.com
on 25 Jun 2014 at 3:40
ok sorry for taking so long to reply and for not giving a lot of info the first post. I am using a knock-off wireless receiver and chatpad if that makes any difference, I'm also running 64-bit windows 8. I've tried using 2 different controllers as well with no difference.
Nothing comes up in the message box as to the controller disconnecting or anything else. I can type what ever I want for about 5 seconds and then I can't type anything for 8ish seconds. I was able to set it all up perfectly and I followed the instructions exactly and didn't run into any problems until this.
I really appreciate your work! This is really amazing so far, I was beginning to think I wouldn't be able to use that chatpad on my comp which really would be a shame. Thank you!
Original comment by Mitchell...@gmail.com
on 29 Jun 2014 at 8:36
sometimes knock-offs will be a little weird with this. They will ship their own
version of the standard driver and this causes lots of issues for us. Try
uninstalling the program and try downloading the original driver from Microsoft
and then setting up with the directions on the home page. Let me know if that
helps.
Original comment by kytechne...@gmail.com
on 28 Sep 2014 at 10:48
[deleted comment]
Original comment by kytechne...@gmail.com
on 9 Jan 2015 at 4:24
I am having this issue as well. I am using genuine hardware. All gamepad
controls are usable 100% of the time, but the chatpad will only allow me to use
any key for a window of about 5 seconds, followed by a window of 30 seconds
where the chatpad has 0 functionality. During the 0 functionality of the
chatpad, I am still able to use the gamepad controls.
Using Ryan Buerger of The Pocket of Resistance, llc, Driver, I was able to use
chatpad 100% of the time (although I do not have any mouse control with his
driver).
So the time-out doesn't seem to be hardware related.
Original comment by weezl2...@gmail.com
on 19 Jun 2015 at 7:13
Original issue reported on code.google.com by
Mitchell...@gmail.com
on 25 Jun 2014 at 9:48