Posts made by roar

@aramsamsam69
No need for that... int means whole numbers, double means numbers with decimals, candle ID is whole number.

I'm not sure what is wrong here.. Try troubleshooting piece by piece:

• Maybe the "(loop) break" causes some bug, originally it's not really meant for this purpose
• Maybe there is something wrong with the custom indicators, try some simple default indicator
• Your top block "Once per tick" is useless, if you are on the OnTick event in the first place:
  

@aramsamsam69 said in Two Condition Trees but if both are true only one of them should trigger a trade:

Did I make a mistake?

Yes, a tiny one

We must reset the ID_var to 0 before the loop work begins. If we don't reset it, the variable will remember its previous value from some earlier calculations: at the end of your test period, ID_var is probably something like 2458

So, put 0 to the white field

Oh, @l-andorrà is totally right - I didn't see your shared

How "once per bar" works here:

• let's say a bar consists of 60 ticks ("events")
• orange will be active on tick 1
• yellow will be active on ticks 2-60

Try putting some filter to that loop block, for example "Not more than 1 trades" starting from newest

The loop should be able to pick them up:

@eli The "once per bar" block. As the name says, that block will limit everything below it to max 1 times per bar.

The numbers don't mean anything if all your logic is in one long string

@adrinicu
I didn't fully understand you, but start with this:
https://fxdreema.com/shared/TAzsDUI5e

It will buy when price is above previous candle high, and
sell when price is below previous candle low.
You can also change the timeframe.

I'm sad to hear you took losses. Please, take your time to develop your EA, the market will always be there, don't trade before your system is ready
Make use of the backtest function!

This is even better, if your system allows it:

@eli Do this:

@marianomartinez You are using the program "showcase". The actual builder is at https://fxdreema.com/builder

@marianomartinez
You must have the same ID on all indicators:

Finally, we should take care of the fact that this loop system could find multiple crossings, so it would open multiple trades.
If this is not what we want, just put a loop break block after the buy - loop will stop at that point.

@aramsamsam69 said in Two Condition Trees but if both are true only one of them should trigger a trade:

@roar sorry to bother you again.

How can I build this.

Condition 1 : If Price has crossed Moving Average to the upside, then enter Long.

Conditon 2 : But only if the 2 Lines Indicator also has crossed above, doesnt matter if it happened at the same time. But the Crossing shouldnt be older than 7 Candles.

For this, I'd introduce a loop logic. Its a bit more advanced thing, but not too complicated.

• First, check that MA cross

• Next, we are going to check two lines indicator 6 times in a row (I don't have that indicator, so using simple MA in the example). Each time we check the indicator, we use a different candle for the measurement. That is accomplished by the candle ID setting. ID 0 is current candle, ID 1 is last completed candle, ID 2 is 2nd completed candle etc.

• I created a variable for the ID setting, called ID_var

• This variable is set to 0 at the beginning of work, and each of the 6 iterations it is increased by 1.

• Now the loop cycles setting will determine how old the 2line crossing can be - you can change the number at your will

https://fxdreema.com/shared/Lxyio0Gbd

@aramsamsam69
Hmm, maybe it's easiest to put some filter before the trade block:

@alphaandy Ah, ok, so all the conditions will be simultaneously true, even though the exact crossing points aren't.
The EA you built should work as expected.

Do you want to check conditions on closed candles, not active candle? In that case, use candle ID 1 in these settings:

By default, its empty, that means candle 0, the current candle.

@alphaandy Ok, this complicates the build a bit.. You see, normally the EA works tick-by-tick, everything that happened last tick will be totally forgotten when a new tick happens.

To "remember", we have to use variables

@alphaandy Technically it's fully working EA. If you chain the conditions like that, the order doesn't matter. The EA checks the conditions on each new tick.

Do you want all the conditions to be true simultaneously, or can there be time difference? Like, today the accelerator condition is ok, tomorrow the rest of conditions are ok but accelerator is not -> open trade?

@alphaandy
The logic flow in the picture is correct, nothing wrong there.

See the Close trades -blocks, have you filtered them to work on only buys / only sells?

Hi @emaniek!

Bombarding the admin with a dozen emails will not help, I'm afraid.
He will answer your messages, eventually.

If it's a technical challenge, I'ts usually faster to ask from this forum, there's more than 1 person answering.

@specialfx Yes, that's a logical error in some function. Check that line 6099 from your .mq4 code.