Posts made by fxDreema

Oh boy, what part of this EA is wrong?

Now the way is to create a new project with different name. But I am thinking to change things a bit. First, I want to remove the Action History the way it is. Instead, project versions will appear there. So if you like the current state of the project, you will be able to hit some Save and put it there in the list. Let's say that something like 5 or 10 storage points will be available (because sometimes less is better).

I also have issues when I'm working on some idea. At some time I like what I created, but I want to try something else and still be able to return to the current point. Which is possible if I create a new project, but then the list of projects turns into a mess. So I will do something about this eventually.

Better build .mq4/.mq5 file and then import this file. Project information is also appended to these files, so no .xml is needed. I think it's time to retire this option

No. The block requests for a new trade but the broker does not allow new trades at the moment and it's response is that Market is closed. At this time you will also be unable to create a new trade manually

Here is some example that I just made for someone else, but it calculates the loss instead of the count of trades in loss. It's the same idea.

I'm also preparing a block to load basket of trades and then to get different parameters for them (sum, max, min, average) in Condition, but I still don't like the way I did it. Sometimes in MQL4/MQL5 I need to do too many tricks with arrays, which unfortunately slows the backtest down a lot.

Ummm... you are probably using some old version. I renamed the old Comment block to Comment (ugly) and I added a new one that works like this, so every Comment block creates it's own lines and can be placed anywhere on the chart

Try is like this: http://prntscr.com/724pyj

There was a special block for this in the past, but I decided to remove it. The problem for me is that temporary variables are used to remember the current state, and imagine what happens when you restart the EA - they reset. Now I believe that it's better to use the trades as a storage for the current state, to check for their count and properties before doing something.

So, counters are probably working, but I'm not thinking in this direction. If you think that this works for you, fine.

Here is another way - to check what was the type of the last closed trade before checking conditions. If it was Sell - you are going to check conditions to Buy. There is a block with stupid name for this - "Check last closed type"

In your project I don't like these "check type" blocks placed there. These are supposed to work in different scenario. And by the way, there are filters in "Close trades" to choose what to close - Buys or Sells.

For MT4, but anyway, it's the same idea... post/9133

It works for me:
https://fxdreema.com/shared/A7q8CbIUd
http://prntscr.com/7200fu

Try this:

No trade is running (set this to Buys) -> Condition (to buy) -> Close trades -> Buy now
No trade is running (set this to Sells) -> Condition (to sell) -> Close trades -> Sell now

This effect? http://prntscr.com/71mt8u New arrow is created (once per bar) only when the current price is +/- 25 pips from the open price of any existing trade.

Here is the EA I used for that: https://fxdreema.com/shared/hxLvgN94
It uses few pink blocks and one Variable, so it's not very beautiful. And in case of many trades it can be optimized.

I think this is useful and can be put in a single block. Some suggestions for name of the block and possible options for it?

Block "Once per bar"?

There is a block for this. To be honest, I didn't tested it lately, but I also didn't updated it lately. I know that people are using it and there were no reports of this block not working.

Otherwise you need to set up e-mail in the settings of MetaTrader first. Tools->Options->Email.

I also pretty much believe that this does not work while backtesting for obvious reasons.

Are you sure that you pass the test?

Yes, most of the output code is never used and it slows down the backtest, because you know... backtesting means many many ticks backtested per second, so everything in the code matters. But this is EA generator after all, it's not the best programmer in the world that can optimize things to the best. It also depends on what blocks are used and how are they connected. Sometimes you can use some indicator and the EA will almost freeze because of it.

How to use SMA? In "Condition" block, somewhere in Indicators find the Moving Average indicator and set it's settings

How to create a custom indicator? Not possible with fxDreema, only Expert Advisors and Scripts can be made with it

The settings for normal Trailing stop? Just add a new Trailing stop block and you will see them.

Trailing Stop MUST be a positive value. This is the distance where SL should be kept when the price is going into profit.

if Ask > SL + TrailingStop+TrailingStep => set SL to Ask-TrailingStop

I can't see something new in your explanations, it looks like normal trailing stop in small scalping scale. I will suggest to play with this block on a normal scale first, to see how it works.

Trailing Start = the level after which the SL can be modified

This is OFF by default, which means that SL can be modified right after it was created, while the trade is still on loss. If you have no SL initially, it will be immediately set. Or if your initial SL is bigger than Trailing Stop, it will be immediately modified to the Trailing Stop value.

There is option "Open price", which means that only if the price moves up a bit, SL can be modified. But if the price never goes in profit (and let's assume that the trade has no initial SL), SL will not be modified by the Trailing stop.

There is option "Pips offset", which means that the price must go beyond some level (in pips) first, then SL can be modified. While the price is below that threshold, SL can't be modified.

The first thing to realize is that even if you are in 5-digits broker, fxDreema is set up to work as the broker is 4-digits. So if you write 20 pips somewhere, this is always translated into 0.0020. To change this, go here and change these: http://prntscr.com/710ntz Or, you can try with using values 10 times smaller - 2 pips instead of 20 pips, 0.1 pips instead of 1 pip.

But in this small scale, to move SL every 0.1 pip... which probably does not happen exactly like that, because the price can jump with > 0.1 pip. I guess it will be the same as there is no step and you are modifying SL on every tick. The broker will hate you and because such modifications takes time, you will probably miss some ticks... if that matters.

Another problem is that normally there is some minimum distance where you can put SL/TP. Check this one: http://book.mql4.com/appendix/limits

So... I don't know. I'm not very good at this small scale, I normally work with distances bigger than 0.0010. But you are free to play with this and to expect possible error messages and weird stuff coming from the broker Try everything on demo first!