Alle Meldungen
Railroad Tycoon: Das Brettspiel Meldungen
#64752: "Upon reload, game. became inaccessible "
wontfix: Dieser Fehler wird nicht behoben werden
3
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
An einer Stelle konnte ich die Spieloberfläche nicht erreichen
Detaillierte Beschreibung
• Was wurde auf dem Bildschirm angezeigt, als du blockiert wurdest (weißer Bildschirm? Teil der Spieloberfläche? Fehlermeldung?)
Part of the game interface loaded and it hung up at Application Loading• Welchen Browser benutzt du?
Google Chrome v98; mobile app and PC webpage
Meldungshistorie
18. Mai 2022 15:17 • andiestuffiegirl • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
On the last play of the game, the end of the double map play, refreshing completely made the game unable to load. Switching to other devices produced the same problem, and everyone in the game had the same issue upon reload attempts. We could go back to the 'Go to Game' screen but multiple attempts made it clear we could not get back into the game at all. We couldn't abandon, the only option was to Quit Game.
18. Mai 2022 17:31 • Brento • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
One thing I would like to add, is this was the Transcontinental map, and we noticed the issue after the 4+ hours played mark. Wondering if maybe new game connections time out after 4 hours, for real time games. I've personally never played a real time game that lasted that long.. so could be related.
18. Mai 2022 18:22 • WetDogIsHappy • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
Can't reproduce at the moment. I think the game timed out and from its point of view ended normally. I will see what I can find out about this.
Games in Training mode with a bug report don't seem to be able to load into my test platform
This might take some time to resolve.
Games in Training mode with a bug report don't seem to be able to load into my test platform
This might take some time to resolve.
19. Mai 2022 3:28 • Brento • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
We had no connection issues reported in the first 4 hours of the game. Might want to comb session vars to see if this is a setting. Not very often a real time game of RotW lasts that long. Training mode not having timers, might also not trigger the timeout refresh on the server too?
But, after 4 hours, I think everyone who closed their browser, and tried to rejoin, couldn't back in. Maybe the session timer is less than that even, but this is when we noticed it.
But, after 4 hours, I think everyone who closed their browser, and tried to rejoin, couldn't back in. Maybe the session timer is less than that even, but this is when we noticed it.
20. Mai 2022 19:52 • Brento • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
Kenny and I started a training mode game last night, and decided to log off to see if it would stay active over night. It appears the game disappeared. Perhaps this is a general issue with all Training mode games? Probably fairly easy to test with 2 clients idle in the background.
Normally this wouldn't be a problem, but apparently this game option can make the game last really really long.
Normally this wouldn't be a problem, but apparently this game option can make the game last really really long.
22. Mai 2022 15:19 • WetDogIsHappy • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
Some folk have been playing in Normal mode, with no time out.
So I am not going to get overly excited on this.
I will leave the bug open for a bit, but mostly I think this is just a Training mode timeout.
So I am not going to get overly excited on this.
I will leave the bug open for a bit, but mostly I think this is just a Training mode timeout.
29. Mai 2022 6:09 • WetDogIsHappy • Dieser Fehler wird nicht behoben werden:
I am pretty sure its a Training mode thing, but I have moved Transcontinental to Full Production, so have fun in the real world of ROTW.
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
