The EVE launcher has bugged out again.
This time it is stuck “Verifying”.
I am tired of reverting to an older launcher version when something like this happens, it works and I can’t see a difference.
Who is working on the launcher and are they making changes for the sake of looking busy and keep their job?
Let’s say that I can be bothered to fix it. What are my rewards for going through that hassle?
Loads of UI bugs like the probe size getting stuck, which forces me to relog.
Settings that don’t save server side, which I can lose with a reinstall or new system. The friction for that with a returning player is massive. How have you not done this yet?!
TiDi that is worse per hundred player than a decade ago on a far and away more powerful PC.
D-Scan with no automatic mode? So I have to keep hitting that button like a pigeon in a cage pushing a button to get food.
Now I know, no one likes to see this sort of feedback but look at your friends list.
How many of them are playing other games because they got fed up with EVE for development reasons?
It may not come down to the people working on the launcher — they’re likely dealing with legacy systems, constraints, and competing priorities we don’t see. The frustration is real, but it feels more like a gap between engineering effort and player-visible benefit. If fixes to core tools came with better stability gains or preserved settings, the time spent troubleshooting would feel more worthwhile. Better feedback loops might help all that hard work land where players actually feel it.
I don’t have any issues with the game except when I undock. It always freezes several times a second before I can enter warp. Good thing is, the freezes help me aim my mouse on the correct destination
Auto for us would be slower than manual, it would give people a chance to probe us down.
It has worked as sonar in almost every submarine game since the 1980s.
That has had some weird results. I think it is linked to player structures and SKINs being poorly implemented.
I haven’t had problems undocking from a NPC station.
Meanwhile, our Fort changes SKIN every week, in one case, I undocked, warped to a gate and jumped to the next system, while neither the station nor my HUD had loaded.
There is something very wrong going on, when something as critical as your HUD loads after the graphics model of a structure.
No doubt it’s frustrating. There are bugs that happen that make me want to log off. Then I remember I’m online. HUD loading after world assets could be a streaming / prioritization issue rather than something fundamentally “very wrong.” Modern engines load visuals and UI on different threads, and under some conditions (latency, caching, or recent changes) they can desync briefly. It’s not ideal, but it’s also the kind of edge case that’s hard to catch without players reporting. Hopefully logs and bug reports help the devs pin it down instead of assuming the whole pipeline is broken.
No.
What is fundamentally wrong, are their coding practises.
That clearly shows that they don’t have a priority loading list.
They have had decades to work out and re-write their POS code and keep using it as a, “Computer says, ‘No.’” excuse.
That they don’t have a test server running with at least a NDA group of testers that play the game is a massive red flag.
They are probably using Agile and Scrum management, to keep pushing new features, however, they are bleeding people as fast or slightly faster than they can attract and retain new ones.
EVE has been treading water for a long time because of how cumbersome and “second job” it has become.
I have re-written live financial systems that had no documentation and no comments in the code with deliberate obfuscation by shady consultants that wanted to ensure they would be called back.
Clearly you overestimate the value of your opinion, I was just letting you know your value to the community now that you’ve decided not to play the game anymore.
Good riddance now, be sure to close the door behind you.
Yeah. Those are annoying. I haven’t encountered any bugs with probes, but yeah… There are bugs in the UI.
Most of the settings can be either exported to files or have their own files already present in the user directory. Ask about particular one, and someone will answer…. Or search EVE University Wiki .
TiDi has nothing to do with your client. It’s a server feature.
An automatic dscan is equivalent to a system wide overview that updates live. I agree that there are specific situations where it makes sense, but in systems with a lot of players and movement, it’s just too much information that changes constantly. Just imagine an overview on Jita 4-4 undock. Can you track what’s happening there effectively? Not to mention the added stress on the server that an automatic dscan would put.
As I said, those things don’t bother me too much. I have a PC from 2015 and I can’t complain about how it handles all the games I have.
My experience with online games is that things don’t always work as they should and I explained why so no need to rant and rave over something my life doesn’t depend on.
Yes because people D-Scan constantly in huge battles.
In many cases it is getting hit more often than if they had to toggle on automatic and let it ride.
Most people probably never touch D-Scan in large battles. Sure, there are a few who have to, but the most of the F1 Monkey line members aren’t.
In many cases, the server is likely getting hit less than if all those fleet members were out doing their own thing, but if every single one of them is running an automatic d-scan, then you can be guaranteed that your idea would cause a great deal many more hits on the server than either of these scenarios.
Rubbish. The launcher used to be entirely cosmetic and could be bypassed completely. Now the launcher uses the same ESI/JWT login as 3rd party apps and at a minimum it was migrated from a QT5 to a QT6 based library since OSX was a supported platform over 10 years ago. If there was any similar code beyond a while () do loop I would be surprised.
T3C configurations causing systems to crash due to graphical engine glitches. Music broken for months. Abysmal performance of DX12 whilst blaming users for not updating drivers time and time again it is surprising anyone even bothers.
The current meta of spamming d-scan faster than people can probe is not healthy, it needs to come with a cost like constantly ‘reconnect to lost drones’ causing a 60 second time out if constantly twigged.
Have you ever loaded a grid and then noticed the citadel suddenly do like a 180 change in orientation ?
Like the overview taking several seconds to re-sort?
That is assuming pushing d-scan is a request sent to the server, rather than polling the local client game state and simply collating objects based on the current destiny tick.
POS (the structures, not the code) and associated modules need to be removed from the market, its time enough already.
Its unconscionable how much EVE money has gone into non-eve endeavors over the years, the sooner echos, frontier and vanguard shuffle off their mortal coil the better.
Especially if its in python, if it were some legacy C object and a header file where the original .c was lost there would at least be half an argument.
Is it wrong to want the game to be better?
Fozziesov was supposed to spread conflict out and it has not, thusly its a game design issue.
There was a time every warp to a gate would fall 15 km short, there was an entire echosystem around selling region wide @0 bookmarks. The load on the server prompted a change to default warps to 0, negating the need to a bookmark. If making d-scan automatic results in the server being overloaded, then d-scan getting changed to a better overall system is not a bad thing.
The burning question is does spamming d-scan really do anything beyond the increments of the destiny tick? Is it just a placebo type effect for people who insist on pushing the button at the crosswalk when two people before them already pushed it?
Again, that is assuming d-scan is a separate call to the server, rather than a result determined by the local client state.
That then begs the question, the more ‘efficient’ system would be to poll the local client, but the more ‘representative’ choice is to poll the server.
Which best meets the expectations of the players? Even that question invites contention, depending on each perspective on which outcome is the priority?
