Why not just reverse it to previous option?
Calculating it based on autopilot settings was imho best option, but now you're trying to make player base 'happier' even if players don't want this change...
Don't fix if ain't broken... but it seems none of devs heard it before.

I don't know if this is Rubicon 1.2 related but prior to the patched, I never got socket closed errors. It's been almost regular this week and now today, I can't even get beyond the character selection screen if I get that far. I had my cable modem replaced and my service checked, just in case. EVE Online is the only service that is giving me connection errors. This is getting quite frustrating. I even disabled all anti-virus and firewalls just to be sure.

Expeditions seem to be bugging out and breaking, specifically Blood and Sansha expeditions, both high and low sec.

I'll get to the next escalation, hit the trigger whether it's killing a ship, building, or shooting at something and the message will appear just like everything worked. After I clean the area out and check my journal I don't have a new entry. Everything happens that would indicate the expedition continued to escalate, but I don't get a new destination. This has happened 5 times since 1.2, and never before then, so I assume it's related to this patch but I could've just been lucky before.

It's really frustrating to go from this: =D

To this: ='(

In the span of a single click with no rhyme or reason to it... Especially if I have to fly through gate camps and dodge combat probe scanning to get back out of low with only a partial reward....

Nope, because I'm usually busy getting shot in the face for the next 15 minutes and/or watching D-scan right after it happens. A lot of these sites aren't easy for me, but the next few I run I'll try isolating the trigger, popping it last, and then handling the bug report if it bugs out.

Thanks for making me realize this is probably something I should do if I ever expect a fix, it's not a natural thought when you're in the middle of a fight, even if they are just rats (this time).

Since the 1.2 patch i've had weird fps issues, where my R9 290 is at 100% activity, it's almost like there's something else in EVE eating up my GPU usage, i hope no one at CCP HQ are using AMD gpus for mining BTC or LTC xD

before patch it was solid 60 fps vsync and 100+ when not vsync, and now it's horribly at less than that(10-35) and most likely because of the 100% activity leak from EVE itself.


full spec is AMD FX 8320
AMD R9 290
16gb ddr3 ram
250gb SSD, where EVE resides.


there has been other instances with game clients operating shadow btc mining tasks for user's GPUs, please don't tell me CCP are trying it out too.

the ambient sounds from incursion systems never go away until you relog. So annoying, I went through some incursion systems to pick up some blueprints and the annoying sounds followed me for the next few hours until I relogged.