Issues, Workarounds & Localization

The Retribution 1.0.8 patch on January 4th, which claimed that "the module activation timer UI has been made considerably more accurate, especially after jumping", actually caused significantly more issues than it solved.

The behavior of the module timers is at times unpredictable and makes it difficult to manage ammo, or analyze when modules will actually deactivate, etc.

Issues I've observed:

• The white timer indicator for the module will often start at a position on the circle that's not at the bottom (the "zero" position)
• The timer indicator always disappears at the bottom if the module is deactivated manually, however this doesn't actually indicate the module has been deactivated as the module will continue to pulse red for several seconds
• The timing indicator will often run significantly faster on the first cycle and then slow down on subsequent cycles, especially if there is any network latency
• Modules will sometimes remain active for an extra cycle after having been deactivated - this is especially noticeable on weapons with a long cycle time where a gun is manually deactivated yet several seconds later the ammo indicator decrements and another full cycle completes before the gun finally deactivates. When this happens the timer indicator stops yet the module icon pulses red for the entire duration of the cycle
• Concurrent use of the EVE monitor (Ctrl+Alt+Shift+M) shows that the server had received the command to deactivate the module yet the module continues for an extra cycle
• Modules deactivating automatically (conditions such as out of ammo, target unlocked, target destroyed, out of cap, etc.) cause the timing indicator to terminate at some other point than the "zero" position at the bottom of the circle
• These issues are present with minimal to no latency, any latency beyond normal severely exacerbates the problem.

I would really like to see these issues addressed. I believe the UI timers before the 1.0.8 patch were more accurate than the supposedly "more accurate" UI timers.

I have also observed most, if not all, of the issues listed despite having fairly low latency to the server.

Module timers have always been quite sketchy at best on a good day. On bad ones, you'll get continued cycling after manually turning a module off (sort of like module lag, but doesn't last for more than a cycle or two past clicking on it). I agree that it still to this day anoys the unholy **** out of me. Curse my OCD.

Best thing (well, only thing really) to do is to ignore it as best you can and don't rely on the timers' accuracy.

Bump.

I've been noticing this as well and especially in missile PVE.

I can turn off the launchers shortly before a cycle ends and the little white bar goes into the next cycle and then the launchers blink red for several seconds in an excruciately long animation before I can fire again.

I've also had troubles with the cloak. When activating it the animation starts as off and then slowly pulses green. So for a split second the cloak is activating but the icon doesn't reflect it. On a gate camp this made me hit it again just to be sure which caused me to deactivate the cloak and leave me exposed for a 30 second reactivation timer.

Thankfully the gate camper only had a web and not a point so instant warp for me but it could have ended badly.



I have split second decisions to make and with a latency of below 200 I should have no more than a 5th of a seconds delay on all commands but it feels like the UI just isn't up for it.


The UI can best be described as "mellow"

I'm fighting for my life but with every command I tap the UI responds with "chill dude. I got it man. Just relax and let me find my glasses and I'll get on that module"

Judging by my UI's passive response to emergencies. It may very well be stoned

I've noticed this same behavior with mods that does seem a lot worse than before.

Bumping for truth. Extermely annoying when you have to operate multiple scripted midslot mods.

Had the same issue on simple things like probe launching - white bar seems to start and stop in random locations, impossible to tell the launcher's actual status

Confirmed I've experienced ALL these issues many many times. It's quite frustrating, especially when it happens with MWD.

I've even had it happen with my Siege module and you can imagine how bad that is (sorry guys I'm stuck for another cycle........bia).

I find modules not de-cycling is sometimes caused by the close proximity of an activating and then de-activating click. Sometimes it frees itself if you move the module around in the UI.

I don't know what causes all this, but yeah it needs to be fixed asap, it's certainly more important than navy bc's...

I've also experienced less UI precision in the past few months, specifically, say I jump through a gate, then break my gate cloak by hitting approach on the gate, then hit my mwd, often times the initial command to approach gate isn't registered unless I spam it, or the mwd command isn't registered after I decloak. **** like this gets people killed.

In fact, doing just about any UI activity in EVE requires you to spam the **** out of the command 3 times before it happens, drones are particularly bad. This isn't in some blob fight, this is just regular skirmishes.

We're having issues in wormholes with this too: approach wh, hit jump, yet no jump occurs.
turn off RR on carrier, it keeps blinking red for up to 5 seconds.
sleeper volleys are stacking up, applying 2-4 volleys at once (almost alpha'ing some battleships and t3's). It's happening more often, and getting worse (or at least it feels like it). Just submitted a bug report on it as well.