| Pages: [1] 2 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
SKiNNiEH
   |
Posted - 2003.11.09 22:08:00 -
[1]
Okay, this is becoming really irritating.
I traveled 40+ jumps out into 0.0 space yesterday with a new setup that i've tested on a roid in Empire space. I normally cap test my laser setup with everything online to see how my cap will level off.
Now, when i was cap testing in Yulai my cap leveled off at about 10%.. not a lot, but with 5 L lasers, 2 M lasers, one XL booster, a Hardener and an extruded (the rest being cap recharge bonus modules). So off i went to my favourite farming ground, which is very deep into 0.0 space and takes me a long time to get there.
This morning i started my first farming activities, with cap dropping to 0% continously (not like it happened in Yulai). So i logged for the rest of the day and got back just now to do a little more farming. To my surprise, the cap didnt seem to want to drop below 90% with everything online! so i happily farmed away while chatting in a few channels. After a while i check my shields, to see my armor was at 70% hp. "Strange, XL Booster offline?".
(Modules on autorepeat tend to go offline after a while, so i turned it back online)
I shot some more, talked some more on a few channels .. check again "What? Offline again?". Cap was still around 95%, guns happily blazing away. Now i paid full attention to my booster and presto, offline in like 2 minutes. I try to turn it back on and i get the message:
"You do not have the required power"
Hmm... cap at 91%, i dont have power?!?.. Anyways, armor was at 60% so i warped away, logged off (****ed) and started to write this topic.
This new setup clearly eats too much cap that i know now, but if the information was correct on my screen i wouldnt have armor damage at this very moment! 40+ jumps from the nearest station with no fixing capabilities closeby.
Also, with my old setup.. i've found cap information unreliable aswell. I never had cap problems then, but i've seen it at 10% and also at 70% its just completely different at certain times of the day (probably because of server-side lag/load problems, e.g. quiet or busy on tranquility).
Your life depends on the amount of cap. Basically, the whole game revolves around the cap hp and the modules you can power with it.
Lots of people (miners, campers**) dont have this issue, because they dont rely on continuously shooting something. Farming npc's demands a lot of the cap recharge, especially when the spawn is speeding up.
(** miners occasionally shoot npc's entering the belt and campers occasionally shoot a player entering the gate area)
The reliability issues i (and probably more people) have with the cap should be high in the priority list of bug fixes.
Okay, got this off my chest.. interesting to see if and how this problem will be fixed. Thanks for your time.
Regards,
SKiNNiEH / SKiNNiEH's Wife and Lord Winzip.
(signed by all my alts:)
-------
|
Ris Dnalor
|
Posted - 2003.11.09 22:37:00 -
[2]
hello,
I was in the same system as skinnieh, at the same time, also having problems with my capacitor readout. the difference for me was that i had been out there for several days straight having no problems with my cap readout. nothing changed on my loadout as i haven't docked during that time.
My cap would drain would show about 25%-30% remaining according to the picture graph & numbers but i would get a message about not enough cap remaining & weapons would begin to shutdown.
i had this problem in the early days of eve but have not had this problem for months. Hope this added info is helpful to someone.
thanx
Ris Dnalor
--
Jump Drive Operation / Rank 5 / SP: 1280000 of 1280000
|
Toramii
|
Posted - 2003.11.10 00:43:00 -
[3]
Had a problem with 4 afterburners on my indy today consuming far more than specified 14 capacitor energy per activation.
I dont think the problem is necessarily solarsystem dependent, but can appear / disappear when you undock or jump. For instance I was travelling though New Caldari today, entered system - activated afterburners, cap ok, then I docked / undocked and warped to jumpgate, activated afterburners to jumpgate, afterburners consumed around 4x as much cap as normal. I passed back though New Caldari a little later with no problems.
There appears to be some variable affected when the client/server loads a new scene.
|
Athan
|
Posted - 2003.11.10 05:09:00 -
[4]
Myself and a team mate had the "cap eaten way too quickly on the UI" problem a few nights back in MN5N-X. Docking, switchin ship, switching back, undocking didn't fix it. The problem was also there in D-Q40X, but thankfully was gone by the time we got to the system we have some handy GSC setup in for loot.
In this case the cap would *visually* run out completely after ~3 mins. Yet I *know* I can run that module (MWD) 'forever' on that setup, tested many times by using it for 10-15 mins straight when AFK (figuring if I'm moving at 1.4km/s I'm going to be hard to catch at all).
This lends some support to this being at least in part a *SERVER* side problem. I'm wondering if overloaded SOL servers can exhibit it.
So Case 1) Cap appears to drain way too fast, so fast that you'd run out way before the length of time you KNOW you can run for on the setup.
Case 2) Cap appears to be fine but all of a sudden you run into "not enough energy to activate module" messages and have to panic and run if in combat.
Possible case 3) The cap visually draining incredibly slowly. Probably an extreme case of #2.
Either way there seems to be some serious client/server synchronisation problems to do with cap use/display.
-Ath
--
http://big.wayland.dk/Lottery.asp - The BIG Lottery |
Elissen
|
Posted - 2003.11.10 09:13:00 -
[5]
I also had the same problems a couple of times last weekend. Cap drained way too fast. Only way to fix is was to log out and wait until your ship disappears (I was in a system without a station).
But there are more serious synchronisation issues. When I was mining my indy alt (second account) was approaching a gate when a couple of rats attacked her. I knew a corpmate was 1 or 2 jumps behind her, so I warped her to a planet.
Strange thing was she was still taking damage while going 2 au/s
Got screenies of that tough
|
Ravenal
|
Posted - 2003.11.10 14:53:00 -
[6]
uhm, how come you can go "away" from you farming ship to chat and stuff?
you dont use autoattacking macros do you?
cause you know...they are illegal 
- i play the game...how about you?
...new sig coming up
Ravenal - Fate is what you make of it. |
Terghon
|
Posted - 2003.11.10 18:49:00 -
[7]
I started having this problem yesterday (Sunday, 9 November) for the first time. Was something changed server-side perhaps? This really is a critical bug for anyone engaged in combat.
|
SKiNNiEH
|
Posted - 2003.11.11 07:14:00 -
[8]
When i got back online in EVE, my cap was still bugged. I think the only way to resolve this is to warp all the way back to the nearest station, unequip my modules and re-equip 'em.
What a waste of time.
-------
|
lickspittle
|
Posted - 2003.11.11 09:24:00 -
[9]
I've only received one usable report of this bug and what the log that came with it indicated was that the player's client's time was around two minutes ahead of the time on the server.
This is why the capacitor seems to show a higher level of charge - it thinks its had however much the time is out of sync as extra recharge time.
Someone else also mentioned that their friend was getting damaged at 2AU, this can also be explained by time sync problems. The warp is simulated on the client according to the times the server gives it, if the client is ahead timewise, then the warp will appear to have engaged when it really hasn't.
Needless to say, this should not be happening and the capacitor sync problems that have been in the past were unrelated having happened with correct time synchronisation.
Can anyone think of anything they are running on their system that might cause the client to fall out of sync with the server?
If anyone who uses the test server manages to reproduce it there, or knows someone who has reproduced it there, a log file from when it happened would be immensely helpful. If you have log files of this happening on TQ, they aren't as helpful due to the limited state change logging we do there, but I'd still appreciate getting them. You can send them to [email protected]
-- Richard
CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Elissen
|
Posted - 2003.11.11 09:40:00 -
[10]
It was my second account that was taking the damage at 2 au/s.
Time differences may occour due to the automatic time synchronisation of Windows XP (my system is set to sync with my server that syncs with the NTP-server of my ISP). But that doesn't explain the syncproblems I've seen between 2 clients that run on the same PC.
I can try to get a log together this week, but I have one question. I'm almost always running 2 accounts on the same PC so synchronisationproblems are always easy for me to spot. Is there a way to use the logserver on a specific client? The only thing I can do at this time is log the last client I start.
|
PropanElgen
|
Posted - 2003.11.11 10:10:00 -
[11]
I'm having this on my 2nd account that I use for hauling (4 AB's using about 4 times more cap than they normally do).
The way I use to fix this is dock at nearest station, Quit game, clear cache.
It then works fine for some hours, after which the problem reappears.
Quite annoying..
All the angels and the puny men of god looked away...
Frightened to death by the evil that was born on that day!
|
SKiNNiEH
|
Posted - 2003.11.11 10:30:00 -
[12]
Edited by: SKiNNiEH on 11/11/2003 12:35:07
It all started to go wrong when i cleared my cache after it got broken last friday. I cleared the entire directory and only kept my prefs.ini. I think the problem is related to the cache.
I still got a backup of my old cache, perhaps that can help CCP in some way? Its 1.8 gig in size though, but i wouldnt have a problem uploading it to some server if it can help CCP solve some problems. I can also burn it on a DVD-R and ship it somewhere?
In any case, i'm running Windows XP aswell that has its time synced with a Windows 2000 Domain Controller. The Domain Controller is also syncing with an NTP server on the internet.
Doing a quick check now, it seems my local time and the TQ-server time are both running in sync.
Last but not least, i like to add that it feels good to have CCP joining the discussion. Thanks for that.
UPDATE: Its now 30 mins after DT, and the problem is gone. My puter hasnt been rebooted or stuff changed on it. Seems server-side if you ask me.
-------
|
Varia
|
Posted - 2003.11.11 10:48:00 -
[13]
I have had the cap drain problem; When ever I log on now I just check how quickly my MWD drains my Cap.
If the Cap starts to drain really fast I just re-log, until the Cap drains at the pace I expect, this may take Re-logging several times.
My current setup gives me a 205 second recharge so I donĘt expect my Cap to drain that fast with my MWD fitted.
Women that strive to equal men lack ambition. |
Preacher
|
Posted - 2003.11.11 13:58:00 -
[14]
I find the same scenario with MWD and this has been occurring on and off now for about a month. Usually a reboot of my system will fix the problem or one or more relog attempts can clear it as well. As for other programs, I usually only have IRC and/or ICQ running at the same time as Eve. Occassionally I will open up a browser or the Calculator but the most part that is it.
"Salvation Awaits" - The Preacher |
Zenobia
|
Posted - 2003.11.11 16:01:00 -
[15]
I've been hitting the cap bug as well during the past few days now, whereas before, I had never had a problem. Now I am never able to rely on what my cap reading says... as you can imagine, this is extremely dangerous in PvP situations where cap can equal life.
It's interesting that the syncing problem was brought up here too. A few of my corpmates, over the past month or so, have noticed that the client sometimes gets way out of sync with the server under certain circumstances. The most noticeable times was during chain spawning... our client would show us, for example, within 1500m of a container, yet the server would insist we were nowhere near it. Other players would also see us in a completely different place than what our client was actually displaying.
I unfortunately have no clue on how to consistently reproduce any of these errors. I do know that the cap bug seems to have reared it's ugly head within the last 3-5 days though.
-- Zen
|
SKiNNiEH
|
Posted - 2003.11.11 20:54:00 -
[16]
Yup, i had that too a couple of times.. I contributed it to normal lag though, but the strange thing about it is that you didnt see your ship snap back a few hundred meters like you would see in systems such as Yulai.
Also, i'm usually so far away in 0.0 space, that it cant be the lag people are experiencing in empire space and the immediate 0.0 around that, for instance. I mean, 40+ jumps from the nearest station.. only the hardcore chainers/farmers meet up there.
-------
|
MaiLina KaTar
|
Posted - 2003.11.11 21:59:00 -
[17]
When I took a ride through Ammar the day before yesterday I warped to the next gate on my trip. I was pretty stunned when I looked at my cap which actually went down instead of charging up like it normally does during warp.
Pretty strange...
Only happened this one time so far but I had others in my corp telling me it happened to them, too.
CCP you might actually want to take a closer look at this entire cap thing. And I¦d really like some more explanations on how the client behaves regarding tymesyncs and so on.
To really spot the problems we need to know how the client actually syncs server- and systemtime.
Mai's Idealog |
Beseb
|
Posted - 2003.11.11 22:41:00 -
[18]
I too am getting cap bugs again and have changed nothing on my system. I did clear my cache some days ago to correct a fitting bug.
|
Eltigre
|
Posted - 2003.11.12 02:58:00 -
[19]
Why not simply force the game client to sync with the server while the game is being played ? This would seem to me to be the simplest and easiest way to ensure the server and client are in fact in-sync. IMHO
 Quote:
I've only received one usable report of this bug and what the log that came with it indicated was that the player's client's time was around two minutes ahead of the time on the server.
This is why the capacitor seems to show a higher level of charge - it thinks its had however much the time is out of sync as extra recharge time.
Someone else also mentioned that their friend was getting damaged at 2AU, this can also be explained by time sync problems. The warp is simulated on the client according to the times the server gives it, if the client is ahead timewise, then the warp will appear to have engaged when it really hasn't.
Needless to say, this should not be happening and the capacitor sync problems that have been in the past were unrelated having happened with correct time synchronisation.
Can anyone think of anything they are running on their system that might cause the client to fall out of sync with the server?
If anyone who uses the test server manages to reproduce it there, or knows someone who has reproduced it there, a log file from when it happened would be immensely helpful. If you have log files of this happening on TQ, they aren't as helpful due to the limited state change logging we do there, but I'd still appreciate getting them. You can send them to [email protected]
SWEET routinely sells BPC's in Sing Laison and Essence Regions. |
SKiNNiEH
|
Posted - 2003.11.12 13:40:00 -
[20]
Somehow i think the servers individually are not synced, time-wise. Problems in one solarsystem, problem gone in the next... As we all know, once you jump to another solarsystem, you might be jumping onto another server aswell. Perhaps the cluster in London isnt in sync with each other?
I have no clue really, the server-part is something i know very little about.
-------
|
lickspittle
|
Posted - 2003.11.13 10:09:00 -
[21]
If anyone can send a log file from when this happened to them to [email protected], it would be appreciated. A description of what you were doing, where how it behaved differed from your expectations and any other pertinent facts you can think of would make the log a lot more usable.
-- Richard
CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Elissen
|
Posted - 2003.11.13 15:53:00 -
[22]
Will do, but is it possible to log 2 clients at the same time on one PC (I don't mind messing around with parameters or configfiles to get it working).
|
lickspittle
|
Posted - 2003.11.14 09:32:00 -
[23]
If you run two clients and a log server, it should log the output from both. Separating the output by client is no problem. By the way, thanks for the log, I'll take a look at it a little later and see if I can determine anything new.
-- Richard
CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Elissen
|
Posted - 2003.11.14 09:57:00 -
[24]
Thanks for the explanation and please let me know of you find anything.
|
Kyroki Tirpellan
|
Posted - 2003.11.14 11:00:00 -
[25]
I've had this problem once in a while for several weeks I think. Lost a hvy cruiser due to it once  At least the cap was going way faster than it should, and not letting me fire weapons even if it looked like I had 30-40% cap charge. I reported it, didn't have logserver running when it came up (it's not like something you run all the time...). I asked GMs to check server logs and see if it was a bug, if I could possibly get compensated for that cruiser I lost... They said the logs were fine, it was propably just a display problem, and there was no way to even prove that. I'm sure they would have seen something wrong if I'd have had a log of the incident...
Another time this came up when I fitted a Warp Core Stabilizer to a ship... (didn't really need it, just fitted it cuz I had a free slot and no more cargospace), activated it, and warped. The cap kept going down at an insane rate even after I shut down the WCS, I had nothing running and still it went down. 
Dunno if this is much help... but if this happens again I'll be sure to fire up the logserver... Oh and someone mentioned this might be releated to WinXP, I'm using that OS so that might be it.
Peace through love, understanding and superior firepower.
Real men structure tank! |
lickspittle
|
Posted - 2003.11.14 11:02:00 -
[26]
Edited by: lickspittle on 14/11/2003 11:04:40
Just for a clarification of what I currently think the problem is, keeping in mind that this area if it is the cause is not one I work on..
I think its that the client-side time has fallen out of sync with the server. Now, the client-side time is slightly different from your system time, its the system time with an offset held internally to the client to give a emulated server time.
So, if you were to change your system time (while the client was running), or if it were to change through some third-party software, it might be causing this problem. I hear that the spyware formally known as gator caused this problem.
Although given that we do not know why this is happening yet, given that it is happening because of this, its possibly a bug in the client and not third-party software causing the problem.
-- Richard
CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
SKiNNiEH
|
Posted - 2003.11.14 12:19:00 -
[27]
Now that you've said it like this...
Perhaps it are all O.S.'es that periodically check an NTP server and sync their time (like mine does, since its in a Active Directory domain). Even though we're talking fractions of a second, perhaps it is enough to make the client do strange things.
Maybe the EVE client would be better off if it didnt do anything with the internal clock of a PC?
As soon as i'll head out to my 0.0 space again, i'll start the log server for sure. I've tried chaos, since you've got better server-side logging there (debugging mode?).. but it was so lagged out, that i didnt even see the station or move my ship.
-------
|
Elissen
|
Posted - 2003.11.14 13:04:00 -
[28]
Whenever the time changes Windows broadcasts an message to all application. If the client is so depending on a correct time the client should detect the message and resync with the server (to calculate a new offset?)
|
lickspittle
|
Posted - 2003.11.14 14:14:00 -
[29]
Just need to confirm this. If this is happening, the problem persists even after docking/undocking or stargate jumps, right?
-- Richard
CCP Programmer. Anything said above is not the official line, but my own take or opinion. |
Katt
|
Posted - 2003.11.14 14:30:00 -
[30]
Yes, it definitely persists.
|
| |
|
| Pages: [1] 2 :: one page |
| First page | Previous page | Next page | Last page |