botmaster
2007-11-25 09:30:03
First post in a LOOONG LONG time. I finally figured out on how to make SCAR work the crosshair in Linux. This means that SOME linux compatibility for scripts is possible, even without rewriting the entire code.
Here's a screenshot:

I haven't tested movemouse and some other stuff yet, but I'm fairly confident that it works if GetClientDimensions(x, y) work.
So autoing on Linux is possible with SCAR - don't know if that's old news. At any rate, previous experiments with me running Firefox, SCAR, and sun's JRE on a Wine server failed miserably, resulting in a crash of WINE. And it was always when I ran the RS applet, so I knew it had something to do with the JRE - this was my main concern at any rate, because running a Virtual Machine inside a Virtual Machine (double virtualization) REALLY slows down the system. And plus, the WINE API might not be able to handle the JRE's commands.
Then, it came to me *insert enlightenment here*: The JRE was running OUTSIDE a graphic environment, meaning that painting onto the client using Java's canvas functions failed.
So then - I emulated a desktop. All I did was edit Wine's configuration to use a desktop to contain all the apps. And voila - I had a fixed coordinate system for both SCAR, and JAVA's devicespace drawing functions.
Mwhahah… :D I'm so proud of myself now. XD
Now all I need to figure out is how to run multiple WINE servers at the same time - then I can run multiple autoers on the same machine, without graphic output or the mouse becoming useless. *evil laugh*. I'm such a genius :D .
There's several drawback's though. Primarily, not all SCAR's functionality is preserved. There are several annoying memory read/write errors when using the menubar of SCAR, resulting in some disabled features (inaccessible Edit, Script, and Help menus).
But otherwise, it runs as smooth as any other application would - and my system is dated 2004 at the latest (3 years old…).
Yeh. I might leave my dormant state. Imagine the new possibilities this gives you:
If this is old news… well, so what. Just had to give my 2 cts. to this topic.
Here's a screenshot:

I haven't tested movemouse and some other stuff yet, but I'm fairly confident that it works if GetClientDimensions(x, y) work.
So autoing on Linux is possible with SCAR - don't know if that's old news. At any rate, previous experiments with me running Firefox, SCAR, and sun's JRE on a Wine server failed miserably, resulting in a crash of WINE. And it was always when I ran the RS applet, so I knew it had something to do with the JRE - this was my main concern at any rate, because running a Virtual Machine inside a Virtual Machine (double virtualization) REALLY slows down the system. And plus, the WINE API might not be able to handle the JRE's commands.
Then, it came to me *insert enlightenment here*: The JRE was running OUTSIDE a graphic environment, meaning that painting onto the client using Java's canvas functions failed.
So then - I emulated a desktop. All I did was edit Wine's configuration to use a desktop to contain all the apps. And voila - I had a fixed coordinate system for both SCAR, and JAVA's devicespace drawing functions.
Mwhahah… :D I'm so proud of myself now. XD
Now all I need to figure out is how to run multiple WINE servers at the same time - then I can run multiple autoers on the same machine, without graphic output or the mouse becoming useless. *evil laugh*. I'm such a genius :D .
There's several drawback's though. Primarily, not all SCAR's functionality is preserved. There are several annoying memory read/write errors when using the menubar of SCAR, resulting in some disabled features (inaccessible Edit, Script, and Help menus).
But otherwise, it runs as smooth as any other application would - and my system is dated 2004 at the latest (3 years old…).
Yeh. I might leave my dormant state. Imagine the new possibilities this gives you:
- Clustered servers consisting out of old, cheap/free hardware purely for autoing are feasible.
- Autoing on more than one account also becomes a possibility, without running a resource-intensive VM.
- Less time to build a respectable autoing army.
- Much much more…
If this is old news… well, so what. Just had to give my 2 cts. to this topic.