Real-time clock
RTC checks calendar fields, converts Windows FILETIME, and does checked arithmetic on ticks. The guest sees a coherent clock without the host's daylight-saving conversion.
Repository notes through October 10, 2026
What the calls do
Titles ask the firmware for the current time, for a conversion between tick counts and calendar fields, and for arithmetic that must not wrap into a nonsense date. PS5PCEM validates the calendar fields, converts to and from FILETIME, and checks the tick arithmetic so an overflow is an error instead of a truncated value.
UTC and local queries return coherent values from the host clock. The conversion that would apply the host's daylight-saving rules to a guest local time is not implemented. A title that only needs a monotonic or UTC stamp still gets a usable answer.
Why it is separate from audio time
Audio pacing uses the host audio device and its buffer clock. AvPlayer uses its own media clock. RTC is the wall clock the title reads for saves, timers and calendar UI. Mixing those clocks up is how a title appears to hang or to stamp a save with a zero time.
The October 9 report added the validation, the FILETIME conversion and the checked arithmetic together with the PNG encoder and three AMPR completion-size exports. Network time and a user-visible clock setting are not part of this surface.
What is implemented
- Calendar field validation and checked tick arithmetic.
- FILETIME conversion.
- Coherent UTC and local queries from the host clock.
What is still missing
- Host daylight-saving conversion of guest local time is absent.
- There is no emulated system settings UI for the clock.
- Network time synchronization is not performed.
Related mechanisms
What these pages are