MetaTrader 5 Platform Update Build 6090: General Improvements - page 5

New comment
 
Alain Verleyen #:

Default parameters ?

Just sent you the template and EA.
EA isn't a robot.
It has a drawing tool, works on click on a candle.
That is the trade layout.
Clicking the button On initiates the EA Entry algo.
I wasn't using the EA, it was idle when the symptoms happen.
 
Alain Verleyen #:

I don't know your name so I can't use it.

I feel I need to set the record straight.

A strong affirmation. What are we supposed to do with it ?

My experience with MT5 is heavy, I built very complex indicators and EA and my experience doesn't confirm you affirmation. Still I am ready to investigate as maybe you have a use case not covered by my experience. So anyone claiming he doesn't receive help is plain wrong. To get help you have to collaborate with the one trying to help, not be dismissive. Whatever the problem, any experienced coder will say you the same : the issue needs to be reproduced. For that you need to provide me what is needed, I can't guess.

Additionally I never insulted anyone. I absolutely don't care about your coding skills.

You can consider I am the representative of MetaQuotes on this forum, even if I don't work for them, I do have good relation and private channel to send them bug report.

So who is blocking the process, what are you afraid of leading you to refuse to provide what is needed ?

In case it's not clear what I need :

A clear description of the issue. A log showing your config (Journal log), if any, a log about the execution. Possibly screenshot(s). Often it's not enough, I need code, code that compiles and reproduce the issue clearly, eventually the parameters used, the chart settings, the steps you used. 

Debugging is an art based on a scientific approach, based on facts, not on assumptions, not on apriorism.

I am still ready, the ball is on your side. That being said it's clearly my last attempt with you.


About this "confusion", if I may?
When I was chatting with AI about this, AI found the earlier complaints or reports which matched my symptoms.
That's how I learned that this issue wasn't new and the link to this thread.
AI also said that reporting to MetaQuotes helpdesk was useless, because they don't answer such reports.
I don't know if that's true or not, but I followed AI's advice to post my report here, so I did.
I think that it would be quicker if all people involved could somehow find the common denominator for all these cases.
For example, I did have a similar case with an indictor I coded for someone.
It was a relatively simple indicator plotting lines at specifed distances from High and Low.
The indicator seemed to cause a very similar symptom:
The error, and the candle was stuck, and the Ask/Bid was not where the candle suggested it should be.
I did optimization (rewrote the indicator) and the user said it was working fine.
The user was also using an EA, not the one I am, but another one, a money management EA.
That was before I seriously started approaching this issue on my MT5.

So, what's the common denominator?

 
Dadas #:
AI also said that reporting to MetaQuotes helpdesk was useless, because they don't answer such reports.

Strictly speaking yes, because the Service Desk is dealing with financial issues only.

The appropriate way is on the forum, where you will get help and answers from moderators or Metaquotes admins.

Dadas #:
So, what's the common denominator?
That's what we will maybe discover from your code. Thank you for sending it. I will keep you posted of course.
 
Alain Verleyen #:

Strictly speaking yes, because the Service Desk is dealing with financial issues only.

The appropriate way is on the forum, where you will get help and answers from moderators or Metaquotes admins.

That's what we will maybe discover from your code. Thank you for sending it. I will keep you posted of course.
BTW, some time before, months earlier, I remember noticing this similar symptom, but I wasn't very interested in MT5, so I just closed MT5 and restared it. The symptom was that MT5 seemed to be unresponsive even with a blank chart, as in nothing was happening, chart wasn't plotting, price wasn't moving. To make things clear, I have 600 Mb/s optic cable internet which is stable, and I am on ethernet cable, so it can't be a connection issue.
And also, I turned off a number of Windows functions which could potentially cause some issues.
 
Andriy Moraru #:

Account change causes EA receives incorrect values for Ask/Bid via SymbolInfoDouble.

Test code:

void OnTick()
{
    Print(Symbol(), ": Ask = ", SymbolInfoDouble(Symbol(), SYMBOL_ASK), ", Bid = ", SymbolInfoDouble(Symbol(), SYMBOL_BID));
}
I'd be interested to see what happens if you add an OnInit() event handler up top, insert a string variable defined as _Symbol or Symbol() therein, and then use that variable in OnTick().
 
Ryan L Johnson #:
I'd be interested to see what happens if you add an OnInit() event handler up top, insert a string variable defined as _Symbol or Symbol() therein, and then use that variable in OnTick().

Same result:


string s;

void OnInit()
{
    s = Symbol();
}

void OnTick()
{
    Print(s, ": Ask = ", SymbolInfoDouble(s, SYMBOL_ASK), ", Bid = ", SymbolInfoDouble(s, SYMBOL_BID));
}
 
Andriy Moraru #:

Same result:


I was trying to help, but it looks like this forum doesn't like it when we ask AI and post the links to the conversation....
Sad, because AI can provide quick solutions to the problem.
The problem is stale data.
Basically, SymbolInfoDouble() still has the old account data cached and needs a bit of time to catch up on the new account data.
So, it's advisable to first sign in to the new account symbol:
string s;

int OnInit()
{
    s = _Symbol;
    if(SymbolSelect(s,true))
   return INIT_SUCCEEDED;
}
Further measures can be taken, too, in order to provide some slack.

BTW, Build 6090 has AI Assistant already implemented in Meta Editor (IDE)!
Files:
QuoteGuard.mqh  14 kb
QuoteGuardDemo.mq5  5 kb
 
Dadas #:
I was trying to help, but it looks like this forum doesn't like it when we ask AI and post the links to the conversation....
Sad, because AI can provide quick solutions to the problem.
The problem is stale data.
Basically, SymbolInfoDouble() still has the old account data cached and needs a bit of time to catch up on the new account data.
So, it's advisable to first sign in to the new account symbol:
Further measures can be taken, too, in order to provide some slack.

BTW, Build 6090 has AI Assistant already implemented in Meta Editor (IDE)!

There is no problem to use AI.

A forum is just not the place to post AI message. People can use AI themselves; they don't need someone else to do it for them and then post it on a forum.

 
rkdius #:

You're right, the EA itself is not a problem, the way it is run by MT5 is the problem.

All I'm saying is that you won't get "indicator too slow" error without the EA running along with indicators. But even without any EA running there are issues with chart response, there is a lag occuring "randomly" slowing down indicators, most of the time it is unnoticed and only comes out on high tick volume charts during busy hours, when the volume is highest. It is small lag that is compounded with each tick. That's all I can figure out. There was no such issues with MT5 until few months ago. It's either MT5 or MQL5 compiler, not your indicator or EA.

Don't worry about Alain complaining on me, I couldn't give him what he's asking me for and we had a row, no big deal. I'm sure he will help you as much as he's able to.

Well, it turns out that the EA actually can be the problem.
I asked the new Meta Editor AI Assistant, and:

Verdict: Yes — this EA can absolutely push indicators past their time limit

I read the whole EA ( StormTrader_BreakOut_EA.mq5 ). It does not touch indicator threads directly, but it doesn't need to. The error  indicators is too slow, rewrite the indicator, please  appears when an indicator's  OnCalculate()  exceeds the terminal's allowed time (commonly cited as ~10 seconds per pass), after which MT5 kills that indicator's thread. An EA can make that happen indirectly in three ways:

  1. Saturating CPU so indicator calculations simply can't finish in time;
  2. Lock contention on the shared history/timeseries cache (all MQL5 programs'  CopyRates / iXXX / HistorySelect  calls synchronize on the same internal data), so indicators block while the EA hammers the same data;
  3. Blocking server round-trips ( HistorySelect  triggering a history sync), which stall anything waiting on that cache.
 
Alain Verleyen #:

There is no problem to use AI.

A forum is just not the place to post AI message. People can use AI themselves; they don't need someone else to do it for them and then post it on a forum.

Isn't the purpose of a forum to help each other?
So, if one person has the time and shares a chat with AI, why is that prohibited?
You could allow only Meta Editor AI Assistant, if you don't want other AIs, here, for example. 

BTW, None of us know everything, or are able to think of everything.
So, useful hints can be provided by AI.
I don't see the logic behind prohibiting AI messages, here.
1234567
New comment