

Pure Function Call Error
Started by Twinkie D Lite, Mar 22 2014 06:34 AM
13 replies to this topic
#1
Posted 22 March 2014 - 06:34 AM
I notice they keep locking the Pure Function Call listings. Is a solution already posted that I may have missed? If so please archive this with the others, my apologies.
It is becoming quite annoying to continually have to restart the game every few rounds. It only seems to happen when you leave a match and attempt to return to the Mech lab. And of course the repair tool does nothing to solve the issue.
It is becoming quite annoying to continually have to restart the game every few rounds. It only seems to happen when you leave a match and attempt to return to the Mech lab. And of course the repair tool does nothing to solve the issue.
#2
Posted 22 March 2014 - 07:46 AM
The only receipe I can suggest to solve this endless pain is to put the umbrella between the backtoll muscles of the each herrige game programmer and revolve them until the bug get fixed.
I'm tired of all this scrap. Fishes, return my money and get all your bugged pixels back.
I'm tired of all this scrap. Fishes, return my money and get all your bugged pixels back.
#3
Posted 22 March 2014 - 08:39 AM
I just got one dropping out of a match early. I think that error is back. Don't drop out early appears to be a solution.
#4
Posted 22 March 2014 - 08:53 AM
I was just curious as they have locked and archived all other topics related to this question. Had it happen 3 times in a row today, a new record.
Edited by Twinkie D Lite, 22 March 2014 - 08:54 AM.
#5
Posted 22 March 2014 - 12:42 PM
Twenty ******* seven times for one day.
**** you, herriges.
Uninstalled.
Return my money or get sued.
**** you, herriges.
Uninstalled.
Return my money or get sued.
#6
Posted 22 March 2014 - 03:22 PM
After the last patch I have had these at least once every time I have played a few matches. Usually twice. I uninstalled the game today, but that has more to do with LRM fest V4 than this bug. It usually occured at the end of the match rather than the middle of the match.
#7
Posted 22 March 2014 - 07:17 PM
I've started getting the error frequently today. Never been bothered by this issue before. After reading this thread I tend to get it when leaving the match early.
#8
Posted 24 March 2014 - 05:03 PM
So, any official response incoming?
#9
Posted 24 March 2014 - 07:26 PM
Any time I leave a match early it is a crap shoot. I either get stuck in "connecting" forever or get the PFC error. I have never had to use the task manager to close a game so frequently in my life. By design, the games wants you to leave the game as soon as you die to jump in another mech and get in another match to earn Cbills. The only official response I have seen is " don't leave a match early and you won't get the error". The game has such potential, but the plethora of bugs that seem to have been around for months and months ruins the game.
#10
Posted 25 March 2014 - 04:24 AM
Also seeing it. Only played ~4 matches recently and the last game crashed it when i pressed exit match.
#11
Posted 25 March 2014 - 04:44 AM
There is no money to be made sitting in spectate mode. They need to fix this thing, and then get to work on the collision issues, there even worse.
#12
Posted 25 March 2014 - 07:49 AM
I'm also struck randomly with this.
Appears to be related to quitting a match early. I think quitting directly after getting destroyed might be a factor. Waiting for a while in spectator mode, even just looking at your kill message seems to be enough to not get the "Pure Function Call" error...
Appears to be related to quitting a match early. I think quitting directly after getting destroyed might be a factor. Waiting for a while in spectator mode, even just looking at your kill message seems to be enough to not get the "Pure Function Call" error...
#13
Posted 26 March 2014 - 01:17 PM
My son and I both get this occasionally. For us it does not seem to be linked to leaving a match early as we've both gotten it after spectating a full match.
#14
Posted 26 March 2014 - 03:44 PM
I got this reply from support when I submitted a ticket:
I checked the know issues forum and could not find this issue listed.
Quote
The problem you have encountered is a known issue and we hope to have it fixed soon. It's caused by exiting a match in-progress, though there currently isn't a work-around short of restarting the client.
I checked the know issues forum and could not find this issue listed.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users