Uber Lab Client Crashes - Nobody Expects Perfection

"

Fruz wrote:

If the client would be capable to send requests to the server @"This is a crash, don't punish me", there would be hacks to emulate it imho, it's as simple as that.

The client can't send anything; it crashed. It would be the server recognizing nothing happened from the client. Effectively, that means the "hack" is Alt+F4. That is VERY different than logging out (which is the client saying something). Regardless, with Alt+F4, you will still have to be alive for 6 seconds, preventing cheese.

"

MrsDeath_ wrote:

I dk what system are u using but i can report this;
i did 500 chests open challenge means 100+ labs this league and i had 0 client crashes.
Nvm the uber lab i ve never got client crash this entire league.

I am on the standalone client. However, I am running SR totem. And if anything of the past proves anything, I bet it is that. (SR seems to be the cause of many client crashes.)
I also have 500 chest challenge, and I've crashed at least 10 times. That's at least 10% of the time. Super bad.

"

Datachanger wrote:

"

Fruz wrote:

If the client would be capable to send requests to the server @"This is a crash, don't punish me", there would be hacks to emulate it imho, it's as simple as that.

The client can't send anything; it crashed.

The client probably could catch some unexpected exceptions/situations and notify the server.

"

Datachanger wrote:

It would be the server recognizing nothing happened from the client. Effectively, that means the "hack" is Alt+F4. That is VERY different than logging out (which is the client saying something). Regardless, with Alt+F4, you will still have to be alive for 6 seconds, preventing cheese.

So you mean those kind of crashes, it makes more sense.
I guess 6 sec delay does seem acceptable, at least to me.
If GGG thought that this was an acceptable solution though, they would have done it by now.

Uber Lab isn't that hard, only deadly things are the traps or if Izaro is at full charges and crits.

They don't need to change anything about it, they did a lot of changes already which improved the Lab Run Experience and that is fine.

I understand however why you are disappointed. Does it crash always at nearly the same places? Then it sounds like a bug with the skill you use. I can confirm, that the Flicker Strike Build I'm playing also causes crashes after a few hours, depending on the map. If I play my Cycloner i barely get a crash (only once in an Incursion and from the patch notes it seems it was a crash for everybody and not related to my skills).

On the other hand of course this could also be related to your system. It must not be your hardware, but sometimes the patches can cause corrupted or missing data, therefore I'd recommend to run the fix tool which comes with PoE. Also make sure that you have installed the latest drivers and may close any unnecessary programs before (e. g. capture programs).

"

Fruz wrote:

I guess 6 sec delay does seem acceptable, at least to me.
If GGG thought that this was an acceptable solution though, they would have done it by now.

Hence my thoughts at the end of my original post. It probably has to do with tech of reentering lab and/or when it has reset since then.

"

Stone__Cold wrote:

Uber Lab isn't that hard, only deadly things are the traps or if Izaro is at full charges and crits.

I agree, but that's not what I am referring to.

"

Stone__Cold wrote:

I understand however why you are disappointed. Does it crash always at nearly the same places?

Never in the same place, and it only happens while a totem is active. Additionally, I have had my carries client crash as well while the totems were active. That has happened at least twice. This leads me to believe it is an across-the-board thing. (Regardless, I have still reinstalled drivers/ran the cleaner tool/etc.)

I have been farming Uber Lab this league again, and there has been only one crash, and it was on my end. (Computer effectively blue screened).

It was definitely the Scorching Ray.

Also, I crashed in the chest room, of all places. Feels bad....
I really want them to implement the ability to return to lab after a crash.

Crashes in Izaro room 4 times this league.
I feel bad for wasting my time, certainly, but even worse when I waste others'.

Cons:

Will be abused by HC players, if there is a grace period they're going to autolog and get back into the lab where they were supposed to die

"

nooooodles wrote:

Cons:

Will be abused by HC players, if there is a grace period they're going to autolog and get back into the lab where they were supposed to die

Logging out is different than disconnection.
Logging out is the client telling the server to leave. In such a scenario, they wouldn't come back to the lab.

A client crash or DC doesn't do this, so the player could come back.

"

Datachanger wrote:

"

nooooodles wrote:

Cons:

Will be abused by HC players, if there is a grace period they're going to autolog and get back into the lab where they were supposed to die

Logging out is different than disconnection.
Logging out is the client telling the server to leave. In such a scenario, they wouldn't come back to the lab.

A client crash or DC doesn't do this, so the player could come back.

It's not different if you emulate it, and you can emulate pretty much everything (unless there is some sort of encryption involved? not even sure, adding some kind of encryption could lower performances overall anyway).

"

Fruz wrote:

"

Datachanger wrote:

"

nooooodles wrote:

Cons:

Will be abused by HC players, if there is a grace period they're going to autolog and get back into the lab where they were supposed to die

Logging out is different than disconnection.
Logging out is the client telling the server to leave. In such a scenario, they wouldn't come back to the lab.

A client crash or DC doesn't do this, so the player could come back.

It's not different if you emulate it, and you can emulate pretty much everything (unless there is some sort of encryption involved? not even sure, adding some kind of encryption could lower performances overall anyway).

Even then, iirc, the client timeout is 6 seconds? Emulating 6 seconds of nothing is not very hardcore friendly.