A flickering light is explicitly named in the official Anomaly Detected description. Luz changes can affect an entire frame, which makes them noticeable, but also makes them easy to confuse with camera noise, display brightness, compression, normal animation, or a shadow crossing the scene. Confirm both the source and its effect before reporting.
Build a lighting baseline
For each feed, identify the main light source, one secondary glow if present, and a surface that clearly shows the normal illumination. A lamp can be the source; the nearby wall or floor can be the result. Remembering both helps when the fixture is small but its effect is broad.
Use plain states: steady, dark, bright, warm-looking, cool-looking, or periodically changing. Color words can vary with device settings, so position and behavior are often stronger anchors. If the room normally contains a moving or cycling light, observe enough of that cycle to avoid treating the normal rhythm as an anomaly.
Keep the display consistent during a contract. Automatic brightness, night filters, reflections, or changing room light around your device can alter the entire image. A true in-game light anomaly should remain tied to a feed, fixture, or illuminated area rather than following every screen.
Confirm flicker over time
Do not decide from one frame. Hold the wide view long enough to see whether brightness changes again. If the behavior repeats at the same fixture or in the same local area, zoom to confirm the source. Use Shift, L2, or double tap according to the creator’s published device bindings.
Compare three layers:
- Fixture: does the lamp, bulb, sign, window, or other source visibly change?
- Illuminated surface: does a nearby wall, floor, object, or shadow respond at the same moment?
- Whole feed: is the effect local, or does the entire camera image pulse together?
A local source-and-surface pattern is stronger than a single full-frame flash. The exact report category still comes from the live interface; the public description gives the example but not every menu label.
Separate light from object and shadow changes
An object can look missing when a corner becomes dark. Check its silhouette or position under the changed light before reporting it as an object anomaly. A shadow can appear to move because a light source flickers; watch whether the boundary moves independently or simply brightens and darkens.
Use Anomalias de objetos and Anomalias de sombra when the comparison points away from the fixture.
Use device settings carefully
Increase readability before the run rather than changing brightness during a suspicious moment. A mid-contract display adjustment breaks the visual baseline. Keep contrast comfortable and avoid filters that crush dark detail or exaggerate flicker.
Mobile screens can dim automatically when warm or under power-saving settings. Controller players may be watching from farther away, making small fixture changes difficult to resolve. Keyboard players can use Shift to inspect, but should return wide before judging whether the whole room changed.
If flicker causes discomfort, stop watching the effect. Do not force repeated exposure for a report or Journal entry. Lower-risk play and personal comfort take priority.
Report and resume
Describe the chapter, feed, source, normal state, and current behavior: “right wall light was steady and now repeatedly flickers.” Use the room and category labels presented by the current game. After a successful report, resume at the next feed in your loop.
If the report fails, test whether the effect followed the entire screen, belonged to normal animation, or came from a shadow or object. Avoid cycling through categories rapidly. One controlled reassessment teaches more than several guesses.
In co-op, the watcher should call the fixture and surface. A confirmer can compare another feed or check whether the effect is device-wide. This makes lighting claims easier to separate from one player’s display.
Track Journal entries
Official badges confirm a 100% Journal goal for each named chapter, but they do not publish the individual light entries. When the live Journal reveals one, record the exact name, chapter, feed, source, effect, report response, and date.
Do not assume a visually similar flicker is the same entry across chapters. Future anomalies are officially described as in development, so a dated record should be rechecked after content changes.
Common light mistakes
- Reporting after a single bright or dark frame.
- Looking only at the fixture and ignoring its illuminated surface.
- Changing device brightness during the comparison.
- Calling a darkened object missing before checking its silhouette.
- Treating every moving shadow as a lighting event.
- Copying an exact chapter list without current Journal confirmation.
Frequently asked questions
Are flickering lights official anomalies?
Yes. A flickering light is one of the examples in the official Experience description.
How long should I watch?
Long enough to see whether the behavior repeats and affects a local source and surface. No universal timing is published.
Should I use zoom?
Use it to inspect a chosen fixture or edge, then return wide to compare the whole room.