Jump to content

Advanced Pixel Search Library


FastFrench
 Share

What do you think of this library ?  

35 members have voted

  1. 1. What do you think about FastFind ?

    • It's really great, I can't imagine doing a script without it
    • It's of some use for me in my current scripts
    • I could use it some day
    • Looks nice, but of no use for me
    • I've tried it, but it doesnt fit my needs
    • Sounds good on the paper, but can't make it work (bug or too difficult to use it)
  2. 2. Have you tried it ?

    • Yes, I'm using it right now
    • Somewhat, I've done some testing, will surely use it later
    • I've downloaded it and just played a little with packaged demo scripts
    • I've downloaded it, but not tried it so far
    • Not downloaded it so far, but I probably will some day
    • It's of no interested for me.
  3. 3. What is missing or should be improved ?

    • It has all the features I may need about Pixels Handling
    • OK it's pretty fast, but couldn't it be faster ?
    • Too hard to use it, could you simplify usage ?
    • Some additional features would be nice to have (please explain in a message)
    • It really lacks some decent documentation (I still hope to find someone to help on that)
    • Some critical features are missing, can't use it (please explain in a message)
    • I found some minor bugs (please explain in a message)
    • I've found some serious bugs (please explain in a message)
    • I've never tried it so far, can't tell
    • It would be nice if you could provide easy access to the associated tool - FFShowPixel
    • I would like to use it other languages. Could you provide wrappers ? (please explain in a message)


Recommended Posts

Posted (edited)

After extensively tinkering, it looks like the code

FFsnapshot(500,500,560,501)

$testVariable = FFNearestSpot(1,1,500,500,0xaaaaaa,45,0)

roughly duplicates the native pixelsearch(500,500,560,500,0xaaaaa,45).  I haven't tested it yet extensively to see if it always returns the same results.  Another solution is to populate every possibly encountered shade variation that would otherwise be captured by the "45" shade variation parameter with

FFaddcolor(0xaaaaaa)
FFaddcolor(0xaaaaab)
FFaddcolor(0xaaaaac)
FFaddcolor(0xaaaaad)...


FFsnapshot(500,560,500,501)

$testVariable = FFNearestPixel(500,560,-1,0)

although this last method may obviously fall short where the target pixel can take on many different shades.  I also don't know if the apparent minimum 2-pixel wide search rectangle that FFNearestSpot and FFNearestPixel force you to use will always return exactly the same result as the 1-pixel-wide search line that is possible to use with the native pixel search.   

 

Edit:  The problem with doing this is that if you need to search multiple areas of the screen then FFsnapshot needs to be called every single time.  While faster, this is only about a 2x speed improvement over the native pixel search.  I've figured out a workaround, but it will take a lengthy although no where near complete rewrite of my program.  It would still be cool if anyone knows of a way to replicate the native Pixelsearch() while maintaining the 40x or so max speed increase that FFNearestSpot can deliver.  
 


 

Edited by UnitedStatesian
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...