(03-22-2014, 09:16 AM)HecticSeptic Wrote: [ -> ]Exclusive access (hiding the DS4 DirectInput) can only be obtained if nothing else is using it. Forcing Steam to let go of it (off the top of my head, as far as I know) would entail dodgy unsafe manipulation of its memory space (I don't believe its allowed either). Unfortunately the only way we can get exclusive access is to do so before Steam takes hold of it, unless Steam is kind enough to implement an option not to open all (or any) game controller devices.
That's a shame, unfortunately Valve is entirely unwilling to make steam more user friendly when it comes to big picture and controller support so that's not an option sadly. The biggest problem is having to restart a game to do anything involving turning on/off the controller.
Quote:DS4 Tool doesn't install any devices, it only emulates the XInput of an X360 Controller through the ScpVBus. The driver installed - the ScpVBus - is what is used to achieve the XInput emulation.
Where would ScpVBus be categorized? What are these peripheral devices that keep trying to install themselves when I connect the controller?
Quote:Sony did not make the most user friendly (or perhaps even reliable) BT connectivity with the DS4 through pairing. What you are aiming for is a 'Wireless Controller' in devices which has an available service in properties which you should enable. I mentioned a youtube link ages ago in this thread which helped me to pair it, see if you can find it as I think it might help you as well.
I did exactly that yeah! It seems to have done the trick, although all the tutorials tell you about using a "pairing" option in windows that just doesn't exist for me. Had to figure it out of my own.
Quote:I have not personally seen any evidence of memory leaks, despite running the wrapper overnight myself. While .NET provides us with Garbage Collection, preventing traditional memory leaks, there is still a risk of inefficient memory management which if serious can result in an Out of Memory exception (but I'm guessing you mean memory leak in purely the 'keeping something you're not using' sense). Since we do have some unmanaged platform invoking that would be one area where a real memory leak could happen. We would have to actually use Scitech's MemProfiler or similar (which I personally don't own) to really see, but could you elaborate on what circumstances this occurs? How often does it happen, if not so often then there should be something specific that triggers it?
Well if nothing happens it will probably not trigger the "leak", sorry for potentially having misused it there. I have a memory dump of the program (270 mb) if that's any help (I'm not even sure if it would pose a risk for me to give that out, maybe you could clarify?). I can't establish what the cause is myself so far, as I'll try to keep task manager up and see when it starts happening. I've - Oh wait.
I tried toggling the hide DS4 controller option on/off repeatedly and it's now increasing by about 1.5 megabytes per second. I'm sure the size of the log is related to the size of the increase per second. It doesn't stop when I clear the log, it doesn't stop when I stop the service. Closing the program doesn't end the process immediately when this is happening (took 20 seconds). I hope this can help you finding the issue, I'll keep monitoring the thread.
Edit: Tried the same thing, toggling on/off, doesn't seem to trigger it per se but related. Went into options to adjust some LED options and it was leaking by the time I saved and exited that. Still no actual trigger found, might be after reaching x memory, might be something with the options window, might be something with the hide DS4 controller option.
Edit 2: Was messing in the options window - noticed the Sixaxis Gyro/Accel Data meters going haywire. Leaking started happening again shortly after. Still not sure what the direct cause was. See gif:
incredibly jittery and inaccurate, halfway through I twist and turn the controller and after that I start making circles with it.
Edit 3: Trigger seems to be... losing window focus? I can't make up any reason for this, but it started right at that point. The whole interface is lagging quite hard too and as seen in the image in my previous post, eats a whole CPU core. Unlike other programs DS4Tool.exe is steadily increasing memory over time, not like a tick per second.