so it isn’t just crossplay it would seem I turned it off and still havent registered with epic and went ahead and made a bunch of custom classes and named them played a match to the end upon return crash, reloaded previous save with only unnamed custom Predator classes have played 5 matches as 3 different predators and 2 with default stock FT no crashing. So it has to be the custom names mixed with the amount of custom FTM(as I just fully customized one FTM and equipped the new rifle and anti cloak grenade and it still hasn’t crashed after 3 matches beyond the 5 stated above) and some combo of the new gear items it would seem, will be back again after a few more experiments.
ERROR CE-34878-0 PS4
I literally crash Everytime now
6 times in a row so far
What have you tried? What are you using? Any info or examples are helpful
I tried closing the app and not opening it again.
It seems to have worked. I am no longer frustrated.
3 Likes
Fair Enough
1 Like
@IllFonic it seems the issue stems from Private Matches: I deleted my Original Save (cautiously, mind you LOL) and the Crash went away. I wrapped a single Private Match and when I went to go to Customization, as in rolling over the Main Menu Prompt, it did the same thing again.
Second Save File has been fine so far (three Hours and counting). While I know these things can be complicated Coding wise, it’s a pain in the ass to have to remember particular settings. I actually wrote them down since I customized a lot of Controller Options.
Deleting the save file and not renaming my classes seems to work.
I haven’t had any issues other than poor performance @OldKingHamlet
1 Like
Deleting the save data is a temporary fix and absolutely unacceptable - this isn’t a measure we should have to take to play a game we paid for.
I have loved playing this game despite bugs and balance issues, cause it’s good fun mostly. But this now is ridiculous. Suggesting WE have to constantly take a measure to fix an issue is not good enough. They need it sorted ASAP or they’ll be shelling out refunds
3 Likes
This crash is from the recent perk cost change
It’s like if
I name load outs - it crashes
Playing with glitched perk set- it crashes
Playing with others that have glitched costs- it crashes
So I’m thinking due to the change of perk costs and the fact the old loadouts are saved onto the PS4 system an not saved the same as levels, customisations and dlcs That some people can retain old set ups which clash with the new costs. Weather it’s you with it or someone in you’re lobby that’s has it that’s when it seems to go tits up
Hi everyone. I’m really late to this discussion, but long story short, I bought PHG, (physical copy) bout few weeks ago, and have been having no ‘game crash’ issues… After yesterday or the day before, the crash issues began. At 1st, only every now and then. Now, it either crashes in the middle or close to end, on most if not all matches I start… even worse, before I even have time to hit ‘quick play’… Have illphonic released any info/solutions on fixing the issues once and for all? This error seems like such a shame considering how fun of a game it turned out to be. If a fix isn’t made soon, will there be any compensation for those of us that didn’t just flat out return the game for a full refund? Thanks again y’all
Revert back to the laat patch, and fix this one please!
It literally has to do with all the new items and implements
You can play with the older items in the game. The millisecond you put on something new and finish a game. Crash.
Never have I been afraid of customising my character so the game doesn’t crash… lol
I don’t think it has to do with the new items. I’ve been running them all, self revive and OWLF rifle on scout, A.C.I.G on Dutch 87, and UAV on Support, no crashes.
I’ve even been fully customizing all of my classes, still no crashes.
The only constant has been naming the classes, as soon as I name any class, it’s like a ticking time bomb to a crash.
I’ve had it freeze up a couple of other times, but much, MUCH less frequently than when I had my classes named, as in like, only 1 crash since I deleted save and didn’t name the class.
I finally got the game to crash!
I was playing as predator in a private match.
But then this is going against everything THEY are suspecting.
Is the game just flat our broken then?
I literally cannot customize my loadouts without it crashing (with the new gear).
No eta on fix.
So am I to understand there’s not a single illfonic employee responding on here anymore? On your own forum? Wow.
I was going to ask why my game now crashes almost every time I enter combat in both game types. I use to love playing this game, and I was good at it. But now I can’t get to the end of a match.
And please don’t tell me to delete my save data because reading through the previous months of unanswered comments I saw 100% of them say it didn’t work.
They’re here you just have to make a sacrifice to the Yaujta gods to make them appear
They’ve said before if there is silence here on their part they are hard at work fixing the game
Since the 2.09 update, the predator parry crash has been fixes, but now, every 2 or 3 games out of 10 or so, tend to crash for me while playing FT games. And it’ll crash specifically when ive been downed and preddy goes for his skull and spine trophy rip. Like as soon as it starts, my game sometimes blue screens… anyone else out thete having that same issue? Happens way less than the pred parry crash but still annoying that it still happens at all… i feel like illfonic might never get the game 100% crash/blue screen free… hopefully I’m wrong anout that tho…
I had this type of crash a few minutes ago, over a PlayStation 4 (slim). I had a build unistall, and fresh install from the PSN of the game and also deleted my profile settings.
Question is, what is the possibility for this thing to occur for example if other users on the session or even the player with the Predator/Hunter not to have the build freshly reinstalled for a longtime, temporary files deleted and profile settings being of an older version.
Is it possible for the issue to affect others on the session by crashing them aside the one who might not have the build reinstalled and all that done?
Pretty much my brow
Well. Kass. But she’s not a dev, and while she DOES report bugs to the devs, she’s not here as much any more. So yeah, nobody is really here.