Posts made by fxDreema

Look at the examples - https://fxdreema.com/examples/
Look at this one - https://fxdreema.com/demo/mt4-wrong-closing-rule
Also look at this one - https://fxdreema.com/demo/mt4-loop-how-it-works And then the others -

It depends where "once per trade" is. You can imagine what happens now. Block 7 runs once and immediately after the trade is created, do you want that?

Answer: put 6 after 7

I don't know, but I will recommend to not use these checkboxes. It was my mistake the fact that I have added them. There are Constants to serve as input parameters.

The only advice I can give is to use less blocks as possible and to connect them in more optimized way, which is something full of depends. Even I don't know everything that happens in MT4/MT5. Other than that, what can you do really... It's my job to make the EAs run faster, but this is not always easy

When you open a trade, at this moment you can look back and do something with the 1st, 2nd, 3rd trade that is older than the current one. Just look at the settings in these For each Trade blocks. So you should be able to pick specific trade and do something specific with it. Very similar to what I have in my lower Area.

That thing with the candle... not so easier at this moment. I will see tomorrow what can I do about this, maybe adding some parameter to get the Candle ID where Open Price of a given trade is.

You are right, there is a problem. I will try to solve it and until then you can try some workaround - change the numbers of "Set flag..." blocks on the left with something bigger than 2238, 2326, 2327. What happens is that AND blocks now think that these Flag blocks are their parents, only because they run first. Obviously I was not thinking about such scenario at all the lasti time I did some code optimizations, sorry about that

The tester gets information from the history data, I don't know how can you change the time

13.5/4 is 3.375. This is __average __profit after all. For total profit there is some block "Check current unrealized profit". You can look at this alternative as well - https://fxdreema.com/examples/#Bucket-of...

You are doing things blindly. And I am even more blind, because I don't even know how your indicator looks like. But once you understand indicators, it's not hard at least to find what the problems are.

Here the first two examples are showing how to inspect values, including indicator buffers - https://fxdreema.com/examples/#Tips-and-Tricks

Before using any indicator make sure that:

• the indicator can be loaded, works well and there are no error messages in the logs
• you know it's values

I also don't really understand what you are trying to do Sorry, check this, check that, lot sizes... and more than 15 other questions to answer I have no ideas, I'm not thinking for strategies, I prefer to answer to very specific questions

Congratulations!

You can try some MM option for the lot size, Martingale maybe. It may sound scary and forbidden, but for this particular option I have added so many parameters that you can do something that is not even close to Martingale. For you, take a look at those parameters - "Add lots on loss" and "Add lots on profit"

You can also calculate the lotsize outside "Sell now", but I think the MM options will work.

__I had read that article but I'm thinking what I was missing was the "name" of the file.

I read the bottom of the indicator upload window and am I interpreting it correctly that I need to use the whole file path for the "Name of the Indicator" field?

like this:

C:\Users\MyUsername\AppData\Roaming\MetaQuotes\Terminal\CBC1E074A032EF0E6A1328D19FB1736E\MQL4\Indicators\SMI.mq4

This is where the indicator's name is SMI.mq4.

Is that correct?[/quote:3ilzjioj]

No, not correct. When you add indicator in fxDreema, only use its name, like SMI

123 is not a data type. This is just number, it's not a type of data. At the bottom of this page https://fxdreema.com/help/-/working%20w ... indicators you can find this picture:
https://fxdreema.com/help/pics/datatypes_mql4.png
Compare this with your pictures and you will see that all of your data types are int. I looked in your profile and the SMI indicator is wrong, but SMI2 looks ok. But then you must have SMI2.mq4. So I will suggest to just fix data types in SMI.

You can always check how some indicator works. Just use that block that was "Indicator tester". I renamed it to "Plot" today and I added more options to it. Currently some example is shown here at the bottom - https://fxdreema.com/help/-/you%20shoul ... indicators

In the Tester all times must be equal:
https://fxdreema.com/shared/o9OVe9vFd
http://prntscr.com/afsnle

I'm in Bulgaria (+2 GMT) and this is what I get in live - http://prntscr.com/afsntb

GMT time is linked with the Local time, because if I change my local time a little bit, the GMT time changes with it. But again, only live, not in the Tester.

I'm not sure if I understand everything, but here is something. It's probably not exactly what you want, but it can give you some idea - https://fxdreema.com/shared/IrmAC41me

This is your EA, but optimized a little bit. I still don't know what is going on in it, but I just simlified it - https://fxdreema.com/shared/aIKeoqCle

There are obviously 0 blocks for converting, otherwise you will see some category called "Converting" or something.

It looks that now I must think for these things as well... Anyway, just in case, there are some native conversion functions like this one - https://www.mql5.com/en/docs/convert/stringtotime

I have to check what is going on in these Trade Statistics, but I will recommend to NOT use them if possible. These work on a global level including all Trades/Orders. The EA itself is supposed to work with it's own trades and orders (most of the time). Because of that there is something called Magic Number. Manually created trades have Magic Number equal to 0. Otherwise it's some different number. Here is more about it - https://fxdreema.com/help/-/working%20w ... d%20groups

And I was thinking that blocks are glowing in this case as well... Maybe there is some bug or I didn't make that for some reason which I don't remember

Everything is possible at code level, but I will not add such thing as an option

I was just looking at your latest EA and I noticed that there is no "For each..." blocks. This is something that I repeat over and over again, this block is a MUST when pink blocks are involved - https://fxdreema.com/demo/mt4-loop-how-it-works