Best posts made by fxDreema

So I got few emails with the same problem - some blocks are missing and the project appears to be empty. I don't know why that happened, I was out of town and I didn't uploaded any updates in more than a week. Few days ago the website was very slow for some reason and I just restarted it. Maybe this explain those missing blocks somehow, but I honestly don't know why the website was slow It was working good since then.

Here is a quick hint for how to "fix" missing blocks - just go to that "History" link in the upper right corner and go to some previous history point that works. Also, every time you export .mq4 or .mq5 file, the project itself is embedded in the end of that file, so the project can be imported back into fxDreema at any time (or at least when the website is working normally :))).

By the way these days I will move the website to another VPS. New VPS - New problems Well, I actually hope that after that it will work a little bit better, at least I will have 1GB of RAM more.

10 pips grid which is updated on every 10 pips? Why do I think that only the first (virtual or not) pending order in that grid will be used

There is a block "Round numbers detector" which passes on every few pips - one of it's outputs is active at a time, depending on the price movement (up or down). It goes up 10 pips - orange out is active. It goes down with 10 pips -the yellow one is active. Up, Down, Up, Up - orange, yellow, orange, orange.
If you connect some "Buy/Sell now" blocks to this block, isn't this similar to what you want?

Take a look at the documentation about NormalizeDouble - https://www.mql5.com/en/docs/convert/normalizedouble

What they say is this:

Please note that when output to Journal using the Print() function, a normalized number may contain a greater number of decimal places than you expect.

There is no guarantee about these numbers. I tried everything, but still sometimes numbers appear long, even after NormalizeDouble or DoubleToString.

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.

It's not because of the size. There is an error in the update script and I need to check why it happens. I guess that you made this on the desktop version where the project's format is... old. The web version tries to update each project to the newest format, but at some point it fails.

Edit: I found the problem, I had some undefined variable in JS code By he way 218 blocks is not huge, I know projects with thousands of blocks

I just added new mode in Trailing stop (each trade), MQL4 only, web version. I marked it as experimental because I'm not sure about it. You can test it and then tell me if it's ok and what should be different.

How it works... you write levels like this:

20/5, 30/10, 45/15

.. which means that when the profit reaches 20 pips, SL will be set to 5 pips (from the Open Price, not from the current price!), at 30 pips of profit SL will be set to 10 and so on...

It's also important to write groups in order starting from the minimum value. 20 first, then 30, then 40... But not 20, 40, 30. This is because MQL4 is very unfriendly when arrays are used and I don't want to add more calculations for sorting.

"Step" is still working. By default it is 1, so we actually have 21/5, 31/10, 46/15. I can exclude it from this mode and set it to always be 0, but... I don't know, people always want more options.

What I don't like in this way is that all numeric values are written in a single string, which means that it will be very ugly if someone wants to use some variable instead. That's why I marked it as experimental.

Otherwise similar functionality can be made using multiple pink blocks. Something like:
For each trade -> pips away from open price -> once per trade/order -> modify stops
but not only this, there must be multiple "pips away from open price" blocks and they must be ordered starting from the biggest profit. Yes, this is also ugly.

I will take a look. I just uploaded some updates and this is most likely the reason.

MQL functions can be used everywhere, all input fuelds in all blocks accept MQL code. The problem is that MathAbs() accepts input parameter between ( and ) and this parameter must be also written manually. If Variable is used it will not look as the blue thing. It will look like this: http://prntscr.com/9f2sil

I think I fixed this

The one from which you want to get absolute value

I have some ideas from where this problem can come, but it can be hard for me to easily fix it, because I have some ugly code there that needs extra care. The problem is that "Shift" parameter is already the actual name of the "Candle ID" parameter and there is a collision. It would be the same if you have parameter "Period". But I can tell you how to escape the problem - just rename the input parameter to something else. Parameter names of custom indicators doesn't really matter that much.

Brokers often have limits. The EA is checking the minimum distance where SL/TP can be placed and if the requested value is lower, the minimum is taken. I think this is the better way, because otherwise you will get error messages such as 130 Invalid Stops

Take a look below StopLevel Minimum Distance Limitation here - https://book.mql4.com/appendix/limits

I'm here But give me more details about these problems. One of the reasons I don't like to answer to questions anymore is that for maybe more than 50% of the questions I'm missing the details and I have to guess what is actually happening and ask the person for more details. I like when the question is full and I can understand what the problem is in no time. It's perfect when I can also reproduce the problem easily.

Here from the question of the author I can only understand that there is some problem with .ex5 files. The title of the topic says that EAs stopped working. Only because some people reported that the new MetaEditor fails to compile some .mq5 files, I know that there is a problem with compilation. But the title doesn't say anything about compilation problems, it says that already compiled EAs stopped working. I tried that on my MT5 and I don't have a problem. So if this is the problem, again, I need more details. Error messages, whatever helps me to understand what is going on.

I also receive emails every day. I just fixed one compilation problem that happens when the new MetaEditor is used. But I'm personally using the .ex5 button and I don't see these problems, so I'm not even aware that they exist

https://fxdreema.com/shared/FiGwA6Bgd

I fixed it... I believe I will give you all some extra time

Ok, I made some updates and here is what we have now:

partial close at every 10 pips - https://fxdreema.com/shared/q1mwIcAQc
add to volume at evry 10 pips - https://fxdreema.com/shared/qrTOdbC0b

There is one big issues as well. Each "pips away" level is calculated from the open price of the previous trade that was made, levels may shift a little bit. I mean, let's say you want 5 levels with 10 pips in between... well, those 10 pips may not be exactly 10 pips

I think the reason why people dislike MT5 is the programming language - MQL5. Now MQL4 has almost everything from MQL5, but MQL5 doesn't have the easy to use functions that exist in MQL4. I obviously have some experience with MQL5, but even I don't like it. There are 3 things there - orders, deals and positions. And I don't mean pending orders. Those 3 things are so confusing. Every time I decide to do something, I have to once again remind myself what these things are. And now if you ask me what they are - I don't know, I forgot. It's really not a good experience writing code in MQL5. While in MQL4 you put OrderSend() with some parameters and voila.

One "Buy now" block makes 1 trade when it runs once. There are ways to make a block to run multiple times, but if you want to quickly make 2 Buy trades, just connect another one "Buy now". I wonder why you want to make 2 Buy trades at the same time, but I guess that I'm still trying to decide what you want to do. So I will say this again - if you want me to help you, make your questions as simple as possible and with all the information I need to know.

Actually the limit is far bigger than 2MB. I just tested a file that is 2.56MB and what I see is that it tries to convert it, the CPU goes high (which it not good), but it takes too much time to spit the result back and eventually it reaches timeout (I think its 30 seconds). On my local PC it succeedes, but it takes more than 11 seconds, and my CPU is quite good (i7-9700). Another file that is 1.74MB converted for 5 seconds on my local PC, and for 15 seconds on the server.

Right now not only I can't raise the amount of bytes, it seems that I should limit them to lower than 2MB. It seems that the speed of conversion is exponentially worse the bigger the file is. I will check what makes it so slow, but this code is kinda complicated and I'm not sure that I will be able to easily fix it.

About the links, I don't mind if they link to something good. When I made this website, initially I put links to it in 2-3 forums, so I understand that. If something is an obvious scam... no, thanks. I know both of you of you, Cam and l'andorrà, as people who have their own courses, and both of you know that I'm kinda like "Yeah, whatever, do what you want". Although I looked at Cam's link and it's not for me personally (I don't like those clocks and stuff), no one ever wrote to me saying that he is doing something bad.

If I am not wrong, this indicator have 1 output buffer, not 2. I feel that you want to do something like this: https://fxdreema.com/demo/mt4-buy-sell- ... conditions