I add another feature to VS_EUROCROSS that allowing EA to show its target. On my experience during last two weeks, it seems the Expert suffered too much slippage. This is especially when Expert holds more then 1 positions and tries to close all position at once.
What I see if price make up down move within 6 pips will make EA react and often EA will get requote. After make several test finally I can add this feature to VS_EUROCROSS without affecting all the exit rules.
POSSIBLE PROBLEM IN LIVE TRADE
Although backtest show there is no much difference when using fixed target (I am not sure but its looked better), but something difference may occur in live trade. All broker can rise their stoplevel and if the stoplevel become the highest then our signal filter or MyOwnTarget, then the target become meaningless. But still it is useful when somehow you loose connection to your Server. Although it is possible to tell EA to set the target every tick or bar, but I decide to let EA doing this thing just when new position is taken. But still the EA will force to give fixed target when it failed in the first attempt. Therefore each position will has difference fixed target.
Another possible problem is the freeze level. This is happened when the expert tries to close an open position while its target is very close with market’s price.
To disabled this feature, then you can set the VISIBLETP variable with FALSE, because I let the default value with TRUE.
You can see my MT4stats; the trades on EURGBP have a fixed target and one of them get hit.
Showing the Target
Wednesday, July 15, 2009
Risk Warning
Please note that Trading in the Foreign Exchange market might carry potential rewards, but also potential risks. You must be aware of the risks and are willing to accept them in order to trade in the foreign exchange market. Don't trade with money you can't afford to lose.
2 komentar:
Is it possible to add a static linked volatily.dll to the download section? I can not test under Vista. I get "cannot load library 'volatily.dll' (error 126)" According to some webpages this looks like a problem loading additional dlls.
Thanks!
Hmm looks like that is not the problem, because all others dll was compiled within volatily dll use static link, that's why it has bigger size. The problem directly to volatily.dll.
Post a Comment