Peaky

[renexxxx]

I've also joined the Peaky fun and must say that I'm extremely impressed:

Peaky.PNG

Hats off to you Steve! If Peaky continues as it has this week, we have a winner!

[Dexonite]

Wow Steve and Leon, just wow.

Hopefully this is of value to someone:

If you, like me, are using a mini or micro account and are struggling to get the dash to work you might want to try what I did:

My charts are marked ie. GBPUSDmicro and did not work as a "reserved" template. What I did was open a chart, USDSGD in fact (you should have the "normal" pairs in your Market Watch, otherwise just press Ctr+U and enable one from there), and set it up as the "reserved" template with the dash expert on it. Then in the expert's field "PairstoTrade" I copied all the pairs in that field, pasted into a text file and added the "micro" bit after each one for example "EURUSDmicro,GBPUSDmicro," and now everything is working perfectly.

I guess this could be fixed in the code but I'm way too novice at this to even attempt so the workaround is good enough for me

Gents, I don't know what inspires me more, the trading some of the folks on here can pull off or the amazing way you put ideas into practice and the crazy speed you do it in...

Anyway, can't wait for Monday so I can start testing Peaky properly.

Have a great weekend everyone

D

[cozybooks]

Peaky closed another 100 pips profit while I wasn't looking on Friday on my live account using the 1 hour TF. Just a top notch trading approach and a great EA to do all of the hard work. Hats off to you, Steve! :hi: :hi: :hi:

[SteveHopwood]

V 1f is in post 1. No biggy this one. All I have done is comment out lines 767-770. These are the lines that sometimes cause a time frame jump. The time frame change goes back to when the Peak Hilo Indicator calculated the number of bars on the chart dynamically, and are no longer needed.

------------------------------------------------------------------------------

Last week:

Last week.png

No idea where the extra take profits came from.

Since starting the demo:

All history.png

This includes the effects of some coding bloops.

I am going live with this when the markets re-open..

[andwen]

Thanks to Steve and everyone for this EA and the most recent update.

:hi: :hi:

Andwen

Noobs - Founding Member

[ZumZum]

As always awesome job Steve, hats off :hi:
Still can't believe you managed to automate this trading approach. Genius. The only EA I can trust. Works perfectly in combination with manual trading.
Below is my demo testing last week on H1 pretty much OOTB fully on autopilot:

PeakyH1.PNG

PeakyH1-2.PNG

Playing around on M1 with some manual intervention:

Peaky 1M.PNG

Cheers,

[SteveHopwood]

I have written a User Guide. Whilst doing so I noticed a couple of redundant variables and renamed a couple more, as well as finding another code block that did a time frame flip.

All this is in 1g in post 1. You do not need either 1f or 1g if you are happy with 1e.

[Zool]

First of all: wonderful idea and coding Steve, thank you very much for this!

I've been away form Forex for a couple of years (big family changes and other everyday life reasons), and now have the time and energy to return I have to relearn a lot of things, and saw that how Bob's method evolved during the time I was away. Somehow I missed all the Sixths thingies when I was around earlier, but now it immediately catched my attention, because it is very close to my kind of thinking and ideas.

On to the topic:
I have found something that maybe intentional or unintentional, but the EA won't change the TP of an active stop order when new highs or lows formed and the order is moved to follow the new sixth line. It could happen that the stop order was moved away from the original location by a hundred of pips and the TP stay at the same place, and when the order is filled it will not reach the TP because it is now 200 pips away - well eventually it will reach maybe - (see attached screenshot).

It was long since I last made some MQL4 coding, but when I checked the EA code I noticed that in the CheckPricesAreStillValid() function it updates only the order price with the new value, but keeps the TP and SL the same as the original (ModifyOrder() call at line 4181). Maybe I'm wrong, but shouldn't it recalculate and modify the new TP and SL levels too?

EDIT: I commented out line 4181 and put this code there, and it seems to me that it solves this TP/SL moving thing:

Code: Select all

   double take, stop;
   stop = CalculateStopLoss(OP_SELL, newPrice);
   take = CalculateTakeProfit(OP_SELL, newPrice);
   bool result = ModifyOrder(OrderTicket(), newPrice, stop, take, OrderExpiration(), clrNONE, __FUNCTION__, oop);

I don't know if this is OK to post this here, if not, Steve delete this if you want...


The other one thing I noticed that if I change the zoom level in the settings, it freezes Empty4. There is a ChartScaleSet() call with the user set zoom level in the Init section, and in the GetSixths() function, but with a set 0 value. The GetSixths() called in the init section, and with every thick through the ReadIndicatorValues() function. Could these ChartScaleSet() calls with a fixed 0 causes the freeze of my platform if I choose other zoom level than 0?

Ps: English is not my native language, so I hope my composition was good enough to get my thoughts through.

[cozybooks]

Steve,

Great User's Guide for Peaky! To everyone else, if you haven't read it yet, Steve is providing a great mini trading lesson besides all the great stuff in the User's Guide. Dexonite had it right - what else can you say but Wow!

Hop between different pairs and timeframes, and you have more trading options than anyone could want.

If Peaky doesn't get you excited about trading, nothing will!

[SteveHopwood]

V 1h is in post 1 in response to Zool's post two higher than this one. Thanks Zool. That was a really helpful contribution that explained those odd take profits I described earlier.

DIYers, go to line 2658, a blank line and insert this:

Code: Select all

      CheckTpSlAreCorrect(OrderType() );

I had not realised that CountOpenTrades() was missing this call. Users of older versions need to make this change, so do a search for:
if (CloseEnough(OrderTakeProfit(), 0) && !CloseEnough(TakeProfit, 0)) InsertTakeProfit(OrderTicket() );

This will take you to the correct place.

cozy, thanks for your kind words. I am glad the User Guide is helpful.