MichaelM » Tue Sep 09, 2014 7:48 am wrote:I've brought this up yesterday, Steve already implemented a fix for it in v1d in post 1 yesterday

spotdespot » Tue Sep 09, 2014 4:46 pm wrote:Would someone who can code mind having a look at the last release please as I set up a new demo, where I wanted to try out some manual filtering on H4 - so literally turn the EA off if certain conditions aren't met on an H4 chart but keep the logic the same as the M15 demo that is doing very well (TradingTimeFrame = 15).

So I loaded exactly the same settings as I have on M15 but have the EA on H4 timeframe charts. What I have ended up with this morning is multiple trades on the "H4" account with those trades taken being taken every 15 minutes e.g. GBPJPY short at 07:00, 07:15 & 07:30 etc. but no trades yet on my M15 original demo.

Every time I look at code it seems I waste people's time

Thanks,
Dave.

MichaelM » Tue Sep 09, 2014 7:53 am wrote:Wait... so you have TradingTimeFrame=15 on H4 charts and you're wondering why it's taking trades every 15mins?

when having done something dumb with a copy/paste is difficult....

spotdespot » Tue Sep 09, 2014 7:05 am wrote:

MichaelM » Tue Sep 09, 2014 7:53 am wrote:Wait... so you have TradingTimeFrame=15 on H4 charts and you're wondering why it's taking trades every 15mins?

Mmmm sarcasm nice - I will ignore that.

It seems I do actually still have the old version somehow despite having "replaced" the EA, void GetFractals still has the null,0 values. I will redownload - I must have screwed up somewhere.

Just saw your comment Shelley - yes I know that. That was the intention. However that wouldn't explain how I could get a trade every 15 minutes on one pair, unless the definition of fractals has changed.

Trying hard not to be offended for being treated like an idiot when having done something dumb with a copy/paste is difficult....

magft » Tue Sep 09, 2014 10:51 am wrote:
I've noticed more and more in the newer versions of MT$ when updating an EA sometimes it doesnt recompile the mq4 to ex4 and so you make a change to the code then compile and then scratch your head as to why it makes no difference!

Safest thing it to close Empty4, delete old mq4 and ex4, then copy new mq4 in to dir and then open Empty4. It should then compile the ex4 and you should be good to go.

BTW Steve i am liking this EA making a steady 1-2% a day using just a basket trailing stop of $50 trailing by 75% on a 10k demo. I know its early days but i'm liking this one a lot.

Just a thought but as for guessing the mindistancetoMA and gap between trades it may be worth using a factor of ADR to adjust for volatility of each pair. i have used this before and it may help with stoping the whipsaw on all pairs once ideal setting found. But i guess like with all of these we need to let it run its course and watch what happens.

Regards

Mike

Optional maximum distance filters

Minimum distance from the Moving Average. If enabled, FB draws a dashed Turquoise line to show this price on our charts, then:
MinDistanceToMaPips: the closest that FB will allow the market to approach the MA before cancelling a trade. Zero value to disable this filter.
ShowMinDistanceOnly: defaults to 'true'. This allows you to have the line on your chart for reference and research, but FB will not use it to cancel a trade.
Maximum distance from the Moving Average. If enabled, FB uses ATR to calculate the price for drawing a dotted Turquoise line to show this price on our charts, then:
AtrPeriod: the default equates to roughly a month of D1 trading. Zero value disables this filter.
AtrTimeFrame: the time frame used to calculate the ATR. Enter this input in minutes. The default is the D1.
AtrMultiplier: multiplies the calculated ATR by this figure.
ShowMaxDistanceOnly: defaults to 'true'. This allows you to have the line on your chart for reference and research, but FB will not use it to cancel a trade.

fxozgirl » Wed Sep 10, 2014 2:53 am wrote:Hi Steve,

Just getting my head around the latest version and have turned on (left as default) the new MinDistanceToMaPips & MaxDistanceFromMa using ATR as described by you in Post 1 below.

Not sure if my jetlagged brain is not firing properly but I assumed the intention of MaxDistance from MA was to prevent FB taking a trade if it was outside the max distance from MA? I had a GBPUSD trade taken this morning that was well outside the line set. Apologies if I have misunderstood this function. (See screenshot below)