Thank you very much footon.I will do as you say.I really appreciate your help.Green pips to you Good Sir.

hi footon! how are you?

I wanna ask you a question, I try to do a indicator for DEMA, but Im not a good programer and I the end, I cant.. I try to modifie and usage as example one indicator  that you do time ago, the "EmaPredictive MA Crossover.cs", without success.

and I wanna ask you if you probably already have DEMA or TEMA in your collection.

thanks!

How's this for that purpose?

https://forexsb.com/forum/post/20890/#p20890

I'll do it in due time.

Zenoni pointed out that Choppiness Index is behaving contrary to its principle. He is correct!

But while looking through my indi archive, I found out that I already have corrected the indicator, but for some reason the repository has the initial version.

I will post the corrected one here, I assume I have done this before already. But the question is whether I should designate the "correct" version as V2. Probably a lot of users are using the initial one and there might be reliance to that particular version, the fact it works oppositely to the way it is supposed to work doesn't mean it cannot be used profitably.

So, if there are no opposing voices, I will rename the "true to the principle" version as V2 and upload it to the repo in the near future.

footon,

I have written some EA using the Adaptable MACD indicator, in some instances is great in others it does not make sense .

I have tray to compare it to the regular MACD but not a clue .:(

Since you wrote this indicator could you please send me logic behind it so I will be able to use it properly.

Thank you.

Following a simple EA using the Adaptable MACD( but the results are too good or too bad- but the logic dos not follow the execution on the EA - which make me think that there is something wrong, or I do not know what I am doing):
Logic
Opening (Entry Signal)
Open a new long position at the beginning of the bar when the following logic condition is satisfied:

Adaptable MACD* (Exponential, Close, Simple, 26, 12, 9); the MACD line rises [EURUSD H4].
Open a new short position at the beginning of the bar when the following logic condition is satisfied:

Adaptable MACD* (Exponential, Close, Simple, 26, 12, 9); the MACD line falls [EURUSD H4].
Closing (Exit Signal)
Close an existing long position at the end of the bar when the following logic condition is satisfied:

Adaptable MACD (Exponential, Close, Simple, 26, 12, 9); the MACD line falls [EURUSD H4].
Close an existing short position at the end of the bar when the following logic condition is satisfied:

Adaptable MACD (Exponential, Close, Simple, 26, 12, 9); the MACD line rises [EURUSD H4].
Handling of Additional Entry Signals**
Entry signal in the direction of the present position:

No averaging is allowed. Cancel any additional orders which are in the same direction.
Entry signal in the opposite direction:

No modification of the present position is allowed. Cancel any additional orders which are in the opposite direction.
Trading Size
Always trade a constant number of lots.

Opening of a new position - 0.01 lots.

I encoutered an issue with Ichi M indicator. I try to use this indicator in Closing Logic Condition. I exported the strategy into MT4 and after I attached the strategy int MT4 chart I will get this error:

2022.01.02 10:12:47.156    12950_USDJPY_30min USDJPY,M30: 12950_USDJPY_30min loaded.
2022.01.02 10:12:47.161    12950_USDJPY_30min USDJPY,M30: Loading data: USDJPY,M30, Minimum bars: 88...
2022.01.02 10:12:47.162    12950_USDJPY_30min USDJPY,M30: array out of range in '12950_USDJPY_30min.mq4' (3882,27)
2022.01.02 10:12:47.163    12950_USDJPY_30min USDJPY,M30: not initialized
2022.01.02 10:12:47.163    12950_USDJPY_30min USDJPY,M30: uninit reason 8
2022.01.02 10:12:47.165    Expert 12950_USDJPY_30min USDJPY,M30: removed€€€€€

Happy New Year!

Ichimoku Kinko Hyo M is a custom indicator created by Footon, you can find the indicator under this link:
https://forexsb.com/forum/post/31971/#p31971

I exported the strategy again using FSB 3.8.10.0, but the problem is still persist

Excellent!

I also took a look at the file.

Is it in the firstBar calculation?

Edit:

missing initialization of Componnet[6] ?

   ArrayResize(Component[6].Value,Data.Bars);
   Component[6].FirstBar = firstBar;
   Component[6].DataType = IndComponentType_Other;

))))))))))))))) Coool!

Have sweet dreams now!