pve auto-ban

wendysue53

so... Logged in after a few days.
waited through the usually updates.
found the game crashing with every loading screen as usually happens after a new update.
tried to do a pve instance - crashed.
typical.

THEN got hit with a 2 hour ban from ALL instances! WTH?!
Never happened before.
Game crashes and the player gets penalized?!
Usually, you could log back in and pick up where the game died.
Not so this time.

Very poor game development concept here.

wendysue53

Seems if you loose connection, you're not going to be able to do anything for a while.
2 hours. Got to be frigging kidding me.

Unknown

This content has been removed.

leemwatson

This has only ever happened once to me. It's not a big deal, do some missions instead. Also, I've never had crashes after updates.

wendysue53

only until the game update balances. Always happens right after updates. Also happens to a large number of players. Started right after 2.0 was introduced, but I've a feeling other game issues are involved. But that's typical with STO, and I've identified most of those concerns on my end. It takes about a day or so to sort it out, but that's not the issue.

No, what's concerning is the application of the auto-ban if you're disconnected for whatever reason.

leemwatson

wendysue53 wrote: »

only until the game update balances. Always happens right after updates. Also happens to a large number of players. Started right after 2.0 was introduced, but I've a feeling other game issues are involved. But that's typical with STO, and I've identified most of those concerns on my end. It takes about a day or so to sort it out, but that's not the issue.

No, what's concerning is the application of the auto-ban if you're disconnected for whatever reason.

What you're not understanding though is that the system isn't recognising that you've disconnected, but it's seeing that you've left the queue, so it's allocated a 'Leavers Penalty'. To be honest, it is a rare thing, but however this sort of thing is necessary to a point. I have had this happen during CCA only though and I rarely get D'cd so it's hard to say what other maps it can happen on.

wendysue53

true. I can understand the reasoning behind it. but the disconnect issue is one that makes me shake my head when it causes something like this to activate.

honestly, all the years I've played, I've never run into this as an issue. first time, which made me wonder if it was added in 2016 at some point. I'll just chalk it up to another game weirdness. That is unless it happens again. If it happens again, I'm going to think it's a new game frig-up on the devs' side. As unstable as STO is, it wouldn't take much to totally mess it up for players.

leemwatson

wendysue53 wrote: »

true. I can understand the reasoning behind it. but the disconnect issue is one that makes me shake my head when it causes something like this to activate.

honestly, all the years I've played, I've never run into this as an issue. first time, which made me wonder if it was added in 2016 at some point. I'll just chalk it up to another game weirdness. That is unless it happens again. If it happens again, I'm going to think it's a new game frig-up on the devs' side. As unstable as STO is, it wouldn't take much to totally mess it up for players.

No, it's not a recent thing. I clearly remember this happening to me well over 2 years ago. I will however dispute your claim that STO is unstable as I've never had a problem with game stability program-wise in nearly 6 years! Even with 2.0 I have had zero issues, and that's on laptops (latest one with AMD A8).

wendysue53

no arguments. by unstable, I'm referring to known issues that can result in game crashes and other things, such as visual/ active defects. so, not addressing that point as anything significant, as those issues are well-known.

never had crash issues until after 2.0 release, which is known to cause a varient of the loading screen crashing issue, but not the only cause. but not worth debating here.

as for years played... for as long as the games been around... *shrug*

glad to hear the issue isn't new as that means it's not something I'm likely to have to deal with again. If it happens again, it's just going to be very annoying...

leemwatson

As I said, it's rare. Be thankful that they haven't been stricter on the AFK/Leaver's Penalty, because IMO the AFK's penalty needs to be incremental and account-wide to discourage the event leechers.

The 2.0 release issue is going to be a pain, I realise that, but the way people go on about it, you'd think the Dev's aren't even working on it going by some of the comments, when in actuality, they've probably all gone bald by now trying to sort this out. I mean fixing the game so it will run on hundreds of thousands of different configurations isn't child's play, like some people think it is. The Consoles have it easy....lol.

wendysue53

yep. exactly this.

think the big thing with the 2.0 issue, is that it can lead to a crash with every loading screen for those unfortunate enough to have that particular issue, and no one is exactly sure why it does it. And it doesn't do it to everyone, which can make any IT person scratch their noggin. It's driven me nuts each time I've run into it or something similar to it, although the cause ends up being different. *shrug*

ah well. The trials of playing sto.

cactolith

What is your video card specs? And what drivers are you using?

Also, try dialing the lighting graphics settings back to pre-2.0 and see if the issue persists. Be sure to gradually do so one notch at a time, as to not potentially hang the game up.

jorantomalak

OP as bad as it is due to the afk/leavers penalty being well rough and not polished, it does help keep afk farmers and bots from leeching on the hard work of actual players and those playing the game.

For what its worth ive had it happen myself a few times, i just load up another toon and farm some dil fora couple hours in the end im a little dil richer and primed to kick some NPC teeth in

wendysue53

It's alright, @cactolith. I'm aware of the issues with 2.0 and how to usually deal with them on my end. Thanks though.

Hmm. You know, I didn't even think of running another toon. Probably because I'd just finished running all the admiratly/R&D/etc on them before-hand. I'll keep that in mind next time and dust off some of my old ones.

groomofweird

My old XP machine used to crash regularly, with increased regularity as time went on.
In the beginning (a good few years ago now), when it was only occasional, I would usually log back into the game where I left off. The exception would be if my space had been taken up with a new player joining in that time. Or the mission had ended.
If my spot had been taken I would usually get a message saying "you are no longer on this team you will be removed from map in 5,4,3...." and be automatically removed with no penalty (or rewards).
Then some considerable time later (newer more stable machine now), I had an as yet unexplained crash mid PVE and got the penalty on returning.
I do remember still being able to log back into a PVE after a crash for some time after the afk penalty came in, with the penalty change after a crash sometime last year (for me anyway) if memory serves.
Just my personal experience with this rare but irksome occurrence.

warpangel

Yeah, the auto-penalties are total garbage and crashing is pretty much the best way to get them. I had a crashing problem in late 2014 and got penalized once or twice for crashing in a queue mission.

The solution was to NOT try to immediately relog to the same toon, but to wait long enough that the queue is definitely over.