| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Slaveabuser
   |
Posted - 2005.12.25 22:34:00 -
[1]
I havent had one of those in ages. But after RMR they are back. Atleast for me. I fly a poc and when I have 50% cap left I cant even fire a laser.
Anyone else experiencing this/anyone heard anything if the next hotfix will solve this?
Having to live on, one knows better than to value life too much.
|
Adoro
|
Posted - 2005.12.25 23:02:00 -
[2]
Jup got same problem. Relog helps :)
---------
Oh!? |
Callistus
|
Posted - 2005.12.26 00:14:00 -
[3]
Its caused by you becoming out of sync with the server, due to an inaccurate internal clock. Clockmon should fix it.
Coreli Corporation Mainframe
|
Slaveabuser
|
Posted - 2005.12.26 01:35:00 -
[4]
Wicked!
thanks Callistus
Having to live on, one knows better than to value life too much.
|
david1090879
|
Posted - 2005.12.30 02:14:00 -
[5]
im having the same problem I active a mwd and no cap is taken, yet after a while i m out of cap when the client thinks i m not.
I tried the timeclock, link seems to be not working
|
jenga
|
Posted - 2005.12.30 03:26:00 -
[6]
I have had this issue a long time and clockmon never fixed it have even tried other programs that claim to do the same job none have worked and i still have the cap bug
|
david1090879
|
Posted - 2005.12.30 11:05:00 -
[7]
it is definatly something to do with the time of the pc. I found out in the end it was my system time. Check that the time and the date is correct in the bios. Someone had been messing with my date / time properties and the wrong day had been selected.
|
Geiran Thorne
|
Posted - 2005.12.30 13:27:00 -
[8]
The only way in which the system clock should have any effect is if it's too fast or too slow. And then only if it's gaining or losing several seconds over ten minutes or so.
This is since the client should keep an internal clock that's updated from the server every few minutes.
I have lost at least two ships to this annoying bug. It's interesting to note how the cap appears to be the only thing affected by it. Shield recharge rates appear to be working just fine.
|
BBQ
|
Posted - 2005.12.30 13:46:00 -
[9]
If it is a clock problem then try downloading "abouttime" (google it) and setting it to update the time every 10s or so. This will sync your clock with an online one and should stop the cap problems due to clock sync.
<< Insert whitty sig here >>
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |