Posts made by fxDreema

Using this: https://fxdreema.com/shared/PIORYUWEc on the backtester I got this: http://prntscr.com/4r6shr
It's Sunday here, so I can't test it live, but on the backtester everything looks as expected, without errors.
What I can suggest is to forget about the optimization checkboxes. Use these for quick optimization, but not for official input parameters. Better use "Constants" for official input parameters. And by the way, Weekly and Monthly timeframes seems to not work in backtester.

Invalid SL or TP normally appears when SL or TP is on the other side of the Open Price, which is rare... especially when you use "Fixed pips" option. So I don't know, something is wrong, but I'm not sure it's the EA itself.

I'm playing with MAs because I don't have your indicator and everything is fine: https://fxdreema.com/shared/Vb0pXyjxc
Will this work for you?

Ok, this is simle. Look at the numbers of blocks - 1, 2 and 3. Blocks 1 and 3 are "first" or "top" or "initial" or however you call it... blocks. They are connected only from their outputs, so they are at top level and they will be executed from the EA for sure - on every tick. Which one will run first? The one with lower number - 1. Which one is next? When 1 runs and passes, the next one is 2. And finally - 3. Here is more about that: https://fxdreema.com/demo/blocks-execution-order

Otherwise you can try this: http://prntscr.com/4qyvvq If what you want is to make TP 3 times bigger than SL...

That is true, but sometimes depends. Sometimes is better for the EA to forget some things when it is restarted. And sometimes not But I don't use some fancy methods to save the current state of any EA when it is closed, all the EAs generated with fxDreema are very normal 1-file-only EAs, where no external files are used and no external files are written.

I am thinking sometimes - can I do something, so blocks like "Once a day" which normally have temporary memory, to store that memory also in external file, so in case the EA is reloaded - to continue from the same point. But there can be problems with that. What if you don't want and don't expect that? What if you remove the EA and add it again with different input parametes (different behaviour of the EA) - if you have "Once a day" block or something similar that will load some state from external file when the EA is loaded, this will probably make the EA to behave differently than expected. Not to mention if variables are saved and restored...

So it's always better to make the EA in a way to continue from where is it, or start again if that is needed. I prefer to use the trades itself as a memory - their open prices, stops, lot sizes are keeping some information and it can be used.

Otherwise I can't understand you in the last few posts - is it working or not... let's say that I don't understand your english very well. And I am also not native english, so...

There is a block named "Indicator tester" which I use and recommend to be used to check what a custom indicator gives to the EA as values. If you got normal price values (like 1.2345) then everything should be ok. If the value is 0 or looks weird, then try with Candle ID bigger than 0 - often indicators are made to work on the previous candle, or even at older candles.

So I can see you are using custom indicator for the open price. Are you sure it's giving you correct values?

I think that "at the end of the day" part is missing. Now I guess you have too much trades, because it's very easy for them to be closed. So I can suggest to use "Once a day" or some time filter like "Time filter" or "Hours filter"... something that will cause the "Close trades" block to run when it's needed only, not all the time when RSI is between 20.5 and 79.5

This is some bug and I have seen it before. I will look at it tomorrow

I can see that there are too much Formula and Modify Variables blocks Setting and modifying a variable is something really simple actually, but when it takes a whole block or group of blocks... you can see how bad it looks. But how can we do this with blocks and without writing code? I can suggest to use the "Adjust" fields when possible, also use this side panel "Variables" which you can see in every block's settings window. In both places you can write anything and it will go directly into the code. I can also suggest "Custom MQL4 code" block.

And connecting these blocks like this in parallel... I don't know why people prefer to do it that way, but this creates problems sometimes. Note that when you have blocks in parallel, which one will run first, do you know? So it's better to connect them one after another, just in case.

I added this EA, I used only 5 candles to calculate "support" and "resistance", so at the end the value of "grid_space_factor" was something like 5 pips... and I got bunch of trades close to each other with about 5 pips. So it probably works.

I fixed "once per order/trade" before, because you had another kind of problems with it. I added a simple check in it - to work only with trades created after the EA was added to the chart and skip all the trades and order that are older than that. So if you add the EA when you already have trades - the block will not work and will start to work when these trades are being closed and new ones are created. At least this is the idea.

So what stops are you using? I can see that you have checked these parameters as input parameters, so they are probably not as default

Simply uncheck the "Compare" parameter. And use those checkboxes only when you want to quickly optimize some parameter. For real input parameters I will recommend to use the "Constants"

"Candle Close" is the candle's close price, this is not an event.
The crossover basically works, it's a little bit pain in the .... to control it

Here https://fxdreema.com/shared/V1ekNf88 I decided to work when the new candle opens, so I shifted the Candle Close value and and the indicator value with 1 - to look at the previous candles, not the current one which is newly created and it's still just a point. But it depends.

Are you sure that your indicator is giving you values at all? Check it with "Indicators tester". Sometimes indicators returns only 0 on the current candle, so it's needed to set Candle ID to 1 or more. Just make sure that you are using some values different than 0 or EMPTY_VALUE (which is some giant number).

The problem of the last project is that "grid_space_factor" is calculated only when there are no trades, and this is global variable for the EA which goes away when the EA is restarted. If you add the EA when there is Buy and Sell trade, the variable does not have a chance to be modified. Possible solution -> "Counter: Pass once"

Normally I turn on and off MetaTrader and charts all the time, if I have to wait hours and days to see if a strategy is working live...

Here is how to detect when there are problems:

• You are not sure if/when a block is passing (orange output goes active) - just connect "Draw Arrow" after the orange output.
• You are not sure about some value? Use "Indicator tester" block, it will draw a line on the chart, which will be the history of values. Additionaly, it will print the values below the candles, so they will be visible even if the values are too big or too small to be seen on the chart.
• You are still not sure about some value? Use "Comment on chart" to print it on the upper left cornet. Multiple values can be printed.
• Still not sure about some value? Use "Custom MQL4 code" block with code like:

Print("My Variable Value Is: " + variable_name);

This was the Print() function, but the Alert() can be used as well. They are described here:
http://docs.mql4.com/common/print
http://docs.mql4.com/common/alert

• Make initial tests using lower timeframes and stops, to make everything faster
• When you have groups of blocks, make sure that block IDs are ok. Lower numbers are executed first, so the group where the first block has lower number - it will execute before the group with greather number
• There is some difference between backtest and live trading. On live you have previously closed trades and orders, while in the backtest there is nothing in the history. On live there is a delay when creating a new trade/order, and sometimes they are created on a different price (slippage). Also, sometimes errors happen on live, so...
• ... always look at the logs for eventual problems

Where you can see (each trade), then this block does what it does to each trade independently. It gets the first trade - it does what it does, then it gets the second trade... until it checks all the trades available.

Where you can see (group of trades), it first calculates the average value of what is needed (like the open price) of all trades, then it modifies what it needs to be modified (like the SL values) for each one, one by one.

Now "once per trade/order" blocks works only for trades/orders created after the EA was started, not for older ones.
I just added this EA to see what is going on, and on my live demo account the value of grid_space_factor is something like 60, which is bigger than the 50 pips required to close the trade on profit, so maybe this also makes some difference.

Normally we can get candle and indicator values from different timeframes in the same chart, at least for Daily and below. Try this: https://fxdreema.com/shared/PyvfiGR0e and you will see the current values of 3 MA-14 indicators with different timeframe settings. There is probably something else

I'm not sure if other charts can be opened from an EAs anyway. At least I don't know for a MQL function to do that, and I don't know for something else as well. And the list of... anything... means that arrays will be used, but in fxDreema the work with arrays is hardly possible. Even the work with variables is too much. There are some things that are easier to do in code generator like this, and other things that are easier to do in plain code, I think that arrays are more suitable for plain code

CurrentSymbol() and CurrentTimeframe() - these are custom functions that I use for the "Current..." blocks. You can use them, but if some day I decide to remove them or change their names, they will stop to work

What about the crossover options in "Condition" block? They do this: https://fxdreema.com/documentation/proj ... er%20works