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
Hi Francesco,
did you find a solution, explanation or any workaround other than downgrading? I'm struggling with the same issue.
Thanks
Hi Francesco,
did you find a solution, explanation or any workaround other than downgrading? I'm struggling with the same issue.
Thanks
Hi there,
many people wrote me, also in private, about this topic and asking for help.
Unfortunately I cannot help, in my case there was definitely something wrong in the tester engine causing internal errors to happen and being stored in the _LastError variable.
So I eventually managed to work around this issue resetting the error status before every call to core functions, and checking for 'real' errors only.
I don't know if that's your case, if you don't make use of global variables or other shared resources you might have been caught as well, and you could try investigating in that direction.
This is the link to the issue breakdown and the solution I adopted.
https://www.mql5.com/en/forum/376067/page5#comment_54267478
Cheers
This is the link to the issue breakdown and the solution I adopted.
https://www.mql5.com/en/forum/376067/page5#comment_54267478
From that same thread, this post seems enlightening:
Forum on trading, automated trading systems and testing trading strategies
Strategy optimization result do not match single run test result
Stanislav Korotky, 2025.12.13 15:41
GetTickCount is a system real timer, while the tester simulates internal timing based on history of ticks and their playback (in visual or fast mode). During one tick of the real timer the tester can replay a thousand of historical ticks.
TimeCurrent is simulated by the tester.
That could certainly explain why I don't experience the issue with an EA that evaluates, trades on, and backtests on OHLC prices only.