Scenarios and automation

#What a scenario does

game.applyScenario(name) (from src/IslandGame.js):

1. pauses the clock and sets the time immediately ('sunset' means a sun elevation of 2.2° at azimuth 205°, over the sea);
2. re-seeds the birds and crabs, sets the sea life to a fixed time and moors the boat at the pier head;
3. switches mode instantly and places the camera: a walker position and view for walk and swim, a boat position, heading and camera view for boat, a camera position and view for drone;
4. fires a scenario event.

underwater is computed rather than stored: it finds the whale's position at a fixed time and puts you 21 m off its inshore flank, 7 m down, looking at it.

#The table

The definitions are in src/config/scenarios.js; add one there and it appears in the HUD, in window.__pro.presets and in the smoke test.

'pier-sunset': {
  label: 'Pier at sunset', mode: 'walk', time: 'sunset',
  at: [70.5, 236], ...look([70.5, 4, 236], [60, 4.2, 330]),
},
boat: {
  label: 'Boat · cockpit', mode: 'boat', view: 'cockpit', time: 12.2,
  boat: [170, 330, -2.35],
},

#The automation contract

demo/main.js exposes window.__pro, the same contract every NatureGL demo uses:

window.__pro = {
  ready: false,                          // true after the first frame rendered
  system: game,                          // the IslandGame
  presets: Object.keys(SCENARIOS),       // the eleven scenario names
  qualities: Object.keys(QUALITY_LEVELS),// ['low', 'medium', 'high', 'ultra']
  applyPreset: name => game.applyScenario(name),
  setQuality: level => game.setQuality(level),
  rain: on => game.rain.toggle(on),      // island extra
};

Open the page with ?smoke for automation: the start card is not shown and no scenario is applied at load.

Through __pro.system a script can reach everything else. The docs' videos, for example, hold keys by adding them to game.input.down, so the real controllers do the driving:

const g = window.__pro.system;
g.input.down.add('KeyW');     // walk, throttle up or fly forward, depending on the mode
// …
g.input.down.clear();

#The smoke test

npm test                                   # every scenario
node scripts/smoke.mjs --presets beach,boat --quality low --settle 1500 --headed

scripts/smoke.mjs starts a Vite dev server on a free port, opens demo/?smoke at 1280×720 in Chromium on the real GPU (--use-angle=metal), waits for __pro.ready, then for every scenario:

1. calls __pro.applyPreset(name);
2. waits for the settle time (2 s by default);
3. counts frames for 2 s to get the fps;
4. saves test-results/<name>.png.

It prints the renderer string, any warnings, and the min, median and max fps. It exits non-zero on any page error, console error or HTTP error (except a missing favicon).

#Other scripts