Thread Rating:
  • 9 Vote(s) - 4.56 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DS4Windows - J2K
#31
Prolly cuz R2/L2 is mapped as an axis and not a "button" I think.
[Image: ov4]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 240GB SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply

Sponsored links

#32
1.4.0.71 works great. Thanks for the error fix! Laugh

I was wondering if anyone knew anything about an issue I'm having: If a physical mouse or mouse receiver isn't plugged into my Windows 8.1 machine, the cursor is invisible. I can still move it with the DualShock 4, but I can't see where it goes, just what it's hovering over at the time. I know this is probably a Windows thing, but does anyone know a registry hack to disable it or something? I like bringing my desktop to friends' houses with the DualShock 4, and I like to minimize what I bring, so being able to not have to worry about a physical mouse being plugged in would be great.
Reply
#33
I think I figured out what was causing the small window in the bottom left. If you want to try this code Jay. Formborderstyle.None should fix the problem on windows 7. Only problem now is if the "start minimized" button is checked it will still be in alt+tab menu until you maximize then re-minimize.

Quote: if (FormWindowState.Minimized == this.WindowState)
{
this.Hide();
this.ShowInTaskbar = false;
this.FormBorderStyle = FormBorderStyle.None;
}
Reply
#34
Is there a way to remap the L2/R2 triggers as buttons as opposed to axis? That is the only issue I am having now that Jays2Kings helped me resolve the other issues I was having.
Reply
#35
(10-14-2014, 10:27 AM)pedrovay2003 Wrote: I'm getting a Microsoft .NET Framework error every time I try to start the program in Windows 8.1 now. Here's a copy/paste:

Im getting the same since it auto updated yesterday.
Reply
#36
Haven't used my DS4 for a while but today i updated to 1.4.0.71 and I can no longer bind left and right touch to back and start, while at the same time share and options are also bound to back and start. When i do that only one of the buttons will work. For example right touch works as start but options doesn't or the other way around.
Reply
#37
(10-16-2014, 08:55 PM)marcoboyle Wrote: Im getting the same since it auto updated yesterday.

If the tool is on 1.4.0.7, just run the updater again, there is another update.
(10-16-2014, 09:02 PM)greenblood82 Wrote: Haven't used my DS4 for a while but today i updated to 1.4.0.71 and I can no longer bind left and right touch to back and start, while at the same time share and options are also bound to back and start. When i do that only one of the buttons will work. For example right touch works as start but options doesn't or the other way around.

I can't test what happened right now but I'll look into it later.

Also I'll try that code later youturnjason, thanks.
Reply
#38
Version 1.4.0.75
Reworked x360 mapping again, better support for mapping multiple buttons to the same thing + swapping buttons
Made the exclusive warning last message when connecting a controller that can't get exclusive control to make it more noticeable
Hovering over the log message at the bottom shows the full message
Default colors provided when a new profile is made for certain controls
Reply
#39
In the latest version, the analogue sticks refuse to work.
All other buttons work fine, just the analogue sticks.
If I install an older version of the tool, they work fine -- no issues on the hardware side, appears to be a major fault in this version.
Reply
#40
Same here. I can only move up and down on the left stick.
Model: Clevo P570WM Laptop
GPU: GeForce GTX 980M ~8GB GDDR5
CPU: Intel Core i7-4960X CPU +4.2GHz (12 CPUs)
Memory: 32GB Corsair Vengeance DDR3L 1600MHz, 4x8gb
OS: Microsoft Windows 7 Ultimate
Reply




Users browsing this thread: 2 Guest(s)