Posts made by fxDreema

Look from NOW to the PAST. This chart you can see - this is all past data which is available for calculations. The same with indicators. Everything you can see on the chart is represented as numeric values in MetaTrader and they are available in every moment.

EA works on every tick - when a new tick comes, you check something and do something if needed.

1. Check condition(s)
2. Do action(s)

To get the value of the Nth candle from the past, there is a Candle ID parameter. If it is 10, this means that you work with the 10th candle from now to the past. That means you can check NOW what was happened in the PAST. There is no need to remember if some condition happens NOW and check that in the future, because this event (and many others) will be in the database.

In short. When working with conditions in some EA, the way to deal with them is from now to the past - when a tick comes, you can have a condition that can check something that happened in the past only by setting Candle ID parameter (aka Shift parameter in MQL).

Well, at the moment there is no way to demo-test this because markets are closed. Let's do than on Monday

I think this will give multiple trades at once, when the signal comes...
It depends on the timeframe of course. 50 pips in 10 candles... there is no reason for these blocks to work only on backtest, so probably you have to wait more.
But when something does not happen, also check error messages.

Well, I'm trying...
This is a simple example of modifying SL in multiple levels: http://fxdreema.com/shared/fM82KlUme
More levels - more blocks, so I really have to create single block for this functionality, but now this is the way to do it.

Just a quick question outside this topic, but now when you export file, how long it takes to be created? Over or less than 10 seconds?

I should probably create some block that will be able to react at different levels. Anyways, when you do something, always try to make it with less blocks as possible. If you want to do something simple, but the number of blocks is too big, then this can be probably made in another way. If there is no way, you can always create a request for new functionality or new block.

Wow, this looks weird to me. But if your question is how to move SL when the profit is for example 10, 15, 18 and 24 pips, then there is a way, but not with Break even block. With loop. You have to check if the profit is 24 pips away from the open price. If yes - go to modify, use "(in loop) Once per trade" to not modify it multiple times. If no - go to the block that checks 18 pips. If yes - modify... if no - check 15 pips... and so on.

I can see your entire EAs actually, but if I have to understant it as a whole... this is hard task. Do you want to say that this EA was ok in the past, and now suddenly it stopped working? Can you understand what exactly is not working in it? I tested (in loop) blocks as you can see, but they seems to work, so I guess it's something else. Also, conditions are working. I think "OR" block is working as well. How are "Formula" blocks?

As you can see, I use "Draw arrow" block to check if something is working. If the block before "Draw arrow" passes, then there are arrows on the chart.

I think this works At least in this form: http://fxdreema.com/shared/r4qQ4YOqb (To backtest it easily, I only changed MA to 14 and SL in block 18 to fixed 50 pips)

I think it's something else, I just checked something simple and it seems to work. Do you have an idea what else can be? Some example EA maybe?

I tested if there is a problem with trailing stops - there are not. Why don't you just try it, it's simple? I don't understand the second question because we talks about virtual stops, not virtual pending orders, but anyway... try it.

Virtual stops are either enabled or not from the project settings. If they are not enabled - stops are normal hard stops, if they are enabled - they are horizontal lines with a little bit different colors. But virtual stops cannot be enabled from inside some block. And they are MQL4 only (for now).

So you tried them to do that and they does not work?

If there are no problems that I'm not aware of...
Virtual stops are there to replace the normal ones, so they must be able to be placed, modified, react to the market price (execute) and go away when the trade is gone.
Of course, they work only when the EA is working, so if you close the EA with virtual stops => then there are no stops. For that reason there is an option to place normal real stops at some distance, I call them "Emergency stops".

This must be fixed Be ready for the next bugs And Thanks of course!

Is it working now?

Indicators has buffers. Every buffer has a value all the time, even when the indicator line (arrow, histogram) is not visible. In this moment the value of this buffer is 0 or 2147483647, it depends on how the indicator is programmed. 2147483647 is the biggest integer value and in MQL4 is presented by a constant called "EMPTY_VALUE". Not all custom indicators can be used in EA, it depends on the programmer as well. Some of the custom indicators may have values on their buffers, or value that does not change, and that's why I created this block "Levels tester...". Now, when you know what the buffers gives to the EA and when, it's a matter of conditions to create a proper trading signals.

There is some problem with "Ask, Bid, Mid" in Condition and I have to fix it, but until then I can suggest to work with Candle Close (for the current candle), which is Bid and can be considered as the current market price.

Something is wrong with what I call "ticks collector", but you don't need this, so if you set "Tick ID" (left Condition operands) parameters to empty (not 0), it will work.

So you have 2 buffers - buffer 0 (blue one) and buffer 1 (red one). I think your file is ok, if there are no errors. But if you run the backtester and after it's done you can see the indicator on the chart - then it works fine.

Well, not all custom indicators use their buffers to connect with EA. Some indicators are programmed only to be used in manual trading mode, so their buffers can return constant value all the time, or some weird values. That's why I made this block called "Levels tester..." - to see in real time what is the value of a single buffer. This block it's somewhere on the top.