Introducing Low Frame Rendering

We are excited to introduce Low Frame Rendering, which allows the render to temporarily stop rendering for as long as it's needed, and will increase and expand to other system elements after we have ironed out everything. This feature can boost FPS by up to 66% (as of 1.1.1.7.4).

How does this feature work?

First off, we have added support for a module known as Render Self Awareness, which allows the render to know what it is doing and how the clones respond to the render. With this module and the ScriptOS Clone Manager, we can stop the render temporarily and increase the clone refresh time to still display an image, whilst not sending a render request.

The first problem arises.

Even though we have increased the render timeout, the clones will still delete at a rate of 1FPS (which means that for every 1 frame, the clone deletes itself). So, we made the clones dynamic, adapting to the refresh time of the render.

Things to expect.

Once we have made this feature reliable enough, we will expand this feature to the whole OS, dynamically changing the clone refresh rate to regulate performance and increase rendering efficiency.

Encountered Bugs.

First off, you might experience more UES screens since this feature is more experimental than ever, but in recent versions, has been extremely stable.

You may experience what is called "clone-on-clone interaction" which means that when a text element updates (like the time on the lock screen) and the previous text that was rendered before appears behind the text that is currently being rendered. This is especially noticeable when the frame rate is limited to 1 and the time updates.

There might also be strange rendering artifacts appearing. This also seems to sometimes occur when the Deep Sleep Mode is off.