Awesome + SS version

[Letsarb]

Other news is Walywonka has come up with a 3SS version with adjusted Flying Bhudda code which im going to try.

Yes I I'm testing a Higher timeframe range (1W, 1D, 4H) and also a lower timeframe range (1H, 30M, 15M) to see if there any any benefits or not...

For those that have been testing this on multiple terminals you'll have also noticed the flying buddha symbols did not match, I also fixed this in addition to adding a 3rd Superslope timeframe so you'll now get the same FB signals across multiple terminals as it should be.

I did run this on a live account last week with positive results.

Cheers Wally

Hi Wallywonka,

Could you tell exactly what you did in the code when you say you fixed the flying buddha symbols that did not match ?
I had a fast look to the code and I did not see any differences for the flying buddha (only the inputs are different with the fast and slow periods)...

Cheers

Letsarb

[Letsarb]

If anyone is having issues with the SuperSlopes not being populated correctly you can download this version which should fix the problem for you.

Is this code correct im not a coder but just an observation should the last line contain SsTimeFrame3rd as opposed to SsTimeFrame1st?

Code: Select all

ChartSaveTemplate(0,StringFormat("ZZT2MTPL-%s-%s-%s-%d-%d-%d-%d-%d-%d-%d","SHF","AWSSG","MULSYM",
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame1st, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame1st, 0))
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame2nd, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame2nd, 0))
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame3rd, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame1st, 0))

If it is correct just to be clear, what was the problem in the previous version which needed fixing?

Hi C1borg,

No worry, it is only a comment, a bad copy paste without any incidence on the code...

Cheers

Letsarb

[c1borg]

Hi C1borg,

No worry, it is only a comment, a bad copy paste without any incidence on the code...

Cheers

Letsarb

No worries didn't notice the comment lines still a novice.

[hilavoku]

Hi,

all together. After some while and trying Awesome last year and happy to see it arise again in a modified way I also started all over with Awesome+SS today.

It has opened some USDJPY trades but all GBPJPY and other trades errored out with

2018.05.15 19:12:57.552 AwesomeSS GBPJPY,H1: Alert: GBPJPY AwesomeSS OP_BUYSTOP order send failed with error(130): invalid stops TF = M5: bid = 148.95 Price = 149.06


I used the set file from the first post and only changed the DailyPercentOfBalanceProfitTarget to 0.0

I had the same problems with another EA where sometimes this error appears. I am using a demo account from Forex4You. I think i need to change the broker. What do you guys think?

thanks in advance
hilavoku

[Gertje]

Hi,

all together. After some while and trying Awesome last year and happy to see it arise again in a modified way I also started all over with Awesome+SS today.

It has opened some USDJPY trades but all GBPJPY and other trades errored out with

2018.05.15 19:12:57.552 AwesomeSS GBPJPY,H1: Alert: GBPJPY AwesomeSS OP_BUYSTOP order send failed with error(130): invalid stops TF = M5: bid = 148.95 Price = 149.06


I used the set file from the first post and only changed the DailyPercentOfBalanceProfitTarget to 0.0

I had the same problems with another EA where sometimes this error appears. I am using a demo account from Forex4You. I think i need to change the broker. What do you guys think?

thanks in advance
hilavoku

I think so too.
The error indicates your ‘broker’ uses a minimal pip distance to enter from current price.

[wallywonka]

If anyone is having issues with the SuperSlopes not being populated correctly you can download this version which should fix the problem for you.

Is this code correct im not a coder but just an observation should the last line contain SsTimeFrame3rd as opposed to SsTimeFrame1st?

Code: Select all

ChartSaveTemplate(0,StringFormat("ZZT2MTPL-%s-%s-%s-%d-%d-%d-%d-%d-%d-%d","SHF","AWSSG","MULSYM",
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame1st, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame1st, 0))
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame2nd, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame2nd, 0))
            SsBarTime[pairsIndex] = iTime(symbol, SsTimeFrame3rd, 0);
         }//if (SsBarTime[pairsIndex] != iTime(symbol, SsTimeFrame1st, 0))

If it is correct just to be clear, what was the problem in the previous version which needed fixing?

Think that's from an older version and not the one above I posted but yeah it was only a commented line so it didn't affect anything.

[tomele]

Hi folks.

The posted code doesnt make any sense. What is that? I cant find it in any EA.

[c1borg]

Hi folks.

The posted code doesnt make any sense. What is that? I cant find it in any EA.

It was posted here http://www.stevehopwoodforex.com/phpBB3 ... 90#p161670 by Wallywonka but is to trry and not been proven as yet.

[hilavoku]

...

I think so too.
The error indicates your ‘broker’ uses a minimal pip distance to enter from current price.

Thank you Gertje. I will open a demo account with GlobalPrime.

[wallywonka]

Hi folks.

The posted code doesnt make any sense. What is that? I cant find it in any EA.

It was posted here http://www.stevehopwoodforex.com/phpBB3 ... 90#p161670 by Wallywonka but is to trry and not been proven as yet.

I think you are looking at an older version of the code mate, the one I posted on the previous page does not have those changes you listed.