Close

Page 20 of 23 FirstFirst ... 101819202122 ... LastLast
Results 191 to 200 of 229
  1. #191
    New user
    Join Date
    29.05.2018
    Posts
    9
    The log from the last version:

    20180530/144518: WiimoteHook Log for version: 20180530/120833/alpha
    20180530/144518: : Windows 8 or newer, using the new send method20180530/144518: : Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)20180530/144520: : The current send-data method failed. Trying another one.20180530/144522: : The send-data method failed yet again. Trying another one.20180530/144522: : Windows 8 or newer, using the new send method20180530/144522: : Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)20180530/144524: : The current send-data method failed. Trying another one.20180530/144526: : The send-data method failed yet again. Trying another one.20180530/144526: : Windows 8 or newer, using the new send method20180530/144526: : Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)20180530/144528: : The current send-data method failed. Trying another one.20180530/144530: : The send-data method failed yet again. Trying another one.20180530/144530: : Windows 8 or newer, using the new send method20180530/144530: : Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)20180530/144530: : Calibration data for a 0x0306:
    20180530/144530: : Base Calibration data: 80 80 80 00 9a 9a 9a 00 40 e3 80 80 80 00 9a 9a 9a 00 40 e3 00 00 00 00 00 00 00 00 00 00 00 00 (128, 128, 128, 154, 154, 154)
    20180530/144530: : Requesting a status manually20180530/144530: : We got a status report20180530/144530: : We asked for this report20180530/144530: : ex: PartiallyInserted mp: MotionPlusInactive con: True atAtBoot: True20180530/144530: : Re-read Partially Inserted: ex: Nunchuk mp: MotionPlusInactive20180530/144530: : pCombo: None nCombo: MotionPlus_Nunchuk20180530/144530: : Nunchuk data: 7a 7a 7c 2c ac ae af 13 e5 21 83 e1 22 75 0e 63 7a 7a 7c 2c ac ae af 13 e5 21 83 e1 22 75 0e 63 (122, 122, 124, 172, 174, 175, 229, 33, 131, 225, 34, 117)
    20180530/144530: : MotionPlus data: 79 6d 78 9a 78 92 2d 46 d3 7f 2c db c8 28 46 74 66 45 79 50 79 75 33 4e cd b0 31 ed 2d 47 25 74
    20180530/144530: : Extension mode set to: MotionPlus with Nunchuk Passthrough20180530/144530: : We got a status report20180530/144530: : We didn't ask for this report20180530/144531: : We got a status report20180530/144531: : We didn't ask for this report20180530/144531: : ex: MotionPlus_Nunchuck mp: MotionPlus_Nunchuk_Passthrough con: False atAtBoot: False20180530/144531: : pCombo: MotionPlus_Nunchuk nCombo: MotionPlus_Nunchuk20180530/144531: : Extension mode: No change20180530/144531: : We didn't ask for this report and therefore we will now set the report type20180530/144535: : ex: None mp: None con: True atAtBoot: False20180530/144535: : pCombo: MotionPlus_Nunchuk nCombo: None20180530/144535: : Extension mode: No change20180530/144535: : We didn't ask for this report and therefore we will now set the report type

  2. #192
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385
    Sorry for the bad formatting of the log by the way; that should be fixed on the current version uploaded (I can read your log fine though so no need to re-send it).

    Interesting log. Problem is I don't see much difference in negotiation compared to an original remote (they have the same ID).


    However, your log indirectly gave me the idea to fix a long-standing issue about concurrent status reports so thanks I guess. The remotes have a tendency in certain cases to keep spamming their "I'm here with a new status!" report even when a previous report is not already done being processed and dealt with. I now fixed a behavior related to that and it simply waits for each report processing to finish before the next one.

    This has fixed a long-standing issue with original wii remotes + MP extension not working properly with the "recheck for extensions" feature but also it should make the whole thing more stable in general.

    First post is updated with that new version

    PS. This change will probably not fix your issue on the 3rd party remote, but I wouldn't be surprised if it does either.
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

  3. #193
    New user
    Join Date
    29.05.2018
    Posts
    9
    You're welcome,
    I just bought an official WiiU remote with motion plus inside, and a motion plus adaptater for my normal wiimote and they work fine.
    But My 3rd party remote still doesn't work with the nunchuck, and strangly it doesn't rumble too.

    Edit: I just noticed that my WiiU remote's motion direction are all reversed o_O
    The log:
    20180530/185739: WiimoteHook Log for version: 20180530/150259/alpha
    20180530/185739: Windows 8 or newer, using the new send method
    20180530/185739: Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)
    20180530/185741: The current send-data method failed. Trying another one.
    20180530/185743: The send-data method failed yet again. Trying another one.
    20180530/185743: Windows 8 or newer, using the new send method
    20180530/185743: Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)
    20180530/185745: The current send-data method failed. Trying another one.
    20180530/185747: The send-data method failed yet again. Trying another one.
    20180530/185747: Windows 8 or newer, using the new send method
    20180530/185747: Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)
    20180530/185749: The current send-data method failed. Trying another one.
    20180530/185751: The send-data method failed yet again. Trying another one.
    20180530/185751: Windows 8 or newer, using the new send method
    20180530/185751: Device ID: 0x0306 (RVL-CNT-01, one of the legacy ones)
    20180530/185751: Calibration data for a 0x0306:
    20180530/185751: Base Calibration data: 80 80 7f 02 99 99 98 21 00 c1 80 80 7f 02 99 99 98 21 00 c1 ff ff ff ff ff ff ff ff ff ff ff ff (128, 128, 127, 153, 153, 152)
    20180530/185751: Requesting a status manually
    20180530/185751: We got a status report
    20180530/185751: Status was free; continuing
    20180530/185751: We asked for this report
    20180530/185753: ex: MotionPlusInternal_Nunchuck mp: None con: True at boot: True
    20180530/185753: Deactivating a previously activated MotionPlus to get Extension info
    20180530/185753: We got a status report
    20180530/185753: Status was locked; waiting
    20180530/185753: We didn't ask for this report
    20180530/185753: We got a status report
    20180530/185753: Status was locked; waiting
    20180530/185753: ex: Nunchuk mp: MotionPlusInactive con: False at boot: False
    20180530/185753: pCombo: None nCombo: MotionPlus_Nunchuk
    20180530/185753: Nunchuk data: 7a 7b 7b 31 ad af ae 07 e4 22 81 dc 25 80 0f 64 7a 7b 7b 31 ad af ae 07 e4 22 81 dc 25 80 0f 64 (122, 123, 123, 173, 175, 174, 228, 34, 129, 220, 37, 128)
    20180530/185753: MotionPlus data: 7c a4 7c b3 7d ae cb 78 35 15 ca c8 c8 81 e6 e3 7c 8d 7c d1 81 1a c8 8d 37 a5 c7 f5 2d 85 cf 57
    20180530/185753: Extension mode set to: MotionPlus with Nunchuk Passthrough
    20180530/185753: Setting the report type after a status report
    20180530/185753: We didn't ask for this report
    20180530/185753: We got a status report
    20180530/185753: Status was locked; waiting
    20180530/185753: Status was locked; waiting
    20180530/185755: ex: MotionPlusInternal_Nunchuck mp: None con: True at boot: False
    20180530/185755: pCombo: MotionPlus_Nunchuk nCombo: MotionPlus_Nunchuk
    20180530/185755: Extension mode: No change
    20180530/185755: Setting the report type after a status report
    20180530/185755: We didn't ask for this report
    20180530/185757: ex: MotionPlusInternal_Nunchuck mp: None con: False at boot: False
    20180530/185757: pCombo: MotionPlus_Nunchuk nCombo: MotionPlus_Nunchuk
    20180530/185757: Extension mode: No change
    20180530/185757: Setting the report type after a status report
    20180530/185757: We didn't ask for this report
    20180530/185759: ex: MotionPlusInternal_Nunchuck mp: None con: True at boot: False
    20180530/185759: pCombo: MotionPlus_Nunchuk nCombo: MotionPlus_Nunchuk
    20180530/185759: Extension mode: No change
    20180530/185759: Setting the report type after a status report
    Last edited by Madao; 30.05.2018 at 19:00.

  4. #194
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385
    Quote Originally Posted by Madao View Post
    I just bought an official WiiU remote with motion plus inside
    Odd, because the newer remote pluses have the 0x0330 id instead of 0x0306. Anyway, for that inversion issue try changing in WiimoteHook.exe.cfg the value of "DoNotInvertMotionPlusAxesOnLegacyRemotes" from "No" to "Yes".

    edit: Ah, it might be an issue with dolphinbar's HIDs (it seems to be done via that because I notice it finds bogus HIDs at the start). I generally prefer using directly a Bluetooth adapter but DolphinBar also works that way.
    Last edited by epigramx; 30.05.2018 at 19:25.
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

  5. #195
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385
    To clarify something implied previously, while I haven't confirmed it myself since I don't own that device, the DolphinBar appears to make virtual devices that always have the 0x0306 ID and that means the axes of the gyroscope might be inverted if the remote is one of the newer ones. I have moved up the relevant option to revert that in the .config and also added a comment to make it clearer.

    The main reason of this oddity is that nobody has managed to fully reverse engineer the MP calibration data yet; when dolphin emulator works correctly with it they mainly do it via low level emulation (i.e. the Nintendo code does it for them). There was an old patch to simulate it with mice but I'm not sure that had completed that work either.

    for reference, example calibration data from an original vs a new remote plus that have inversed gyroscope axes against each other:

    Code:
    0x0306: 7a 8a 77 2b 77 3a 31 48 d5 27 27 e6 c8 30 b1 f9 83 4d 78 45 78 e0 36 da d1 dc 2a cc 2d 4f 48 cd
    
    0x0330: 7c 8f 7c 4e 7c ed cc 10 33 b0 cb 27 c8 96 78 7b 7c 2c 7b 0b 7d b6 c9 72 36 d2 c7 eb 2d 65 ff 79
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

  6. #196
    New user
    Join Date
    29.05.2018
    Posts
    9
    Ok, I changed the "DoNotInvertMotionPlusAxesOnLegacyRemotes" value as you say and it worked thank you alot.

  7. #197
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385
    I'm interested in people's "MotionPlus data" line from the log.txt in order to maybe find some patterns that distinguish old from new motion plus hardware (let me know if your remote is a genuine remote plus with an id of 0x0330 or not (dolphinbar might show it as 0x0306 but a direct connection to a bluetooth adapter might show the real one being 0x330). I think I saw a pattern already but it might be a red herring without further samples (most samples I can find on the web are either from old remotes or unclear from what they are).
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

  8. #198
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385

    I made an attempt to autodetect MotionPlus type (new or legacy) from its static calibration data mainly in order to go over DolphinBar possibly always simulating them as old ones so that the inversion of axes is done automatically more correctly. Since it's experimental, the behavior can still be overriden in the .config with a new option, "InvertMotionPlusAxes" if set to "Yes" instead of "Auto".

    Thanks to BooNhana, Madao and others for offering log data. I'd still be interested in log.txt files from people with 0x0330 remotes (the newer and genuine Remote Plus ones).

    First post is updated with that new version.

    PS. While I were at it I updated it so that if a .config file has a syntax error it no longer crashes but offers help
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

  9. #199
    New user
    Join Date
    29.05.2018
    Posts
    9
    Thank you for the update. The auto invertion option is verry convenient.

    If your still interest about log from "bluetooth dogle" + " newer genuine Remote Plus"
    Here is the log log:
    20180601/115119: WiimoteHook Log for version: 20180531/064642/alpha
    20180601/115119: Windows 8 or newer, using the new send method
    20180601/115119: Device ID: 0x0330 (RVL-CNT-01-TR, one of the new ones)
    20180601/115119: Calibration data for a 0x0330:
    20180601/115119: Base Calibration data: 80 80 7f 02 99 99 98 21 00 c1 80 80 7f 02 99 99 98 21 00 c1 ff ff ff ff ff ff ff ff ff ff ff ff (128, 128, 127, 153, 153, 152)
    20180601/115119: Requesting a status manually
    20180601/115119: We got a status report
    20180601/115119: Status was free; continuing
    20180601/115119: We asked for this report
    20180601/115121: ex: MotionPlusInternal mp: None con: True at boot: True
    20180601/115121: Deactivating a previously activated MotionPlus to get Extension info
    20180601/115121: We got a status report
    20180601/115121: Status was locked; waiting
    20180601/115121: We didn't ask for this report
    20180601/115123: ex: None mp: MotionPlusInactive con: False at boot: False
    20180601/115123: pCombo: None nCombo: MotionPlus
    20180601/115123: MotionPlus data: 7c a4 7c b3 7d ae cb 78 35 15 ca c8 c8 81 e6 e3 7c 8d 7c d1 81 1a c8 8d 37 a5 c7 f5 2d 85 cf 57
    20180601/115123: Extension mode set to: MotionPlus Exclusively
    20180601/115123: Setting the report type after a status report
    20180601/115123: We didn't ask for this report
    20180601/115125: ex: MotionPlusInternal mp: None con: True at boot: False
    20180601/115125: pCombo: MotionPlus nCombo: MotionPlus
    20180601/115125: Extension mode: No change
    20180601/115125: Setting the report type after a status report
    A second log from the last wiimotehook's version (which works correctly):
    20180601/120513: WiimoteHook Log for version: 20180601/062907/alpha
    20180601/120513: Windows 8 or newer, using the new send method
    20180601/120513: Device ID: 0x0330 (RVL-CNT-01-TR, one of the new ones)
    20180601/120513: Calibration data for a 0x0330:
    20180601/120513: Base Calibration data: 80 80 7f 02 99 99 98 21 00 c1 80 80 7f 02 99 99 98 21 00 c1 ff ff ff ff ff ff ff ff ff ff ff ff (128, 128, 127, 153, 153, 152)
    20180601/120513: Requesting a status manually
    20180601/120513: We got a status report
    20180601/120513: Status was free; continuing
    20180601/120513: We asked for this report
    20180601/120515: ex: MotionPlusInternal mp: None con: True at boot: True
    20180601/120515: Deactivating a previously activated MotionPlus to get Extension info
    20180601/120515: We got a status report
    20180601/120515: Status was locked; waiting
    20180601/120515: We didn't ask for this report
    20180601/120517: ex: None mp: MotionPlusInactive con: False at boot: False
    20180601/120517: pCombo: None nCombo: MotionPlus
    20180601/120517: MotionPlus data: 7c a4 7c b3 7d ae cb 78 35 15 ca c8 c8 81 e6 e3 7c 8d 7c d1 81 1a c8 8d 37 a5 c7 f5 2d 85 cf 57
    20180601/120517: Extension mode set to: MotionPlus Exclusively
    20180601/120517: Setting the report type after a status report
    20180601/120517: Status was locked; waiting
    20180601/120517: We didn't ask for this report
    20180601/120519: ex: MotionPlusInternal mp: None con: True at boot: False
    20180601/120519: pCombo: MotionPlus nCombo: MotionPlus
    20180601/120519: Extension mode: No change
    20180601/120519: Setting the report type after a status report
    Last edited by Madao; 01.06.2018 at 12:11.

  10. #200
    Super-Moderator epigramx's Avatar
    Join Date
    13.09.2017
    Posts
    385
    Quote Originally Posted by Madao View Post
    thank you for the update.

    If your still interest about log from "bluetooth dogle" + " newer genuine Remote Plus"
    Here is the log log:
    Yes, I'm still interested; thanks.

    That too seems to follow the same pattern observed so the last update should work correctly for that one too (regardless of DolphinBar or not which might conceal the true ID).
    Author of WiimoteHook; co-author of Static FPS mods, author of guides to game assembly patching , compiling mesa and high-res screenshots

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •