Repository navigation
EVO Player (PPSA99039) #6338
Replies: 1 comment
|
Update with media playback, which the first report didn't exercise. Setup: Media: four 10 s clips I generated with ffmpeg (
Browse USB lists the four files with thumbnails decoded through Videodec2, and Back, the "Stop playback?" dialog and the subtitle panel respond to the scripted input. So the 10-bit HEVC output path that #6709 added decodes in a real title here. One note: after the switch to HDR10, Not tested: a real GPU, Windows, audio output ( |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Existing thread
Title
EVO Player (PPSA99039)
Content version tested
01.012.000
AnyPS5 commit
main a08de68, built from source. No pull requests merged on top. Follow-up runs below were
on main 03c4cb5.
System tested
Windows 11 Home Single Language build 26200, NVIDIA GeForce GTX 1660 Ti (driver 32.0.15.5597), MinGW-w64 GCC 15.2.0 (WinLibs x86_64-ucrt-posix-seh, 15.2.0posix-14.0.0-ucrt-r7), CMake 3.31.8, Ninja 1.13.2, Release.
Furthest point
Menus
What is shown
Reaches its own menu UI: the Welcome screen with BROWSE, RECENT, FAVORITES, PROVIDERS,
SETTINGS and SCREENSHOT, a clock, a highlighted entry and the Select/Back prompts, running
steadily at about 10 FPS at 1088x612 and still up after 4000 frames. Its boot log passes
"EVO boot: frame 4: present done".
Working: Vulkan device selection and swapchain creation, the shader disk cache (171 hits,
0 misses, 79.9 MiB read in 68 ms), the filesystem mounts, and font loading from app0/assets.
Not exercised: controller input was not sent, so the menu is reported as rendered rather than
confirmed responsive. Audio, media playback, the network and Stremio features were not tested.
Current blocker
An intermittent fault in the NVIDIA driver on a thread whose stack is in libSceAgcDriver,
tracked in #6335: 6 crashes in 15 runs on main 03c4cb5 on 15 October, every one at the same
faulting address (nvoglv64.dll+0xa13a46, 0xc0000005, read of 0x10). It follows the line
[gpu] storage image 0x213800000 destroyed with GPU results pending
although that line also appears on runs that do not crash.
Not currently reproducible: 0 faults in 35 runs on the same commit the next day, across plain
main, main with #6414 merged, and a wiped shader cache. Not reproduced on RTX 4060 or RTX 3070
by other reporters. No open pull requests or local changes are known to address it.
How it was run
Both eboot.bin and sce_module/libc.prx ship as SELF containers and need unwrapping first:
python tools/unwrap_self.py PPSA99039/eboot.bin src/eboot.elf
python tools/unwrap_self.py PPSA99039/sce_module/libc.prx src/sce_module/libc.prx
relinker --windows src/eboot.elf run/app.exe
The relink reports 342 external prx references and 1 converted module, exit 0.
Beyond the usage guide: the title needs its original eboot.bin in app0/. Without it, it falls back to /data/homebrew/<title id> and reopens /data in a loop.
No environment variables are required. ANYPS5_GPU="GTX 1660" was used for some runs; it does not change the outcome.
Release used: https://github.com/sainsaji/EVO-PLAYER-PS5/releases/tag/v0.12.0, EVOPlayer-v0.12.0-PPSA99039.zip, sha256 98788be10b3d2fe2909f6e353e2e09409ad29e46c2bc37112e2f35d9baa00d8a
All reactions