Difference between revisions of "Talk:Padscore.rpl"
Jump to navigation
Jump to search
CreeperMario (talk | contribs) m (Responded with results to Tueidj's theory.) |
|||
| Line 3: | Line 3: | ||
: Just a guess but try actually checking the return value of WPADRead? [[User:Tueidj|Tueidj]] ([[User talk:Tueidj|talk]]) 11:46, 20 April 2016 (CEST) | : Just a guess but try actually checking the return value of WPADRead? [[User:Tueidj|Tueidj]] ([[User talk:Tueidj|talk]]) 11:46, 20 April 2016 (CEST) | ||
:: Just tested that theory, and it appears that WPADRead always returns with 0, regardless of the input. The value of WPADStatus.err is randomized when remotes are disconnected, sometimes being zero, sometimes not. [[User:CreeperMario|CreeperMario]] ([[User talk:CreeperMario|talk]]) 12:45, 20 April 2016 (CEST) | :: Just tested that theory, and it appears that WPADRead always returns with 0, regardless of the input. The value of WPADStatus.err is randomized when remotes are disconnected, sometimes being zero, sometimes not. [[User:CreeperMario|CreeperMario]] ([[User talk:CreeperMario|talk]]) 12:45, 20 April 2016 (CEST) | ||
| + | ::: In that case check if there's a function called WPADProbe which is what the wii's WPAD library uses for controller detection. [[User:Tueidj|Tueidj]] ([[User talk:Tueidj|talk]]) 01:44, 21 April 2016 (CEST) | ||
Revision as of 01:44, 21 April 2016
Reading Remote Values
Does anybody know how to correctly read data from the Wii Remote? Calling WPADRead and reading the button presses works perfectly, as long as the controllers are actually connected. If the controllers aren't connected, (mostly with controllers 3 and 4) I get a garbled mess of fake button presses. Does anybody know why? (see Wii Remote Button Tester for an example) You will see that some buttons are reported as being pressed, even though the controller isn't connected. CreeperMario (talk) 10:28, 20 April 2016 (CEST)
- Just a guess but try actually checking the return value of WPADRead? Tueidj (talk) 11:46, 20 April 2016 (CEST)
- Just tested that theory, and it appears that WPADRead always returns with 0, regardless of the input. The value of WPADStatus.err is randomized when remotes are disconnected, sometimes being zero, sometimes not. CreeperMario (talk) 12:45, 20 April 2016 (CEST)