Set destination for all clients (doesn’t matter at all if you are docked or in space).
Click on the yellow gate in the overview on all clients.
Click on the Jump button in the Selected Item window on all clients while quickly alt-tabbing between them.
Repeat step 7 until next gate is not auto-selected.
I’ve noticed it happens more often the more clients that are running and less often when only 1 or 2 clients are running. It also seems to happen more often when there are a lot of items (or filtered items not being displayed) in the overview list.
Simple fix would be to just code it to select the next gate in the overview list after the list is completely loaded as it looks like the issue stems from the auto-selector trying to select the next item before the overview list is completely populated or is still in a “filtering” state. (i.e. It is selecting the next gate then the list is being refreshed due to still populating or filtering instead of the other way around).
Simply set a route in-game. After jumping into a system and cloaked, instead of the next gate in the route being selected in the Selected Items box, the gate you just jumped through is selected instead. This occurs every one in three or so jumps probably, while in the past it occurred maybe one in every fifty or more jumps on a route.
If you don’t notice this and simply click “Jump” in the Selected Items box, you will slowboat back to the gate you just jumped though, instead of the expected behavior which would be the next jump in the route is selected and you warp to it.
The deployed fix may have reduced the instances of the issue, but it still occurs far, far more frequently than pre-update.
Someone mentioned (can’t remember where, maybe in my alliance’s discord) that it may happen when grid loads before your overlay loads, but this was before the update when the error did not occur as often.
The more I think about it why not just select the next item in the overview list that is marked yellow. The code already knows which one to mark yellow so why the hard time telling it which one to auto-select? From a programming standpoint this should be beyond easy.
Heaven forbid that someone might be more competent at the game than a lame instalocker camp on a gate.
But just wait. CCP will fix this with the upcoming cloaky camping fix and, in their grand tradition of favoring collateral damage over actual thought through changes, make the only way for DSTs to survive in high sec and low sec and null sec impossible to use. Just wait and you will be allowed to get your easy claps soon enough.
Not really, blockade runners can warp while cloaked so you don’t see when and where they go, align much faster and have higher warp velocity than any other haulers that you may want to do the cloak mwd trick on.
On top of that, blockade runners are the only haulers capable of taking a blops bridge, making them the safest haulers out there, as well as the only possible fuel hauler for a blops fleet.
Please continue how blockade runners are useless because of the MWD trick.
Out of curiosity: Has someone else noticed that damage does not apply any longer to NPCs when you started warp? I have just had the following situation: I was shooting a frigate that was 5km next to me with missiles while I was aligning for warp on an acceleration gate. It fired 4 volleys at this frigate but not a single volley was registered as the shields of the frigate did not go down a single hit point. I aborted the warp and suddenly the damage started to apply again. Started the warp align again and the damage stopped again.
11:31:30 Notify Please type in at least 1 character
I get that all the time now when I try to delete bookmarks by pressing Enter quickly. This message appears in fact all the time when I just press Enter without having focused any text input field, but typing does not add any text anywhere.
I use Windows 7, and the new jump tunnel animation is causing audio problems for me.
I log in, undock and everything is fine until I take the first gate. I jump through, the new animation plays, I appear in the next system and everything still seems normal. However, no matter what I do next, the ambient audio of the stargate that I just came through will continue to play indefinitely. That humming noise and chatter just keeps going in the background while I’m warping around and doing sites … sometimes it will even continue after docking up!
It seems to me that this was usually but not always related to some key I didn’t know I was hitting. I’m going to have to guess it was the space bar which does a number of things depending on window focus but I’m not sure. As it is now most of my jumps require finding the next gate in the overview manually and it seriously sucks. When I’m jumping I need to pay attention to what I’ve landed in, not scrolling the overview frantically.
Tested it with a single client running, EVE-Client always focused and it happened two times running from Hek to Jita.
Tested it with a single client running, Alt-Tabbing between eve-client and other applications and it happened 1 time running from Hek to Jita
Tested it with a single client running, making sure to be tabbed out as much as possible but especially during the jump animations and entering a new system and it still happend.
Tried the same using a Linux client to see if it makes a difference but it still kept happening.
What I find interesting is that everytime it happens the gate you just used is selected instead of the destination gate. I don’t know how this is coded but to me it seems like the function that handles this cannot select the target gate and defaults to something else which is the entry gate. Just a layman’s guess though.
Mission agent dialogues all mixed up with choosing to delay a mission triggering the agent to act like you have rejected the mission. In addition, you used to be able to minimize a mission offer after acceptance and it would later pop back up once you completed all the requirements for the mission being completed . Didn’t we also have green checkmarks when a mission goal was accomplished? Marks remain blue now.
I did 54 jumps this morning to JIta and 54 back.
I set the destination and use the jump icon only
Route to Jita the greyed gate in overview wasnt the yellow route gate for 7 of the jumps.
On my return this only happened 3 times and wasnt the same gates.
tow the line? "Toe the line " is an idiomatic expression meaning either to conform to a rule or standard, or to stand poised at the starting line in a footrace.
Did another 32 jump route, out of that 19 of the yellow highlighted gates in the route wasn’t automatically selected. I had to scroll through the Overview and manually select them so they would appear in the ‘Selected Items’ box just so I could then click the ‘Warp to / Jump’ option.
Really ironic this issue becomes active during an event that gives 90% drop rate in loot from all destroyed player ships.
I’m seeing it for most jumps. Not using autopilot. Not switching windows, or even window focus inside of Eve.
It is a very very good way to get killed…
Heaven forbid that someone might be more competent at the game than a lame instalocker camp on a gate.