SRL Archive - Revisions / Releases

Hello,

I've tagged Simba 0.98-rc5. It contains fixes that should fix any issues you might have previously had with FindDTM in Simba 0.98-rc1.

Note that this release may not be completely stable. I don't recommend everyone to upgrade, just the few brave scripters who want to play with the new CTS 3 and other new toys. Or people who just want to get Simba 0.98 out as soon as possible.

It won't eat your computer or files, but you may experience bugs. If you run into any issues that you didn't experience previously, let us know. And let us know about the other bugs you encounter as well.

Download the installer here http://simba.villavu.com/bin/Release/0.98-rc5/SimbaInstaller.exe or https://www.moparisthebest.com/jenkins/job/Simba_Next/28/artifact/SimbaInstaller.i386-win32.exe

(Or just grab the binary here https://www.moparisthebest.com/jenkins/job/Simba_Next/28/)

Changes since 0.98-rc1:

$ git shortlog simba-0.98-rc1.. --no-merges|cat
Cohen Adair (7):
      Extensions: SRLRemote.sex
      Edited Extensions/SRLRemote.sex via GitHub
      Edited Extensions/SRLRemote.sex via GitHub
      Made frm.position screen center (my taskbar always covered the top of frm)
      Removed Reflection from SRL updater and added SPS and MSI
      Emptied MSI updater so it doesn't conflict with new updater
      Renamed SRL remote and changed the name and menu option

GitBraK (3):
      Added Example for HoldMouse to Docs
      Add more Mouse+Keyboard Documentation
      More Mouse+Keyboard Documentation

Kevin Brightwell (1):
      Updated srl.sex to not use the reflection include.

Mark Janse (1):
      Add plugin memory manager setting.     Might be useful for passing objects between dll/app

Merlijn Wajer (19):
      Add SendKeys to documentation.
      More Mouse+keyboard documentation.
      Update documentation todo.
      Add GetProcesses documentation.
      Fix segfault in all DTM functions.
      Update lape HEAD..
      Add AUTHORS file.
      Fix FindDTMRotatedAlternating documentation.
      Bump version to 974.
      Finder: Remove double code.
      FindBitmapSpiralTolerance clean up.
      Update lape submodule.
      Export TMufasaBitmap.LoadFromTBitmap.
      Fix spelling.
      Fix spelling for lape too.
      Fix lp_file.inc
      Fix SendKeys example.
      Cleanup.
      Small fix.

Raymond (2):
      Removed Find*Optimised     XYZ is no longer treated as percentages (values from 0..1, instead of 0..100).     Added cts -1, which is only accessible from withint Finder (it ignores the tolerance parameter)     Made Find-functions that took no tolerance parameter use the tolerance version with cts -1     Inlined colour conversion for cts2 and cts3 (which should optimize cts2 'quite' a bit).
      Small bugfix in Font-loading

h (1):
      SPS Updater

What is the difference between CTS, CTS2, and CTS3?
Someone should edit ACA to work for CTS3 now too huh?
Thanks to all devs!

From: YoHoJo
What is the difference between CTS, CTS2, and CTS3?
Someone should edit ACA to work for CTS3 now too huh?
Thanks to all devs!

Exactly what he said. It would be really nice if ACA had CTS3 support.

Yessssssss SPS auto updater :D

Good work Wizzup? as always, using now.

FWIW, SPS updater can be acquired via the Simba Extension updater, so don't suggest newbies download this just yet :p

Just to let you know I'm playing with the new CTS3. It's have much more success finding small/difficult to spot colors than the previous CTS2. It probably differs based on the color, but if you're doing a color+tolerance search using CTS3 I recommend tolerance set at 1. ;)

I've been doing some testing oh Fishing spots. If I get around to it I'll post a couple examples between both CTS2/3 and the difference between color tolerance 1/2+.

From: Flight
Just to let you know I'm playing with the new CTS3. It's have much more success finding small/difficult to spot colors than the previous CTS2. It probably differs based on the color, but if you're doing a color+tolerance search using CTS3 I recommend tolerance set at 1. ;)

I've been doing some testing oh Fishing spots. If I get around to it I'll post a couple examples between both CTS2/3 and the difference between color tolerance 1/2+.

Well, if the tolerance is much too high right now (or quickly raises to unusable), we can add some modifier at least.

When is CTS3 going to be added to the ACA ?

It wasn't until I set the tolerance to 10+ (using CTS2) until I saw results to match CTS3 at tolerance 1.

Here's something I threw together quickly:

Function FindObjEx_F(Color, Tol, Bounds, Xs, Ys: Integer; UpText: String; Var X, Y: Integer; DeBug: Boolean): Boolean;
  var
     TPAA: T2DPointArray;
     TPA: TPointArray;
     CTS, I: Integer;
  begin
    CTS := GetColorToleranceSpeed;
    ColorToleranceSpeed(3);
    FindColorsSpiralTolerance(Xs, Ys, TPA, Color, MSX1, MSY1, 470, MSY2, Tol);
    ColorToleranceSpeed(CTS);
    if DeBug then
      SMART_DrawDotsEx(False, TPA, 65280);
    TPAA := TPAToATPAEx(TPA, Bounds, Bounds);
    SortATPASize(TPAA, True);
    for I := 0 To High(TPAA) do
    begin
      MiddleTPAEx(TPAA[i], X, Y);
      MMouse(X, Y, 3, 3);
      If WaitUpText(UpText, 300) Then
      begin
        Result := True;
        GetMousePos(X, Y);
        Break;
      end;
    end;
  end;

  Function FindObj_F(Color: Integer; UpText: String; Var X, Y: Integer; DeBug: Boolean): Boolean;
  begin
    Result := FindObjEx_F(Color, 1, 30, MSCX, MSCY, UpText, X, Y, DeBug);
  end;

I'll continue to play around, but it looks nice so far.

From: Flight

It wasn't until I set the tolerance to 10+ (using CTS2) until I saw results to match CTS3 at tolerance 1.

Here's something I threw together quickly:

Function FindObjEx_F(Color, Tol, Bounds, Xs, Ys: Integer; UpText: String; Var X, Y: Integer; DeBug: Boolean): Boolean;
  var
     TPAA: T2DPointArray;
     TPA: TPointArray;
     CTS, I: Integer;
  begin
    CTS := GetColorToleranceSpeed;
    ColorToleranceSpeed(3);
    FindColorsSpiralTolerance(Xs, Ys, TPA, Color, MSX1, MSY1, 470, MSY2, Tol);
    ColorToleranceSpeed(CTS);
    if DeBug then
      SMART_DrawDotsEx(False, TPA, 65280);
    TPAA := TPAToATPAEx(TPA, Bounds, Bounds);
    SortATPASize(TPAA, True);
    for I := 0 To High(TPAA) do
    begin
      MiddleTPAEx(TPAA[i], X, Y);
      MMouse(X, Y, 3, 3);
      If WaitUpText(UpText, 300) Then
      begin
        Result := True;
        GetMousePos(X, Y);
        Break;
      end;
    end;
  end;

  Function FindObj_F(Color: Integer; UpText: String; Var X, Y: Integer; DeBug: Boolean): Boolean;
  begin
    Result := FindObjEx_F(Color, 1, 30, MSCX, MSCY, UpText, X, Y, DeBug);
  end;

I'll continue to play around, but it looks nice so far.

Is it faster?

From: bevardis
Is it faster?

Theoretically, it will be slower. Its more calculations.. TIAS though.

Any feedback so far?

Durf, Just realized I got this and I've been getting those our of memory (or something) errors quite often now. Where you can click ok or cancel bla bla risk data corruption.

I'll try to catch it next time I see them and let you know.

That has happened on older Simbas too, I am pretty sure they are not new bugs. It happens to me usually when I load more than one Simba at once, they both try to load the font cache at the same time.

Yeah I'm aware it happened before too, it seems to happen more to me now though. But come to think of it… I think it happened most of the time when I had multiple open, so maybe it's nothing new.

I'm not sure what kind of bug you guys are talking about, so file a bug report please.

Regardless, the fact that you didn't run into any other issues is a good thing… :)