Open Ipxildor opened 2 years ago
Upload the log file after the crash
where do i upload it?
in order to start a game I have to start it with the controller unplugged and once it is run, connect it. if I do it with the remote connected the emulator crashes
I don't see any crash in the log
I think I can hardly access the log because when you run the game with the controller connected the emulator crashes and I have to pull the task manager to close it and when I close the file that you say it disappears :(
I have the same problem, windows 11 with a ps4 nacon wired controller. Happens to a few games (I don't know which ones anymore) and sometimes also the Rufus partition tool. I just unplug it before launching bios or a game. Maybe some apps treat it like a faulty or portable storage device.
@thijsi123 thank you very much for writing in this post and I hope that your comment and mine serve to investigate the reason why this error is caused and it is solved. I do not know if the file that I have uploaded is the correct one so that they can know what is happening.
This may or may not be related to the same issue, but when my PS5 controller disconnects, the emulator crashes. RPCS3.log
Please test again
RPCS3.log RPCS3.log.gz TTY.log some log files IDK if these are any of help. I just recorded it too, the moment the controller disconnects the application will load the bios/games. This file size of the gif is a bit too big for GitHub so I'll just link the Imgur here: https://imgur.com/a/6JX6Yld This is all on the latest version as far as I know.
@LeronHinds your controller doesn't seem to report the expected data. This would suggest that it is not an original DualSense controller.
i'm getting the same issue as @LeronHinds too with a 100% OEM dualsense controller (bought new in box like 4 days ago). it seems to be directly correlated with the dualsense pad going into sleep mode and disconnecting, so i'm not sure it's actually in scope of this ticket as reported (i will open a new ticket if asked to do so).
log reports:
F {Pad Thread} SIG: Thread terminated due to fatal error: Segfault reading location 00000000000000e0 at 00007ff8157acb0b.
Emu Thread Name: 'Pad Thread'.
and it's reproducible, too:
i'll happily provide any further information upon request and a full log if someone could direct me to the log location on macOS (it's not in ~/.cache like on linux and i haven't been able to find any documentation about where it is on macOS).
system specs: macbook pro M1 Pro (10 core) 32 GB RAM macOS monterey 12.3.1 rpcs3 version 0.0.21-13446-21f744e2 (manually patched to use libmoltenVK.dylib v1.1.6 to fix a compatibility issue with kingdom hearts 1.5)
edit: found logs TTY.log RPCS3.log.gz
i'm getting the same issue as @LeronHinds too with a 100% OEM dualsense controller (bought new in box like 4 days ago). it seems to be directly correlated with the dualsense pad going into sleep mode and disconnecting, so i'm not sure it's actually in scope of this ticket as reported (i will open a new ticket if asked to do so).
log reports:
F {Pad Thread} SIG: Thread terminated due to fatal error: Segfault reading location 00000000000000e0 at 00007ff8157acb0b. Emu Thread Name: 'Pad Thread'.
and it's reproducible, too:
- boot game
- go into a pause menu or something
- wait for dualsense controller to fall asleep and disconnect
- segfault
i'll happily provide any further information upon request and a full log if someone could direct me to the log location on macOS (it's not in ~/.cache like on linux and i haven't been able to find any documentation about where it is on macOS).
system specs: macbook pro M1 Pro (10 core) 32 GB RAM macOS monterey 12.3.1 rpcs3 version 0.0.21-13446-21f744e2 (manually patched to use libmoltenVK.dylib v1.1.6 to fix a compatibility issue with kingdom hearts 1.5)
edit: found logs TTY.log RPCS3.log.gz
still reproduceable, on same metal mac on MacOS Ventura, with DualShock4 on rpcs3 0.0.25-14360
i guess it's a general error not realted to particular game, since we have a Segfault reading location
.
I was having this issue because of my dualsense. Not sure if its related but my games would crash every time i was using that controller. I switched to xinput and its stable. Anyone know why?
This is still a thing in November 2024. Can restart the PC and play one game okay, that'll boot, then anything after that will crash/lockup the emulator. Unplug the controller and it'll launch games again. Nacon ps4 controller. Bizarre that this is still a thing :( Absolutely zero problem with this controller on any other emulators, or games for that matter.
I also have a Hori pad, wireless, and RPCS3 launches stuff fine with that connected. Definitely an issue with Nacon stuff (and 8bit do and some others it seems?). Why would/could this be? Seems very odd. Nacon are a massive 3rd party pad company, too, and a lot of people have those pads. They're one of the best "low end" pads available. Would be great if this could get resolved.
Hello from a year ago to here the emulator crushes when launching any game. At first I thought it was a matter of emulator updates but I just realized that it is the command I use that causes this error. The remote I use is from the nacon company. url: https://www.mediamarkt.es/es/product/_mando-nacon-ps4-controller-con-cable-negro-1381980.html?utm_source=google&utm_medium=cpc&utm_campaign=MM_ES_SEARCH_GOOGLE_CATEGORIES_PLA_PEGOSIDE_CATEGORIES_PLAEGOJOROSIDE_SMEGORIES_PLA_PLA-SMIDE_SMITTAL_PLAEGOJORIES_CATEGORIES_Pla PH_TV_ALL_ALL & ds_rl = 1280902 & ds_rl = 1280902 & gclid = Cj0KCQiAoNWOBhCwARIsAAiHnEhhd4ddRmMKL7D9lle_JeOCRl8PeDw1c2hjqFIsaIHjDjMeIHAL_whjqFIsaIHjDjMEIHawtw5djMeIHawdwAdw5DjMeIHAL gwAdw5DjEIHawtwAdScBcAwAdScBc
I write here so that you know that this error exists and I hope you can solve it. All the best