MetaTrader 5 : Next Generation Trading Platform
Friday, November 27, 2009
Finally, MetaQuotes Software Corp. launches their newest version of MetaTrader Trading Platform which now is the fifth generation. The newest, MetaTrader 5 is in beta testing now. MetaTrader 5 has newest programming language called MQL5 meanwhile MetaTrader 4 was using MQL4. Learning from changing of the previous generation, it supposes that many works will have to do to synchronize the indicators and expert advisors. Many EA programmers will hate this but some are expected this upgrade. Hopefully our hard work will be worth with the newest features of MetaTrader 5.
Meanwhile, for traders there will be a lot of questions about this MetaTrader 5. The rumor is this version implements the newest NFA rules about trading. There will be no hedging and will implement FIFO (first in first out) in this MT5. I hate to say that regulators and some institutions use many ways to prevent traders to gain profit but the facts are going to this situation. If MetaQuotes can’t find solutions for these, I think there will be a lot of traders are looking another platforms for trading.
In case that you want to try the beta version of MetaTrader 5, you can find it at here.
Posted by Aryana 10:21 PM 0 comments
Potential Bug in MT4 : All EA Traders Please Take Note!
Monday, February 16, 2009
Hi friends...
It has been a long time since my last post. Lets say that I almost lost my interest of Automated Trading in that time...
So, back to forex world :D
I got a message from CK.. He is the famous EA Reviewer from Singapore. Hopefully this message doesn't make us to step back from Automated Trading.
Ck Owyong (Singapore) wrote on January 6, 2009 at 11:36am
dear all,
i got a heads up from a respected trader informing that a MT4 broker has discovered a bug in MT4. it intermittently affects OrderClose and EA-side (in-code) trailing stops, potentially leaving positions open when they should be closed.
more details below.
ck
==================
To all ATC EA traders,
Please be aware that ATC has discovered a known bug in the MT4, causing intermittent operation of EAs. Further, due to the nature of how this bug affects EA operation, it affects the server flow control that the AR system relies on to provide stable operation to EA’s. For reasons beyond the scope of this notice, we do not believe that Metaquotes is inclined to solve this problem right away, given we have notified them. Therefore it is ATC’s place to be sure that our traders are aware of the issue and until we have solved the problem here, (hopefully by this weekend), traders can decide from the information below, if they should continue trading today.
Cause: The AR kit ATC is developing, uses most of the available server flow control commands that MQ provides for “Controlled and Proper” server communication, which in part plays a role in connection stability and CPU / TCP control. It further assures against poorly written EAs / scripts from “storming” the server in an uncontrolled manner. Since the MT bug is directly involved in one of the critical flow control commands, the more a programmer relies on better flow control coding, the more likely the problem will interfere with an EA; clearly a “Catch 22” which speaks to a long history of problems with MT4.
This problem affects all MT brokers, not just ATC. Sadly, many brokers do not impose proper EA design and therefore it may falsely “appear” some are not affected.
Impact: Traders may find that EA’s which do perform orderly flow control, may suddenly refuse to trade, without warning. If logging is turned on and the experts tab reads “Not Connected” or “IsConnected = False“, during failure to trade, then the bug in MT has surfaced, which can be proven by verifying that ticks are still flowing into the price feed, while the EA is failing in this way. Normally, this results simply in an EA that cannot “create” a trade. HOWEVER, if the bug surfaces while trades are in play AND the EA in question directly manages CloseOrder events, the EA may fail to close the order timely and the price then can pass through the intended close. This is mostly an exposure where the EA itself is managing a direct “OrderClose” or the trailing of a TP or SL is being done in code. Fortunately this affects less EAs as these forms of order close are not commonly used by most EA designers.
It is also possible, depending on the EA design, that a standard “Trailing Stop” fired from within the EA, could also fail to fire and therefore the trailing stop may not advance as it would normally, had it been fired manually from the MT4 by the user and the result would be higher losses or a failure to capture profit via trailing stop.
Fortunately, discovery of this problem comes at End of Year when most traders tend to lay back and wait for volume to pick up in coming days. Accordingly, ATC programmers are now working around the clock, through the weekend to develop a solution we feel will remove this exposure completely, regardless of Metaquotes apparent dismissal of the issue.
If a trader is uncertain if his EA could be affected this way, ATC recommends holding up on trading for today and until a solution is announced this weekend.
We do expect the solution will be two fold…
1) An AR update at revision 0.032, by this Sunday evening which will include a DLL requirement and enable safe trading immediately
2) The eventual replacement of the OpenSource OrderReliable include file, for a closed source retail replacement, scheduled for January 15, to complete.
Thank you for your attention to this issue and please watch for further news as we complete testing.
ATC Brokers - Support
Posted by Aryana 11:59 PM 11 comments
