Posts made by roar

@pei Hi!
I don't see any mistake in the blocks overview. Perhaps there is some small setting wrong.
Maybe your "if trade" counts only buys?
How about the "close trades", is it filtering only buys?
Did you remember to use ID1 in all calculations, candle ID and bollinger ID? The bollinger indicator ID is hidden in the "more settings" section:

This error can be more confusing, as the stop-loss doesnt seem to use any timeframe:

But it is hiding in the drop-down menu, "Custom (pips)". Uncheck that timeframe box. No error!

How to troubleshoot an error like this:

Hmm, inp43 = problem is block 43, left operand, something about timeframes...
Lets check the block in fxdreema:

Hmm, maybe I should untick the timeframe box:

voilà, no error anymore! To the next error ->

I don't look the profit factor at all. If you optimize by profit factor, many times you end up with only 10 trades, no losing trades at all. It is not a reliable result, because 10 trades can be coincidence.
My first criteria is number of trades. If you can make 200 trades (in about 1-3 years) and still be in profit, that is much more reliable result.
Second factor is drawdown % relative to max profit (the recovery factor). Don't make those EAs that go a straight line up and then boom 100% loss.
I prefer a graph like this - steady up, no big spikes down, lots of trades:

Also, if you optimize your parameters, use half-period to find the parameters and other half-period to test the optimal parameters. Thats the scientific way

Here's my rough approach:

https://fxdreema.com/shared/3A74lKQwb
I used these constants:

This has the potential for some ugly slippage deviations, but should be ok as a starting point

@justmatt
I'm not sure, but one explanation could be trading costs (spread, commission, swap). If your backtest assumes today's standard trading cost to the history prices, it is essentially exploiting trading opportunities that, in fact, were never possible.
When the test approaches this day, the assumed trading costs also approach the actual costs, and "profit" disappears.

@xander
Hi! I've never done this but the MQL4 function DayOfWeek() should get you going:
https://docs.mql4.com/dateandtime/dayofweek

@frewster
Yeah the adjust variables thingy pops up when you click the tab. You're a very fast learner, it took me a year to learn this lol
The white box means adjusting before the main block does its work,
and the orange (or yellow) box is adjusting after the main block does its work. So, in this case we want to use the orange adjust

I didn't fully understand your strategy, but hope my example helps. Study it carefully and apply the method to your own project.

https://fxdreema.com/shared/ciLGHAj9c

You need to use a variable in the calculation, follow these steps:

1. Create the variable (you can choose the name, I just used "variable"):
   

2. Modify your variable with "modify variables" block. Right-click in the field to select your variable. Put ATR in there, and then "adjust" the value by multiplying by 1.5. Then adjust the variable a second time, "variable" becomes 100/"variable"
   

3. Use a variable lot size, again by right-clicking the field:
   

@luiska
No. You can only guess its mechanics and reverse-engineer it, but direct import is not possible.

I have noticed most brokers nowadays offer only hedging mode on new accounts, I've usually had to ask their support to change my account to netting mode.

Relax, you will get your subscription. I have used this program since 2013 - its not a scam, I can assure you. The admin is a really nice guy and he will surely sort things out. You probably should have contacted him first before posting to a public forum...

To troubleshoot it, export the .mq4 and try to compile it in the windows MetaEditor.
It will give a more detailed error report, and you can find which block causes the problem

@vish
Here's the whole project: https://fxdreema.com/shared/swP7HlvGc
That is not a block, just press this button:

It is meant to quickly modify variables without the "modify variables" block

@vish
Using the "for each..." loop is one (slow) solution. Why do you want to limit trades, especially? Your client can just adjust the testing period, and combine many tests to go around the trade limit. I'd rather limit the demo version to a certain date.

@ricpap
Here: https://fxdreema.com/shared/ExqnpJBZ
This only does as you described, I think it can be improved by setting some limit to the time distance between the fractals

@sami92
Congratulations buddy!
I'd really like to see your backtest report but also respect your decision not to share it, of course.

@vnpython-0
I have never tried with mt4, but seems possible - there's a history center if you press f2, and I found the import and export buttons

@arrow82
Maybe this is simpler than the grid system:
https://fxdreema.com/shared/4OAKoF3eb

My opinion: randomly scalping 3 pips will destroy your money, because spread and commission take a huge part of your profit