BaseN,
First, thank you so much for all the effort you have put into this application. It really is a sanity saver. (And a sleep saver, too)
Second, I noticed something odd in the randomized number of seconds added to the loop delay. It works perfectly at lower numbers, but when I started running longer delays (an hour or more) it seems like the RNG always adds 4 seconds. I have 5 instances running on a 7300 second loop and every one of them shows "Delaying for 7304 seconds". If the purpose of the randomizer is to avoid seeming too precise, this may not be doing what you intended.
I'm certainly not complaining, just thought I'd let you know.
EDIT: Third: Since no-one else answered above, do you know if APBU will run under WINE? I've got a 64-bit Ubuntu machine sitting idle about 20 hours a day that I would love to put into service as a APBU slave. I'm tempted to just dive in and see, but I thought I would ask first.
Last edited by Spaznetz; 04-07-2014 at 03:48 PM.
Tried running the bot tonight, I installed it fresh from the first post and it gave me a message that I needed to search for a compatible version ? A few weeks ago I ran it with no problem but now it says not compatible with my version of windows ( Windows 7 Ultimate).
The only thing I have done recently with my laptop was I tried installing a program that required that I install THREED32.OCX into my system32 folder, and something else similar, I don't know if that has anything to do with it but its the only change I have done since the last time I was able to get everything working.
The Error message is
The version of this file is not compatible with the version of windows your running. Check your computers systems information to see weather you need an X86 (32-bit) or X64 ( 64-bit) version of this program, and then contact the software publisher.
Any ideas?
Ok these are the two items I installed and registered ( with command promp)
threed32.ocx and msmask32.ocx
I have an older Windows 7 32-bit operating system..
Did I mess something up?
Ok did a search inside this thread and turns out that I must be mistaken, I must have never been able to run this program on my laptop as it is a 32-bit system that is not supported by this program. ( It must have been on my home computer)
Ok now that makes me wonder how old my laptop is.....
I have already explained that I am compiling Qt and QtWebkit from git (and their dependencies due me using VC11 toolchain). This is because standard Qt and Qt Webkit are compiled by default with features that increase memory consumption and cpu usage that APBU does not need--eg SVG, sensors etc-- (and also picking up zero day QtWebkit bugfixes which are quite frequent. When one has possible ramifications with APBU, I rebuild.).
Do try and compile Qt with QtWebkit from git and you'll get an idea of what I am trying to avoid. I said that if there is actual demand for this (and by actual demand I mean enough demand to justify me packaging and uploading everything twice--I update this very frequently/or a donation with such a request), I'll compile it (the x86 version only) against prebuilt Qt/QtWebkit binaries only and it will have increased memory footprint (as much as 25%) and CPU usage.
The compilation of APBU itself takes 1-2 seconds. EDIT: And before you ask why I chose to compile the x64 version to begin with, it's because I use the particular set of libraries for two other projects as well that depend on more than 4GB RAM allocations (those projects don't use QtWebkit but I'm already compiling Qt with the same options for them. So it all boils down to saving time...)
That said, sorry guys for the delayed updating but I'm having two consecutive hell weeks at work (working on a lot of projects simultaneously) and that's pushing APBU development in the backside. Hopefully it will clear by the end of this week and I'll get the time to hunt/fix the reported issues on the 0.4.0 closed beta.
Last edited by BaseN; 04-07-2014 at 11:45 PM.
I guess I'm just sure what you get out of recompiling Qt for every weekly distro instead of just using whatever current stable version that's out there. A one-time compile of the most stable version (removing the unnecessary parts if you're that adamant about it), maybe another one down the line, but not as frequent as you're currently having to do it. Not to mention it would cause less stress having to find out what the hotfix just did to your own program. Also, in this day and age with GIGS of ram and TB of space, especially considering the preference to x64... is footprint that big of a deal? Is this using CPU resources of a significant degree?
As I've said, I don't really know as I only have one computer that is running a 64-bit OS and it's not my preferred machine to run this on (a Win 7 x64, also have a Win 7 32 and a Vista 32). In an ideal world, I'd run it on a secondary computer of low power consumption instead of my power computer that is also used by others in my household.
There have been fixes in QtWebkit that would affect APBU and I have to pick them up. Not recompiling when I know something that could cause a problem is fixed is just a poor decision and/or lazyness.
Now regarding the resource usage, a lot of people use APBU with multiple accounts so low memory footprint is very important. Low CPU usage is a must for these people as well but also for the majority of the users who use it on their main PC system and want it to use as less resources as possible so it doesn't actually affect the performance of them running the game etc. Currently it is not using many resources no. But that is because I use the optimized Qt/QtWebkit builds and I'm constantly optimizing code for resource usage. Also there is no stress at all about finding out what a hotfix does to my program because I know that before hand. If you are familiar with the libraries you are using, you just examine the patch and you know exactly what it fixes, why and how it could affect your program or how your program could misbehave if you did not apply the patch. Since the start of the development of APBU, there have been at least 5 or 6 fixes that if left unpatched would create issues for APBU. One of them was a leak in Webkit's part of the code that has to do with loading and unloading jpeg image resources, which the gateway is full of (for example).
As I said if there's enough demand for this I'll compile 32bit version against prebuilt Qt which while have increased footprint/CPU usage.
If I understand what spiritdays is asking for, I'd like to add my vote for these features. (Pffft, like this is a Democracy, right?)
It would be fantastic if it were possible to tell APBU to perform a series of actions like:
1) Log in
2) Perform task list
3) Log out
4) Wait specified time and repeat
Since all the tasks seem to be in multiples of an hour, I end up setting Base Loop Delay to 3600 and letting it run. Either that or I stop APBU and try to remember to start it again (and forget). It would be nice to have the ability to set delays up to whatever the maximum task time is (18 hours?) The 'Log In/Log Out' feature would be ideal, but longer delays would be nice, too.
Curious, but is anyone experiencing time out issues with the Gateway? I mean, yeah, it's Cryptic, but today, it's been really bad.....