Reading through this and the other docs I couldn’t see how you can detect when a model purge occurs (so that you know to start a new download and session). Would all the API calls for an active session start to throw/reject if the underlying model was purged? Or is there an event to listen for?

There's two kinds of PKD books: A chilling vision of a future America ruled by hippies on speed
and
God is speaking to me from outer space and here are His coordinates

I also had it set to 'auto' which seems to default to dimming everything on startup & then slowly brightening up zones over time based on some brightness adaption heuristic. Turning it to off fixed the bug - so this time it was the hardware :) 5/5

Turns out I had 'local dimming' enabled. This setting on LED monitors tries to dim the backlight on sections of the screen with low light to try to enhance blacks, however my monitor obviously doesn't have enough dimming zones and... 4/N

I ran the graphics debugger & it showed that for a frame with the bug, the output colors were *identical* to a frame that looked correct. At this stage I was out of ideas & as a hail mary thought I'd look into my monitors settings to see if it was doing any postprocessing 3/N

I assumed it was the scene luminance calculation & adaption code as that does change exposure over time - however even with that disabled the bug occurred 2/N

Planning to add more of these over time at vibes.pixelheart.io