SRL Archive - Help and Support

Hey, SCAR won't find the bitmap. Is there a way for SCAR to find the bitmap WITHOUT setting the client, OR clicking outside the client on non-negative coords?

what are you using it for?

From: The Un-Named
Hey, SCAR won't find the bitmap. Is there a way for SCAR to find the bitmap WITHOUT setting the client, OR clicking outside the client on non-negative coords?

If you don't select the client, your whole desktop is the client. I tested it before

For the second part, (I assume you selected the client), if you choose coords outside the client I think the Mouse goes crazy or something.

From: WhiteShadow
If you don't select the client, your whole desktop is the client. I tested it before if you choose coords outside the client I think the Mouse goes crazy or something.

I know it's the desktop, and yes, if you choose coords to go outside of client mouse goes crazy so I didn't set the client but then it dosen't find the bitmaps.

I just used PopUp.

Bitmaps in RS change too often to use that. I suggest you use FindColorSpiralTolerance or whatever..that may be easier because my auto-miner does, and it works much better.

The Un-Named, I can help you with any problems you have with SCAR over MSN. I'm usually available for help and I love to do it (it's a huge part of the reason I'm not active with the SRL include right now.. You'll see ;)). Here's the deal though:

SCAR finds bitmaps on a client. If the client is incorrect, SCAR has no chance of finding the bitmap you want. Basically, you'll see that SCAR won't find it because it is programmed to only look in the specific client. If it were not, you could only imagine the time it would take to look through everything on the screen (and the programming needed to accomplish it).

About the mouse thing. Any procedure or function that uses MoveMouse can go outside the client window (not outside your screen's viewing area). Anything that doesn't use MoveMouse can not (I've seen them go to -1,-1 fine, though). In other words, MoveMouse and any procedure/function that uses it can go anywhere on the screen. MoveMouseSmooth and MoveMouseSmoothEx and any procedure/function that uses them can go within the client.

From: driger1592
The Un-Named, I can help you with any problems you have with SCAR over MSN. I'm usually available for help and I love to do it (it's a huge part of the reason I'm not active with the SRL include right now.. You'll see ;)). Here's the deal though:

SCAR finds bitmaps on a client. If the client is incorrect, SCAR has no chance of finding the bitmap you want. Basically, you'll see that SCAR won't find it because it is programmed to only look in the specific client. If it were not, you could only imagine the time it would take to look through everything on the screen (and the programming needed to accomplish it).

About the mouse thing. Any procedure or function that uses MoveMouse can go outside the client window (not outside your screen's viewing area). Anything that doesn't use MoveMouse can not (I've seen them go to -1,-1 fine, though). In other words, MoveMouse and any procedure/function that uses it can go anywhere on the screen. MoveMouseSmooth and MoveMouseSmoothEx and any procedure/function that uses them can go within the client.

It goes berserk unless I end scar's process.

I told you, it's because any mouse procedure that uses anything but MoveMouse doesn't let it go outside the client window. Next time, read what I write. If you want to go outside of the client, use MoveMouse, or a mouse procedure that only uses MoveMouse as a movement method.