Posts made by fxDreema

It always happen to me to do something stupid as well, we are on the same boat

Use "Indicator tester" block to test and find buffers, like this: https://fxdreema.com/demo/mt4-indicator-tester
There is more info about indicators here: https://fxdreema.com/documentation/gett ... indicators and here: https://fxdreema.com/documentation/proj ... indicators

"Indicator appear" works when indicator value goes from EMPTY_VALUE (or 0) to a price level

No, there is no such thing like "after" here. Conditions are checked on every tick, again and again, multiple times per minute and sometimes multiple times per second. Everything happens at the moment - if all conditions are true, "Once per bar" is reached and a new trade is created. Then, most probably the conditions remain true, but "Once per bar" will not work until a new candle is created.

Do you have some logs or screenshots? I don't know how much time it will take if I put this EA to work on a live account

https://fxdreema.com/shared/vdsS1O2Ec

Something like this, but not this. The problem here is that new pending orders are created every day, and at that time there can be an old trade still running. Then, because I used "No trade/order exists", a new pending order is created when everything is closed (no orders, no trades) and at these moments the last closed trade is... who knows how old is it. Some trades will be missed.

https://fxdreema.com/shared/0FhOX0hN

This is similar, but not the same. Note that "once per trade" have memory that is cleared when the EA is reloaded.

At least you can get some idea

At the beginning of the new candle, are all of the conditions true?

This EA also uses multiple timeframes - M30, H1, H4, Daily. I will suggest to check your indicators with "Indicator tester". Who knows, maybe there is something that I am missing here. And also be sure that you are using this EA, not some other EA with the same name

30 min CCI EURUSD? This should be able to open a new trade in the middle of a candle, because "Once per bar" is after the conditions, and conditions are for candle 0. But it's probably not impossible to meet all conditions right in the beginning of a new candle?

What is closed by SL is the trade that is result from your pending order, so you are going to work with it. There are different ways to do that.

• Use "on Trade" event to detect when the trade is closed by SL. The downside is that this event is generated by the EA in the moment when the trade is closed, so if for some reason the EA is not working at that moment (you have closed MT or remover the EA from the chart), the event will be missed.

• Do it under "on Tick". You can check if there is no trade at the moment, then check the last closed trade - if it was closed on loss, create new pending order using the same parameters from that closed trade (Open price, SL, TP and lot size). There are no events you can miss here, but imagine if you close the EA for some hours and then run it again - it will create a pending order where the last closed trade was, but hours later the price will be... who knows where.

Here is some way to do that: https://fxdreema.com/shared/bA2I4HVQ
The other way is to calculate SL and TP before Buy now/Sell now
And the other way is if I add "% of..." options in Buy now/Sell now blocks, similar to block modify stops. In any case, what do you prefer - % of... (where you write values like 100, 200, 50, 25) or times from (where you write values like 1, 2, 0.5, 0.25)?

These options are similar to the same in the regular trailing stop. Trailing stop mode = where to place the stop, Trailing Stop = how often to modify it. Yes, the step can be 0.

When I first made this block, it was with horizontal line. But then I modified it a little bit and now it draws these numbers. What they mean is that when the profit becomes 2.52, trades will be closed, but now the profit is 5.1. In other words: Current Profit => Trades will be closed when the profit becomes this. These numbers comes from the block, MT4 itself does not have such options.

Try this option "% of group profit". But in this case you need to use some "Start", because initially your profit is too low and everything will be closed within seconds. So you need to delay, to reach some profit first.

Condition -> Value -> Numeric -> right-click over the input field and choose the variable from the list

Those variables you are using are also called global variables, but they are different kind of global variables

Hopefully, but the chance is that this parameter does not work at all, because the broker itself does not work with it I think I read somewhere that this is normal for ECN brokers.
Someone was asking the same question and I did some tests with OrderSend() and different values for it's slippage parameter - I still got trades with slippage, no matter what value for slippage I used, and I tried values like 0, 1, 10, 100, 1000 and negative values. I don't remember which broker I used for this.
Don't rely on this parameter too much

Yes. Back then I decided and created this "Status" message and the block within... 4 hours. It was pretty fast, so maybe not the best idea But some people are using it. I tried to remove the block in the past and somebody wrote to me like you. But... you know, there are variables, there are flags, there are objects... many things that can be used as a temporary storage. Do you really want to see your temporarily saved value on the chart, or you just don't know how to use regular variables?

This block was used to read the text from some object, but I decided that it's better to do that by using normal variables And I changed the default values of this status text, which is something that I want to be able to do without wondering "Is anybody using those default values now in the Check Status Message block?"

Here is some example... https://fxdreema.com/shared/EWkOD5r9d

No, you can't upload .ex4 file, fxDreema does not understand it's code. You can open such a file in a text editor and you will see why. But MetaTrader can understand this code and you can see all input parameters and buffers, so at the end you can add this indicator manually, by writing it's parameters manually.

It looks like this for me: http://prntscr.com/5o6ltw I think that it's fine. One of the slow MAs is exponential, that's why there are two long MAs over there, but this is your project. Otherwise it looks correct for me.

If you are talking for those moments that does not look as a crossover AFTER the backtest ends, then this is because the current candle is used for the crossover and as you know, the current candle is unfinished. So there were some crossovers that "disappeared" before the current candle's end.

You can add it to fxDreema manually:
https://fxdreema.com/documentation/gett ... indicators
https://fxdreema.com/documentation/proj ... indicators

The best will be to inspect the last X candles for this cross, but this is not easily possible in fxDreema. This is something that indicators normally do.
But I will suggest to use some variable to set it to some value when cross happens, and then check that variable when you detect bear/bull candle.

Put the output .mq4/mq5 file here (project data is appended at the end of the file). Also .xml file can be exported