Posts made by fxDreema

The default is to open History Center and download some data. There are some options in Options-Charts that I think change the way that history data is downloaded, but I'm not sure about this. The problem is that very often we got these holes of missing data for some reason and I don't know what is the reason for that, but it sucks. Also it actually depends on your broker, because the data is downloaded from the broker.

You can go in MetaTrader's installation folder and look in it's "history" subfolder. I think you will understand how things work.

When backtesting, just before the test, a giant file (it depends on the period) of data is generated and it contains all the generated ticks that will be used for the test. Those ticks are generated from the lowest available timeframes. If data from M1 is present, ticks will be generated out of that data.

You can also look at this http://tickstory.com/ and this http://eareview.net/tick-data-suite to learn about what is known as Ticks data

Note that you can only use external history data in MetaTrader 4. MetaTrader 5 does not have History Center.
And you can only backtest 1 symbol at a time in MetaTrader 4. If you try to backtest another symbol that is not the current one, you will get an error message.

Turn off "Caps Lock" when possible.

No one ever asked me how to put stops on a trade and I'm not sure that what I am reading is what it is really. But maybe you have different way of thinking.

It's as simple as it can be. "Buy now" or "Sell now" are blocks who able to create 1 new trade when you run them. The parameters of that trade are specified in their parameters window. Parameters such as volume (lot size) market (symbol), stop-loss and take-profit. All values should be positive. There is no point for stop-loss to be negative value. If you write 10 for stop-loss, this means that the size of stop-loss is 10 pips, it means that the horizontal line of stop-loss is put at 10 pips distance from the horizontal line of the opening price. It also means that if the market price reaches that line the trade will be closed on loss and the result will be negative, but sometimes people move that line and sometimes the trade can be closed as profitable by that stop-loss line.

Yes, you described what can be done in this situation. It would be the same if you use Variables instead of flag-blocks, because in fact those flag blocks use variables to keep their memory.

The example I posted above is similar, but the difference is that the memory that is used is external, it's in the trades that are created. So, instead of storing and checking temporary information (variables in the EA are in RAM), I use the type of the trade as such information. But this is very particular example where this can be used. Anyway, what I want to recommend is to first try to find a way to use information from the trades/orders/candles, and if this is not possible Variables/Flags can be used as well (and sometimes this will result in faster EAs for testing).

In this way the EA will opening new trades over and over again. Put some "No trade" above. This can be seen on the very first example here: https://fxdreema.com/examples/

By putting "No trade" above you will also limit the number of trades to 1, so you will have 1 trade at a time. If you want to separate buys from sells, then two "No trade" (one for buys and one for sells) and two "Condition" will be placed.

I think in this case "Once per bar" will also work. One before "Buy now" and one before "Sell now".

As you can see sometimes there are multiple ways to do the same ot similar things.

In the web version I actually can't re-open it after I close it. This is the problem I see, but it looks to be the opposite of what you are saying. Otherwise the descriptnion should automatically appear when the project is loaded.

I will probably not make such a block, but you can try with the trailing stop block. As you know, BE is similar to TS (trailing stop) and the regular TS block can be set to work as BE.

I think it was something like this. Set "Start" to the profit where SL must be modified. For example 10 pips. Set "Stop" to the same value. Set "Step" to some big value. Something like this: https://fxdreema.com/shared/dfaqAlMpc

By the way I decided to find a way to do this thing, to add new event called "on Hold" where if any block fails to pass, to retry it on the next tick. Many people are asking for this and many people are thinking that things work that way. I'm tired to explain those things again and again, so I think it's better to just do it, even if the result is slow.

Otherwise yes, it's possible to set any Variables. The Time as a data type is "datetime", which is similar to integer (whole number) and two Time variables can be compared.

Martingale is to double the lot size on loss. Loss means that the last closed trade is not profitable and it's also closed.

Some people wanted to do it in the "wrong" way - do calculate the lot size from the newest already running trade for example. So the block first searches for such trade and only if it doesn't exists it takes the lot size from the last closed trade.

For Martingale there is no memory where the last lot size is stored. It depends on the lot size of the last trade. If that trade was loss - it doubles that value, otherwise the value is reset to the initial. And of course it depends, because there are many options, but I'm talking for the default Martingale settings.

So I think that you have one trade still running when the new one is created and it works with its lot size. If you want to separate things, try with different Group numbers.

But Virtual stops are disabled by default. So, everything works now?

If you have one block for each step and all blocks are connected one after another, then the answer is no. In "on Tick" blocks run on every tick and there is no situation when you reach one block that currently can't pass and wait for it to pass. If a block does not pass, nothing happens, for that tick everything is over and the block will probably be "asked" again on the next tick.

You may want something like this here: viewtopic.php?f=5&t=3274 But as you can see, I decided that this model was slow and I stopped working on it.

So when you work under "on Tick" you must think from that perspective. Here is another example where people are thinking that the EA will stay on some block waiting for it to pass, but it doesn't work that way: https://fxdreema.com/demo/mt4-wrong-closing-rule (this is the example called "Wrong: Closing rule" from the examples here https://fxdreema.com/examples/)

If you placed trades with expiration settings, these will eventually be closed by the EA. Because I use the comment attribute to write information about the expiration and then the EA works with that comment attribute, which cannot be changed with the EA again.

But if you create trades without expiration, I don't see reason for them to be closed by expiration. Maybe you have other blocks that are used to close trades by some condition.

I don't remember exactly, but I think that the way to detect white-red and red-white transitions was by detecting crossover of High and Low values. Because these swap over time.

Here somebody wrote about this indicator long time ago: viewtopic.php?f=2&t=1782&p=1830&hilit=heiken+ashi#p1830
And I posted some example also long time ago: https://fxdreema.com/shared/JvDgZliqc

Hmmm... I don't know. What was the case? When you write your description, make sure you click on the Save button that appears above

Yes

I don't fully understand the question, by I have this feeling that you may want to try something like this

Project example: https://fxdreema.com/demo/mt4-buy-sell- ... conditions
Image:
https://fxdreema.com/examples/screenshots/mt4-buy-sell-buy-sell-opposite-conditions.png

Are you sure about this condition and the path to "Sell now"?
http://prntscr.com/9z33xg
http://i.imgur.com/A43PC8i.png

At least on my chart AD values are something like -100404, whatever that means. MA values are like 1.25110 and I don't see how this can be compared with -100404

Here I tried to explain how stuff works in fxDreema: https://fxdreema.com/help/-/working%20w ... d%20groups

By default all blocks work with the same magic number, which comes from the input parameter "MagicStart". In the EA you can use multiple magic numbers by working with the "Group" parameters. In some way this Group number translates to Magic Number.

Here is something that I tried now:
[MQL4] https://fxdreema.com/shared/Y7hn2uq1d
[MQL5] https://fxdreema.com/shared/uWj3Hc36b

I also defined the variable as int and I used values like 0 and 1 for it, but I can't find something wrong. Can you give me some project or tell me which one of your projects should I look at?

__If you don't mind my asking, who do you use?[/quote:1rksqrky]

I created my real accounts long time ago, before fxDreema. The first one I have is in a broker that does not use MetaTrader. The second one is in a broker where I used some Saxo platform and then I started using MetaTrader 4. It also offers MetaTrader 5, but I never used it.

I must say that I am not a trader, I was just playing few times with my real account and I was losing every time. I never traded automatically, only manually. Obviously I created this tool called fxDreema that many people are now using, but my job now is to make sure that it works properly and to answer to questions. I just don't deal with brokers and I have no professional opinion about them

In the EA when you are using one indicator, MetaTrader knows that and loads that indicator with the particular settings. If the same indicator is used with different settings, two indicators will appear.

There is no matter how many times you request value from an indicators. Normally for the EAs important things happen when ticks are received, because a new tick means that the price changed and everything you do when you are trading is to react on price changes. But indicators does not really care about that.

The first time the EA calls to an indicator, MetaTrader loads that indicator and gets the value from it. If you are backtesting that indicator does not even appear visually, so I think that it does not even recalculate if you are not using it. Only if you put it visually on the chart, then it must be recalculated so you can visually see all the changes, but MetaTrader handles that by itself.

Just use "Condition" with that Moving Average where you need it and as often as you need it. "on Tick" is not mandatory, it's only where most things normally happen.