Far Cry Primal

Far Cry Primal

View Stats:
Game is beautiful, but severely bugged.
In the first 2 hours of exploration play (starting after the "get green leaves for Sayla" mission, AKA the first chance you have to explore on your own):

#1 Campfire east of village about a mile, south of small round lake. Went to light the fire, and the entire campsite burst into flames. Not just the campfire. After the girl ran away, I needed to wait for the fire to all die out and the girl to come back so I can talk to her. But why did that much fire happen in the first place?

#2 Wenja Escort Mission at same campfire. Finally talked to the girl. When she was done talking I got no objective indicator at all. Got attacked by wolves and Udam right away though. But that was not the mission. The mission was to kill off a pack of Dholes living somewhere. But I never found out where. The attack by the Udam and wolves seemed to have glitched out the mission. The mission start icon was simply removed from the map.

#3 Wenja Hostage Rescue just north of that area. The Udam guards spotted some Wenja and they went to chase them quite a long ways away from the hostage. About 3 miles! By the time I finally got the message to go back and get the hostage. He was lying on the ground like he was dead. (Another glitch?) After looking at him for a few moments, his eyes were blinking and face twitching and then finally said something. It gave me the message to untie him. And when I did, it said mission complete, and um, then he died. Weird.

#4 Similar problem to one that existed in Far Cry 4. The "New Location Discovered" message popping up right in the middle of a mission or an attack and obscuring my aim point, for what seemed like forever, rendering me helpless until it goes away so I can see. There is no Interface Option to turn this off, so at the very least Ubisoft should have considered some options: message at top of screen, shorter display time, or my fav, put some code in there to surpress those popups when something is starting. Let's see, you already have music queue when danger is near, kind of a clue pointing to code that is already in the game.
Last edited by AlconburyBlues; Apr 6, 2020 @ 1:33am
< >
Showing 1-4 of 4 comments
Supermarine Apr 7, 2020 @ 12:09pm 
Interesting and weird. I have over 30 hours playing and never encountered a single bug.

Have you tried checking the integrity of game files?
AlconburyBlues Apr 8, 2020 @ 2:01am 
Yeah #4 is not so much a bug as an annoyance. In FC4 every time I would go to take an outpost the Location Discovered would pop up just as do a takedown, or defend myself, and I would die. So on the 2nd playthru, I started going to those areas first to get the area "discovered" then quick travel out of there, even on a mission if I could (if I didn't get close enough to trigger the you-are-leaving-the-mission-area "forcefield"), and go back. It seemed to be the only logical way to avoid it sometimes.

And yeah I don't think it's a game files problem because they are packed. When file integrity is the issue with packed files (or "packages" as they as called in the dev world), the game doesn't run because an entire package is corrupt.

Back in the day when they still made games with all the files unpacked/unencrypted and were not worried so much about people snagging copyrighted content, then individual file corruption with the game still able to run, might be a concern. (Been a developer and beta tester since the 80s.) But now most game developers use packed files, whether they have encryption or not, to ward off most people (with average knowledge) that would have an interest in doing so. [Note: That's why most modders these days have to use special tools to unpack/decrypt the files. And if you repackage them incorrectly, the game doesn't run.]

I'm just chalking it up to strange circumstances.
Last edited by AlconburyBlues; Apr 8, 2020 @ 2:19am
Guts Apr 10, 2020 @ 1:02am 
1.Fire is weird because they tried to make it a physical object. Sometimes it does weird things.

2.I also had the problem with the pack of Dholes mission.

3.That's a common farcry bug. I've had dead enemies do the talking thing. One time a heavy even got up and shot me in the face.

4.This should not be a problem in [current year]. Just lazy programming.

I'm more upset that primal doesn't really have a story to speak of and it seems to be made mostly from bits and pieces of other farcry games. It's almost an asset flip.
AlconburyBlues Apr 10, 2020 @ 2:37am 
@N473, your response to #3 had me rolling! LOL,

and for #4 I meant to say "...kind of a clue pointing to RELATED code that is already in the game." I mean you already have "danger detection" going on, so use that same code section to surpress messages that are not important at the moment. Right?
< >
Showing 1-4 of 4 comments
Per page: 1530 50

Date Posted: Apr 6, 2020 @ 1:00am
Posts: 4