These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Still major bugs in eve

Author
Elvis Preslie
NRDS Securities
Apocalypse Now.
#1 - 2013-03-25 05:14:24 UTC
Flying cheetah with inertia stab, mwd, covert cloak (covert ops lvl 4)

04:21:38 Generic Jumping from Auga to Kourmonen
04:20:57 Notify Covert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next Less than one second.
04:20:57 Notify Covert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next Less than one second.
04:20:56 Notify Covert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 1 second.
04:20:55 Notify Covert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 2 seconds.
04:20:54 Hint Limited 1MN Microwarpdrive I is already active
04:20:54 Notify Covert Ops Cloaking Device II fails to activate as it is still recovering from its last period of operation and will be for the next 3 seconds.
04:20:53 Notify Interference from the cloaking you are doing is preventing your systems from functioning at this time.
04:20:52 Notify Aligning to Kourmonen
04:20:40 Generic Jumping from Amamake to Auga

After jump from amamake to auga, the covert cloak was NOT activated again, it was attempting to be activated but always failed while the mwd worked unusually fine.

Sometime I think certain parts of systems are intentionally bugged to make people lose something, those that havent lost anything in forever, like how it uncloaks itself without a ship or object being around (hasnt happened to me in a long time though, way before retribution or inferno); everyone knows of the uncloak bug.

Then, when people lose things because of these bugs, we get responses like "unable to reproduce or unable to verify" and blamed is the machine the client is running on.

This machine does not crash or even disconnect (socket closed) like most others are having; the point where others see the "socket closed" message, my machine recovers from the glitch in the eve engine and continues on; i use longer than normal UDP/TCP timeouts along with checksums.

speaking of another recent bug, I have a huge feeling that the socket closed bug is coming from the patching, instead of fixing, the memory hole errors that i DID have long ago. I reported the memory hole in another bug report; its very few certain things that, when rendered, would cause eve to start eating memory slowly, until it got up to 16 GB of memory used (the max of the machine). it would then crash.

When this starts happening, you guys made eve refresh its memory commit its using INSTEAD of fixing the root cause that makes the hole. This is why my eve freezes after the memory hole has been triggered and other people's pc's timeout quicker when mine waits for new ACK from TCP.

The simple fact is the second I align, seeing as it takes more than three seconds to jump, I should be able to activate cloak with one Function key press instead of having to tap it two or more times. Your lead programmer resigned, whom caused the majority of bugs you guys did a good of fixing in retribution. WHY cant we get the rest of his screwups out of eve, like this problem of clients being non responsive between session changes.

During a session change, I should be able to keep typing to others without the window focus being changed to another window or inhibit me from doing tasks; you try typing this bug report while traveling.

I know bugs still exist in eve that I've reported a year ago, yet to be fixed, including the HUGE mining exploit.

STop adding stuff to eve before making sure you have a version of eve without ONE hitch in it. You've added dust and the patch in june is fine, while I hope it fixes some or all of what I said; however, after the june patch, you need to address every bug report in the system before moving on, especially the two issues i mentioned above.

Stop patching code; rework it to be more fluent for the cpu's. It only causes more unforseen bugs when you patch, the reason the programmer probably resigned, as he realized the mess he piled up on himself and caused you guys.

I KNOW this is how parts of eve are being written, as its evident not only playing eve but in the diagram for the old criminality system alone.

>MOST IMPORTANTLY< release a 64-bit version of exefile.exe which will help a lot in programming, preventing bugs, and increase client responsiveness. We're being limited to 3GB on 32-bit process when we have 16GB or so available.
seth Hendar
I love you miners
#2 - 2013-03-25 10:31:10 UTC  |  Edited by: seth Hendar
agreed on the bugs being present, also fix the latency issues.

a lot of bugs are related to latency issues on servers, like:

point not being effective
ship taking forever to warp even if aligned (more than 10 seconds this weekend for half a nano vagabond fleet!!!)
stop ship not always working (i.e. almost never working would be more realistic)
docking sometimes taking more than 5 seconds while at range
modules not activating
upon landing, you need 5+ seconds to initiate a lock, while in that time you are lockable (5 sec at least from the moment your ship resume displaying your speed instead of "warping") logi pilots love this so much!

now, as stated above, i can understand that some bugs are present, in such a complex game.

BUT, this does not excuse or shouldn't prevent you from making the appropriate moves to fix them, or at least stop saying that "all went normal" (while t is obvious it does NOT) to avoid refunding losses incured only to thoses bugs!!!!!!!

take your responsibilities, accept you have issues in that games, and act as grown up people, instead of closing your eyes and blaming your customers rig / connection or whatever.

when a fleet encounter the same bug, while half of them are in US and other are in EU, how can it be related to our RIG / ISP that we encounter the very same issue at the very same time?
Corp 5py
Doomheim
#3 - 2013-03-25 13:10:21 UTC  |  Edited by: Corp 5py
seth Hendar wrote:
agreed on the bugs being present, also fix the latency issues.


ship taking forever to warp even if aligned (more than 10 seconds this weekend for half a nano vagabond fleet!!!)


I had this too a few times, more specifically when flying deep plated armor ships.
I vividly remember a few times last week when the ship was aligned, initiating warp .. and at 85-90% max speed the ship still wasn't warping ... lag maybe ?
seth Hendar
I love you miners
#4 - 2013-03-25 14:16:42 UTC
Corp 5py wrote:
seth Hendar wrote:
agreed on the bugs being present, also fix the latency issues.


ship taking forever to warp even if aligned (more than 10 seconds this weekend for half a nano vagabond fleet!!!)


I had this too a few times, more specifically when flying deep plated armor ships.
I vividly remember a few times last week when the ship was aligned, initiating warp .. and at 85-90% max speed the ship still wasn't warping ... lag maybe ?

it also happen with various ships, i encountered it on large scale this weekend on a nano vaga fleet, all were aligned (long time aligned, like 15 sec+), warped squad, only half entered warp, other complained they were "stuck" in "warping", +-5sec later they all entered warp.

all thoses issues started with last summer update, got worse with winter update, and even worse when dusties joined us.

clearly, the server is not following, plus we encounter those issues far less often during non-pick hours(I.E. non-US TZ), so clearly it IS related to server load.

bad code optimisation + limited server power == bad issues in pvp where decision are to be made on a split-second.

there is not a single PVP related activity in EVE we run at our alliance (400+ ppl) where we do not encounter thoses bugs (props to the 5 sec delay, this one happen 100%, very usefull when landing on gate on an ennemy fleet and ou are just sitting ducks for 5 long seconds, in a 20+ fight on each side, no logi and no firepower means the landing fleet is dead before even logi can establish or lock anyone)
seth Hendar
I love you miners
#5 - 2013-03-27 09:12:10 UTC
bump