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
Start making a demo mt5 account with bx. You will receive an email with a link to the distribution. At the server selection stage you choose not a demo server, but for real trading. Create an account with arbitrary data. Create a certificate. All you have a real account with zero balance with real quotes and history.
Start making a demo mt5 account with bx. You will receive an email with a link to the distribution. At the server selection stage you choose not a demo server, but for real trading. Create an account with arbitrary data. Create a certificate. All you have a real account with zero balance with real quotes and history.
In the "based on real ticks" mode the positive slippage of limit orders is about 50% higher than in the "based on generated ticks" mode.
This results in a mishap - we introduced real ticks to increase the accuracy of the tester, but introduced positive slippage of limit orders, artificially hovering over the backtest results.
On the exchange, limit orders do not slip, but are executed exactly at the order price. But this is not the case in the tester.
This bug can be avoided using the library described in the link above. But this is a crutch solution. It makes sense when the tester itself works accurately.
I'm asking forum members for their opinions on this subject. Since, for obvious reasons, the opinion of one member of the community is poorly taken seriously by the developers.
It's a pity that no one had a say in it.
This topic has already been discussed here on the forum somewhere and the developers themselves seem to have said they'll fix it in the new builds. Try to look for it, I didn't really get into it...
P.s. Here's a topic that was also unanswered https://www.mql5.com/ru/forum/86591/page4.
This topic has already been discussed here on the forum somewhere and the developers themselves seem to have said they'll fix it in new builds. Try to look for it, I didn't really get into it...
P.s. Here was a topic, also unanswered https://www.mql5.com/ru/forum/86591/page4
It's a shame no one spoke up.
Because you have no evidence base whatsoever.
It's much easier to save the report and zip it up. Show me an example of one transaction with the calculations.
Because you have no evidence base whatsoever.
It's much easier to save the report and zip it up. Show an example of a single transaction with a statement.
Thought that would be enoughhttps://www.mql5.com/ru/code/16134.
Got it. I'll prepare it.
Adviser
Tester Log
Slippage of limit orders is marked in bold. The slippage in the tester is worse when a Limit order slips through the session - at opening. But I didn't take these cases as an example. I took the usual market.
Is it reproducible?
Unfortunately, the debugging doesn't work, so it was not convenient to create the example.
Forum on trading, automated trading systems and strategy testing
Bugs, bugs, questions
fxsaber, 2016.09.01 20:18
Adviser
Tester Log
Slippage of limit orders is marked in bold. The slippage in the tester is the highest when a Limit order slips through the session - at opening. But I didn't take these cases as an example. I took the usual market.
Is it reproducible?
Unfortunately, the debugging does not work, so it was not convenient to create an example