starred/shadPS4
1
0
Fork 0
mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 08:15:59 +03:00
Code Issues 120 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1782] RTC functions in module libSceRtc are returning zero #615

New issue
Closed
opened 2026-02-27 21:07:14 +03:00 by kerem · 1 comment
kerem commented 2026-02-27 21:07:14 +03:00
Owner
Copy link

Originally created by @DISREL on GitHub (Dec 14, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1782

For some reason after a few patches, shadps4 on my Mac M4 Max started crashing frequently. Removing libSceRtc helps.

With the module:

[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetCurrentClockLocalTime (nid: ZPD1YOKI+Kw) called, returning zero to 0x9018c311c
[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetTick (nid: 8w-H19ip48I) called, returning zero to 0x9018c3140
[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcSetTick (nid: ueega6v3GUw) called, returning zero to 0x9020ea232
[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetCurrentClockLocalTime (nid: ZPD1YOKI+Kw) called, returning zero to 0x9015653f3
[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetTick (nid: 8w-H19ip48I) called, returning zero to 0x90156541b
[Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcSetTick (nid: ueega6v3GUw) called, returning zero to 0x9020ea232
[Debug] <Critical> vk_presenter.cpp:operator():768: Assertion Failed!
Device lost during waiting for a frame

Without the module:

[Kernel.Fs] <Info> file_system.cpp:sceKernelOpen:61: path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx flags = 0x0 mode = 365
[Kernel.Fs] <Info> file_system.cpp:sceKernelStat:469: (PARTIAL) path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx
[Kernel.Fs] <Info> file_system.cpp:sceKernelOpen:61: path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx flags = 0x0 mode = 365
[Kernel.Fs] <Info> file_system.cpp:sceKernelStat:469: (PARTIAL) path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx
[Kernel.Fs] <Info> file_system.cpp:sceKernelClose:188: Closing /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx
[Kernel.Fs] <Info> file_system.cpp:sceKernelClose:188: Closing /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx
[Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0xb2ace4c 
[Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0x201cb43d 
[Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0xd729c469 
[Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0x5f76eb3d 
[Debug] <Critical> vk_presenter.cpp:operator():768: Assertion Failed!
Device lost during waiting for a frame

This issue can be replicated on other platforms as well. Although I am not sure if other builds today had this issue, but it started after #1776 it seems.

Originally created by @DISREL on GitHub (Dec 14, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1782 For some reason after a few patches, shadps4 on my Mac M4 Max started crashing frequently. Removing libSceRtc helps. With the module: ``` [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetCurrentClockLocalTime (nid: ZPD1YOKI+Kw) called, returning zero to 0x9018c311c [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetTick (nid: 8w-H19ip48I) called, returning zero to 0x9018c3140 [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcSetTick (nid: ueega6v3GUw) called, returning zero to 0x9020ea232 [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetCurrentClockLocalTime (nid: ZPD1YOKI+Kw) called, returning zero to 0x9015653f3 [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcGetTick (nid: 8w-H19ip48I) called, returning zero to 0x90156541b [Core] <Error> stubs.cpp:CommonStub:42: Stub: sceRtcSetTick (nid: ueega6v3GUw) called, returning zero to 0x9020ea232 [Debug] <Critical> vk_presenter.cpp:operator():768: Assertion Failed! Device lost during waiting for a frame ``` Without the module: ``` [Kernel.Fs] <Info> file_system.cpp:sceKernelOpen:61: path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx flags = 0x0 mode = 365 [Kernel.Fs] <Info> file_system.cpp:sceKernelStat:469: (PARTIAL) path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx [Kernel.Fs] <Info> file_system.cpp:sceKernelOpen:61: path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx flags = 0x0 mode = 365 [Kernel.Fs] <Info> file_system.cpp:sceKernelStat:469: (PARTIAL) path = /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx [Kernel.Fs] <Info> file_system.cpp:sceKernelClose:188: Closing /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001206.flver.dcx [Kernel.Fs] <Info> file_system.cpp:sceKernelClose:188: Closing /app0/dvdroot_ps4/map/m21_00_00_00/m21_00_00_00_001137.flver.dcx [Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0xb2ace4c [Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0x201cb43d [Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0xd729c469 [Render.Vulkan] <Info> vk_pipeline_cache.cpp:CompileModule:490: Compiling fs shader 0x5f76eb3d [Debug] <Critical> vk_presenter.cpp:operator():768: Assertion Failed! Device lost during waiting for a frame ``` This issue can be replicated on other platforms as well. Although I am not sure if other builds today had this issue, but it started after #1776 it seems.
kerem closed this issue 2026-02-27 21:07:15 +03:00
kerem commented 2026-02-27 21:07:15 +03:00
Author
Owner
Copy link

@StevenMiller123 commented on GitHub (Dec 14, 2024):

The libSceRtc part of this issue implies that your dumped firmware libraries are encrypted or corrupt. This is a known issue where, if a dumped module fails to load, our reimplementation doesn't load either.

<!-- gh-comment-id:2543239493 --> @StevenMiller123 commented on GitHub (Dec 14, 2024): The libSceRtc part of this issue implies that your dumped firmware libraries are encrypted or corrupt. This is a known issue where, if a dumped module fails to load, our reimplementation doesn't load either.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
trophies_and_saves
user_and_settings
0.15.1branch_part6
Pre-release-shadPS4-2026-04-25-a762f70df3fc23185540f88724b261b065e5d979
v.0.15.0
Pre-release-shadPS4-2026-02-26-19d2027105679d751328357d7c85cd83a84c9758
v.0.14.0
v.0.13.0
v.0.12.5
v.0.12.0
v.0.11.0
v.0.10.0
v.0.9.0
v.0.8.0
v.0.7.0
v.0.6.0
v.0.5.0
v.0.4.0
v.0.3.0
v.0.2.0
0.1.0
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
Bloodborne

   
bug

   
contributor wanted

   
documentation

   
enhancement

   
frontend

   
good first issue

   
help wanted

   
linux

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
release

   
verification progress
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shadPS4#615
No description provided.