MetaTrader 5 Platform Update Build 5660: Improvements and Fixes - page 3

New comment
 
4xonly #:
Please forgive my ignorance, I thought the one I posted was the journal log. Can you point me to the right path and name, please?

It was the Experts log. Journal tab is beside the Experts one.


 
jguellbo #:

New update,  but same problems. My platforms work slowly, charts frozen, since update 5640. Actually it's worse now. Last week I could work with at least one open platform, now not even that. I usually  worked with 5 open platforms, which is now totally impossible.

 I am seriously considering stopping working with metatrader, after many years of doing so. I will file the appropriate complaints with my brokers.

Could be a Windows issue.  Since I've migrated to Linux Mint MetaTrader 5 is significantly faster (among other things).  However there are problems here too.

A LOT of "0120:fixme:file:GetLongPathNameW UNC pathname L"\\\\?\\C:\\Program Files\\MetaTrader 5\\MQL5"" error messages are written into ~/.xsession-errors file.  Its size is increasing rapidly.  I have to redirect this to /dev/null with

ln -sf /dev/null ~/.xsession-errors

if I want to spare my SSD.

 
Alain Verleyen #:

It was the Experts log. Journal tab is beside the Experts one.


Right, so you meant to post a screenshot of the Journal tab, correct? In that case I'll have to wait for the issue to occur again, most likely tomorrow, as it seems to show when the amount and speed of data increase.
 
Luu Tuan Trung #:

Please do not let it automatically reset the "Fixed maximum" and "Fixed minimum" price levels here.




fix it please
 
Alain Verleyen #:

It was the Experts log. Journal tab is beside the Experts one.


Here's my journal log for today while the issue is occurring again.

Files:
Journal_log.png  78 kb
 

This version is still having the same issue that causes the chart to lag and even worse. The execution of indicators is just not working as it used to. I had to resort to almost absurd workarounds just to make MT5 usable.

Here is one example that I use just at the beginning to drop all calculations. I never had to resort to such absurd conditions. I don't think these should even exist...

int OnCalculate([...])
  {
// [...]

   MqlRates rates[];
   MqlTick lt;

   if(CopyRates(_Symbol, _Period, 0, [...], rates) < 0)
    //  [...]

   if(SymbolInfoTick(_Symbol, lt))
    //  [...]

//---  workaround for MT5 bugs
   if(
      (int(fabs(rates[0].close - lt.last) / _Point) > 0) ||
      (lt.last > lt.ask || lt.last < lt.bid)
   )  
     {
      //  [...]
      return(rates_total);
     }
//---
         
// [...]
}        
 
4xonly #:

Hello. Reporting the same problem I had with previous build 5640. The commands slow down. Along with the journal, I'm attaching a video, showing how dragging the lines on an trade manager EA I use moves slowly and in steps. Dragging the price on the right side of a plain chart shows the same. Downgrading to build 5509 solves the problem.

P.S. I had to upload the video as it's too big for the allowed size as an attachment https://drive.google.com/file/d/1Jy5_l2suxorQBuy0MxkKhxz1M-3ZI2BN/view?usp=sharing

I installed a new version from scratch updated to build 5660, but my problem still persists, while build 5509 still works fine.

Just for the record, at some point I was sure that I saw an update (maybe 5667-March 3rd. Did I dream about it?) with still the same lagging issue, but now the latest is back to 5660.

 
4xonly #:

I installed a new version from scratch updated to build 5660, but my problem still persists, while build 5509 still works fine.

Just for the record, at some point I was sure that I saw an update (maybe 5667-March 3rd. Did I dream about it?) with still the same lagging issue, but now the latest is back to 5660.

You would need to check if you are still experiencing this issue with a "naked" chart.

So remove the tools you are using, one at a time, and see if the lagging/freezing is still there or not. 

It's perfectly possible that a tool works well with 5509 but not with 5660 due to the change of GUI rendering engine.

 

I'm running MT5 Portable on Windows 11. After upgrading to Build 5660 auto-update is triggered by showing Help > About (in order to check the current version). After the update is re-applied, the Build number is still 5660 with the same behavior.

 
Alain Verleyen #:

You would need to check if you are still experiencing this issue with a "naked" chart.

So remove the tools you are using, one at a time, and see if the lagging/freezing is still there or not. 

It's perfectly possible that a tool works well with 5509 but not with 5660 due to the change of GUI rendering engine.

I have done that: no change. As of today I have an instance updated to 5663 (installed from scratch) and another one to beta 5672 and there's no difference, whether with naked charts or not. Meanwhile the one that I keep downgrading to 5509 keeps working smoothly in any condition.
12345678910
New comment