ConsoleTuner

Code: Select all

* Multi Interface HID: Output resolution of sticks increased from 8-bit to 16-bit {GitHub#274}

The stick resolution for HID Output, are showing up as 11-bits for me.

-1025 to 1024.

These results are correct. The value range is now from -1024 to +1024 (which effectively allows the use of first decimal place in GPC scripts). However, to accommodate this new value range, the corresponding HID field size has been increased from 8-bit to 16-bit. The changelog was updated to avoid confusion.

There should be "GBC Bytecode".

Thank you Michael. However, "GPC Bytecode" is correct, means what is being published is the bytecode generated from the GPC script, hence GPC bytecode.

Thank you Michael. However, "GPC Bytecode" is correct, means what is being published is the bytecode generated from the GPC script, hence GPC bytecode.

I get it now. Please forgive my ignorance and thank you for your patience and time to explain this.

By the way, please drop the "Gtuner_cn_(Simplified Chinese)_v1.05.ts", because I changed the "GPC Bytecode" to "GBC Bytecode" in this one, and it's wrong.

Michael wrote:By the way, please drop the "Gtuner_cn_(Simplified Chinese)_v1.05.ts", because I changed the "GPC Bytecode" to "GBC Bytecode" in this one, and it's wrong.

I only just found out about the Virtual Controller feature, pleasantly surprised! Up to this point, to display controller input for consoles, I've been using KMG Capture to pass a PC-connected controller to console. This removes the need for this workaround.

As far as the Virtual Controller goes, is it possible to pass PS4 touchpad input through to PC as well?

Lollie wrote:I only just found out about the Virtual Controller feature, pleasantly surprised! Up to this point, to display controller input for consoles, I've been using KMG Capture to pass a PC-connected controller to console. This removes the need for this workaround.

Awesome!!

Lollie wrote:As far as the Virtual Controller goes, is it possible to pass PS4 touchpad input through to PC as well?

Yes, just select "Dualshock 4" on the Virtual controller drop-down box. Please note the software you are using for controller overlay needs to support the Ds4 touchpad inputs.

J2Kbr wrote:Yes, just select "Dualshock 4" on the Virtual controller drop-down box. Please note the software you are using for controller overlay needs to support the Ds4 touchpad inputs.

Weird, I guess I'll have to look further into this. I have a custom display built in Unity (via Rewired) that has no trouble showing touchpad inputs when the DS4 is connected directly to the PC, but they don't show up via Virtual Controller - though they're definitely being read by GTuner IV.



Fwiw, all other inputs display fine! I can live without this, I just figured it was worth mentioning in case something was up.

You are absolutely right, the official ViGEm drivers does not support the DS4 touchpad (I assumed it did, sorry for that):

https://www.reddit.com/r/gpdwin/comment ... ps_button/