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.
 

CCP need to WAKE UP

Author
nikon56
UnSkilleD Inc.
#1 - 2013-06-26 13:09:36 UTC  |  Edited by: nikon56
Hello everyone,

i'm posting here because this game we all love, is clearly going down ATM, and CCP seems to ignore us.


here is a list of what need CCP's IMMEDIATE attention:

1- bugs need to be corrected

  • FIX THE COLORTAG / BACKGROUND ISSUE, this whole game is based on this, how is it possible this go to live server while it was reported during SISI test????
  • audio not working
  • random freeze / crash of the client (since week now, random freeze of 2-3 seconds happen)
  • launcher need to be removed
  • lag need to be fixed, it is not acceptable that a ship, locked and pointed by a hictor, is able to warp out, that we got rolled back etc... (


2- odyssey expansion "exploration" need to be removed and fixed

  • exploration overlay need to be fully deactivated when we set it to "off"
  • fix WH spawn rate, or is it normal that a C2 spawn only 1 sig every 5 days?
  • remove the cosmic signature from the overlay, showing them is NOT exploration
  • let us the ability to DISABLE FULLY the gate animation, it give ppl motion sickness, and is full of bugs (random color filled screen, next system has blank overview / brackets, stuck in the animation for several minutes (my own "record" is 5 so far))


3- admit your issues and compensate when it happen.

lost a ship due to your crazy gate animation, where i loaded the next grid in my ship, to see me rolled back in my pod.

petitioned it just to have the GM answering me that the log i provided were forged (seriously?)


now, one would argue that issues are related to my comp / internet connection (lags etc....)

so here it is:

i7 2600k 4.2 ghz / 16GB DDR3 / gtx670 / gtx 560ti( physx dedicated) / SSD (crucial M4 256MB)

internet connection: optical fiber 100Mb/s (see here for monitoring details: http://www.grenouille.com/... )

it is certainly not the most powerfull, but also FAR from being the worst, and i tested everything, fresh windows install, several drivers release, no antivirus / various antivirus, returned to stock value to ensure O/C is not to blame etc...

T° are all OK, rig is fully watercooled, highest temp while running eve on 2 account is around 50°C (almost never reached, unless a really hot day + playing both account in "interval one" (gas coud anyone?))
it is time for CCP to react, all this is reported since odyssey is on SISI, even more since it reached TQ, and some issues are known for way longer (2012), and the only reaction we have from CCP: they ignore those.

i guess it is more important to break the T1 transport ship right?
nikon56
UnSkilleD Inc.
#2 - 2013-07-01 13:06:05 UTC
bump
Rroff
Antagonistic Tendencies
#3 - 2013-07-01 15:36:06 UTC
I've multiple times typed out a long response to this but each time the more I typed the more I was questioning why I'm still playing this game which is quite depressing.
Aetourus
DEVGRU-M
#4 - 2013-07-22 05:34:44 UTC
Same here. I gave them evidence of a client crash and they claimed the logs could be forged. You can tell the GMs who handle tickets aren't developers themselves, because developers know that's a ridiculous excuse and total baloney. First, they could easily prevent people from tampering with the logs simply by storing their hash on the server. Any attempt to alter them would result in an incorrect hash. Second, items like the session ID are already formed in a non-deterministic way. That is, it's impossible to predict what the correct ID for a given session was, is, or will be. This is done specifically to prevent forgeries which could result in exploits.

I hate to say it, but I've seen this sort of thing before. The reason they want to *say* that people could doctor the logs (but don't want to fix it) is because it makes their job a lot easier. God forbid they should have to do their job and evaluate reimbursement requests on a case-by-case basis instead of just discarding them wholesale.
seth Hendar
I love you miners
#5 - 2013-07-22 08:44:29 UTC
Aetourus wrote:
Same here. I gave them evidence of a client crash and they claimed the logs could be forged. You can tell the GMs who handle tickets aren't developers themselves, because developers know that's a ridiculous excuse and total baloney. First, they could easily prevent people from tampering with the logs simply by storing their hash on the server. Any attempt to alter them would result in an incorrect hash. Second, items like the session ID are already formed in a non-deterministic way. That is, it's impossible to predict what the correct ID for a given session was, is, or will be. This is done specifically to prevent forgeries which could result in exploits.

I hate to say it, but I've seen this sort of thing before. The reason they want to *say* that people could doctor the logs (but don't want to fix it) is because it makes their job a lot easier. God forbid they should have to do their job and evaluate reimbursement requests on a case-by-case basis instead of just discarding them wholesale.

ho yes, i know too too well WHY they keep the logs this way, while it is fully possible (from a technical POV) to ensure players log can be read AND ensure they cannot be forged, there are many many ways, but they keep the current one.

the thing i like the most, is when you do a petition, without log, they ASK for them.

so you give the logs, just to see the GM tell you '"NO, our logs, still show nothing, and yours do, so they are forged".

keep doing this CCP, ignore the bugs, ignore the customers, this is the best way to manage this, really.....