Jump to content

skimpniff

Active Members
  • Posts

    76
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by skimpniff

  1. Does "STRING_DELAY 50 %userprofile%\a.bmp" actually work? STRING_DELAY is ment to be a global setting like DEFAULT_DELAY. 50 seems too high of a number, In my testing STRING_DELAY of 1 worked great. Much higher was too slow. Here is an example

    http://www.iducke.com/Encoder/IDE/44

    In that example, using "STRING_DELAY 1" is exactly the same as if you did

    STRING t
    DELAY 1
    STRING h
    DELAY 1 
    STRING e 
    DELAY 1
    STRING q
    DELAY 1 
    STRING u
    DELAY 1 
    STRING i
    DELAY 1 
    STRING c
    DELAY 1 
    STRING k
    DELAY 1 
    STRING b
    DELAY 1 
    STRING r
    DELAY 1 
    STRING o
    DELAY 1 
    STRING w
    DELAY 1 
    STRING n
    DELAY 1 
    STRING f
    DELAY 1 
    STRING o
    DELAY 1 
    STRING x
    DELAY 1 
    STRING j
    DELAY 1 
    STRING u
    DELAY 1 
    STRING m
    DELAY 1 
    STRING p
    DELAY 1 
    STRING s 
    DELAY 1 
    STRING o
    DELAY 1 
    STRING v
    DELAY 1 
    STRING e
    DELAY 1 
    STRING r 
    DELAY 1 
    STRING t
    DELAY 1 
    STRING h
    DELAY 1 
    STRING e 
    DELAY 1 
    STRING l
    DELAY 1 
    STRING a
    DELAY 1 
    STRING z
    DELAY 1 
    STRING y
    DELAY 1 
    STRING d
    DELAY 1 
    STRING o
    DELAY 1 
    STRING g
    

    STRING_DELAY 50 worked fine for me whereas 1 was still too fast. I worked my way up to 3 and it was still too quick, so I just made the leap to 50 out of frustration and it worked. A lower number would probably work, I just wanted to be able to effectively test the scripts. Once I confirm they work properly, I will work on fine tuning the timing. I imagine it could be a variation in the way our VM's are setup. Theoretically, a normal computer wouldn't need the STRING_DELAY, right? I haven't seen this issue anywhere else in the forums other than referencing VM's.

  2. No love here eh? To clarify, I am not trying to add DELAYS to slow down the script execution, just to slow down how fast the duck types the actual keystrokes. It is entering incomplete commands because the VM Bus is unable to keep up.

    After some experimentation I have found the answer. To insert the delay between STRING character inputs, the proper syntax is

    STRING_DELAY N (where N is the time delay)

    I found STRING_DELAY 50 to work perfectly, ie.

    GUI d

    DELAY 500

    PRINTSCREEN

    DELAY 100

    MENU

    DELAY 300

    STRING V

    DELAY 40

    STRING D

    DELAY 300

    GUI r

    DELAY 700

    STRING_DELAY 50 mspaint

    ENTER

    DELAY 1200

    CTRL v

    DELAY 500

    CTRL s

    DELAY 1000

    STRING_DELAY 50 %userprofile%\a.bmp

    ENTER

    DELAY 500

    ALT f

    DELAY 400

    STRING K

    DELAY 100

    STRING F

    DELAY 1000

    ALT F4

    DELAY 300

    GUI d

  3. My question is the same as above, regarding the STRINGDELAY for slowing down the text input. I have the same problem, my VM bus can't keep up with the duck speed. So would a simple STRINGDELaY n preceding the command e.g

    STRINGDELAY 5

    STRING SomeText

    be sufficient or does a more detailed breakout need to be done, as in

    STRING S

    STRINGDELAY 5

    STRING o

    STRINGDELAY 5

    STRING m

    Thanks for the assist.

    No love here eh? To clarify, I am not trying to add DELAYS to slow down the script execution, just to slow down how fast the duck types the actual keystrokes. It is entering incomplete commands because the VM Bus is unable to keep up.

  4. If you use iducke.com you can specify a string delay. http://www.iducke.com/About/Features

    My question is the same as above, regarding the STRINGDELAY for slowing down the text input. I have the same problem, my VM bus can't keep up with the duck speed. So would a simple STRINGDELaY n preceding the command e.g

    STRINGDELAY 5

    STRING SomeText

    be sufficient or does a more detailed breakout need to be done, as in

    STRING S

    STRINGDELAY 5

    STRING o

    STRINGDELAY 5

    STRING m

    Thanks for the assist.

  5. Do you just enter this once at the top of the file?

    e.g

    STRINGDELAY 5

    STRING SomeText

    or do you have to :

    STRING S

    STRINGDELAY 5

    STRING o

    STRINGDELAY 5

    STRING m

    STRINGDELAY 5

    STRING e

    STRINGDELAY 5

    STRING T

    STRINGDELAY 5

    STRING e

    STRINGDELAY 5

    STRING x

    STRINGDELAY 5

    STRING t

    Was there ever an answer figured out for this?

  6. I am getting a similar problem. I am not sure if it is because i am testing in a VM, but when I test the wallpaper script it appears that the string is being typed to0 quickly. on some occasions mspaint is typed incorrectly, leaving some of the letters out, on other occasions the userprofile string is not getting some of the characters entered. obviously this means the commands are not getting executed as unrecognized text is being entered. can this be solved by changing the delays or is it simply the VM is not responding quick enough to keep up with the ducky? Any ideas? I don't want to try testing more complicated scripts until i can work the little bugs out first.

    I have found the answer further in the forum, my apologies for not looking further before asking.For reference see the post on page 2 titled "slowing down key strokes"

  7. turns out if you update the encoder to the newest one, and add a delay in between line 7 and 8, and 4 and 5 (i added 500 delay jut for debugging) it worked out fine. sorry for the dumb post. i was just reaching out for what ever resources i could

    I am getting a similar problem. I am not sure if it is because i am testing in a VM, but when I test the wallpaper script it appears that the string is being typed to0 quickly. on some occasions mspaint is typed incorrectly, leaving some of the letters out, on other occasions the userprofile string is not getting some of the characters entered. obviously this means the commands are not getting executed as unrecognized text is being entered. can this be solved by changing the delays or is it simply the VM is not responding quick enough to keep up with the ducky? Any ideas? I don't want to try testing more complicated scripts until i can work the little bugs out first.

×
×
  • Create New...