Viewer Discretion Advised: Shall we shag now or should we shag later? :-)
- #5,061
- Edited 5:06am Jun 18, 2010 4:52am | Edited 5:06am
- | Commercial User | Joined Jul 2009 | 5,375 Posts
- #5,062
- Jun 18, 2010 4:59am Jun 18, 2010 4:59am
- Joined Apr 2009 | Status: Trader | 2,035 Posts
Hi, This is probably for piptician. I just loaded v11 and seem to get the same errors a couple of other people back a few pages. Can you help me with it please? Ta. Matt
help you he could probably do with a bit more information!
- #5,065
- Jun 18, 2010 5:20am Jun 18, 2010 5:20am
- Joined Apr 2009 | Status: Trader | 2,035 Posts
The EA is optimised for GBPUSD and this pair was chosen for its volatility, even
during the relatively quiet Asian session 22 pips is easy to get.
You could argue that other GBP pairs should have a similar price action and this
could be the case but, if you look at GBPJPY for instance, you will see that for
our EA to work you would need a very large stoploss to get round the drawdown
during the Asian session.
In short, if you want the EA to work on another pair you would need to do a lot
of optimisation passes to find the sweet-spot!
during the relatively quiet Asian session 22 pips is easy to get.
You could argue that other GBP pairs should have a similar price action and this
could be the case but, if you look at GBPJPY for instance, you will see that for
our EA to work you would need a very large stoploss to get round the drawdown
during the Asian session.
In short, if you want the EA to work on another pair you would need to do a lot
of optimisation passes to find the sweet-spot!
- #5,066
- Jun 18, 2010 5:27am Jun 18, 2010 5:27am
Sorry to be a pain but there have been a few different errors and for piptician to be able to
help you he could probably do with a bit more information!
- #5,068
- Jun 18, 2010 6:09am Jun 18, 2010 6:09am
You need to check the MT4 journal to see if any errors are reported at the relevent time.
However, I should point out that this EA is designed to operate on GBPUSD H1 only and
we cannot support any other pairs or time-frames on this thread, it is just too much for
myself and piptician to cope with!
- #5,069
- Jun 18, 2010 6:13am Jun 18, 2010 6:13am
- Joined Apr 2009 | Status: Trader | 2,035 Posts
noted.. thank you geoffb65
- #5,071
- Jun 18, 2010 7:37am Jun 18, 2010 7:37am
- Joined Oct 2008 | Status: Sailing for pips | 2,099 Posts
- #5,072
- Jun 18, 2010 7:38am Jun 18, 2010 7:38am
- Joined Apr 2009 | Status: Trader | 2,035 Posts
Live on FXDD last night running v4a.. +1 (don't understand that), but demo V11.. +22, +3, and +11.
I'm wondering if I should use V11 on live account, but use 1 trade preset....
- #5,074
- Jun 18, 2010 8:13am Jun 18, 2010 8:13am
- Joined Dec 2009 | Status: Trader | 6,603 Posts
It's the trailing stoploss that causes that and it is just the same with Tokyo v11 !
- #5,077
- Edited 11:13am Jun 18, 2010 10:37am | Edited 11:13am
These trades are triggered during the sunday GAP ! Its always dangerous to trade in the sunday night - huge gaps may occur - if some of the brokers have coincidental unfavorable data (that means: "unfavorable" for a given broker only !) - the EA could open a trade. Other brokers with another datasheet wouldn't open this trade. So in the cases of IBFX and FXDD in this week we have to say - tough luck ! I remember - some members here posted about these losses too - but take into account: only 2 brokers failed in this special case ! All the others didn't trade sunday night - and that was well done !
Of course if you are experienced enough - you could trade the gaps consciously ! Very often the gaps will close sooner or later !
Of course if you are experienced enough - you could trade the gaps consciously ! Very often the gaps will close sooner or later !
.