Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Caya
|
Posted - 2004.06.08 14:19:00 -
[1]
Well its not so new, but i have no more patience with is. The bug looks like this. I still should have more than 15% cap, but the system thinks i have not. Modules wont work, cause i dont have enough energy. I can never know when thsi happens till it happens. I bet u can imagine the situation when this means death to your ship. And im sure i wont get it back by petition. Any1 recorded this bug too? Any1 is already working on it?
|
Arbenowskee
|
Posted - 2004.06.08 14:48:00 -
[2]
Yes i had problems with it to. Sometimes it sais i have no cap, but when i warp or use a module, my cap is full... or even worse, i think my cap is full and try to do something and i get msg: not enough cap. verry annoying i must say.
|
Imhotep Khem
|
Posted - 2004.06.10 15:16:00 -
[3]
Sounds like poor coherency architecture between client and server. Allowing lag to cause display poor data. It would be better to simply show an icon to indicate your display has not been updated so the user can do his own assumption about what the current value probably is. As opposed to some inaccurate client side prediction.
I doubt this or any of its variations will be fixed anytime soon. But the new servers should mitigate it on avarage. If you get into a big battle though you could see it return... Just my guess. ____ If your not dyin' your not tryin'. |
lickspittle
|
Posted - 2004.06.11 07:48:00 -
[4]
Never heard of it until now. Any idea how to reproduce it? -- Richard CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Sokra
|
Posted - 2004.06.11 11:06:00 -
[5]
Edited by: Sokra on 11/06/2004 11:09:01 It happens to me quite often, if I¦m locking something and it gets bugged my locking timer counts from 75secs down, after that you slowly get back to the original time but still see ships and stuff which is already destroyed and not there. It can¦t be reproduced it just happens from time to time. After that it¦s bugged the cap doesn¦t update so you have cap when it shows it¦s empty and suddenly when it¦s empty it shows it¦s full on the display
|
Hellek
|
Posted - 2004.06.11 11:51:00 -
[6]
I also had it once that my cap suddenly went to 100.0% while I was in space (and had activated moduels before, so it was simply impossible to have so much cap, still I did), was very, very weird. I noticed that only very few times in about a year of playing eve, I fear it will be very hard to reproduce (I have no clue how to do it).
|
Mikelangelo
|
Posted - 2004.06.11 12:09:00 -
[7]
Yeah I had that happen to me.
Let's say you MWD to dock to a station, and you are at 1/3rd cap. You dock to the station, mess around for a while, go afk for 10 minutes, then you come out, and the cap shows full.
When ya try to activate the MWD, it says not enough cap (even though even if you were at a third cap you could still do it).
Weird bug.
|
Grimpak
|
Posted - 2004.06.11 13:30:00 -
[8]
Originally by: lickspittle Never heard of it until now. Any idea how to reproduce it?
hmm... dunno if it's the same, but when I undock after fit a mwd (more specificaly, it happened when undocked a BB and just finished to fit a 10mn mwd), and if I activate it for a single burn, the cap goes down to arround 20/30% (kinda impossible for even a single burn from a 10mn mwd), or if I warp out, the same happens, even if it's only a 5AU jump. -------------------
Quote: Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
flummox
|
Posted - 2004.06.11 13:58:00 -
[9]
yes, i have had this happen as well just 3 days ago... brand new Armageddon, 100mn MWD, undock, warp to stargate (only a few AU's away, say 8 AU), come out of warp, activate MWD and immediately my cap was at 18%.
further testing shows that 82% cap is not used to activate the MWD (duh!). and, i have warped much farther AU's and not had this happen to my caps...
hope this helps a little...
flummox
there is a fine, but dissasterous line between a fart and a shart. i suggest you make sure which side you want to be on... |
Cherok
|
Posted - 2004.06.11 18:01:00 -
[10]
I too have had this happen. I will be hunting rats and when I go to dock in my APOC, I will have 0 shields (armor tanked) and say about 30% cap (I use lasers, I suck). I will undock a couple minutes later and I still have no shields and my cap is still at 33%. As soon as I activate anything, my cap will jump to 100% like it should have been all along. My shields will still be regenerating from 0%. As soon as I take any damage, my shields go to 100%. I have also had my cap be at 100% when I undock and as soon as I start firing or using cap, it drops to like 60% or something like it did not regenerate when I was docked.
Weird.
|
|
Lansfear
|
Posted - 2004.06.11 20:06:00 -
[11]
This bug seems to come and go.
I lost my first three cruisers to it after release.
Theres no real way to reproduce it, it just happens. Activating a module would all of a sudden suck out 60% cap per cycle. Leaves you completely helpless. Ive petitioned this bug three times and the devs have never heard of it.
Thats scarey, what the hell do you all do with our petitions?
|
Tease
|
Posted - 2004.06.11 20:30:00 -
[12]
Originally by: Lansfear This bug seems to come and go.
I lost my first three cruisers to it after release.
Theres no real way to reproduce it, it just happens. Activating a module would all of a sudden suck out 60% cap per cycle. Leaves you completely helpless. Ive petitioned this bug three times and the devs have never heard of it.
Thats scarey, what the hell do you all do with our petitions?
happens to me randomly as well, the only way I know for sure to reproduce it is to dock with a BS or cruiser(or some other large-cap ship) switch to a shuttle, launch and try to warp somewhere in the system. Can't go more than a few AU due to a full cap charge suddenly becoming less than 3%
I've also sent bug petitions about this and never heard anything back. And this is the umpteenth time the players have been told that the devs know nothing about a bug tons of us have petitioned.
----------------------------------------- [2003.12.17 06:35:20] Corwin > Orvolle is .4? Doesn't that mean that it's less than .5 ? and isn't .5 what starts the danger level? [2003.12.30 07:15:50] Corwin > Tech 2, IE expanded cargo holds I, MIning lasers 2, etc.... TL2 is being released all around you [2003.12.30 07:21:20] Corwin > tech 2 is released to players. Some players are busy researching the BPs before building stuff. Others are sitting on the BPs making copies to make money off of them that way |
teh pR3acH3r
|
Posted - 2004.06.11 20:52:00 -
[13]
I posted a detailed thread about this bug about a month or 2 ago and didnt seem to get much of a response.
Since it happens to me quite frequently, here's what I've been able to come up with:
It does in fact seem to be a random occurance. Sometimes happening for a few days in a row then just magically dissapearing or a while.
I do believe it to be a connection problem with client / server because one of the first signs of the bug is "rubber-band" lag. Where it shows you warping away or coming out of warp, 2 or 3 times in one instance.
Not only does it affect the graphics display of the amount of capacitor you have, but also the graphics display of your shield hp. You know this when it is too late, because it may appear you have 90%+ shields but as soon as you get shot, you see your armor tearing away.
It also causes game crashes/lock ups. As your time logged in progresses (assuming you do have the bug) the severity of the bug increases. Soon it will appear that you are using 0% cap (graphically) to warp across an entire system that is actually using all of your cap. Soon after that there are a few different things that will happen:
1. If you are in space and active in combat: Your screen will start shaking violently and you will be unable to take any action in the game and must exit the game.
2. If you are in space warping: It will appear that you have been stuck in warp and the game will again be unresponsive and you must relog.
3. If you are in a station: The game will either goto a black screen or a grey screen and will again be unresponsive, and you again must relog. _________________________________ Indefinately MIA Former CEO Occassus Republica - Military Division Leader Founding members of the Venal Alliance You'll Find Religion When I Find You |
ZeroMinus
|
Posted - 2004.06.11 21:38:00 -
[14]
I have the same Issues as Preach... At first I though it was related to MWDs, but then it started happening on ship stacking CPRs. My final conclusion is that this is just random. I can play a week without the bug then suddenly it reappears. I will have to write a macro soon considering I must relog every hour due to one of the follow reasons:
- Cap shows more cap than present (modules turn off & i become sitting duck) - Shields show 25-45% yet there is no shields (all dmg is done to armor) - Cap image error (Cap recharges by taking cap away) - Docked then Grey or Black Screen just appears (Time to Relog) - Docked and suddenly game stops doing anything (can't chat, just watch ship orbit - Time to relog) - Channel Stops Sending Messages (Click the Channel Title and keep hitting Enter) - Warping then game Stops (Time to Relog) - Undocking and the grey screen (No space just grey, Time to Relog) - Screen Shakes (Screen suddenly starts shaking, Time to Relog) - Sometimes After awhile of dealing with cap bug the modules start to lag by 5-10secs (Time to Relog)
That is about all that I can remember at this time. But I can assure everyone I am very unhappy about CCP lacking the motivation to even respond to Petitions. I almost feel that they have purposely ignored this error. And yes Everyone knows, "Clear your Cache". ---------------------------------------------- -= Proud Member of Phoenix Alliance =- |
teh pR3acH3r
|
Posted - 2004.06.11 22:33:00 -
[15]
How Ironic, I just login and guess what....cap bug.
Guess I'll be sitting in a station all day, relogging every 15 minutes. _________________________________ Indefinately MIA Former CEO Occassus Republica - Military Division Leader Founding members of the Venal Alliance You'll Find Religion When I Find You |
Torment
|
Posted - 2004.06.11 23:22:00 -
[16]
Very easy to replicate:Assemble new ship,undock,warp to anywhere or activate module=0 or 5% cap display....i have this everytime i undock in a new assembled ship on chaos and try to warp somewhere
|
Lansfear
|
Posted - 2004.06.12 02:45:00 -
[17]
Originally by: Torment Very easy to replicate:Assemble new ship,undock,warp to anywhere or activate module=0 or 5% cap display....i have this everytime i undock in a new assembled ship on chaos and try to warp somewhere
This is only one of the ways it can hit. Pre-castor, i lost a thorax from the cap bug hitting me three hours *after* i started the chain.
Second time it hit when i was fighting a PC rate in Syndicate and when i hit my shield booster cap hit 10% from about 80%.
Third time was when i was mining and defending with just drones (precastor) and have my shield booster sucked up too much cap again.
Docking or relogging seemed the only way to fix it.
Comes and goes as it pleases.
|
Tigersbane
|
Posted - 2004.06.12 08:42:00 -
[18]
I am going to relate my experience of this bug here as well.
In ALL my cases of this, it has happened during/after instances of severe lag. The symptoms are pretty much the same as everyone else in the thread. When I say lag, I mean connection lag not graphics lag.
My guess is that the server and client become out of synch and the client displays the incorrect figure.
I do not see that much can be done about the problem apart from improving the communication code for the client/server, however I would summise that this is pretty good at the moment.
|
lickspittle
|
Posted - 2004.06.12 09:19:00 -
[19]
Thanks for the information those that have posted above. With the given information, ignoring the other unrelated problems which people have attached on to their reports, its possible that the capacitor/shield sync bug is fixed in the upcoming patch.
I spent some time tracking this down after receiving a good reproducibility case a couple of weeks back and the given case was fixed. In fact there have been a range of fixes to this code.
Please keep an eye out after the upcoming patch and let me know if it still happens then.
-- Richard CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Tigersbane
|
Posted - 2004.06.12 22:14:00 -
[20]
Lickspittle, any chance of you voicing what you found the problem to actually be in the case you were able to reproduce?
|
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |