Client not always return miner to starting system (1 viewing) (1) Guest
 | | |
TOPIC: Client not always return miner to starting system
|
Client not always return miner to starting system 12 Years, 6 Months ago
|
Karma: 0
|
Client not always returns miner to starting system despite the marked "return" box in settings
|
|
asmith
Fresh Boarder
Posts: 25
|
|
|
Re:Client not always return miner to starting system 12 Years, 6 Months ago
|
Karma: 803
|
It will not always return ship to starting system. There are two processes. First process is normal execution of a general algorithm. When you check "return to home system on start" you tell program to follow one of execution routes in general algorithm on start. But there is second process - priority execution in case of some events (fight mode activation if you logged in damaged, or connect lost detection if eve dropped connection just after first login, etc). Second process may cancel normal execution of a first process and will return execution to some point in general algorithm where operation can continue but without advanced features.
|
|
|
Send logs to my mail -  with subject 'log files' to pass spam filter.
How to record logs in knowledge base
|
|
Re:Client not always return miner to starting system 12 Years, 6 Months ago
|
Karma: 0
|
I see, this is the case for sure , I will monitor it,
best remedy in any way just to reload the client
lots of txs for prompt support
|
|
asmith
Fresh Boarder
Posts: 25
|
|
|
Re:Client not always return miner to starting system 12 Years, 5 Months ago
|
Karma: 0
|
Slav2 wrote:
First process is normal execution of a general algorithm. When you check "return to home system on start" you tell program to follow one of execution routes in general algorithm on start. But there is second process - priority execution in case of some events (fight mode activation if you logged in damaged, or connect lost detection if eve dropped connection just after first login, etc). Second process may cancel normal execution of a first process and will return execution to some point in general algorithm where operation can continue but without advanced features.
I'm still experiencing the same problem and in order to return my hulks to the home system I need to reload the client after DT.
How to get priority on a first process?
Txs
|
|
asmith
Fresh Boarder
Posts: 25
|
|
|
Re:Client not always return miner to starting system 12 Years, 5 Months ago
|
Karma: 803
|
asmith wrote:
Slav2 wrote:
I'm still experiencing the same problem and in order to return my hulks to the home system I need to reload the client after DT.
How to get priority on a first process?
Txs Do you have custom timer which start before DT and stop after DT? May be miner dont detect DT? Why to guess? Send me logs please, I will look.
|
|
|
Send logs to my mail -  with subject 'log files' to pass spam filter.
How to record logs in knowledge base
|
|
Re:Client not always return miner to starting system 12 Years, 5 Months ago
|
Karma: 1
|
I notoced similar behaviour with my 5 miners sometimes.. one way i managed to get around it was to leave the travel reatures on but have only one system in the list.. but that would defeat the point of travelling in most cases.. f
I did find it useful for moving the miners easier though.
|
|
|
|
|
|
 | | |
|
|