[PlayStation] When pressing the circle button right after joining, the client exits the experience

Bug Reports Engine Bugs
,
#1

In my experience there’s a main menu that players sometimes want to close immediately after joining with the circle button (ButtonB on Xbox). The problem is if you do this shortly after joining the experience, this makes you leave the experience.

Expected behavior

The client shouldn’t exit the experience when pressing ButtonB right after joining.

5 Likes
#2

Same thing happens on Xbox:

4 Likes
#4

Thank you for linking the issues, omega. Indeed they seem to be relatd.

Here is an update: the team has implemented changes being rolled out in a future release that should help alleviate the back button not being unbinded after the experience has loaded. Please stay tuned!

3 Likes
#5

This is not fixed. It still occurs in my game. Nothing in my game that is bound to ButtonB/Circle would cause a crash, or even an error. Here’s it happening to one of my players when he presses the circle button

1 Like
#6

I think you need to replace the battery in your smoke detector

#7

Not my footage, but I agree. I actually told the person who recorded this video to do that too

1 Like
#8

Can confirm this still happens in my game, user have reported it happens when they teleport while in-game to different servers through a server list, not always but still happens, they press B on console and the game closes.

It affects my users a lot as B button is binded to combat and they get combat logged when the bug occurs when they are engaged on a fight.

1 Like
#9

This bug is still happening, just today I got a bug report regarding this matter, this is the video the user sent: (they tried pressing LT + B to execute a move)

I would really like any input regarding this matter as this heavily affects the console community in my game, it’s not 100% guaranteed to happen but when it does it’s harmful.

#10

Hello!

Thanks for the follow-up and I am sorry to hear that this issue didn’t get resolved with the previous patch. I am going to re-open this ticket so that we can work on another patch for it (hopefully this one sticks).

For those experiencing the issue in their experience:

  1. How long does it take for your experience to load?
  2. Do override the default loading screen or leave it?
  3. How often does this happen?
  4. How long after loading completes can this issue occur in your experience? (eg. few seconds, minutes, indefinitely)

Thanks,
SolarCrane

#11

Hello, sorry for not responding earlier, didn’t get a notification and I want to help

I asked the person about this matter, and they said it seemed to stop doing that since last week, did the team try doing any fixes? If that’s the case I believe it worked, thank you and sorry again for the long wait for a response.

#12

We believe the root of the problem is a race condition, therefore it is not unexpected that it may have stopped happening without much explanation. We are simultaneously hardening the code against race conditions and aim to ship that soon. Hopefully, when the new code ships it will be nigh impossible to see this issue.

Thanks,
SolarCrane

#13

I appreciate it, If you still want the answers for the questions you asked up there I’ll be glad to provide you with the information I have. Thanks in advance.

#14

If it isn’t too much trouble, I would love to get some of that data to confirm our theories! No need to be super precise, mostly trying to get a rough idea of the scenario.

SolarCrane

#15
  1. Takes less than a minute with good internet connection
  2. Default loading screen currently is removed due to another glitch on console: Console loading screen freezing on join, but 3 months before my update on this matter because it was still happening, it didn’t remove the default loading screen and was just Roblox’s default one
  3. It used to happen randomly but often, the users affected had to join the game, press B (on xbox) on menu to check if they had the glitch so they could keep playing without unexpected disconnections
  4. Seems to happen even minutes after the game loaded, could be indefinite but not sure, the users that reported the bug showed them waiting on the menu for some time and pressing B before spawning in and the bug still occurred

The experience for testing if needed, since it used to happen there, is linked on our PM message

Hope this helps :pray::pray:

#16

Thank you kindly, this does sound like symptoms that would be caused by the race condition we see.
Sorry, about the additional loading screen issue as well!

We’ll get to work on getting this ‘B’ button sorted.

SolarCrane

1 Like