Unsolved Using a Delay Function in the MT5 Tester

[Archer]

Hello Forum!

I'm trying to build an EA but I'm having an issue with the tester on MT5 right from the first few blocks.
Funny enough, on the live market everything works fine and according to my expectations, at least at this early stage of building.
For some reason, the tester is not fully respecting Block #19, which is supposed to disable the buy function:

https://fxdreema.com/shared/1bPrMQl4b

Even though the log shows that the block has been disabled, the EA still immediately opens a new position.
Based on logs, it seems to me that the problem lies in the lack of time/tick delay in the tester and the EA sees both the disabled block and the condition to open a position at the same time:

I've tried adding functions like "skip ticks" or "delay" after Block 18/19, but the tester completely ignores them and doesn't delay anything.

I did manage to create an "artificial" delay in the tester by adding a condition before the BUY block:

and everything starts working as it should. Unfortunately, even such a small variable affects the tester results compared to when this variable is absent, rendering the entire backtesting meaningless.

So, my question is: how can I delay the BUY block in the tester so that the EA waits for at least 1 second before taking any action after the execution of Block #19?

[BBMess]

There is a 'Delay' block found under "More" and it's use is described in the picture below;
You will need to go into your MetaTrader terminal and go to "Tools/Options/Expert Advisors (Tab) and click the "Allow DLL Imports"
This will ensure the delay actually happens naturally in the tester.

[BBMess]

You can add a constant in the seconds area to test if 1 second will be enough or change it in the EA Parameters without the need to compile a new version every time you want to test it.

[Archer]

Thank you, but as I mentioned in the first post, I've already tried using that block.
It only pauses the tester for a selected period of time and doesn't affect the delay in trading itself.
The conditions that were met during the pause are still being executed when the EA resumes its operation.

In general, I'm looking for a method that will compel the EA on the tester to fully respect the fact that the BUY block has been turned off.
It doesn't necessarily have to involve a time delay because I can see that the tester doesn't respect time-based blocks as it does on the live market.
I only hope any proposed solution won't impact the delay in the price itself, similar to my suggestion in the first post, as it has an impact on backtesting results.
In other words, in this case such a solution cannot be placed directly before the BUY NOW block. Unless I am mistaken... please correct me if I'm wrong.

[Archer]

While still considering another logical function for this EA to work on the tester like on a live market, I was wondering if there is any method to limit the operation of blocks under 'ONCE PER CONDITION'?
Something similar to the 'ONCE PER OBJECT' block, but in this case, the EA would open positions only once when a specific condition is met and somehow wait for a reset before opening a position again only after the condition is met once more.

I applied this logic in the project I shared, and it works well on the live market thanks to enabling and disabling blocks. However, I'm unsure how to translate it to the tester.

[Archer]

Hey guys, any suggestions regarding the above?
All ideas are more than welcome. Don't be shy

[l'andorrà]

I'm not an expert in this field but as far as I know time cannot be delayed in tester. Someone else with more knowledge could confirm, please?

[Archer]

I have the same request from my side as well.
And if it's not possible to achieve that, I kindly ask for a suggestion on how to construct the blocks in a way that they will function similarly to the ones in the project I presented but be customized for the tester's requirements.

[jstap]

What you can do is create a timer, so until enough seconds have passed, blocks won't activate.

[Archer]

@jstap Thank you for your suggestion.
I've tested all available time blocks on the platform to create such a timer, but none of them work on the tester.
They do work on the live market, though.
Could you please show me an example of the block structure you have in mind and where it should be placed?
Or perhaps you're referring to some form of formula or code that goes beyond the standard FX functions, which I personally am not familiar with.
I would appreciate further clarification.

[jstap]

Create one, start by adding 1 onto a variable every second, then reset this to 0 when needed. Then you can check this with a condition, and do what you want.

[l'andorrà]

@jstap Just curious. How can you do that on tester? Backtest is using tick data, not real time. If there are no ticks for 3 seconds, for example, the timer will be wrong.

[jstap]

Backtest uses server time, not tested MT5 but should work the same as MT4:

MT4 https://fxdreema.com/shared/4cQR6lW9c
MT5 https://fxdreema.com/shared/IwxuA3zKd

hope this helps

[Archer]

Thank you @jstap.
Your solution should work.
In the meantime, I managed to find another one. I added the "every n ticks" block here:

It doesn't significantly affect the backtest results because it's enough to set the value to 2 for the EA to have time to realize that the requested block has been disabled. Now, the EA waits to open a position only when the condition is met again, just like in the live market where this block is not needed at all.

However, if someone doesn't want to have the slightest difference in backtest results, a better solution is a timer that should appear after block 18 or 19.

[Archer]

Great! I've solved one problem, and now another has appeared.
EA works well only in visual mode. Otherwise, it only executes a few trades and terminates the backtesting.

The only thing I added is a time filter block, which I always apply and it never caused any problems with other EAs of my.
If I remove it, everything works fine. After adding it, it becomes chaotic and only works in visual mode.
Do you guys know what could be the cause of this situation?

https://fxdreema.com/shared/foWqnFkqb

Why does everything have to be so hard to attain...

[l'andorrà]

@jstap Interesting. Thank you very much.