
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
I didn’t understand anything: I can’t understand what exactly you want.
After you have selected "Debugging on real data" ( ) You go to MetaTrader 5 - a new chart will open in the terminal on which debugging will be performed. This is normal. It is right?
This doesn't Happen.
Once I am taken to MT5 No new Chart is opened The EA Panel which Common Input tabs doesn't even pop up.
I am taken Back to Metaeditor in less than 2 seconds from pressing F5 while in Metaeditor
No New Chart is Open. EA Runs OnDeinit.
if you set a breakpoint inside the code in MetaEditor. Do you put a breakpoint?
If I set a Break point or Toggle Bookmark or even non at all same thing Happens
This doesn't Happen.
Once I am taken to MT5 No new Chart is opened The EA Panel which Common Input tabs doesn't even pop up.
I am taken Back to Metaeditor in less than 2 seconds from pressing F5 while in Metaeditor
No New Chart is Open. EA Runs OnDeinit.
If I set a Break point or Toggle Bookmark or even non at all same thing Happens
I see only one reason - an error in your code interrupts debugging. View the Experts and Journal tab of the terminal.
I see only one reason - an error in your code interrupts debugging. View the Experts and Journal tab of the terminal.
I inserted printf functions through out my code and those from Initialisation and deinit are the only Printed infomation in the Expert and Journal Tabs
I run the same code inside two different Broker MT5's debug works perfectly, but on the MT5 i downloaded from metaqoutes (default MT5) it has this error even the simple code
this also has same problem in the default MT5, but on Broker MT5 it procedes to Debugging.if the issue was in my code I take it that broker MT5 would also display same behaviour but that isnt the case the case is only on the default version
No errors in log, only the "disconnected" message.
Regardless if I have made any changes or not to the chart before I saved the debug template.
The mere presence of the template file seems to have the debugging disconnect.
As soon as I remove the debug.tpl the debugger launch works again.
On Windows 11.
In my case if I save a template "debug.tpl" for the EA I am debugging, and then launch the debugger with Start on Real Data (F5) then the chart flashes by faintly and exits.
No errors in log, only the "disconnected" message.
Regardless if I have made any changes or not to the chart before I saved the debug template.
The mere presence of the template file seems to have the debugging disconnect.
As soon as I remove the debug.tpl the debugger launch works again.
On Windows 11.
there have been a few threads recently from users with template issues. And like yourself, their issue was fixed when they deleted the template. I suggest that you recreate your template from scratch.
In past this was a common issue after every mtx update, but it seemed to have gone away finally after years and years of it happening. I still have process of having 3 or more copies of my fav templates as my normal process, as direct result of those/this issue in years gone by.
And apparently this issue has popped up again.
If your issue continues. another possible solution has been to delete the metaeditor.ini file.