Posts made by roar

Looking at the source, the time model seems to use TimeLocal() and TimeGMT() but then immediately remove the difference to server time - I wonder what's up with that @fxDreema

Also a good thing to remember:

When running a genetic optimization, sometimes the best results converge towards an inputs set that produces a very small number of very successful trades. This is usually a bad thing, because few very successful trades is statistically less reliable than a lot of semi-successful trades.

To avoid this optimization problem, you can code a custom criterion that takes trade number into account, but if you are lazy like me, you can use a "handicap": create some extra blocks that make 100% bad trades -> now the optimization discards all results with too few trades, because those trades cannot offset the intentionally bad trades. Input sets that produce a lot of good trades will have the upper hand in optimization.

Example of a simple handicap model:
https://fxdreema.com/shared/Jdk6zDAtb

@PauloSouza the lot size is set in this custom block. You can replace 0.10 with your constant name.

@El_Moein seems like it. Next step I would crete a fresh project and try again with the fxdreema block.

@zearma yes, but there is some oversight neither of us can see right now.

Ok, so compiling is not the problem here.
I need to see the loop and when does the loop end.

@BBMess MA method is always an enumeration by itself, that might cause problems.
https://www.mql5.com/en/docs/constants/indicatorconstants/enum_ma_method

Please send a shared link of your example

Can you show the error log of the metaeditor when you try to compile?

Does your loop ever end?

What does this output for you?

test.ex4
test.mq4

Is this a backtest chart or live chart?

@GTOAT777 the magic number can be found in the project settings

@Chikano11 Select price fraction and then select the ATR indicator

@slydexx naturally you need to check the current stop before modifying it. In the latest version you are modifying every position regardless of their stop.

Also, switch the "If position" block to a "for each position". Pink blocks always need a purple loop block as a parent. The blue blocks sometimes work, but they are not intended to work like that and thus not reliable.

@slydexx the block I mentioned isn't there