Page 4 of 5

Re: Crash course on using the Input Translator

PostPosted: Fri Nov 15, 2019 6:29 pm
by Max10
J2Kbr wrote:While back I spent almost one week on Uncharted 4 mouse settings. Not really satisfied with the results (specially when not aiming), ended not publishing the Input Translator. The aiming mechanics on this game does not favor mouse input in anyway.

If you are interested, here is where I stopped:
Code: Select all
GIVMXYF:0705000168000017EB17EB009F000003EB07D70C8C10781463184F1B731F5E234A27352B232E453233361E3A0A3D2E4119443A48284C1405000135002B0F4A0E800037000015F51F5E25A32A592F0F32FA361E39403B9C3EBD4119437345CC482849B84C144DA35000519154B3

And what can be done with this code, it can be somehow changed, what can be changed in it, how can it be configured, what can be changed in it, maybe I will continue to adapt it to the yoke, tell me where to start, just many people play Uncharted 4 multiplayer on mouse and keyboard, through similar devices, type XIM apex. Is it possible to configure the Titan Two in the same way?

Re: Crash course on using the Input Translator

PostPosted: Fri Nov 15, 2019 6:42 pm
by J2Kbr
Sorry, I assumed you were familiar with the Input Translator sharing code.

First click on "Select All" and copy (Ctrl+C), open or create a Input Translator (GIT file) and, in the Mouse XY Converter section, click on the paste icon (the one with blue arrow point down). This will set all mouse parameters according the copied code.

Re: Crash course on using the Input Translator

PostPosted: Sat Nov 16, 2019 3:44 am
by Max10
J2Kbr wrote:Sorry, I assumed you were familiar with the Input Translator sharing code.

First click on "Select All" and copy (Ctrl+C), open or create a Input Translator (GIT file) and, in the Mouse XY Converter section, click on the paste icon (the one with blue arrow point down). This will set all mouse parameters according the copied code.

Thanks for the help and hint, I will do so. But I would like to try to change this code or edit and improve it, tell me how it can be changed and I will adjust or improve it myself

Re: Crash course on using the Input Translator

PostPosted: Sat Nov 16, 2019 2:02 pm
by J2Kbr
Hi Max, the changes are performed using the Input Translator editor.

For this specific settings (UC4), the deadzone should be good, for both looking and aiming. Note there are two separated settings you can select in the combo box located at the top-left corner: Default and Alternate. Alternate is activated when pressing L2.

I would focus any change on the the Sensitivity, Y/X Ratio and DD Factor parameters.

Re: Crash course on using the Input Translator

PostPosted: Sun Nov 17, 2019 6:48 pm
by Max10
J2Kbr wrote:Hi Max, the changes are performed using the Input Translator editor.

For this specific settings (UC4), the deadzone should be good, for both looking and aiming. Note there are two separated settings you can select in the combo box located at the top-left corner: Default and Alternate. Alternate is activated when pressing L2.

I would focus any change on the the Sensitivity, Y/X Ratio and DD Factor parameters.

Thanks for the hint of J2Kbr, a mouse with macro support will come in a week and I will try to configure it by loading macros into it and putting your values ​​through the Input Translator. If it’s not difficult for you, tell me again the link to the photo or the description of the exact connection TW + mouse + keyboard to which ports do you need to connect to work with MODz? (diagram)

Re: Crash course on using the Input Translator

PostPosted: Sun Nov 17, 2019 8:58 pm
by Mad
Max10 wrote:or the description of the exact connection TW + mouse + keyboard to which ports do you need to connect to work with MODz? (diagram)


Output to PS4
Mouse into Input A
DS4 into Input B
Keyboard into Prog via OTG adapter.

Or if you have a PC close by:

Output to PS4
Prog to PC
DS4 into Input B

Then run Gtuner>Tools>KMG Capture and make sure Keyboard & Mouse are selected and then enter capture mode.

Re: Crash course on using the Input Translator

PostPosted: Mon Dec 09, 2019 7:45 am
by Max10
sorry, I didn’t quite understand. The last point when connecting to a PC is where to connect the mouse and keyboard? Only 1 usb port left

Re: Crash course on using the Input Translator

PostPosted: Mon Dec 09, 2019 7:52 am
by Mad
Max10 wrote:sorry, I didn’t quite understand. The last point when connecting to a PC is where to connect the mouse and keyboard? Only 1 usb port left


For the first option you need an OTG adaptor.

If you're using the last option you leave the keyboad and mouse plugged into the PC and use KMG capture.

Re: Crash course on using the Input Translator

PostPosted: Mon Dec 09, 2019 11:21 am
by Max10
Mad wrote:
Max10 wrote:sorry, I didn’t quite understand. The last point when connecting to a PC is where to connect the mouse and keyboard? Only 1 usb port left


For the first option you need an OTG adaptor.

If you're using the last option you leave the keyboad and mouse plugged into the PC and use KMG capture.

OK Thank you

Re: Crash course on using the Input Translator

PostPosted: Thu Dec 26, 2019 5:00 am
by Max10
Good afternoon, tell me what I'm doing wrong, is there such an error when connecting a keyboard and mouse via a PC?