Ticked already ofc, same as I said i did with the old. like i said, just sits there. Multiclient miner has two threads - main thread for mining and secondary thread for DH/HP/Jamming checks. Secondary thread make checks each 3 seconds and only when window of the client active. That means if you have some very fast stage, macro can switch to another module and secondary thread had no time/chance to make full scan of everything. In result program mines faster and checks HP/jamming rarer. In 2.4.2 version I added maximal time after which secondary thread dont wait while main thread give a chance to do something, but activate window by its own and tell to main thread - wait while I working.
This will reduce chance to miss low HP or jamming but also reduce speed a bit. Test what is max time most appropriate for you.


Why would I want the repairer to go constantly all the time? I'd have to compromise tank and look like one of the obvious macros u see at ice belts flashing away. I just liked it to quickly pwn the rats, rep back to 100% stop the rep, carry on; The old one did it perfectly. I will check how miner use repairer during active tanking method. It should do the same like old miner.

Sorry mate but how did the old miner work it out? used to be amazing at doing it, just after a cycle ended and the next started it could stop the cycle and the roid be done (shadow of its former self), then go right onto locking the next roid. Old miner calculated maximal content in the asteroid and switched off lasers when it was not necessary to work anymore. But if asteroids dont have less ore then predicted, new miner should work even better, because it has cycling of lasers. You can divide cycle by 2 or 3 periods and make more or less good yield even in 0.9-1.0 systems. The only way to get perfect prediction is to introduce scanner support. After we fix bugs I will look if we can have scanner support. New version of the program has much better functional.

Anyway, just poking around, i know nothing i say makes sense to you and vice versa No, continue please I am also miner and put more attention to something I use. If you see something working not ok better ask, because I might not return to this part anymore.

simonk6 stop being a child throwing your toys out of the pram because somebody didn't do exactly what you wanted, there and then.

Slav has certainly not ignored the users, he has implemented features and fixes that the users have brought up.

He is allowed to add another feature if he wants to or if he believes it will enhance his program.

Yeah...thanks Kylara..helpful as always If I was to test drive a car i'd expect the engineer to work on the issues with it - not work on his lawnmower. Look, I know what i am about to say is not true because Slav is very hard working, but others who are new may think that perhaps the developer has his own agenda rather than fixing the issues we already have. So keep your hair on - I am entitled to be frustrated - after all, we went from a stable program, to EM and were promised that EM would be top priority - This program is marketed as a miner macro, developed as a miner macro, I paid for a miner macro, stands to reason I want the mining side of this project as a priority right?

As stated - DT detection bugs still in effect and systems with same names imbedded still not working - i.e. if I have Tar and Tarta in my list EM cannot handle it.

Let me know if you need logs again - will have to generate again as I just updated to Windows 7 and didn't save my data dumps.

Cheers.

simonk6 писал(а):
As stated - DT detection bugs still in effect and systems with same names imbedded still not working - i.e. if I have Tar and Tarta in my list EM cannot handle it. Yes, generate logs. Also you can use test stand. Open eve with search window with Tar, lock to this window and press TestSolSysWin button. In case of Tar program correctly finds position of the system in 1st line for me. To search Tarta you need type Tarta in search window and there is only one result.

simonk6 писал(а):
but others who are new may think that perhaps the developer has his own agenda rather than fixing the issues we already have. Program uses general methods. If you test deliverer you test traveling function in miner. If people test planet explorer they test text reader function. I doing to use it in refining and statistics module. Dont think this is complete waste of time when I create some new functions. I had to change one basic text reader function because only in PE I was able to find a bug - program did not read colored text. All windows in planet view are transparent. Automatic detection of most appropriate color was written with wrong assumption that some text on blue background has better contrast if we read it in opposite (e.g. red) color. It seems text letters accept some of blue color intensity from background and contrast increases if we read this text in blue colors.

Dont think this is complete waste of time when I create some new functions

Never said it was a waste of your time , just not what anyone was looking for at the time. Will gather some logs when I get 5 minutes.

Cheers.