Don’t be too hard on them. Even if you have a very detailed picture of the problem, it can still be really hard to locate where it is.
2 Likes
Hahaha…
Got on the game this morning, running down noob river toward Skulkers End and fatal error occurs. Same Bounty Hunter Pot message. Are you ever going to fix this Funcom?
Has there been anything we’ve found in common with the people it’s happening to? At one point we were speculating that it was related to DLCs (not having one or more of them), but that doesn’t seem to be the case.
I think our strongest lead is someone caught that a spider or something was trying to spawn on top of the bounty hunter pot and caused some kind of collision error, which makes some sense given the nature of the error message. I don’t believe it has anything at all to do with owning DLCs.
Tried a few of the fixes suggested in this forum, none have worked.
Uninstalled and re-installed a couple of times with no success. Sometimes the game crashes before it even loads fully.
Wish Funcom would revert back to the game as it was before Age of Sorcery chapter 3.
I have 2000 hours up between main game and the Public Beta Client game.
Hello Funcom,
Are you there?
Are you dead?
If not, can you please fix this.
I don’t think they have to go that far. If it’s really just the bounty hunter pot causing problems, then the straightforward solution is to delete the pot. Of course, that means we can no longer turn in sorcerer skulls. But with the age of sorcery coming to an end, that might even be the plan they have in mind anyway.
I’m having this issue as well. Single/co-op, isle of siptah the beach. As soon as I start the game and run towards the forest, the game crashes every single time. My boyfriend is not having this issue, even though we’re playing in the same place. It’s the bounty hunter pot that crashes the game and now I can’t even start the save. Ir crashes right away.
Nope, its in the base game, not dlc
Well folks, this post is going nowhere… what do you all think? We all go to steam and flag the game/devs?
I mean if one of us does it, well yeah, but if we all complain to steam they will have to contact the devs.
Hey guys & gals, im as fed up as you all (to the point that ive abandoned a game i paid for…) and if you allnwant to get together and raise a case on steam, ill be in on that - but its not worth just me - either we all do it or forget about the game…
To flag a game:
https://www.hardreset.info/devices/apps/apps-steam/report-game/
It’s pretty clear their attention is elsewhere and not on a game they released 5 years ago. Unfortunate, but I really don’t see that landscape changing.
Their attention is on selling dlc after dlc, leaving the destruction in their wake…
If everyone was to get together and make a complaint on steam, they wouldn’t have to act…
Theres no point in just doing it myself, ill get nowhere. But if a heap of folks complain to steam, theres obviously an issue.
Or we cal all just forget the money we paid for the game and live with the fact its unplayable, whilst coming here to moan about it.
Question is, do you really want something done about it? and if so we have to agree to stand up for ourselves…
Huh, I triggered with this same error walking over the mesh of the Precise Firebowl cauldron. I wonder if there is a pathing bug when interacting with meshes?
Ive started playing another game since the devs haven’t fixed the bug or even let us know if they have plans to fix it.
Ill check back after the next content patch, or maybe not…
As i say, the only way we might see any interest with fc is if we all agreed to flag the game on steam…But its all or nothing a single voice is not enough, but many has volume and steam wound have to act.
I beginning to think sitting here moaning about something the devs have no interest in is a complete waste of our time…
I just bought the DLC today and can’t even walk away from the shipwreck area. I’ve gotten this same error four times. This is completely unplayable as is. I hope a fix is coming.
edit: This is the error.
Fatal error: [File:C:\B\tech_exiles\code\Engine\Source\Runtime\Engine\Private\AI\Navigation\NavCollision.cpp] [Line: 463]
Attempt to build nav collision data for /Game/Items/Placeables/Meshes/SM_bountyhunter_pot.SM_bountyhunter_pot:NavCollision_1 when we are unable to. This platform requires cooked packages.
!0x0000000000000000
1 Like
A foolish move, giving the devs yet more money…
They’ve not given any update at all and this post has been up for over 2 month’s. Their silence speaks volumes - they are not interested and there’ll be no fix.
Personally, I’ve found that when it starts happening consistently, like two or three times in the same spot, verifying my steam files somehow resets things and temporarily fixes it.
It doesn’t even have to find any corrupted files. Just going through the verification process seems to clear it for a while. I’m guessing there’s some cache file or something that gets cleaned out in the process, but that’s just speculation on my part. And like I said, it works until it breaks again, but it’s enough to get past those times where I can’t go anywhere.
I kept getting this error out of nowhere and the only thing that fixed it was changing the way my character looked via a mod that changes my character whenever I want ingame. Haven’t had any issues since! So possibly it could be a character issue? my character was originally maxed on every slider because I wanted to look stupid
It’s definitely random, but I don’t think your character settings would impact it. Probably just a coincidence, but the act of modding the game may have forced the files to sort of reset themselves enough to (at least temporarily) fix the issue.
My experience has been very inconsistent. I had this crash occur all the time at every camp back when Chapter 3 first came out. I had to develop routes specifically around avoiding certain areas because the crashing was so consistent, and Steam verification did nothing. Then it just went away one day (possible related to me installing some mods myself).
Fast forward to yesterday, and the crashing started again just as consistently as before. I came to this forum to theorize the how and why, but my most recent test just now had no issues or crashes. No hotfixes, updates, new mods, disabling old mods, etc. The first time I crashes, I verified the Steam files and it found 2 corrupted files to fix. Then I crashed again anyway. Load in one more time to prove consistency before posting here, and suddenly no issues again.
It’s utter madness through and through. I just hope that with Age of War coming out next month, they get rid of the sorcerer pot completely so this game breaking bug goes away for good.