So what you are saying is that you want a profile option that allows the controller to show that it is still there even though it's not on or plugged in (like a place holder) so that games will be tricked into thinking that it is always there when it is not so that full hotplugging will always work regardless?
Hey guys, coming from DS4 Tool, amd I cant seem to get my bluetooth dongle to discover my DS4 controller. Everything works flawlessly when I hardwire the controller, but with the DS4 searching and the Bluetooth on my PC looking I cant seem to find anything.
it worked fine when I had DS4 Tool.
My steps:
uninstalled DS4Tool.
installed DS4 Windows
reinstalled the virtual bus driver
already have the 360 controller driver installed
reinatalled my bluetooth dongle driver
search for device, put DS4 in discover mode (PS and share for 3 seconds)
long story short, i get nothing.
anyone have something I missed?
EDIT: On windows 7 x64
(06-28-2014, 09:17 PM)shinra358 Wrote: [ -> ]So what you are saying is that you want a profile option that allows the controller to show that it is still there even though it's not on or plugged in (like a place holder) so that games will be tricked into thinking that it is always there when it is not so that full hotplugging will always work regardless?
umm, well yeah. i can't think of why that would be a problem in any standard single controller scenario, sure i am not considering the scenario where someone uses several controllers and might need to swap controller 2 to be controller 1, for the purpose of a multiplayer game like maybe audiosurf or portal2. in theory, there should not be a problem with any scenario where all controllers are ps4 controllers, or where limits were used to cap the number of reserved controllers. the thing is, i am asking about an option, *could* it be an option, not asking to have it forced.
(06-28-2014, 09:49 PM)PoWn3d_0704 Wrote: [ -> ]Hey guys, coming from DS4 Tool, amd I cant seem to get my bluetooth dongle to discover my DS4 controller. Everything works flawlessly when I hardwire the controller, but with the DS4 searching and the Bluetooth on my PC looking I cant seem to find anything.
it worked fine when I had DS4 Tool.
My steps:
uninstalled DS4Tool.
installed DS4 Windows
reinstalled the virtual bus driver
already have the 360 controller driver installed
reinatalled my bluetooth dongle driver
search for device, put DS4 in discover mode (PS and share for 3 seconds)
long story short, i get nothing.
anyone have something I missed?
EDIT: On windows 7 x64
i assume other bluetooth devices work? when you right click on the bluetooth icon in your statusbar and ask it to search for other devices it finds other devices like a headset, your cell phone, the roku attached to your tv, whatever? the cell phone is a good device to test with as just about everyone has one that uses bluetooth, does your cell phone see the ps4 controller? if your computer can see the cell phone, and the cell phone can see the ps4 controller then you can narrow the problem down to the bluetooth in your computer not being compatible with the controller. if you cant see the cell phone from the computer then the problem goes back to checking computer settings.
Yeah, my phone sees the controller. It also sees my Steambox. My computer sees neither my phone nor the controller.
I know it is something to do with my PC, I just can't figure out what.
(06-28-2014, 05:11 PM)Captain Cheescake Wrote: [ -> ]yes
yes it is orange
yes
yes
yes
okay im not sure why you bothered to respond with a list of yeses without any more information. from what you just indicated everything is working perfectly. you claimed you installed the driver, and by the "yes" under checking the log i take it to mean "yes the log showed the controller detected and working properly". at this point all you need to do is play a game that supports XInput, maybe select the xbox controller from the options page.
now if by "yes" you meant "NO, no it doesn't list my controller" then you need to go back to the drivers and click the checkmark for forced install.
(06-28-2014, 10:19 PM)PoWn3d_0704 Wrote: [ -> ]Yeah, my phone sees the controller. It also sees my Steambox. My computer sees neither my phone nor the controller.
I know it is something to do with my PC, I just can't figure out what.
yes that is a difficult one. sadly i doubt we can help here. try
http://answers.microsoft.com/en-us/windo...87713f22f1
(06-28-2014, 10:19 PM)PoWn3d_0704 Wrote: [ -> ]Yeah, my phone sees the controller. It also sees my Steambox. My computer sees neither my phone nor the controller.
I know it is something to do with my PC, I just can't figure out what.
Is the dongle minimum 2.1 with EDR and does it have the Windows/broadcom stack? Also, I am assuming you are using the right button combo to pair (PS + Share).
(06-28-2014, 09:49 PM)PoWn3d_0704 Wrote: [ -> ]Hey guys, coming from DS4 Tool, amd I cant seem to get my bluetooth dongle to discover my DS4 controller. Everything works flawlessly when I hardwire the controller, but with the DS4 searching and the Bluetooth on my PC looking I cant seem to find anything.
it worked fine when I had DS4 Tool.
My steps:
uninstalled DS4Tool.
installed DS4 Windows
reinstalled the virtual bus driver
already have the 360 controller driver installed
reinatalled my bluetooth dongle driver
search for device, put DS4 in discover mode (PS and share for 3 seconds)
long story short, i get nothing.
anyone have something I missed?
EDIT: On windows 7 x64
Could you link me to the dongle you have?
Also Version 10.651 is live:
Fix for loading older profiles before 10.65
DS4Updater: update.zip remains if couldn't unzip the files for whatever reason
Hey Jays, had a wee prob this morning - when i turned on my computer it offered an update, which i ran, but then it said (as it usually does for me) that the updater has stopped working and needs to close. But for some reason this time it has deleted the .exe for the DS4 tool. and i cant run it anymore. I had to manually extract from the zip again. Just thought i should make you aware of that.
Also i actually like Drossiuss suggestion of a permanent placeholder type thing for if the controller is turned off. I have a bad time with the tool not detecting, freezing, crashing etc, when the idle time out happens (and while running as well). The only fix is to turn my machine off and back on again.
I had mentioned before its like when i turn the controller back on again from an idle time out, steam (or something else) grabs the controller as a DS4 first, and then the tool never reconnects. I think you said before that that shouldn't happen though so it might be something on my end - have you got an suggestions as to what i could do?
Incidentally, I regularly have the tool crash on me in the last while as well while running, like every couple of hours probably. I havent mentioned it though because, well its still in development, with regular updates and bug fixes so its to be expected to some extent, and also it just shuts without me being able to see a crash log or anything so i dont know if there any info I can provide to assist you in making a fix.
So as it crashed again, I managed to catch this error log in the temp files as it wanted to send a report to microsoft - can anyone tell me is this anything to do with the tool or is it my machine maybe?
Im hoping someone can use their Neo skillz to read the code and make sense of it....
The error report said:
Files that help describe the problem:
C:\Users\marc\AppData\Local\Temp\WER94D3.tmp.WERInternalMetadata.xml
C:\Users\marc\AppData\Local\Temp\WERAFA4.tmp.appcompat.txt
C:\Users\marc\AppData\Local\Temp\WERAFC4.tmp.mdmp
So the info on the text file says :
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="DS4Windows.exe" FILTER="CMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="DS4Updater NEW.exe" SIZE="560128" CHECKSUM="0x680ED890" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="Updater2" PRODUCT_NAME="Updater2" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="DS4Updater.exe" INTERNAL_NAME="DS4Updater.exe" LEGAL_COPYRIGHT="Copyright © 2014" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="06/15/2014 06:38:29" UPTO_LINK_DATE="06/15/2014 06:38:29" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" FILE_ID="00001600b0709930729b26a0e18aad516cadc177316f" PROGRAM_ID="00038434028d7cc3ea48a055cbe603f556f300000000" />
<MATCHING_FILE NAME="DS4Updater.exe" SIZE="560128" CHECKSUM="0x61773EB2" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="Updater2" PRODUCT_NAME="Updater2" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="DS4Updater.exe" INTERNAL_NAME="DS4Updater.exe" LEGAL_COPYRIGHT="Copyright © 2014" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="06/13/2014 21:39:56" UPTO_LINK_DATE="06/13/2014 21:39:56" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" />
<MATCHING_FILE NAME="DS4Windows.exe" SIZE="2134016" CHECKSUM="0x3D7FADDB" BIN_FILE_VERSION="1.3.0.0" BIN_PRODUCT_VERSION="1.3.0.0" PRODUCT_VERSION="1.3" FILE_DESCRIPTION="DS4 Tool" PRODUCT_NAME="DS4 Tool" FILE_VERSION="1.3" ORIGINAL_FILENAME="DS4Windows.exe" INTERNAL_NAME="DS4Windows.exe" LEGAL_COPYRIGHT="Copyright © Scarlet.Crush Productions 2012, 2013; Copyright © InhexSTER, HecticSeptic, electrobrains 2013, 2014" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.3.0.0" UPTO_BIN_PRODUCT_VERSION="1.3.0.0" LINK_DATE="06/13/2014 21:46:35" UPTO_LINK_DATE="06/13/2014 21:46:35" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="KERNELBASE.dll" FILTER="CMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="KernelBase.dll" SIZE="424960" CHECKSUM="0x10125A28" BIN_FILE_VERSION="6.1.7601.18409" BIN_PRODUCT_VERSION="6.1.7601.18409" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="Kernelbase" INTERNAL_NAME="Kernelbase" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6D430" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18409" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18409" LINK_DATE="03/04/2014 09:43:54" UPTO_LINK_DATE="03/04/2014 09:43:54" EXPORT_NAME="KERNELBASE.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" FILE_ID="00008d6b3cb998b50f6e63911e41d15340ece331d10b" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="1163264" CHECKSUM="0x86B04804" BIN_FILE_VERSION="6.1.7601.18409" BIN_PRODUCT_VERSION="6.1.7601.18409" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1207C4" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18409" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18409" LINK_DATE="03/04/2014 09:43:53" UPTO_LINK_DATE="03/04/2014 09:43:53" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" FILE_ID="00000a9e4db67a30c505bba883ceaffe964e50131a5f" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
</EXE>
</DATABASE>
@J2K
is there a way to customise where the installer installs the Virtual Bus Driver to?
I would like to keep everything to Program Files rather than that being at the root