v0.117.0-rc23 Whole Worlds

Everything in rc22, plus a refresh rate that follows the window, additive scenes that leave the running world alone, and new decals that wait for their ground.

Frame pacing

• app.refreshRate() reports the display the window is on, and follows it when the window moves to another one. Before the window is first shown it answers with the fastest display, so a frame cap set from it never holds a game below its display. Read it when you set the cap: app.setFrameCap(app.refreshRate()).
• When a compositor presents the window on another display's clock, the frame-time panel and the Console say so and name both displays.
• With Adaptive or Immediate presentation, the frame-time panel no longer reports dt snapping as a fault: nothing in those modes waits for the display, and the panel says how to hold frames to the refresh instead.
• A display path that cannot do the presentation a project asks for (such as Adaptive under XWayland on some drivers) falls back with a Console warning that says what it fell back to and what that means.

Scenes and decals

• scene.load(name, { additive = true }) starts only the new layer's sounds and effects. Before, it restarted every sound and effect already playing in the world. Its steps are named in perf.parts like a full scene change.
• A new decal waits for the ground under it to be ready before it is laid, instead of preparing that ground on the frame. A mark asked for just before a dig now lies on the dug ground.
• The terrain shadow's first volume after a world arrives is always made in the background, even when the GPU is short of memory, and the shadow work is named in parts.

Profiler

• perf.counts() reports the terrain's field chunks: fieldChunks at full detail, fieldEdited dug or built, and fieldStandIns put away.

Upgrading

Nothing to do. A game that relied on an additive load restarting the world's sounds or effects should start them itself.