Yellow Error Message Problem Processing Game Logic sh_challenges.gnut #264
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number AMD Radeon R290X
Enter RAM memory size in GB 32
What is your gamertag/PSN ID/EA Account name? MisterMcStabby
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)? Loba
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? Loading into the match from the lobby
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Main Lobby, found a match, loading in, then error message
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Was in Training Arena as Loba, left, starting finding a regualr Trios match
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 12.05.20 18:30
How often does the bug occur? Often (50% - 99%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? Game goes to a yellow error message screen with the message: "sh_challenges.gnut #264 [UI] First parameter is not a hud element"
What should be happening instead? Not that lmao
Steps: How can we find the bug ourselves? Start game, load into Training Arena, was playing as Loba, test the weapon changes, teleport to Nessie (super easy now btw), leave, find a regular Trios match, then get the error message
Trying to load into a game, get the "game entering sound", then crashes to the attached yellow error screen with message:
There was a problem
processing game logic.
Please try again.
-----
sh_challenges.gnut #264
[UI] First parameter is not a
hud element
I was loading in solo -- I did not have premade teammates.
While typing this bug report, I reloaded the game, went into a match successfully. After it was done, I tried loading a 2nd match, and this same error happened again.
I've never had Apex crashing / error messages like this in the past.
Thanks for the updates!
[Marking this post as a solution just for visibility. This is still an ongoing investigation, and we are not considering this resolved at the moment.]
We've heard from the Apex Legends team that they are currently investigating this issue and working on getting it fixed.
Thanks for bearing with us while this is under investigation.
/Kent
