After the latest build 5200 update, my MT5 only sees half of the cores. I’ve always had 32, now just 16. Why are there so many problems with the latest updates?
You can check if the optimization time is reduced by enabling all CPU cores.
@Wanton#: Hello, please add the ability to see indicators and tools at the top of the Windows screen and above the chart in future versions. Thank you.
Do you mean, to be able to add indicators to a chart?
If so, then you can already do that from the toolbar (customise it if you don't already have it enabled) ...
If not, please explain in more detail, and also explain what you mean by "tools"
This change to the timeframe tabs makes no sense. If it's possible to view multiple timeframes during the test, then once it's over, the various timeframes should still be available. This is clearly a mistake. MT5 should be more careful.
since the update to 5200 (and now with 5227) the strategy tester is not updating the charts if i switch between different timeframes.
My expert uses 3 different timeframes - 3 indicators with separated times.
After this 5220 update in the bottom of the tester chart three tabs are displayed (Daily, M30, M5). But if i select another tab, the chart is not updating - the tabs are switching, but not the content of the chart.
If i switch during the expert is running/testing, the chart switching is correct. But if the expert is finished, no chart update can be triggered. So i cannot analyze the expert logic and actions.
Is this a known bug? I didn't found the issue here in the forum.
Before installing build 5200, I could see two different timeframe charts in the strategy tester: 5m and 1m. Now, in this build, MT5 opens two chart tabs, 5m and 1m, but both windows are the same, 5min. I need to see the tests on both timeframes for my analysis. Has anyone else encountered this issue?
After updating the 5200 version, although the display interface for different periods after the backtest was fixed, the cycles could not be switched. I hope the official will fix this bug as soon as possible.
Has anyone noticed that the MQL5 Forge Git functionality, only considers Unicode/UTF16 files as valid (green check-mark after a commit)?
Other file formats, such as ASCII, UTF-8 (with or without a BOM) are successfully committed, but remain marked with a red warning bubble, even though on the forge they are all correctly updated and displayed.
After the latest build 5200 update, my MT5 only sees half of the cores. I’ve always had 32, now just 16. Why are there so many problems with the latest updates?
You can check if the optimization time is reduced by enabling all CPU cores.
Форум по трейдингу, автоматическим торговым системам и тестированию торговых стратегий
Новая версия платформы MetaTrader 5 build 5200: расширение OpenBLAS и усиление контроля в MQL5
fxsaber, 2025.08.18 15:28
Number of agents - 3.
Number of agents - 6.
Do you mean, to be able to add indicators to a chart?
If so, then you can already do that from the toolbar (customise it if you don't already have it enabled) ...
If not, please explain in more detail, and also explain what you mean by "tools"
EA crash after update mt5 to 5232, I compile the EA with this version and run it.
then I downgrade to 5226 and compile again, run at downgraded version, everything works fine.
Issues after the test ended with changing tabs on strategy test continue on 5232. See that I'm on M30, but have clicked on Daily tab.
Just a summary of scattered posts that I noticed, related to the "tabs" malfunction in the Strategy Tester ...
Has anyone noticed that the MQL5 Forge Git functionality, only considers Unicode/UTF16 files as valid (green check-mark after a commit)?
Other file formats, such as ASCII, UTF-8 (with or without a BOM) are successfully committed, but remain marked with a red warning bubble, even though on the forge they are all correctly updated and displayed.
Reference: Build 5200 ...
EA crash after update mt5 to 5232, I compile the EA with this version and run it.
then I downgrade to 5226 and compile again, run at downgraded version, everything works fine.
@Ilyas
checked build 5233, problem still there.