@VHV-Profit-Masters Happy to help. I did look at the latest version and when I adjusted to speed it up, it still took the same trades so I don't think there was a difference in execution. I think that at least when backtesting, it's important to leave off stuff that will slow it down because you don't want it to take hours to complete. It can always be added when you decide to go live with it. I added the visual because I like to see emotion on the chart and it helps understand when and where the EA does not so good.

@VHV-Profit-Masters Muchas gracias hemano

@sktsec ok thank you

@l-andorrà My brother, you are a crack, thank you for helping so many people in this forum...

@Safeer992 You need to do this:

00.png

Did you check if the custom indicator is compatible with fxDreema? That is the first step before moving on.

Do you really need those lines? You can store those values into variables instead and make the EA far more efficient.

Can you please open a new thread for your question?

Are you paying a full membership subscription? If you are not, you created a project with more than 10 connections between blocks. This is why the error popped up.

The problem is that you combined two indicators (MA and RSI) into the same chart window. Sadly, fxDreema cannot understand that. You will need a custom indicator combining both into one only file and then import it into your fxDreema account to be used in any 'condition' block.

so if you want to do it with history , use this

image.png

https://fxdreema.com/shared/AYXfqrZte

https://fxdreema.com/shared/AYXfqrZte

Try this ... https://fxdreema.com/shared/AYXfqrZte

@VendettaFX 👍

@VHV-Profit-Masters This was done by mistake 😖

@MT4stefano If you are using the standard 'pending order' block and you type 20, it immediately understands +20 pips for a buy and -20 for a sell. You don't need to use any symbol unless you want to consider subtracting (for a buy) or adding (for a sell).

@Johnster Yes, you can do it by using different group numbers, one for each different strategy to consider.

@Matatika You're welcome.

@MT4stefano The problem is that 'once an hour' block. It will limit the execution of all block below it to every o'clock hour. How can you be sure that the condition below the block will only be true exactly at that time and not every 40 minutes, for example?