| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
ReePeR McAllem
   |
Posted - 2005.10.23 12:53:00 -
[1]
Ok this is something with which I can put up with no longer grahhhH!!!
now I know im not the only one that gets this quite frequently my corp mates get the same, your at 8.4k range from a ceptor: you try to activate your nos and webber.. message come you must be within 10km to activate this module AHHH!!!! im 8.5k away.. hell even when you bump into it, your still out of range. I wouldnt mind if it were like just once in a blue moon, but its quite frequent.
in some situations it makes life such a pain in the hoohah! 
Courage is rightly esteemed the first of Amarr qualities... because it is the quality which guarantees all others. |
Dark Shikari
|
Posted - 2005.10.23 13:00:00 -
[2]
Its called being out of sync.
Generally its caused by lag of some sort. It can also be caused by an inaccurate BIOS clock, which can be fixed by replacing the motherboard battery.
-
Proud member of the [23].
Don't get the reference in my sig? Click it.
|
ReePeR McAllem
|
Posted - 2005.10.23 13:02:00 -
[3]
oww interesting, *gets out tweezers*
Thanks for that 
Courage is rightly esteemed the first of Amarr qualities... because it is the quality which guarantees all others. |
Allen Deckard
|
Posted - 2005.10.23 14:13:00 -
[4]
dont think bios clock has crap to do with it.
Personally it seems duplicatable most of the time by simply running at full speed into an immovable object.
It's not just me its everyone I know it happens from time to time usually fixable by simply docking and undocking.
I agree though that it is some sort of sync problem but dont think it has anything to do with clock.
|
Dark Shikari
|
Posted - 2005.10.23 14:16:00 -
[5]
 Originally by: Allen Deckard
dont think bios clock has crap to do with it.
Personally it seems duplicatable most of the time by simply running at full speed into an immovable object.
It's not just me its everyone I know it happens from time to time usually fixable by simply docking and undocking.
I agree though that it is some sort of sync problem but dont think it has anything to do with clock.
Well I know that the cap sync problem is caused by the clock (i.e. where you have full cap on screen but zero cap when activating items). So it would be a good guess to say that this might be it too.
-
Proud member of the [23].
Don't get the reference in my sig? Click it.
|
Xelios
|
Posted - 2005.10.23 14:29:00 -
[6]
Edited by: Xelios on 23/10/2005 14:30:53
It could be the bios clock I guess. They're not terribly accurate, most either lose or gain between 5-10 seconds a day, and the software clock each computer runs when its on is even more inaccurate. Since a lot of the client side code probably depends on one of the two clocks (the clocks get used a lot in game programming for everything from controlling the fps to timing update requests from the server) an inaccurate clock could bork the system.
Unfortunatly replacing the battery won't help much, the clock is inaccurate by nature and is affected by things like temperature. They're more inaccurate than your standard wris****ch even.
But I don't think this bug is caused by the clock, it sounds to me like normal lag. Your client receives an update from the server with the target's position, the client then takes over and 'guesses' where the target will be x seconds from now until another update is received from the server. When you try to activate a module the server sees the ship as not being in range, and sends an 'activation failed' packet to your client. Your client still hasn't received an update on the target's position, so it's still guessing, all it gets is the failure packet even though on your screen it should have worked.
The only way to fix it is to increase the number of times other ships are updated from the server, the problem is even updating just twice as often doubles the load on the servers which creates more lag.
/edit Wow the board bleeped out wrist-watch, I love censorship 
Signature removed. -Zhuge ([email protected])
Woot.
|
Dark Shikari
|
Posted - 2005.10.23 14:32:00 -
[7]
Well a really low BIOS battery can cause the clock to lose like 10-20 minutes PER HOUR. This can cause problems... 
-
Proud member of the [23].
Don't get the reference in my sig? Click it.
|
M3ta7h3ad
|
Posted - 2005.10.23 14:56:00 -
[8]
Dont even bother replacing the battery. I have no battery (physically removed it) in mine. And as for a low battery causing the bios clock issue... *******s mate. It will run off of the standby power coming from your powersupply in your computer case if there is zero battery.
The bios clock doesnt go "out of sync" its the windows software clock that goes out of sync. Its all explained here: Microsoft Knowledge Base
and a solution involving a free bit of software (as well as a more "laymans" explanation of the problem is available here: ClockMon
Install the little program, run it, and shove a shortcut to it in C:\windows\program files\startup\ and then you need never worry about cap/shield/armour/struct/distance issues again.
|
Dark Shikari
|
Posted - 2005.10.23 15:00:00 -
[9]
Originally by: M3ta7h3ad
Dont even bother replacing the battery. I have no battery (physically removed it) in mine. And as for a low battery causing the bios clock issue... *******s mate. It will run off of the standby power coming from your powersupply in your computer case if there is zero battery.
The bios clock doesnt go "out of sync" its the windows software clock that goes out of sync. Its all explained here: Microsoft Knowledge Base
and a solution involving a free bit of software (as well as a more "laymans" explanation of the problem is available here: ClockMon
Install the little program, run it, and shove a shortcut to it in C:\windows\program files\startup\ and then you need never worry about cap/shield/armour/struct/distance issues again.
ClockMon doesn't change the system clock, only the windows clock, and EVE reads from the system clock, so that could not possibly fix it.
And while it would make sense that the motherboard would work off standby power, it doesn't seem to, as I have plenty of old computers that have stopped counting correct time because of having dead batteries.
-
Proud member of the [23].
Don't get the reference in my sig? Click it.
|
M3ta7h3ad
|
Posted - 2005.10.23 15:14:00 -
[10]
1.) I have a 486 acting as a small "basic" programming box. It used to have an AA battery in it, plugged via a header. This battery has been removed. Aside from power cuts it keeps time perfectly.
2.) I also used to have a 286 and 386, similar story... kept time in the bios perfectly, this is also true with the 2 Pentium II affairs downstairs, and my modern computer upstairs.... I find it highly unlikely that these 6 computers (Spanning most of the era of home computing) are complete flukes of existance.
I should reiterate, "standby power" being the default 5V line that is kept live so long as your powersupply is plugged into the mains (your computer does not need to be booted up for this).
3.)You clearly read the knowledge base article, read the clockmon functions, then apparantly completely ignored the information, and formulated a random thought?! The problems occur within eve when the following is true.
The windows clock is out of sync with the system/bios/cmos clock.
they do not occur because your windows clock is not the same time as the eve clock.
Clockmon syncs the windows clock with the RTC (aka system/bios/cmos clock), therefore solving any related issues with EVE.
Okay?
|
EaglesFire
|
Posted - 2005.10.23 16:01:00 -
[11]
Tried the Clockmon, and so far it has fixed all my cap bug issues. Thank you for the tip!!!
"Knowledge is power, and the uninformed SHALL be punished!" |
M3ta7h3ad
|
Posted - 2005.10.23 16:10:00 -
[12]
No probs mate :) Just wish folk would try it before naysaying it :) Glad it helped.
|
Nyphur
|
Posted - 2005.10.23 16:40:00 -
[13]
Originally by: M3ta7h3ad
No probs mate :) Just wish folk would try it before naysaying it :) Glad it helped.
I thought I'd see you here ;). I'm giving Clockmon a try. Apparantly it can also help with CTDs.
|
M3ta7h3ad
|
Posted - 2005.10.23 16:48:00 -
[14]
lol \o :)
Yeah I dont know if networking is affected by it but it isnt out of the realms of possiblities :) Hope it works!.
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |