[Cosmetic BUG REPORT] MaxAim / MaxAim DI
2 posts
• Page 1 of 1
[Cosmetic BUG REPORT] MaxAim / MaxAim DI
MaxAim (v.3.2) | MaxAim DI (v.4.25)
numpad 5 button.setText ; incorrectly displays as numpad 6
numpad 6 button.setText ; incorrectly displays as numpad 7
This is purely cosmetic and it does not negatively impact functionality of either keys but it's still a mistake that should be addressed, in a future plugin update.
numpad 0 through 4 & numpad 7 through 9 are all properly labeled.
numpad 5 button.setText ; incorrectly displays as numpad 6
- numpad 5 command ; key-press command correctly mapped as numpad 5
numpad 6 button.setText ; incorrectly displays as numpad 7
- numpad 6 command ; key-press command correctly mapped as numpad 5
This is purely cosmetic and it does not negatively impact functionality of either keys but it's still a mistake that should be addressed, in a future plugin update.
numpad 0 through 4 & numpad 7 through 9 are all properly labeled.
Kolibri King | https://tinyurl.com/BF1KK
I take pride in the fact that I achieved this the honorable way. With an unmodded official XB1 controller.. Without the help of any other foreign device. Grind, well, spent.
I take pride in the fact that I achieved this the honorable way. With an unmodded official XB1 controller.. Without the help of any other foreign device. Grind, well, spent.
-
mjfame - Sergeant Major
- Posts: 99
- Joined: Sun Sep 27, 2015 3:44 am
- Location: USA
Re: [Cosmetic BUG REPORT] MaxAim / MaxAim DI
Thank you for reporting, issue added to GitHub and will be fixed for the next MaxAim DI release.
https://github.com/J2Kbr/GtunerPRO/issues/5
https://github.com/J2Kbr/GtunerPRO/issues/5
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
2 posts
• Page 1 of 1
Return to Gtuner Plugins Support
Who is online
Users browsing this forum: No registered users and 83 guests