premohq/PS5CEMU-HAR v4.0.1

PS5CEMU-HAR 4.0.1

on GitHub

Download

PS5CEMU-HAR-v4.0.1.zip (52.5 MB), attached below and on the releases branch.

SHA-256: 5d441d73957276e0d2f92bd2f56c70e33020a75483075aaf03cea9ae05028816

From 3.0.0 or later, the app offers this update itself as it starts (Settings > Online checks again). Otherwise extract the ZIP and copy the PPSA99360 folder to /data/homebrew/PPSA99360, replacing the old one. Your settings, saves and games in /data/ps5cemu stay as they are.

What's new

Fixes for 4.0.0.

Network shares

• SMB shares connect again (#46, #49). Connecting to one crashed the app: libsmb2's AES and Cemu's had the same name, and signing a session called Cemu's. libsmb2's ciphers now have names of their own.
• A share's tab opens in the folder chooser (#49), so a folder on a share can be picked as a games folder in the app.

Nintendo DS

• Sound at the right speed (#47). DS sound crackled and ran too fast because the app took the DS's frame rate as half what it is. The speed shown is now the DS's too (it read 200%).

Leaving a game

• Back to the library on more setups (#48). Leaving a game starts the app over, and some setups refused that restart, so the app closed instead. It now tries every place the app can start from, and says so if none of them works.
• A home screen tile's game says Quit to the home screen in its in-game menu, as it closes the app afterwards.

Artic Base and Artic Setup (#45)

• Artic Setup says which keys it needs before it starts. The app builds no keys in, so the setup needs otpKey and otpIV (under :AES) and rootPublicXY (under :ECC) in aes_keys.txt from your own console, in /data/ps5cemu/azahar/sysdata. Without them it copied everything and then failed with "Some console unique data is invalid".
• Artic Base connections time out instead of hanging, and a 3DS that closes the connection no longer ends the app.
• After a failed Artic load, the connection is closed and the app starts over cleanly, once any update check still on the network is done.
• Clearer errors: a 3DS that answered and then stopped is told apart from one that never answered, with Azahar's own message when it has one.
• Copy logs to USB includes Azahar's log of the session before (azahar_log.old.txt), which is where a 3DS game's failure ends up once the app has started over.

Notes

• Report problems with the logs from Settings > Diagnostics > Copy logs to USB. Known issues are in the guide.

Thanks

FenrisSkoll, CatchMeZZo and EverlongNZ (#46, #49), TimStoecker (#47), CorpseSlayer (#48) and Phononenom (#45) for the reports and the testing.