Strategy Tester fails with custom .set file after build 6180 update
Osmar pinheiro:
Has anyone else experienced this after updating to build 6180?
I once experienced the same issue in a previous Build. I was able to "force" the settings into the Tester anew by resetting and resaving the settings in the Tester window─not in the Expert window. It appears from your OP that you did most everything except recreate the set file.
Has anyone else experienced this after updating to build 6180?
Comments that do not relate to this topic, have been moved to "MT5 5.00 Build 6180 Command-Line Backtesting Error".
Osmar pinheiro:
The problem is specifically when loading a custom .set file via ExpertParameters.
The problem is specifically when loading a custom .set file via ExpertParameters.
Your report is not useful.
What is "ExpertParameters" exactly ? A screenshot maybe to be sure about what you are doing.
You need to provide a log file of the Tester Journal.
Provide one of your set file.
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Hello! I'm having a reproducible problem with the Strategy Tester on MetaTrader 5, after the automatic update to build 6180 (was build 6140 before).
The problem: Any backtest (single pass or optimization) that uses a custom Expert Parameters (.set) file fails instantly, with the result "some error after pass finished", taking 0:00:00.000 — meaning the test never actually runs, no trades are simulated at all.
Most importantly: this happens even with a .set file that was working perfectly BEFORE the update — an EA that has been running live for weeks, using the exact same file and parameters. It only broke after the MT5 update to build 6180.
When I run a backtest WITHOUT any custom .set file (just the EA's default input values), it works normally. The problem is specifically when loading a custom .set file via ExpertParameters.
What I've already tried, without success:
Technical details:
Has anyone else experienced this after updating to build 6180? Is there a known fix, or a way to request the previous build (6140) while this gets resolved?
Thank you!