By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!This. Basically if you have a slow connection you will see the loading screen informing you that it is downloading instead of crashed.Actually it shows but it is pretty fast so it is hard to see it
Lol well it would probably be a good idea to either make it stay on screen longer or make a separate window show until the client loads back upThis. Basically if you have a slow connection you will see the loading screen informing you that it is downloading instead of crashed.
Pretty sure it does exactly what you're asking for, but I may be misunderstanding. Can you explain again in full detail what scenario you're talking about? @Cloud tag to confirm.Lol well it would probably be a good idea to either make it stay on screen longer or make a separate window show until the client loads back up
When there's a client update, all i see is it loads to 30% then closes, nothing to show that it's updating. When it's finished downloading the update the client restarts seemingly out of nowherePretty sure it does exactly what you're asking for, but I may be misunderstanding. Can you explain again in full detail what scenario you're talking about? @Cloud tag to confirm.
You're right, it does say it's updating, but it's not even visible for half a second before it disappears. I only saw it because i was looking for it.Pretty sure it does exactly what you're asking for, but I may be misunderstanding. Can you explain again in full detail what scenario you're talking about? @Cloud tag to confirm.
This. Basically if you have a slow connection you will see the loading screen informing you that it is downloading instead of crashed.
It's not possible because the way the client updates is a multi process solution that involves process replacement.Just have it stay open for a few seconds after the update is finished.
I have one idea but it may not be as reliable as we need.@Cloud any brilliant idea to resolve this UX issue?
We use essential cookies to make this site work, and optional cookies to enhance your experience.