Posts made by josecortesllobat

@maty

https://fxdreema.com/instructions/builder/things-not-to-do

Es preferible usar la apertura de vela en lugar del cierre de vela. Ten en cuenta que una vela nueva empieza justo después que cierra la anterior. Por tanto, se puede decir que la apertura de vela nueva el lo mismo que el cierre de vela anterior.

Entonces, del último proyecto que has compartido, prueba esto

Bloque 1 (superior) -> "Once per bar" (el proyecto se ejecutará cuando abre una vela o, si prefieres considerarlo de esta forma, cuando ha cerrado la vela anterior)

Añade los bloques de acuerdo a tu proyecto.

De acuerdo a tus condiciones, estás comparando valores del indicador en la vela 1 (última) con la vela 2 (penúltima). Si son ciertas, se ejecutan los bloques siguientes.

I totally support @roar suggestion.

My way is to test the EA on a demo account with those parameters sets that passed my acceptance criteria and let them work to see if the results are consistent and accordingly to the optimization results.

There could be many ways to do it. You just need to find one for which you feel confident with.

1st graph is the optimization results for the IS (In Sample) data where the Expert Advisor has been testing all the parameters combinations according to the genetic algorithm search and the fitness function.

2nd graph is the forward test results for the OOS (Out Of Sample) data where the EA test the best parameters combinations that had good results in the IS data.

https://www.metatrader5.com/en/automated-trading/strategy-tester

Take a look at the first block of your project

If you choose "Group mode" to pick up a specific trade, you have to fill in "Group #" field. If you do not set anything there, the block will never be true.

If you choose "All", none specific trade will be picked up.

Sí, se ejecuta en cada tick en modo de prueba al tick o demo/live. Si pruebas en modo Open Prices, sólo se ejecutaría en la apertura de vela.

Mi consejo para probar si un bloque (o rama) se ejecuta y verlo visualment, es conectarle un bloque del tipo "Draw arrow" o "Draw text".

Are they working with other brokers?

I have a Swissquote demo account but I did not add any EA created with fxDreema to run there. I am currently using Darwinex to test my EAs and they work pretty well.

Candle 0 is still being formed. So the indicators values might change as well.

https://fxdreema.com/instructions/builder/crossover

@leventecsibi

You will have to see if you have set the CANDLE ID in the "Condition" block in order to specify in which candle the condition must to be checked out.

https://fxdreema.com/instructions/builder/indicators#3

@Javed77 If you want to check the conditions at the bar´s open price, you have to set the candle´s ID where your code will be executed

https://fxdreema.com/instructions/builder/indicators#3

It is usually not good to mix "pink" blocks with "blue" ones.

Try this

Yes, it's like that in MT4.

The behavior is different in MT5.

Try to set a candle's ID where the condition will be checked

@khalids222 Candle 0 does not have Close price because is still being formed. Close price (0) depends on the Ask/Bid (Mid) price and changes while the the price moves. For that reason, those specific blocks were developed on fxDreema. They look for crosses between the price and an indicator.

Give it a try with

Price x> Indicator
Price x< Indicator

I would suggest to calculate the trailing step beforehand.

This could be a starting point for a long trade.

OpenPrice = 1.00000 (get the openprice as a variable)
PointSize = 0.0001 (get this value from the market properties)
PercentToMove = 11%
TrailStepPercent = 4%
TrailStopLevel

PriceToMoveStopLoss = OpenPrice + PercentToMove = 1.00000 + 1.00000*(11/100) = 1.11
PipsToMoveStopLoss = (PriceToMoveStopLoss - OpenPrice)/PointSize = (1.11000 - 1.00000)/0.0001 = 1100
TrailStepPips = PipsToMoveStopLoss x TrailStepPercent = 1100 x (4/100) = 44
TrailStopLevel = StopLossLevel + TrailStepPips (as a price fraction)

If Price (Ask, Mid, Bid) >= PriceToMoveStopLoss -> {Move stop loss to (SL + TrailStepPips as price fraction) AND Modify [PercentToMove = PercentToMove x 2 (or +11) AND TrailStepPercent = TrailStepPercent x 2 (or +4)]}

As a project, something like

It does not look very polite but it can be improved.

Don´t forget to reset variables to initial point when a new trade opens.

Hope this might help a few.

"If Testing" block is working correctly on my projects

I saw the first minutes of the video shared and this is my opinion

IS = 5 months
DD = 7629.68
Max. Consecutive Losses = 156 (6578.52)
%WINS = 5.51
Av. Loss =34.25

Your average risk per trade is (34.25/200)*100 = 17.125 what means that you will loose your account if 5.83 (5) consecutive loss trades happen. Accordingly to your maximum consecutive loss streak (156), there is a high probability to loose your account. In addition to that, there is a Max DD of 7629.68 in a 5 months period what it should be considered enough to do not trade this strategy,

BUT...IT´S JUST AN OPINION

There are some simple programs available at the How To page that are good to be used as a starting point

https://fxdreema.com/howto
https://fxdreema.com/howto#Simple-Programs

The one that you can have as a reference is

https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions

You should walk in fxDreema starting from its instructions page

https://fxdreema.com/instructions

As well as in the HowTo page

https://fxdreema.com/howto

You will get resolved most of the questions you have using the builder.

What you are lookin for is: