Results 1 to 7 of 7

Thread: Invalid DTM-String

  1. #1
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default Invalid DTM-String

    I was running a script smoothly for an hour then suddenly the script was forced terminated and this error is written:

    Error: Exception: Invalid DTM-String passed to StringToDTM: mrAAAAHic42BgYMhlYmBIBuJyIC4F4hQgLgPiaiAuAeInQDWvg fg+ED8D4vdQDBK/BcS9BloMHXHWYMzLwwMUYULB/EASH2ZCw4xoGAYA/y4OqA== at line 1042

    The file antiban was opened, and the DTM-String matches oneFreeSpin. I have no spin ticket at that point, but I'd seen the function working and solving the free spin in the past. Any idea what's causing the error?


    EDIT: a similar error occurred for a different string:

  2. #2
    Join Date
    Aug 2012
    Posts
    4
    Mentioned
    0 Post(s)
    Quoted
    0 Post(s)

    Default

    I have the same problem, it occurs in both antiban and rewards.

    It only happens rarely, like once every hour or so. If you run 16 bots at once it happens to one about every 10 minutes.

  3. #3
    Join Date
    Jun 2012
    Posts
    4,867
    Mentioned
    74 Post(s)
    Quoted
    1663 Post(s)

    Default

    Quote Originally Posted by sl3 View Post
    I have the same problem, it occurs in both antiban and rewards.

    It only happens rarely, like once every hour or so. If you run 16 bots at once it happens to one about every 10 minutes.
    I've never had this happen so it is less frequent than once every hour. You thought the number of smarts open affects it, how many were open for the once every hour one?

  4. #4
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default

    Quote Originally Posted by BMWxi View Post
    I've never had this happen so it is less frequent than once every hour. You thought the number of smarts open affects it, how many were open for the once every hour one?
    He doesn't mean the no. of Smart opened affected the frequency. It's like if you have 1 Smart open and you get the error every hour, and if you have 6 Smart open statistically you get the error every 10 min (on one of the Smart opened), assuming it follows a Poisson distribution.

    This error is intriguing because the DTM string is actually valid, so i have no idea what's causing this. (Possibly some memory bug with Simba?)

    Is anyone else experiencing this? If not i may try re-installing Simba to see if it solves the problem.

  5. #5
    Join Date
    Jun 2012
    Posts
    4,867
    Mentioned
    74 Post(s)
    Quoted
    1663 Post(s)

    Default

    Quote Originally Posted by riwu View Post
    He doesn't mean the no. of Smart opened affect the frequency. It's like if you have 1 Smart open and you get the error every hour, and if you have 6 Smart open statistically you get the error every 10 min (on one of the Smart opened).

    This error is intriguing because the DTM string is actually valid, so i have no idea what's causing this. (Possibly some memory bug with Simba?)
    Is the issue only with some people then? I've never had this despite running one smart regularly for more than an hour. I'm using smart 8.0 and simba 991 if that helps.

  6. #6
    Join Date
    Feb 2011
    Location
    The Future.
    Posts
    5,600
    Mentioned
    396 Post(s)
    Quoted
    1598 Post(s)

    Default

    Perhaps the DTM string can't be decrypted properly. Decompressed->Base64->FindDTM, etc..
    Last edited by Brandon; 10-26-2012 at 02:50 AM.
    I am Ggzz..
    Hackintosher

  7. #7
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default

    Quote Originally Posted by BMWxi View Post
    Is the issue only with some people then? I've never had this despite running one smart regularly for more than an hour. I'm using smart 8.0 and simba 991 if that helps.
    Yeah that's what i'm trying to find out. I'm using the latest Simba/Smart as well. This error isn't bothering me now though since i did a hard-coded bypass but would be good if anyone shed some light on the cause.


    EDIT:
    Got a new error today:
    Error: Exception: The bitmap[3] does not exist at line 651
    Simba Code:
    Function FoundBar: Boolean;
    var
      X, Y: Integer;
    begin
      Result := FindBitmapToleranceIn(SRL_NAVBAR_BITMAP, X, Y, 482, 20, 489, 29, 10);
    end;

    Seems like there are some memory bugs to do with Simba?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •