[p]Hello, this is the HIGH-END Games /
PLATiNA :: LAB development team.[/p][p]Moving forward, we will use these periodic
Developer Notes to transparently share update details and future plans.[/p][p]This first article focuses on the
Performance Optimizations implemented through our recent updates. Additionally, we would like to share how we are reviewing and planning to incorporate the valuable feedback you have shared with us.[/p][p][/p][p][/p]
The Background for Considering “Performance Optimizations”
[p]The performance issues many of you have experienced stemmed from defects rooted in
technical debt accumulated since the early design stages. Our team identified that these underlying problems became more apparent over the extended period of operation following our Early Access launch.[/p][p][/p][p]
Key Background:[/p]
- [p]During the early phases, our focus was on rapid feature implementation, which led to a prolonged technical transition period. Consequently, core code remained in an inefficient structure without sufficient architectural refinement.[/p]
- [p]A significant amount of legacy code was not optimized for the \[Unity Engine] + \[Rhythm Game] environment.[/p]
[p][/p][p]Ultimately, we determined that a comprehensive rebuild of the existing client was essential for a fundamental solution. As a result, we have focused our efforts on a large-scale overhaul of in-game performance optimization.[/p][p][/p][p][/p]
What is “Performance Optimizations”?
[p]Our goal for “Performance Optimizations” involved a fundamental redesign and reimplementation of the rhythm game component of
PLATiNA :: LAB (hereafter referred to as the 'Core Logic').[/p][p]We focused on rebuilding the following areas from the ground up, including all closely integrated sub-elements. As a result, the vast majority of the source code for the rhythm game’s Core Logic has been rewritten:[/p]
- [p]Note Judgment (Hit Detection)[/p]
- [p]Note Rendering[/p]
- [p]BGM Playback[/p]
- [p]BGA (Background Animation) Playback[/p]
- [p]Visual Effects, including 'Key Beams' and other on-device animations[/p]
[p][/p][p][/p]
Key Points of “Performance Optimizations”
[h2]1) Input System Enhancements[/h2][p]In rhythm games, the most critical element is processing user inputs with
perfect timing. This requires the input detection process to run at an extremely high frequency without interruption.[/p][p]To achieve this, the Core Logic thread of
PLATiNA :: LAB is designed to operate at
1,000Hz, while the Input Polling thread runs at rates
between 1,000Hz and 8,000Hz.[/p][p]However, the default input system provided by the Unity engine has structural limitations when it comes to meeting the extreme precision required for high-end rhythm gaming.
To overcome these barriers, our team has gone through extensive trial and error to develop and implement our own proprietary input system specifically optimized for PLATiNA :: LAB.[/p][p][/p][h2]2) Refined Note Judgment System[/h2][p]While rhythm games can calculate judgments based on a note’s
visual position relative to the judgment line, we believe that
time-based calculations—processing the exact moment a note passes the line—are essential for consistent and precise judgment. (In fact,
PLATiNA :: LAB utilizes the latter.)[/p][p]However, our legacy core logic was performing redundant operations alongside these time-based calculations. This created an inefficient structure where the computational load increased proportionally to the number of notes in a pattern.[/p][p]
This inefficiency clashed particularly with the new input system mentioned earlier, causing severe performance spikes in certain patterns with high note counts.[/p][p]
By completely stripping away these unnecessary operations, we have addressed the root cause of the performance degradation. The core logic is now optimized to deliver stable, consistent performance regardless of the total note count.[/p][p][/p][h2]3) Mitigation of Frame Drops[/h2][p]The root cause of the frame drops many of you experienced lies in the inefficient way the game managed available memory. To explain this, we first need to look at a process called “Garbage Collection (GC).”[/p][p]During gameplay, the system performs Garbage Collection to clean up unnecessary memory. When this occurs, it can cause the game to momentarily stutter or freeze. To prevent this during active play, it is crucial to design code that minimizes unnecessary memory allocation.[/p][p]Unfortunately, our legacy structure suffered from excessive memory allocation. This inefficient management caused the “GC burden” to accumulate quickly. Furthermore, this was exacerbated by an issue where memory was being allocated thousands of times per second in proportion to the \[Polling Rate] setting.
This is why those using higher polling rates or playing for extended periods experienced more frequent frame drops.[/p][p]
We have now restructured the game to prevent these unnecessary allocations, significantly reducing both the frequency of Garbage Collection and its impact on performance. We are also continuously reviewing further optimizations to eliminate any remaining vulnerabilities that could cause frame drops in the long term.[/p][p][/p][p][/p]
Remaining Tasks
[p]Through the “Performance Optimizations” efforts carried out so far, we have successfully addressed the major root causes of heavy performance loads in a step-by-step manner.[/p][p]In particular, the overhaul of previously inefficient code into a more developer-friendly structure has laid a critical technical foundation. This ensures we can now swiftly identify and respond to any future issues.[/p][p]Despite these achievements, we recognize that several tasks still require further attention and action.[/p][p][/p][h2]1) Client Freezing on Exit[/h2][p]We are aware of the persistent issue where the game client stops responding or freezes upon exit.[/p][p]This phenomenon is closely tied to the process of releasing memory back to the system when a shutdown is triggered. Specifically, we have identified bottlenecks during the unloading of high-capacity sound assets as the most likely cause.[/p][p]We plan to resolve this by optimizing the unloading process for sound and various other game assets.[/p][p][/p][h2]2) Audio System Enhancements[/h2][p]The FMOD engine currently used in our game is originally optimized for spatial audio, common in genres like 3D FPS. Consequently, it contains several redundant features when applied to a rhythm game framework.[/p][p]Our immediate priority is to stabilize the current FMOD-based system. Looking ahead, however, we plan to conduct a multi-faceted review of alternative sound engines that are more natively optimized for the unique requirements of rhythm gaming.[/p][p][/p][h2]3) Special Key Compatibility[/h2][p]We are aware of the issues some of you faced when using non-QWERTY layouts or trying to assign special keys like
\[Caps Lock] in the settings.[/p][p]These bugs were unintended side effects of our ongoing work to improve global keyboard compatibility. While many of these problems were prioritized and fixed in the latest patch, we aren't stopping there.[/p][p]We are committed to upgrading our input systems to eliminate any conflicts with system-wide shortcuts and to ensure that the game flawlessly recognizes every single key press, exactly as you’ve mapped it.[/p][p][/p][p][/p]
Q&A
[h3]Q. It would be great if we could adjust the judgment timing.[/h3][p]In addition to the current \[Judgment Line Height] and \[Audio Delay] settings, many players have requested an option to
adjust the absolute timing of when notes appear.[/p][p]
This feature is currently in the final stages of development and will be available in an upcoming update. Furthermore, we recognize that optimizing judgment settings can be daunting for new players. To address this, we are exploring ideas such as a “Judgment Setup Assistant” that automatically finds the ideal settings for each user.[/p][p][/p][h3]Q. I hope the range of customization options for the play screen expands (e.g., adjusting the position or visibility of judgment text, combo counters, and FAST/SLOW indicators).[/h3][p]We are planning a much wider array of customization features for the play screen than what is currently available. These options will be rolled out sequentially as soon as their development is finalized.[/p][p][/p][h3]Q. I hope the pause penalty standards are relaxed. Are there plans to exempt pauses that occur in “safe zones,” such as the interval right after the game starts but before the first note appears?[/h3][p]We have been carefully listening to your feedback regarding the current pause penalty system being too strict.[/p][p]Originally, this system was introduced to ensure that players couldn't exploit the pause-and-resume mechanic to compromise the fairness of our ranking leaderboards. However, we deeply agree that this has resulted in overly restrictive constraints for a PC rhythm game environment that should encourage free play.[/p][p]Consequently, we will be updating the system so
that penalties are no longer applied to pauses made before the first note appears. Furthermore,
we plan to eventually phase out the current penalty system entirely and replace it with a new system better optimized for the gameplay rules of PLATiNA :: LAB.[/p][p][/p][h3]Q. What is the specific release schedule for the upcoming \[Multiplayer Mode] feature? Also, if it is released, will it support cross-play between the Steam and STOVE versions?[/h3][p]
We are designing our \[Multiplayer Mode] feature to support a unified environment where all players can meet and compete, regardless of whether they are on Steam or STOVE.[/p][p]However, building a robust multiplayer experience requires in-depth consideration—from server architecture and latency optimization to the establishment of dedicated gameplay rules. As such, we expect it will take some time to reach full completion.[/p][p]Because we know how much you are looking forward to this feature, we are committed to delivering a highly polished result. We will continue to share our progress through future
Developer Notes, so please stay tuned for further updates.[/p][p][/p][h3]Q. The lack of explanation for unique systems like \[P.A.T.C.H.] and \[Sections] makes the barrier to entry feel high for beginners. Are there plans to provide official help guides?[/h3][p]We believe the strongest motivation to keep playing a rhythm game is the sense of growth gained through “competing with oneself.” Systems like \[P.A.T.C.H.] and \[Sections] are the core engines of
PLATiNA :: LAB, designed specifically to support that experience. We plan to continue expanding these elements based on this core principle.[/p][p]For instance, we aim to present a “Roadmap for Growth” through self-challenge by introducing features such as
section-based performance analysis, goal-setting tools, and
personalized song recommendations based on your current performance to help you break your P.A.T.C.H. high scores.[/p][p]Most importantly, we are exploring various ways to offer support—such as integrated in-game guides—to make our existing systems more intuitive.
Additionally, we are preparing official documentation for our website and Discord server so that you can easily access detailed information on all major systems in the near future.[/p][p][/p][h3]Q. Since both Standard and Plus patterns are combined for P.A.T.C.H. point calculations, increasing the score feels quite difficult.[/h3][p]We understand that the experiences of playing \[Standard] and \[Plus] patterns should be treated as distinct categories.
Accordingly, we plan to update the P.A.T.C.H. scoring system so that scores for Standard and Plus patterns are calculated independently.[/p][p][/p][h3]Q. Although there is a function to adjust BGA brightness, it’s hard to find due to lack of guidance. Are there plans to improve visibility or provide better instructions?[/h3][p]This is already included in our future roadmap. Additionally, as an option for lower-spec environments, we plan to introduce a setting that allows users to use static images as backgrounds instead of video BGAs.[/p][p][/p][h3]Q. I’d like to see more diverse reactions from the
DBs.[/h3][p]The core appeal of
PLATiNA :: LAB is completed not just by rhythm gameplay, but through interactions with the
DBs. We are committed to actively introducing more content that allows you to engage and enjoy your time with the
DBs in even more diverse ways.[/p][p][/p][p][/p][p]We hope the information shared today helps clear up any questions you may have had and gives you plenty of exciting changes to look forward to. Moving forward, we will continue to release these
Developer Notes as a platform for close communication, allowing us to review and refine our development process alongside your valuable feedback.[/p][p]It's hard to believe 2026 is already moving so fast, with spring right around the corner. We ask for your continued support as
PLATiNA :: LAB continues to evolve and grow, much like the vibrant new life that arrives with the spring season.[/p][p]Sincerely,
PLATiNA :: LAB Development Team[/p]