Sometimes when Hex is started the ReplicatedFirst UI will load but then nothing will happen.
Remote functions fired yield without response from the server.
When you try to open the server error console (F9) nothing appears. It appears server is not responding.
This has been experienced by multiple players and was PARTICULARLY bad during our Creator Show stream. In that incident 99% of servers simply wouldn’t respond at all.
This happened to a very small extend yesterday and to a very large extent April 17th. Is it perhaps caused by a lot of people joining the game?
This is a pretty critical problem that I do not want effecting the Ultimate Competition launch on Monday.
This seems like it’s related. Fracture has had a similar issue with a new game it has, except these errors were shown after the server stopped responding. None of the scripts in the game could have caused it as they all yield at the given point.
I am ~100% sure this is a Roblox server issue not a my-code issue.
The fact that the server output window wasn’t responding pretty much solidifies that to me.
Edit: Now that this problem appears to be ‘coming back’ I am very concerned that it will plague the ultimate competition launch on Monday. Hex is particularly vulnerable because without server remote-event response the client simply wont load.
Our problems may be related. However in my instance I can’t even open the server output. The server simply isn’t giving any response. Which is VERY unusual as ReplicatedFirst loaded.
[quote] Our problems may be related. However in my instance I can’t even open the server output. The server simply isn’t giving any response. Which is VERY unusual as ReplicatedFirst loaded. [/quote]I experienced the exact same issue, except the server began to respond and then I viewed the output. I also visited HEX and yep, I saw exactly what you said. It’s the same issue, seems to be due to ROBLOX servers.
[quote] It’s still going on now? Damn. [/quote]Players began to complain they were lagging, then I noticed it to. The game was responding, but only every couple of seconds. Eventually, the entire game just stopped altogether, clients could still move and interact, but with no connection to the server the game was unplayable.
They were talking about a roblox911 email or something a while back, you could try sending a message that way, they said to send messages of critical glitches in roblox that need immediate attention, so I assume you could get same-day results
[quote] They were talking about a roblox911 email or something a while back, you could try sending a message that way, they said to send messages of critical glitches in roblox that need immediate attention, so I assume you could get same-day results [/quote]They didn’t respond all that quickly the last time we used them. I think you’re just as well off with this thread.
I had this problem a few days ago with my loading screen. Two players would join in the time frame (within seconds of each other) and one got stuck on their loading screen. The client got stuck on the portion that has nothing to even do with remotes, it was a fake loading bar that stopped moving- basically this code:
for i = 100,1,-1 do
loadingbar.Size = UDim2.new(i/100,0,0,30)
wait()
end
[quote] I had this problem a few days ago with my loading screen. Two players would join in the time frame (within seconds of each other) and one got stuck on their loading screen. The client got stuck on the portion that has nothing to even do with remotes, it was a fake loading bar that stopped moving- basically this code:
for i = 100,1,-1 do
loadingbar.Size = UDim2.new(i/100,0,0,30)
wait()
end [/quote]
That’s not the case here. The case here is remote functions are yielding because the server isn’t responding.
[quote] I had this problem a few days ago with my loading screen. Two players would join in the time frame (within seconds of each other) and one got stuck on their loading screen. The client got stuck on the portion that has nothing to even do with remotes, it was a fake loading bar that stopped moving- basically this code:
for i = 100,1,-1 do
loadingbar.Size = UDim2.new(i/100,0,0,30)
wait()
end [/quote]
That’s not the case here. The case here is remote functions are yielding because the server isn’t responding.[/quote]
It called a remote half way through the loop to get the character ready, and then one when it ended to setup everything else.
[quote] I had this problem a few days ago with my loading screen. Two players would join in the time frame (within seconds of each other) and one got stuck on their loading screen. The client got stuck on the portion that has nothing to even do with remotes, it was a fake loading bar that stopped moving- basically this code:
for i = 100,1,-1 do
loadingbar.Size = UDim2.new(i/100,0,0,30)
wait()
end [/quote]
So I’m not the only one who’s dealt with this? I up and redid my intro because half the time it got stuck, stranding those who didn’t think to reset.