#DSX crash when disconnecting bluetooth controller
66 messages · Page 1 of 1 (latest)
well, i also have the same problem, dsx freezing/unresponsive after disconnecting controller on bluetooth when i stop ds4windows service
send logs plz
i think my problem is reproducible:
- run ds4windows with service started
- run dsx (show the app window)
- turn on ds4 until detected both by dsx and ds4windows
- stop ds4windows service
- dsx freeze
Well do i need to send event viewer logs and dsx logs again? All my messages in support were deleted
do you need the event viewer too?
does the crash still happen on demand? or random?
Im not able to reproduce it, it's so rare and random
you mean the dsx logs? the logs i sent had in them the .net runtime crash i think, but if i remember correctly when this weird "DSX window stuck" happens, if i close via task manager, there is just no exceptions, maybe only the controller disconnecting log.
Btw when this happens again i'll let you know, but it's so rare that it can take some time
The fact is that it happens when disconnecting the bluetooth controller but the (no longer available) screenshot i made shown that the dsx window was stuck on the moment before disconnecting, with the controller apparently still connected
again stuck like this after disconnecting the controller
logs while dsx is stuck/after terminating via task manager
And, idk if i can check in some ways the disconnection time of devices on windows, but when i killed dsx there was a sound of a device disconnected, so probably it didnt "disconnect" the emulated device
Just sending another file, happened again after a 2 hours game session
idk if this would be useful as an information, but i use a multi action button created on dsx (ps button + options) to disconnect my controller
I just noticed from the logs i have no Motion profile, even if i dont remember deleting it
I dont know if it is in some ways related, i created a new Motion profile and i'll check in the future if this bug happens again
this seems interesting
I think i have just resolved this. encountered it, and was able to make adjustments so that this doesn't happen again.
About to submit patch
i'll wait for the next update then to check if it still happens to me
It’s part of 3.0.2
Oh
Well you said this 1 hour after the 3.0.2 update, so I thought I had to wait
I pushed a silent patch
Ok, will update in case this still happens
@wintry garden
Mhh seems to work until now, but i noticed that when i disconnect the controller, dsx throws a bunch of exceptions in the logs
here
Yes that i know, me and Ram were able to make some adjustments that it no longer hangs for me
without the throwing of many exceptions
so maybe the next update can resolve this
Ok, thank you
oh and btw you should add a log message when using an action to turn controller off or when using the shut down button in dsx ui. Just for the logs, it can be useful sometimes i think
Right now logs just say that it's attempting or preparing to disconnect the controller, but what if it got disconnected by something else (like disabling bluetooth adapter)? you won't know i think
it says that because when attempting to read data from the device or writing data to the device when it has been disconnected gives exceptions and so we use that exception to remove the device from DSX
it handles all scenarios if a device turns off unexpectedly or is disconnected unexpectedly from wire
ok what the hell
dsx logs just go on a while(true) if i disconnect the device via usb
haha
from 111kb to 3mb
All has been improved in the update I will soon push out
They say you shouldn't push too hard and just let it come naturally 
ok, thank you, ill try later then
Very curious to know the results in v3.0.3
Do say if you have issues
yeah yeah, you know, for the crash of dsx itself it seems i had to game for some time at least, idk why
I'll let you know in about 8 hours if i had some problems while doing some game sessions
It has happened to me without any gaming
Just when disconnecting
well i dont really know the "code" reason, just 90% of times it happened after a game session
There was also disconnect logic being called multiple times from multiple places which may have created a bug that led it to freezing and ultimately requiring to end task it
just to know, is this exception normal? Like maybe you use it do disconnect the device itself?
Yes this is normal
This exception is raised when attempting to read data from the controller but the controller is disconnected so it fails thus leading to an exception being raised
I left it there to be displayed in case there’s other issues like processing the input data or output data which isn’t related to connection/disconnection
Ok, thank you, will let you know if something happens
I just had a 2 hours game session and no problem at all when disconnecting. I dont think i will test for the next 3-4 days because i probably won't have time to play