Macros/Modifiers special code

Talk about anything concerning the source code.
User avatar
Zero
Posts: 68
Joined: Tue Aug 16, 2011 9:10 pm

Re: Macros/Modifiers special code

Post by Zero » Tue Jan 22, 2013 6:19 pm

I know that much, I've already done that (optimization set to zero but the debug param was already set), even tho it fails to hit a breakpoints (I think no symbols are loaded, even to the path is correct).
I'll try a few things out and try to figure it out if not I'll just write a logger to log the data and help me debug the app.

User avatar
Matlo
Posts: 5426
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Macros/Modifiers special code

Post by Matlo » Mon Feb 04, 2013 6:42 pm

I fixed issue 199. I removed the toggle event because people using the driving mode will have to tweak the mouse sensitivity and acceleration.

It would be nice if you could test it.
GIMX creator Donate Shop

User avatar
Zero
Posts: 68
Joined: Tue Aug 16, 2011 9:10 pm

Re: Macros/Modifiers special code

Post by Zero » Sun Feb 10, 2013 9:01 pm

Hello,

I've had some free time today and I've managed to get the most up to date code, hoping to test the 199.

However I've encountered an issue.
Whenever I move the mouse (bound to the rstick) all sort of input "gets transited" to the teensy.
My character in game starts to jump, crouch, shoot, aim, look around, its like the bytes are not mapped properly on the output structure.
This only happens when I move the mouse, when I move using keys (bound to the rstick) it work correctly.
I've looked at the output but found nothing funny there. According to the log the only thing that gets outputted (when I move the mouse) is the rstick x and y with correct value ranges.
I've used one of my configs that works on the stable 0.51

Edit:

Image

As suspected the bites are altered but the controller state is ok.
The top report is modified with a key press (rstick min value), the second report is using the mouse.
Besides rstick negative value the button bytes get written on the mouse report.
I will look further into it ... would love the possibility to attach a debugger and navigate the call stack. :roll:

User avatar
Matlo
Posts: 5426
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Macros/Modifiers special code

Post by Matlo » Mon Feb 11, 2013 6:55 am

What source code revision are you using?
GIMX creator Donate Shop

User avatar
Zero
Posts: 68
Joined: Tue Aug 16, 2011 9:10 pm

Re: Macros/Modifiers special code

Post by Zero » Mon Feb 11, 2013 7:54 pm

1381 on windows

User avatar
Matlo
Posts: 5426
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Macros/Modifiers special code

Post by Matlo » Tue Feb 12, 2013 9:23 am

I opened issue 209, and I fixed it.
GIMX creator Donate Shop

User avatar
Zero
Posts: 68
Joined: Tue Aug 16, 2011 9:10 pm

Re: Macros/Modifiers special code

Post by Zero » Tue Feb 12, 2013 8:03 pm

Cool, I'll test it and 199

User avatar
Zero
Posts: 68
Joined: Tue Aug 16, 2011 9:10 pm

Re: Macros/Modifiers special code

Post by Zero » Sun Feb 17, 2013 3:00 pm

209 seams to be fixed.
regarding 199, for some reason it won't switch to "driving mode" can you provide a example config for this?

User avatar
Matlo
Posts: 5426
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Macros/Modifiers special code

Post by Matlo » Sun Feb 17, 2013 8:48 pm

1. copy-paste profile 1 to profile 3
2. uncheck Advanced>Link controls
3. select profile 3
4. change the mode from aiming to driving
5. define a same trigger for profiles 1 & 3
6. calibrate the mouse parameters for profile 3
GIMX creator Donate Shop

User avatar
Matlo
Posts: 5426
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Macros/Modifiers special code

Post by Matlo » Tue Feb 19, 2013 8:59 am

Does it work?

I suggest you to start with dz=0, sens=1 and acc=1 as calibration parameters for the third profile.

Config example: link.
GIMX creator Donate Shop

Post Reply