Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
One more reason to spot animals before shooting. Because the spotted animal will show on your map and make it a lot easier to locate the where the shot landed.
Spotting an animal might reflect its aerial position directly below to the ground, which is of course better than nothing at all, but I think the bigger problem here is that the bird bodies are quite small, and they don't necessarily drop straight to the ground. So unless you manage to observe and calculate the direction of the drop, it's still a large area of potential to search.
Try to begin that search by placing yourself in the center of that purplish map hit spill, and figure out where you were when you fired, and the direction the bird was travelling.
Combine this with Squirrels spotting suggestion is really the only options.
Of course, always have the glowing corpse turned on when looking for hard to locate bodies.
I suppose it can get difficult if that happens to be over deep water. But if it is shallow water, the blood spots still drop and are visible under the water.
Goose blood trails may disappear when near the corpse.
So you were actually probably really close to it when and the tracks then vanished.
This is obviously somehow related to the AI tracking things involving height variables, positioned above the ground level. Which also could potentially correlate with other disappearing track glitches being reported where the tracks might be positioned on a part of the terrain that has some sort of collision issue involving height map connections, steep hillsides with lots of rocks, sudden precipices at edge of cliffs, etc.
This is where many track disappearances seem to occur, and I doubt that it's coincidental.
Having said that I have to be fair by also stating that I have only had a couple of instances like this and I'm sure many would agree that the majority of these reports are probably caused by personal system issues and/or inexperience with tracking.