Posts made by fxDreema

hmmm, interesting, this means that some PHP error happened. I tried to upload an indicator and it worked. Can you upload another indicator? If you can, then if this one is not too private, put it here in this topic and I will investigate it

Input parameters are something that must have some meaning. I will always recommend to define and use some Constants, there are actually input parameters for the EA, and you must give them meaningful names.
Then, these Constants can be used inside the code in various ways. For example: https://fxdreema.com/shared/L3ZklD28c

If someone have good idea of how to make this in easier and more intuitive way, let me know.

This "cross width" parameter is something that I added without many thinking, I don't think it's appropriate for your case. You can see what this parameter means here: https://fxdreema.com/documentation/proj ... er%20works
In any case, it does not mean that the crossover is detected on every X bars. It will probably cause the Condition to pass even more often.

I think there is some bug when working with those ckeckboxes for input parameters. In the code it looks that "Extremes" is checked, but it's not in the block...

Nevermind, because this parameter is "weird". Sometimes they define something like custom data types inside custom indicators (also in EAs, in any MQL5 code), and this is what happens with that particular indicator. "Applied_Extrem" is not a valid datatype from the EA standpoint, also there is no constant HIGH_LOW defined in it. These are defined inside the indicator, but the EA does not care. The EA can only read indicator buffers, nothing more from the code of the indicator. Well, HIGH_LOW is some numeric value for sure, so you can use that value instead HIGH_LOW. And use "int" datatype instead of "Applied_Extrem". Somewhere on the top of the .mq5 file of this indicator you should find information about "Applied_Extrem"

If you use "Condition" block for crossover, then this block works in the whole candle. Check this to see how it works: https://fxdreema.com/documentation/proj ... er%20works

There are two different crossover blocks in "Indicators" category, they are a little bit different - they produce 1-time signals.

Every N bars passes ONCE on every N bars, so it probably matters where it is placed.

Get some "Draw arrow" and connect it below some condition that is used. Then one step below... one step below... and if some block does not produce the signals you need, you will see it immediately.

Trailing TP is the same as SL, but the opposite - moving TP when losing. If someone needs it, who knows.

Why don't you try things in separate EA before using them in that EA. Try how martingale works in separate, then when you see that it's working - add it here. At least this is what I do when something does not appear to work, and when I simplify things the problem shows up.

Martingale. Before creating a new trade, the lot size of the previous one is checked. The previous one that is from the same group! No matter buy or sell. So you can have Buy and Sell blocks that can all work with the same Martingale. But when you have different groups, each group is individual.
I removed these groups before, I don't know why you want to work with them. Now they separate the logic for Martingale. This is something that you may want actually, but I'm not sure that this is true.

You tried that Trailing stop? It's not only what it sounds like, it can follow the ATR levels or the levels of any similar indicator. As a result SL is placed at the newest ATR level. I think you are trying to make it the hard way. Yes, normally the Trailing stop block moves SL at fixed pips distance, but this block is one of these with many options. It can also trail TP, which sounds the opposite of Trailing Stop.

I don't know, I have this: http://prntscr.com/4em4c5
Some trades are opened at some levels and I don't even see how they can close. Also I think that Martingale should be used when there are no trades opened, which is not the case here. Now it gets lot size from the last opened trade, I enabled this because some people wanted it, and this is... I don't know, I can't get it.

Please, learn one simple thing. When you want to add something new to the project, try the new thing in another EA, only the thing, as simple as possible, with only few blocks. Then if it does not work you will know it and you will be sure where is the problem. Because now... you are adding something new over something complex and then you try it... things are getting more and more complex and hard to debug. I believe In this case you are going nowhere

By the way, define "jumping lot size". I can see you have added fixed lots on loss, which turns Martingale into something that is called Grand Martingale. If you don't realize that you may think that these 0.01 are something else... initial or something.

Yes, but in this picture I can't get the idea where everything starts and how it continues, there is only 1 position and I decided that this can be somewhere in the middle of the test

Now it must be fixed

Please, explain things as accurate as possible to me! It's not only that my native english is not native, I am just not focused normally, many people are asking me questions about different strategies and I just can't process all the data.

The problem is this: All the positions are opened fine except the very first one. The problem is that when the EA is started it detects that the indicator (blue line) has just appeared, while on the chart it looks that we are in the middle of it.

Remove all the Counter blocks, this was not for your case. I will check what can be done to fix that erratic signal detection, I think I can fix it.

I can think of some type of flip-flop functionality, let's say you have a block who passes on every 2nd run. This is not hard to program, but I can smell some problems in this case. If this is a single block placed after the Condition (which detects signals), then it can easily go out of sync.

I think it needs to be something like this: https://fxdreema.com/shared/4fOTvUmfb
The Buy side resets the Sell counters and vice versa. I added "Pass once" to make it pass once in case 3rd, 4th or more signals are generated, but this block can be omitted if it's not needed.

How do you want to enable/disable these?

If the EA itself needs to to that automatically, I can suggest Turn ON blocks and Turn OFF blocks. There are also few blocks in "Flags category". Also, Variables can be used.
It this needs to be done manually, define some Constant (input parameter) and check it's value in some Condition.

Will it work if you add this group of 2 Once per bar blocks after 7 and 9?

Unfortunately the EA builder is weak when it comes to mathematical calculations, this thing is normally done by the indicators themselves.

It's easier to write such a custom code instead of building it with blocks, because this some normal "for" or "while" loop with few extra variables to control it. I don't know how to make things like this with blocks... I mean... there are already some loops available (for example this big category with pink blocks), but many people have problems understanding how to deal with this, even if it's not that complicated.

Otherwise in some loop you want to check indicator values for the last candles, having some variable to count and starting from 0. When the detected value is lower/bigger than something - break the loop. Then use the value from the counter. Additionaly, to optimize things, add some "once per bar" functionality. Or something else.

Is this some indicator?
Maybe something like this: http://prntscr.com/4ef2ar

Here is some basic information of how indicators work: https://fxdreema.com/documentation/gett ... indicators
And here is some basic information of how to manually add custom indicators when you don't have .mqX file: https://fxdreema.com/documentation/proj ... indicators

What matters is the number of input parameters - they must be right. Also their data types - they can be only "string" and "double", but it's better if they are also right. Their names can be different, but it's better if they are the same. Their order matters, it must be the same. And the buffers count matters... buffer names don't.

But if your indicator does not use any buffers to send data to the EA, then you can only use the object that it draws. Which is another story

These things are only visual, the EA does not care what visual limits you have for the indicator. But if you want to use these, first check this "Fixed maximum" and write 100 for it, then go to "Levels" tab and add two levels at 20 and 80. But this will not change the way Stochastic works. So the problem for the EA is somewhere else - inspect how/when trades are placed, something in the logic could be wrong.

Hmmm, I think at the moment there is no easy way to do that. With some custom indicator for sure. I think this was requested before, but I'm not sure how to make it - in the Condition block as options or somehow in a new category of blocks.

I don't like the first method because I must add who knows how many parameters (people always want more) and it will become a soup. Someone will say - I want this, but for the last X hours. Other will say - I want this, but the average value.

And the other method as well, because some hard-to-use blocks will appear

The break even block sets the SL at Open Price (or close to that price) when there is some profit for that individual trade. Yes, it works individually, not for a group of trades.

This is what I got: http://prntscr.com/4ecg2z
from this: https://fxdreema.com/shared/9eaRMigPc

SL goes to 5 pips above the open price when the profit reaches 15 pips.

The built-in Stochastic moves between 0 and 100 and also has two helper lines at 20 and 80. This is how it looks to me for MT5: http://prntscr.com/4e47a7