Hi everyone,
I’m having an issue with MT5 Strategy Tester where the test doesn’t start at all (0% progress, no trades, no clear errors in the log).
The EA is relatively complex (multi-timeframe: M5 entries, H1 confirmation, H4 trend, multiple indicator handles, CopyBuffer usage, trade throttling). The same logic works fine on a live/demo chart, but in the Strategy Tester just refuses to run and i forced to roll back to an earlier more stable build in order to complete the test.
My question is:
Is reverting to an older MT5 build the only reliable solution in cases like this, or are there known fixes/workarounds for recent builds?
I’m trying to understand whether this is a platform/build limitation or something that can be handled purely in code.
Any insight from people who’ve dealt with similar tester behavior would be appreciated.
Thanks in advance.
Step 1: contact your EA developer.
That’s why I’m trying to understand whether this is a known Strategy Tester build related limitation, or if there are specific tester related constraints (multi-timeframe data loading, CopyBuffer timing, indicator initialization order, etc.) that should be handled differently in recent builds.
Thanks again
That’s why I’m trying to understand whether this is a known Strategy Tester build related limitation, or if there are specific tester related constraints (multi-timeframe data loading, CopyBuffer timing, indicator initialization order, etc.) that should be handled differently in recent builds.
Thanks again
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi everyone,
I’m having an issue with MT5 Strategy Tester where the test doesn’t start at all (0% progress, no trades, no clear errors in the log).
The EA is relatively complex (multi-timeframe: M5 entries, H1 confirmation, H4 trend, multiple indicator handles, CopyBuffer usage, trade throttling). The same logic works fine on a live/demo chart, but in the Strategy Tester just refuses to run and i forced to roll back to an earlier more stable build in order to complete the test.
My question is:
Is reverting to an older MT5 build the only reliable solution in cases like this, or are there known fixes/workarounds for recent builds?
I’m trying to understand whether this is a platform/build limitation or something that can be handled purely in code.
Any insight from people who’ve dealt with similar tester behavior would be appreciated.
Thanks in advance.