
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
Yes of course, that's the first thing I always do. complete logging is the first thing I always do. as you correctly pointed out it was the indicator readings but I couldn't figure out Why that thing keeps happening only inside non-visual tester. that was the very core of my question
"Why" was explained from very beginning.
If you don't have an access to the source code of the indicator, you could possibly try to create your own wrapper indicator for it, and insert tester_everytick_calculate directive into it, but I'm not sure if this helps. Just an idea.
PS. Looking at the screenshots I suppose you can find similar indicators with open source."Why" was explained from very beginning.
If you don't have an access to the source code of the indicator, you could possibly try to create your own wrapper indicator for it, and insert tester_everytick_calculate directive into it, but I'm not sure if this helps. Just an idea.
PS. Looking at the screenshots I suppose you can find similar indicators with open source.Sure it got solved early on and that specific indicator is not a big deal. the rest is just our discussion about the underlying logic that allows for such problem, in which you can have a perfectly working EA inside live chart and visual backtester but not in the non-visual tester with the same configuration.
And the Idea, It should work I believe. if so it would recompense the non-visual tester's *not respecting* every tick modeling.