For over the hill wildlife photography, the reliable starting move is to centre the animal in the viewfinder until the recognition indicator turns green, then take the photo. If an animal is missing from your journal, check the compendium area first, because at least one June demo entry pointed at a region outside the demo's accessible area. The steps below mix an official feature preview with community demo instructions, so each part is labelled rather than blended.
The important mindset is that an animal entry, an exploration milestone and a saved photo file are three different things. Confusing them is the most common reason a player thinks a photo "did not count" or a completion run is stuck.
How to photograph an animal
The official feature exists: Funselektor's Animal Photo Journal preview, linked from an August development update, shows wildlife photography in a pre-release build. Watch that source for the interface rather than relying on a made-up shortcut, because it is a preview rather than a release tutorial.
The concrete procedure below comes from a June 14 illustrated community walkthrough, so it is a community demo observation, not an independently tested method.
- Find an animal and open the camera using your build's controls.
- Put the animal in the centre of the viewfinder.
- Wait for the recognition indicator to turn green, then take the photo.
- Inspect your journal afterward to confirm the intended entry was recorded before moving on.
Step four is the editorial addition, and it is the one that saves time. A landscape screenshot alone is not evidence that the animal was recognised, so confirming the journal entry costs a few seconds and prevents a long search for something you already captured.
Check the compendium area first
Before spending another hour on the same loop, select the missing animal and read any area information shown in your build's compendium. This is the fastest way to find out that you are searching in the wrong place.
The grizzly bear and mountain goat entries point to Gimli Ridge, outside the June Demo's accessible area. — community demo observation on compendium regions
That report comes from a missing-animals thread and is a useful check rather than an independently verified restriction for every build. The same thread contains conflicting assumptions about how many animals belong to the region, so treat the area text in your own compendium as the authority and the thread as a lead.
Do not use an exploration map's "100%" claim as proof that every wildlife photo is complete. In a separate demo-completion discussion, a player explicitly asks whether all wildlife has been photographed while describing animals as difficult to find. Check the actual animal entries rather than assuming a community map includes them all.
Community demo sighting leads
These reports come from June 13 to 14 in an animal compendium discussion. They are not guaranteed spawns, have not been reproduced here, and one player reported finding nothing at a suggested beaver spot.
| Animal and reporter | Location clue | Limit |
|---|---|---|
| Beaver — William | Near the second abandoned crate below Eagles Perch | A landmark to inspect, not a coordinate or a promise |
| Beaver — Chassegallerie | Where forest meets river | The reporter cannot identify which river |
| Wolf — Chassegallerie | The pass toward Boulder Crest lodge, near the East River trail | No exact position, time of day or repeatable spawn |
The original poster also reports finding other wildlife, including a black bear and an eagle, but that does not establish where you should go. Do not substitute the wolf or beaver landmarks for missing bear locations, because a sighting is not a map pin.
When a photo does not register
If the animal is visible but the photo does not count, the community walkthrough's advice is to try the centred-subject and green-indicator check again, then inspect the journal. That is not a verified fix for every registration problem, and the exact recognition distance, required zoom level and a universal fix all remain unverified.
| What you see | Useful next action | What it does not prove |
|---|---|---|
| Missing entry names another area | Compare that area with the locations accessible in your build | That the entry is bugged or a hidden path must exist |
| A sighting spot is empty | Treat that report as exhausted for this visit and explore elsewhere | A fixed respawn timer or a set time-of-day requirement |
| Animal visible but the photo does not register | Retry the centred-subject and green-indicator check, then inspect the journal | That repeated scenery screenshots will unlock the entry |
| Wildlife remains unusually scarce | Record your build and region if you report the issue | That reinstalling or deleting a save will fix it |
The pattern in the third column is deliberate. Each action is a check you can perform, and each failed check is evidence about your situation rather than proof that the game is broken.
Journal entries versus saved photo files
An animal entry, an exploration milestone and a photo file are three separate things, and knowing which one you are looking at changes the answer. If your question is where the image went on your PC, that is a save-and-screenshot-location question rather than a wildlife question.
This page covers finding and photographing the subject, not locating the resulting file. The same distinction applies to completion claims: a journal entry can be filled while the file lives somewhere else, and a file can exist without an entry if the recognition step was missed. Check both, and do not assume one implies the other.
The comparison also protects you from a wasted night. "The animal is there but did not register" and "the animal was never there" look similar in a screenshot but call for opposite next steps.
What missing animals actually tell you
Sparse encounters are the demo's normal state, not a strong signal. The June reports describe wildlife as hard to find, but they do not measure spawn probability, so this page cannot tell you to wait a specific number of minutes or to sleep until a particular hour.
What you can do is keep a short list of missing entries and already-checked leads, so an unsuccessful trip does not become an endless repeated circuit. When a sighting spot comes up empty, mark that lead as exhausted for the visit and move on rather than re-running the same loop on the assumption that a timer is about to fire.
Do not treat bait, a respawn rule or a fixed spawn point as a proven method. None of those appears in the checked evidence, and inventing one would turn a search into a guess.
What remains unknown before release
The open items are substantial and worth listing rather than glossing over. The final animal roster, fixed coordinates, spawn timers, per-animal rewards, repeat-photo rewards and whether one co-op player's photo updates anyone else's journal are all 待确认.
For regional context rather than sightings, the map overview is the relevant reference, and for access rather than mechanics, treat any historical demo instruction as past rather than a current offer. Until the release build states the roster and the spawn rules, the honest plan is location-first: check the compendium area, centre the subject, confirm the journal, and refuse to fill the gaps with numbers nobody has published.