Pages: [1] 2 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Okura's
interimo
|
Posted - 2008.07.13 14:08:00 -
[1]
Allright, I have reported this bug already, but somehow I'm not getting what I want: a reimbursment.
So Here is what happens:
For any level 5 mission, you need logistics support. I use a Dominix as tank, and a Ravenw ith 4 remote reps as logistics. It works just fine. I tank all missions easily, as long as i put on racial hardeners.
Now I warped into another mission a while ago, and after agro i warped in the Raven. Then this happens:
13:53:30 Notify Your attempt to target Dominix failed.
I tried locking the Dominix several times, but each time i try to lock it, above message appears at the end of the lock cycle. Its extremely annoying, and so far it has costed me 2 Dominix's. Why? a level 5 mission does 2000-3000 dps, so without logistics the armor goes down like soft butter.
Now i have petioned both losses, and the respons to the first one was as usual:
Hi,
Thank you for contacting customer support.
We are sorry to hear about your ship loss. Unfortunately we are unable to reimburse the ship as our server-side logs do not indicate that a bug/error within the game or a server related problem was the reason for your loss.
Our reimbursement policies are very strict and we can only reimburse if we are able to verify that a bug or server error caused the loss. We hope that you understand our position and that you will recover swiftly from the loss.
Best Regards, GM Mario The EVE Online Customer Support Team
After writing down the whole story again, he answered the following:
Hi,
You may have been caught in a laggy situation which caused the failure of targeting, however, it is true that we can't find any server related issues surrounding the time you lost your ship, which keeps our hands tied with regards to reimbursement. Please refer to our reimbursement policy page for more information:
URL: http://www.eve-online.com/pnp/reimbursment.asp Our apologies for any inconvenience you may have suffered because of this.
Best Regards, GM Mario The EVE Online Customer Support Team
Now, dear GM's, can you please confirm above situation as a bug, and reimburs my two ships!
Greetings,
Okura's
|
Lubomir Penev
interimo
|
Posted - 2008.07.13 14:23:00 -
[2]
10/10. CCP deserves it for forbidding discussing its abysmal customer service. -- Coming to you, Assault Ships fix, by the people saying that the Gallente Recons are fine. |
Khlitouris RegusII
|
Posted - 2008.07.13 19:30:00 -
[3]
I get this all the time in missions pvp etc its a right pain in the arse.
|
Arous Drephius
Alpha Research Group
|
Posted - 2008.07.13 21:00:00 -
[4]
In before mods nerf those GM quotes.
|
Whype
|
Posted - 2008.07.13 21:04:00 -
[5]
huh? did he relay say this? |
ZephyrLexx
|
Posted - 2008.07.13 21:15:00 -
[6]
isn't this just lag? I get it all the time doing various things, try to open the wreck? window opens then closes...
|
Lubomir Penev
interimo
|
Posted - 2008.07.13 23:07:00 -
[7]
Originally by: Arous Drephius In before mods nerf those GM quotes.
Read better it's not quotation, as forum rules forbid a plain cut and paste you have to get creative -- Coming to you, Assault Ships fix, by the people saying that the Gallente Recons are fine. |
Falkrich Swifthand
Caldari eNinjas Incorporated
|
Posted - 2008.07.14 07:50:00 -
[8]
Perhaps you failed to target because your target died?
nullnull
My sig is not my sig. |
Krollin
Minmatar Ki Shoda United Corporations Against Macros
|
Posted - 2008.07.14 12:16:00 -
[9]
Hi,
Firstly, your post made me spit coffee all over my keyboard, brilliant post.
Second, In before the lock and edit!
Third, I too have had a similair problem, I even warped out of a mission went to a gate and then was presented with the message that normally appears when I warp into the mission!!!
Ofc these are all lag related issues, but sadly when doing a Level 5 mission and loosing ships it is not really the answer you want to hear. That said I can also see CCP's side when it comes to these things.
At the very least they should see you lost 2 ships in close succession, which should indicate some form of issue, especially as those ships would have been lost to a mission rat or 20....
I feel for your losses, lets just hope CCP do something nice for you...fingers crossed.
Kro
|
Lubomir Penev
interimo
|
Posted - 2008.07.14 15:09:00 -
[10]
Originally by: Falkrich Swifthand Perhaps you failed to target because your target died?
You get a "You failed to target nothing" message in those case IIRC... I had that issue both in mission and in PvP myself, what is a bit astonishing is that it would leave no traces whatsoever server side, if EVE is a dumb client as claimed.
Or logs just don't exist.
-- Coming to you, Assault Ships fix, by the people saying that the Gallente Recons are fine. |
|
Caius Sivaris
Dark Nexxus
|
Posted - 2008.07.14 15:27:00 -
[11]
Originally by: ZephyrLexx isn't this just lag? I get it all the time doing various things, try to open the wreck? window opens then closes...
I doubt it's lag...
Here's an example, I was trying to lock a Rifter. No visible lag. At one point I even lock a wreck to check and it works instantly... Had the victim not been scrambled. Interestingly enough I eventually got the lock right after reloading. 2 minutes to lock while at same time modules activated and anyway I was able to lock that wreck without issue. The game just not let me target what I wanted to target, while otherwise working. There is definitely some bug linked to targeting, and worse, the kind that leaves no traces on the server (do any bug leave traces actually?)
[ 2008.05.15 19:55:01 ] (notify) Your attempt to target Rifter failed. snipping a few of those, 40 seconds worth [ 2008.05.15 19:55:41 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:55:45 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:55:47 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:55:51 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:55:55 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:55:57 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:02 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:05 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:09 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:13 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:17 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:19 ] (notify) You have started trying to warp scramble Serpentis Chief Patroller Wreck [SEYC](Serpentis Medium Wreck). [ 2008.05.15 19:56:21 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:25 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:29 ] (notify) Warp Disruptor II deactivates because its target, Serpentis Chief Patroller Wreck, is not locked. [ 2008.05.15 19:56:29 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:34 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:40 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:42 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:46 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:48 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:51 ] (notify) Loading the Ammo into the Projectile Weapon; this will take approximately 10 seconds. [ 2008.05.15 19:56:51 ] (notify) Loading the Ammo into the Projectile Weapon; this will take approximately 10 seconds. [ 2008.05.15 19:56:51 ] (notify) Loading the Ammo into the Projectile Weapon; this will take approximately 10 seconds. [ 2008.05.15 19:56:52 ] (notify) Loading the Ammo into the Projectile Weapon; this will take approximately 10 seconds. [ 2008.05.15 19:56:52 ] (notify) Your attempt to target Rifter failed. [ 2008.05.15 19:56:52 ] (notify) Loading the Ammo into the Projectile Weapon; this will take approximately 10 seconds. [ 2008.05.15 19:57:00 ] (question) This action is an attack on your target. Attacking this target is a crime, will result in a security status penalty for you and will bring CONCORD to enforce the law by destroying your ship.<br><br>Do you wish to proceed with this dangerous action? [ 2008.05.15 19:57:03 ] (notify) For initiating combat your security status has been adjusted by -0.1000. [ 2008.05.15 19:57:03 ] (combat) Your 720mm Howitzer Artillery II barely misses PoorVictim
|
Okura's
interimo
|
Posted - 2008.07.21 15:07:00 -
[12]
anyone else having this problem? Please post if you do!
|
Rooker
Lysian Enterprises
|
Posted - 2008.07.21 20:23:00 -
[13]
FYI
-- Let Us Avoid Systems Via Autopilot |
Siona Windweaver
|
Posted - 2008.07.22 12:58:00 -
[14]
Edited by: Siona Windweaver on 22/07/2008 12:59:14 I also get this problem from time to time, its quite annoying. No visible lag whatsoever was present.
[ 2008.07.16 13:25:52 ] (notify) Interference from the warp you are doing is preventing your sensors from getting a target lock on Ishkur. [ 2008.07.16 13:25:52 ] (notify) You cannot do that while warping. [ 2008.07.16 13:25:53 ] (notify) Interference from the warp you are doing is preventing your sensors from getting a target lock on Ishkur. [ 2008.07.16 13:25:54 ] (notify) You cannot do that while warping. [ 2008.07.16 13:26:05 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:15 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:15 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:22 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:24 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:29 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:32 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:41 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:43 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:52 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:53 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:26:58 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:00 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:04 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:06 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:09 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:12 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:25 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:31 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:32 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:36 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:38 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:42 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:27:56 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:02 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:07 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:14 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:14 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:31 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:31 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:39 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:39 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:42 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:45 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:48 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:52 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:28:59 ] (notify) Your attempt to target Ishkur failed. [ 2008.07.16 13:29:04 ] (notify) Your attempt to target Ishkur failed.
After 5 minutes, i locked on ishkur and killed him, but he also killed 2 of my corp mates. I didnt petitioned it of course, i knew GMs were busy touching themselves, it would be rude to interrupt them.
|
Okura's
interimo
|
Posted - 2008.07.27 12:31:00 -
[15]
anyone else? I need more examples to back up my petition.
|
Serret Nevets
The Hull Miners Union The Red Skull
|
Posted - 2008.07.27 14:56:00 -
[16]
this is a fairly common problem in pvp too. the difference is, you loose your ship faster with blob warfare. Also, I doubt CCP will listen to this because they're more interested in nerfing speed.
Carebear at heart, but peer pressure gets the better of me. |
Okura's
interimo
|
Posted - 2008.07.28 10:03:00 -
[17]
After escelating my petition i again have had a negative respons. Keeps telling me that the logs dont show naything etc.
Now i have to file a bug report, but offcourse the problem is that to file one, I first need to get the bug again with the bug-report-tool running. Getting the bug again would mean losing another domi, and I'm not really up for that...
|
RaTTuS
BIG Libertas Fidelitas
|
Posted - 2008.07.28 10:05:00 -
[18]
run it all the time while doing these missions as soon as it starts you know you should be warping out ... ^ best I can offer
-- BIG Lottery, BIG Deal, InEve
|
clyno
|
Posted - 2008.07.28 11:14:00 -
[19]
Lag and desync... Coupled with CCPs logs that "show no error or issue". Happens in pve, pvp, or when traveling through system with 12 pilots all docked in station.
Many have tried to petition this... would be nice to say "few succeeded" but I haven't heard of the case where this would be true. GL with your petition.
Maybe CCP should start thinking of a way to log lag and desync issues. It still wouldn't solve them, but at least it would give them an idea of how crappy this game can get from time to time.
|
Okura's
interimo
|
Posted - 2008.08.01 23:01:00 -
[20]
first time in pvp:
22:56:27 Notify Your attempt to target Phobos failed. ------many more of these same errors----- 22:57:49 Notify Your attempt to target Phobos failed.
and then he got away moments after
ARGHHH...CCP FIX THIS!
|
|
Pavlinka
Minmatar
|
Posted - 2008.08.02 19:30:00 -
[21]
Edited by: Pavlinka on 02/08/2008 19:30:57 Edited by: Pavlinka on 02/08/2008 19:30:36
Originally by: Okura's Edited by: Okura''s on 13/07/2008 14:18:17 ... we dont want you in this game anymore.
Best Regards, GM LickmahDonges The EVE Online Customer Support Team
... must add this to my sig
Quote: ...we dont want you in this game anymore.
Best Regards, GM ... The EVE Online Customer Support Team
|
Okura's
interimo
|
Posted - 2008.08.02 23:25:00 -
[22]
I have managed to reproduce the bug with the Eve bug tool running, so now I have evidence. Lets hope its gonna help them to get this retarted bug out of the system.
|
Gark32
Suddenly Ninjas
|
Posted - 2008.08.02 23:29:00 -
[23]
i've had this happen also, generally as i was attempting to get a suicide gank. if i turn on my cargo scanner before i try to target, the lock fails. every time. if i don't have the scanner flashing, i can lock. every time. after watching 20 haulers go by unlocked, i figured out what was going on and adapted accordingly; this does not mean, however, that all's right with the world. this needs to be fixed. ________________________________________________
|
Okura's
interimo
|
Posted - 2008.08.02 23:55:00 -
[24]
Because having flashy nmods to get high alpha is a feature of this game, and it should work
|
Elle D
The Taco Stand
|
Posted - 2008.08.03 00:47:00 -
[25]
Originally by: Gark32 i've had this happen also, generally as i was attempting to get a suicide gank. if i turn on my cargo scanner before i try to target, the lock fails. every time. if i don't have the scanner flashing, i can lock. every time. after watching 20 haulers go by unlocked, i figured out what was going on and adapted accordingly; this does not mean, however, that all's right with the world. this needs to be fixed.
this.
|
Mythrell
Omega Enterprises Mostly Harmless
|
Posted - 2008.08.03 10:47:00 -
[26]
It's normal EVE lag, get used to it. I'd recommend that you save your domis and do lvl4's because apparently your domi isn't well enough tanked to handle lvl5's (lag is part of the game, and if that makes you die it means your tank isn't good enough).
Dev's can't do jack about it in short time and over a long time all the lag reducing fixes they make gets eaten by increased player base.
Here's a little vid I made last december after the nodes went down, sure it's pvp but in second scene you can see me trying to lock a ship for some time and failing to do that in time to get into a kill mail. I didn't petition it tho :( . first and last scene are 2x speed and second is 4x or even 6x, can't really remember. I bet the other guys didn't get reimbursed either, I mean the whole node went down so there's nothing on the logs, rite?
http://dl.eve-files.com/media/0708/lagfest_low.wmv
|
Andrea Skye
Caldari The Python Cartel
|
Posted - 2008.08.03 15:28:00 -
[27]
Edited by: Andrea Skye on 03/08/2008 15:28:53 Theres something you can do about it.
1. First time it fails, DONT PRESS ANYTHING ELSE.
2. Now click target again, and you should get "fail" again, now dont do anything else...
3. Now just sit and wait, dont press anything at all. And eventualy it should target, even tho its not saying its targeting, it only takes a few seconds.
If you spam the button it refreshes the command to target, so all your ever doing is targetting. Or something like that.
Anyway, it works for me, lost a few ships in PvP due to this bug, but hey, they wasnt really that expensive, just annoying.
|
Phlegia
|
Posted - 2008.08.03 15:41:00 -
[28]
Just an idea: Can it be possible, that you were not able to lock, because the ship was out of range because of desync? I donŠt think that you would get an imbursement, but you should file a bugreport in any case. |
Suitonia
Gallente interimo
|
Posted - 2008.10.07 06:42:00 -
[29]
Bumping this because I just got this in PvP which caused me to miss out on a kill.
[ 2008.10.07 06:27:52 ] (notify) Warping to Zoohen IV - Asteroid Belt 1 [ 2008.10.07 06:28:32 ] (notify) Interference from the warp you are doing is preventing your sensors from getting a target lock on Burp. [ 2008.10.07 06:28:38 ] (notify) Your attempt to target Tristan failed. [ 2008.10.07 06:28:43 ] (notify) Your attempt to target Tristan failed. [ 2008.10.07 06:28:43 ] (notify) Your attempt to target Tristan failed. [ 2008.10.07 06:28:49 ] (notify) Your attempt to target Tristan failed. [ 2008.10.07 06:28:51 ] (notify) You have started trying to warp scramble Blood Collector Wreck [T W T]. [ 2008.10.07 06:28:52 ] (notify) Your attempt to target Tristan failed. [ 2008.10.07 06:28:53 ] (notify) Interference from the warp Burp is preventing your sensors from getting a target lock on them.
I warped in, target was invincible. I managed to lock and scram wreck to prove that my ship was somehow not at fault. God help someone if they actually get this bug when someone is actually shooting them.
|
Andrue
Amarr
|
Posted - 2008.10.07 10:18:00 -
[30]
Originally by: Okura's Edited by: Okura''s on 13/07/2008 14:21:23..snip..
It's funny but probably doesn't help us. People are generally more inclined to help out when you are polite and forgiving. Your attempt at humour risks appearing to the GMs and Devs as being rude and childish. -- (Sarcastic mission running veteran, 4+ years)
[Brackley, UK]
My budgie can say "ploppy bottom". You have been warned. |
|
|
|
|
Pages: [1] 2 :: one page |
First page | Previous page | Next page | Last page |