@ambrogio I will test it tomorrrow more and let you know

@ambrogio Understood. Thank you. You've been extremely helpful!

@roar
I found another indicator same as this , THX alot ^^

@fxdreema said in Calculation drawdown of balance and equity in mql5:

By the way I wrote to the author in email. I will post a screenshot of it here, just in case:

Thanks @Fxdreema !! it worked well 🙂

@fxdreema do as you like

I agree. Aditionally be sure you specify candle ID 1 on on both operands 'More settings' tab.

For your second question, how many open trades are supposed to be active at the same time?

@gee Check the journal tab in your strategy tester, it has a message for you

@l-andorrà thanks

thanks for respond im not good in this so if you can help with screenshorts of the blocks will be helpfull

In general any generated EA will be slower that the same strategy if you are able to carefully code it manually. This is because the generated EA is full with useless code. My EA builder is not so clever to only include the code that is needed and to optimize it in the best way, so you always end up with bloated slow code. But it should not be too slow... like waiting for hours to backtest one day. It is important what blocks are you running on every tick. Try to connect them in such a way, so the slowest block are running more rarely. Of course, you can't always say which blocks are slower than others... even I can't tell that without testing them. But maybe you are using some custom indicator - maybe this indicator is poorly written and it is too slow. Put that indicator in few blocks and the time stops 🙂

Only do that if you want to have something like 2 (or more) different strategies in the same EA. Like 2-in-1. But remember that it is still one EA and if the strategies are completely different, it's better to just make two separate EAs.

Otherwise... imagine that you have 2 different groups of blocks that are separate - one for the first strategy and one for the second. In all blocks in the second groups of blocks where you have Group, you should set it to 2 for example. Such blocks are "No trade", "Buy now" and basically all these blocks who are working with trades or pending orders.

The EA will have one master magic number (it's the MagicStart parameter of the EA) and where you have Group number that is different than 0 (empty value), the magic number will equal to MagicStart + Group.

Did you know that blocks 10 and 11 are working on different groups? Buys are considering all trades (manual and automatic), whereas sells are only restricted to group 2 trades. Is that intended?

So there is something called lot step. For example, if the lot step is 0.01, you can open 0.01, 0.02, 0.03... lots. If the lot step is 0.1, you can open 0.1, 0.2, 0.3 and so on. Lot step is the difference between two possible lot sizes. If you try some middle value, for example 0.012345, it will give you an error. So the EA that is generated would always use possible values. If your balance is 2641 and the lot size is calculated as 0.02641, this value is then rounded to the nearest possible. I guess that I used MathRound(). But as roar wrote, you can always write your own function. Some functions that you can use are AccountBalance(), AccountEquity(), MathFloor(), MathCeil() and MarketInfo() if you want to get the lot step. Take a look at their description in the documentation for MQL4 in MetaEditor (Help -> MQL4 Reference)

I would also blame the history data. I'm not aware of anything in the code that can change the behavior of the Tester. Almost everything in the code happens in that OnTick() function that is automatically called by the Tester on each tick. So it's the Tester that is preparing the ticks data before even start testing, and then using that data to call OnTick().

Just in case, you can try another EA... even EA downloaded from internet. I think you should see the same effect on any EA. But if you see it only on FxDreema EAs, then this obviously means that the problem is in them and I need to investigate it.

In your example I see you are doing something with the objects that are created by the EA, but I don't really recommend to use the data from them.

And yes, try "For each position". In case you don't know, in netting mode you can have 1 position per symbol. This block would load only that position if it exists. In its filters by default the current symbol is used (the value is empty, which means the current symbol). It's also possible that you can even omit this block and still be able to load the position in 203, but I recommend using "For each trade", so it can be clear what is going on. And yes, as it was said, block 203 doesn't work now in this example only because it is not connected to another block.

I figured it out. I assigned Candle ID 1 to the RSI cross so that the indicator rise had a chance to happen on the current candle.

0_1565725451588_Screen Shot 2019-08-13 at 12.42.49 PM.png

I have found a solution.
You can change the value (1 or 2) while the robot is running.

Still can't understand Variables V1, V2 .... F1, F2 .... the system.
Just there were some more examples.
What appears under "Examples" doesn't make me wiser.
.
0_1565720731097_Skærmbillede 2019-08-13 20.21.05.png

I'm afraid this is more of a programming problem. Maybe roar or miro could offer a better answer?

@roar Yeah... you are right, my friend.

But... who knows! lol

I'm studying and trying to find a way to do it... let's see!

Thanks for your reply!