I can't disable the lightbar in this one either?
Seems DS3Tool is really the only option. Both this and the other DS4Windows keeps disconnecting constantly...can't keep a connection at all. DS3Tool works perfectly
(01-18-2015, 06:43 AM)Mkilbride Wrote: [ -> ]I can't disable the lightbar in this one either?
Seems DS3Tool is really the only option. Both this and the other DS4Windows keeps disconnecting constantly...can't keep a connection at all. DS3Tool works perfectly
You disable the lightbar by dragging the color bars to 0.
Would the battery reporting be off if you have replaced the original 1000mAh battery with a 2000mAh one? Did this a month or so ago and it seems to be accurate? Hard to test.
Though I'm no coder, I had a look at the source and couldn't see where there would be any problems from the DS4Windows side, so perhaps how accurate it is will depend on the Sony driver? Probably have no idea what I'm talking about, but I'm guessing the code block below is where you take the battery status from some Windows API and convert it to a usable integer? ("ofr" intentional?)
DS4Library\DS4Device (#414-425):
Code:
try
{
charging = (inputReport[30] & 0x10) != 0;
battery = (inputReport[30] & 0x0f) * 10;
cState.Battery = (byte)battery;
if (inputReport[30] != priorInputReport30)
{
priorInputReport30 = inputReport[30];
Console.WriteLine(MacAddress.ToString() + " " + System.DateTime.UtcNow.ToString("o") + "> power subsystem octet: 0x" + inputReport[30].ToString("x02"));
}
}
catch { currerror = "Index out ofr bounds: battery"; }
Also, is there a technical limitation that prevents displaying the battery status in increments of one or five instead of ten?
So sometimes DS4Windows works for me and sometimes it just doesn't.
Everything will run perfect for one day. Next day, random input lock/lag followed by, "Controller XX:XX:XX:XX:XX:XX was removed or lost connection." Then I turn the controller on/off, hit the start/stop on the DS4Windows GUI, maybe repeat this 2, 3, or more times until my game finally sees the "Xbox 360" controller and starts working again (for 10 minutes). Next day, could work fine, might work half the day then have this problem for 15 minutes, or it could be intermittent throughout the entire day. Frustrating...
The controller still stays connected to my PC via Bluetooth but disconnects from DS4Windows.
This seems to be completely random and it happens with both of the DS4Windows tools I have found. Looking for a resolution to this issue while using the other DS4Windows is what led me to find and try this version.
I would be grateful for any ideas on how I might resolve this problem. I love this tool but am not opposed to trying a different one, if it will work, if anyone has suggestions.
Using the built in Bluetooth 4.0 that comes with the Asus Maximus VII Formula motherboard. All drivers and bios are up to date.
http://www.asus.com/us/Motherboards/MAXI...I_FORMULA/
(01-17-2015, 09:59 PM)Jays2Kings Wrote: [ -> ]Version 1.4.222
Added Press/Toggle Key to Special Actions, you can hold a trigger to hold a key or toggle a key with one set of buttons, and untoggle it by pressing or releasing another set of buttons
Added Disconnect BT to Special Actions, PS+Options to d/c is now added to Special actions and can be enabled for each profile. You can now set Disconnect BT to any control(s) and how long you need to hold the control(s) to take affect
Added Partial German Translation (Thanks Michél)
Added 95% Finished Russian Translation (Thanks overclockers.ru members: KoNoRIMCI & Sr_psycho)
Added Partial Italian Translation (Thanks Giulio)
Updates to the translations sheets, they should now have every bit of text in DS4Windows, minus the controls of the controller
English Spelling fixes
Main/Starting tab only shows info for connected controllers, and context menu only shows options for connected controllers.
Mouse wheel scrolling with analog sticks/triggers/gyro, the mouse now scrolls smoothly
Slightly reworked analog mouse movement + mouse acceleration (not as janky anymore)
When starting DS4Windows, if no controllers are connected, DS4Windows defaults to the profile tab
Certain log warnings (Like unable to get controller exclusively) shows up in red
Easter egg: try pressing a few buttons in sequence while in the log tab
Fixed Start Profile with TP off being unchecked next time a profile is opened
Other minor Bug Fixes, such as clearing the log then moving to a new tab crashing DS4W
Also a little tidbit about the press/toggle keys. Someone asked me for an xpadder like function: to press L3 to toggle Left shift to keep sprinting in an FPS, and to untoggle it by letting go of the left stick, but by holding L3 down, you keep sprinting until you let go of L3. It wasn't something I could set up easily in the regular controls, but I was able to do it in special actions. You can do such a thing but assigning left shift to L3 and the unload trigger to left stick up, if something in the main controllers is assigned to the regular trigger in the main controllers, the toggle key automatically changes to a tap to activate action.
I know what you mean, and yeah the next version I can change that.
modifier keys behave weirdly depending on the game, try assigning left shift using the left ***** button in the select an action window then just pressing left shift in the window.
I'm not sure what the missing word is between "didn't" and "rumble" but if it's notice, that's because games don't have a way of accessing dinput rumble.
That's even weirder, I think you'll have to reinstall the driver.
I accidentally broke it in the last version, but it's fixed again
Special action still seem to work incorectly because setting 3 keys and action gets activated by only two of them.
Example:L1+R1+square to launch a game. pressing R1+square works too.
doesn't seem to take mandatory that all 3 keys are pressed.
On another matter can you make it possible that log catches controller response readings that are highter than 10ms (wich would be a problem) or even a sound alarm of some kind when this happens.
(01-19-2015, 03:08 AM)Hijinks686 Wrote: [ -> ]So sometimes DS4Windows works for me and sometimes it just doesn't.
Everything will run perfect for one day. Next day, random input lock/lag followed by, "Controller XX:XX:XX:XX:XX:XX was removed or lost connection." Then I turn the controller on/off, hit the start/stop on the DS4Windows GUI, maybe repeat this 2, 3, or more times until my game finally sees the "Xbox 360" controller and starts working again (for 10 minutes). Next day, could work fine, might work half the day then have this problem for 15 minutes, or it could be intermittent throughout the entire day. Frustrating...
The controller still stays connected to my PC via Bluetooth but disconnects from DS4Windows.
This seems to be completely random and it happens with both of the DS4Windows tools I have found. Looking for a resolution to this issue while using the other DS4Windows is what led me to find and try this version.
I would be grateful for any ideas on how I might resolve this problem. I love this tool but am not opposed to trying a different one, if it will work, if anyone has suggestions.
Using the built in Bluetooth 4.0 that comes with the Asus Maximus VII Formula motherboard. All drivers and bios are up to date.
http://www.asus.com/us/Motherboards/MAXI...I_FORMULA/
I have the exact same problem, though I'm using an Asus USB dongle, which hasn't given me trouble with any of my other hardware. I was initially using the original DS4 tool, and only experienced these issues after installing this, and the other forked versions. It was only after running a search and deleting every single file that referenced DS4 that I was able to connect my controller for longer than 10 seconds.
Although now when it does work, I get terrible lag that makes it not worth using my DS4 controller.
(01-18-2015, 12:24 AM)shinra358 Wrote: [ -> ]Yep yep, howdy doody good fellows 
1. Can we have a checkbox that brings back the slow pulsating low battery light indicator and when it is checked, the low battery blink is replaced with the low battery pulse? I know it was changed to have more battery conservation, but I kinda miss it. It just looks cooler 
2. On wired modes only (with full battery state only), can we have a checkbox that enables starting with the light off when first plugged in (or initiated) and the light will function as normal once a button is pressed? This will prevent the light coming on when the OS first starts or when you first connect the controller when you aren't intending to use it yet.
3. When going to Auto Profiles tab, always have the last program entry highlighted that you had highlighted before. If you hadnt highlighted an entry before, it defaults to the first entry. This prevents the confusion that happens when nothing is highlighted and you go to set a profile by the controller only to realize that you didn't have a program on the left highlighted.
1. was never a feature previously however it can be added
2. Already exist in a sense for coloring by battery mode, when it's charged it will slowly turn the light off. I can put this in full battery mode as well though
(01-18-2015, 06:43 AM)Mkilbride Wrote: [ -> ]I can't disable the lightbar in this one either?
Seems DS3Tool is really the only option. Both this and the other DS4Windows keeps disconnecting constantly...can't keep a connection at all. DS3Tool works perfectly
As stated above you can disable the light by setting the values to 0. As for the disconnecting, can you tell me what Bluetooth adapter you're using?
(01-18-2015, 10:01 AM)Aleksandr Wrote: [ -> ]Would the battery reporting be off if you have replaced the original 1000mAh battery with a 2000mAh one? Did this a month or so ago and it seems to be accurate? Hard to test.
Though I'm no coder, I had a look at the source and couldn't see where there would be any problems from the DS4Windows side, so perhaps how accurate it is will depend on the Sony driver? Probably have no idea what I'm talking about, but I'm guessing the code block below is where you take the battery status from some Windows API and convert it to a usable integer? ("ofr" intentional?)
DS4Library\DS4Device (#414-425):
Code:
try
{
charging = (inputReport[30] & 0x10) != 0;
battery = (inputReport[30] & 0x0f) * 10;
cState.Battery = (byte)battery;
if (inputReport[30] != priorInputReport30)
{
priorInputReport30 = inputReport[30];
Console.WriteLine(MacAddress.ToString() + " " + System.DateTime.UtcNow.ToString("o") + "> power subsystem octet: 0x" + inputReport[30].ToString("x02"));
}
}
catch { currerror = "Index out ofr bounds: battery"; }
Also, is there a technical limitation that prevents displaying the battery status in increments of one or five instead of ten?
You can try to display by ones and fives, but if you haven't seen, 10s isn't very accurate, as it's just a report of the voltage, there is no real way to see how much is left. There's a reason why the ps4 only shows the ds4's battery in 4 states.
(01-19-2015, 03:08 AM)Hijinks686 Wrote: [ -> ]So sometimes DS4Windows works for me and sometimes it just doesn't.
Everything will run perfect for one day. Next day, random input lock/lag followed by, "Controller XX:XX:XX:XX:XX:XX was removed or lost connection." Then I turn the controller on/off, hit the start/stop on the DS4Windows GUI, maybe repeat this 2, 3, or more times until my game finally sees the "Xbox 360" controller and starts working again (for 10 minutes). Next day, could work fine, might work half the day then have this problem for 15 minutes, or it could be intermittent throughout the entire day. Frustrating...
The controller still stays connected to my PC via Bluetooth but disconnects from DS4Windows.
This seems to be completely random and it happens with both of the DS4Windows tools I have found. Looking for a resolution to this issue while using the other DS4Windows is what led me to find and try this version.
I would be grateful for any ideas on how I might resolve this problem. I love this tool but am not opposed to trying a different one, if it will work, if anyone has suggestions.
Using the built in Bluetooth 4.0 that comes with the Asus Maximus VII Formula motherboard. All drivers and bios are up to date.
http://www.asus.com/us/Motherboards/MAXI...I_FORMULA/
(01-21-2015, 01:24 AM)jaybot31k Wrote: [ -> ]I have the exact same problem, though I'm using an Asus USB dongle, which hasn't given me trouble with any of my other hardware. I was initially using the original DS4 tool, and only experienced these issues after installing this, and the other forked versions. It was only after running a search and deleting every single file that referenced DS4 that I was able to connect my controller for longer than 10 seconds.
Although now when it does work, I get terrible lag that makes it not worth using my DS4 controller.
It could be the way Asus does Bluetooth, and not being a generic windows Bluetooth driver. See if you can go to device manager, and update the bluetooth to a generic mircosoft bluetooth protocol.
(01-19-2015, 09:39 AM)apoklyps3 Wrote: [ -> ]Special action still seem to work incorectly because setting 3 keys and action gets activated by only two of them.
Example:L1+R1+square to launch a game. pressing R1+square works too.
doesn't seem to take mandatory that all 3 keys are pressed.
On another matter can you make it possible that log catches controller response readings that are highter than 10ms (wich would be a problem) or even a sound alarm of some kind when this happens.
I'll see what's up with the actions, and I'll work on a way to show a high delay.
Also great news for Windows 10 testers: the newest build has fixed the issue causing hide ds4 not to work, rejoice.
Also I have noticed that x360 emulation doesn't start sometimes (DS4 windows set to autostart with windows) and when i connect my controller (BT) only Wireless Controller is shown in devices.
Restarting windows is the only solution to get it working again.
Everything so far is flawless except auto-updating isn't working for me.
I set exclusions in my antivirus and firewall (I even tried disabling it), but daily updates, manually running the updater, and selecting "check for updates now" doesnt seem to work. The .exe file version still shows as 1.4.212.0.
Not a big deal, but wanted to let you know.
Just a heads-up.
The latest Windows 10 Technical Preview seems to have added the service that was needed for exclusive mode back in, DS4 working perfectly on Win10 as of now.