Topics created by mashna1364

@mashna1364

Thanks 🙂

Are there missing signals on a normal backtest without Renko?

Not exactly. I expect this to fail the first time it runs, because the order of the blocks is like this - 147, 148, 149. After that it may work most of the time, but better connect the bucket blocks one after another.

select atttribute set 1 (numberic)

Try something like this:
0_1548369311963_6e87bf1d-7152-447d-93b0-7ac4efa72b01-image.png
This block will create a pending order at that price, which is Candle Close of the previous candle (because I set Candle ID to 1) + 3 pips (look in Adjust). The price offset is 0.

And the other way is to use that price offset parameter:

0_1548369419481_e5ac33a9-5179-4e12-89dc-6b3e548df11b-image.png

@josecortesllobat The ea in this post I mean please...

http://fxdreema.com/forum/post/25168

The way to do it is to always start again from the initial trade after all trades in the group have been closed. It should not matter if they have been closed in loss or profit. This is how most martingale EA's work.
Hopefully this change can be implemented soon to the system as it should be a relatively small issue to fix. It could also be added as on option to the buy/sell blocks.

I'm sorry but I'm not exactly sure of what you are trying to do. But maybe you could have a condition that on the bar before the signal that the signal is not valid?

i.e. for buy, candle low (2) < MA7 or candle low (2) < TEN.

Not sure if this is what you are after?

Also, why do you have a 'once per tick' block?

In your conditions you ask whether or not the indicator is green or red at the moment. Well, technically you are checking whether or not the values in the buffers are different or equal to EMPTY_VALUE. The thing is that obviously the green (or red) line stays green (or red) for multiple candles in a row. What you actually want is to detect when the indicator line turns green or turns red, you want to do something on the first "green" or "red" candle.

You can try "Indicator appear" block, this one detect when the buffer turns from EMPTY_VALUE to something else. Or try a condition like this:

Indicator x< (Numeric -> Value) EMPTY_VALUE

or...

Indicator x> (Numeric -> Value) 0

I didn't tested these conditions now, I might be wrong, but I think they will work.

In blocks 23 and 29 try x> and x< instead of > and <