fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search

    I have an icustom script from an author of an indicator, but I have no idea what to do with it? The buffers were not registering when I manually entered them...

    Questions & Answers
    2
    6
    2188
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      MIKEIKE last edited by

      Hi,

      Can you offer some guidance?

      double CIvalue = iCustom(NULL,0,"Choppiness Index",14,1,1,1,0); // Current Choppiness Index Value

      Thanks,

      Mike

      1 Reply Last reply Reply Quote 0
      • fxDreema
        fxDreema last edited by

        iCustom() is a function that loads custom indicators and gets their values. In this case the indicator is called "Choppiness Index", you probably see it as a file named Choppiness Index.ex4... assuming that we are working on MT4. The indicator has 3 input parameters, all with type "int" and values 14, 1, and 1. The last two numbers are the buffer index (1 - the second buffer) and the candle index (0 - the current candle). If this is MQL5, then all the numbers are input parameters, because iCustom() is used in a little bit different way there.

        I will suggest to manually add this indicator in "My Indicators". If you have its .mq4 file you can even "upload" it. Then you don't need to write this function anywhere.

        1 Reply Last reply Reply Quote 0
        • M
          MIKEIKE last edited by

          I found the problem and it may be common with other users.... I successfully manually entered the indicator inputs and buffers with FXDREEMA, but I realized that when you download a custom indicator from the MQL5 community marketplace the indicators download to a Market Folder. I just needed to copy the file and place it in the Indicators folder and then it worked.

          I am not sure if other users figured this out, but marketplace indicators download only .ex4 files so you must manually enter inputs and buffers through FXDREEMA indicators. If you don't match the inputs in order, it won't work. Duplicate the inputs, define the buffers, BUT most important is to copy the .ex4 file from any subfolder (Market or any other) and paste directly in the MT4 indicators file. This will solve a world of grief figuring it out.

          1 Reply Last reply Reply Quote 0
          • M
            MIKEIKE last edited by

            However, My current issue is related to our email. I am using MQL4 and I am setting up my EA to run on a VPS. Since I run multiple charts, I want to reduce memory and CPU usage by simply loading the EA and NOT attaching the indicators to the charts.

            I run daily chart trades so I cannot clearly tell if the EA is functioning properly. I have some custom indicators where I had only the .ex4 file and I'm not sure if any of these indicators need to be attached to charts in order for the EA to work properly. Can you advise?

            1 Reply Last reply Reply Quote 0
            • M
              MIKEIKE last edited by

              I found another issue... The error on tester says one of my indicatorers where I only have the EX4 file is error : "Shortname too long". It appears that the EA still functions and trades, but I'm not sure if this is going to be an issue running the EA live?

              1 Reply Last reply Reply Quote 0
              • fxDreema
                fxDreema last edited by

                If you have indicator in a subfolder in MQL5/Indicators, then in fxDreema you can add the subfolder in the name field. If the indicator is named "indicator", then you can write "subfolder/indicator"

                No, you don't need to manually add indicators on the chart. The EA is connecting with the indicators on its own, you can't see this process.

                "Shortname too long" - if this comes from the indicator itself, then I guess you can't help much. I think that this is some property of the indicator itself and is located in its code, but you don't have that code anyway.

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post

                Online Users

                M
                A
                M
                W
                E
                G
                K
                E
                A
                S
                O
                S
                A

                22
                Online

                146.7k
                Users

                22.4k
                Topics

                122.6k
                Posts

                Powered by NodeBB Forums | Contributors