Hi Scott,

My MT4 specific question (others on the MT4 comments board!)...

You say that you have tested using Dukascopy data.  I have been using and writing for MT4 for many years using TDS suite for testing but I'm a bit new to MT5 and I'm not aware of a mechanism for using external tick data with MT5.

Actually, scrub that - a little research has just located "TickStory" which I presume is the solution?  I'll add this question anyway in case you have alternative/better solutions.

Thanks, David.

PS.  Here's my test run from 2021-01-01 to date using the native MT5 test data!  Not good...

This does not look like you are using the correct setting. Your test still shows it is in profit. I would not say a profit is bad but this back test does not look like mine.
Come to Telegram and I will help you set this up.

Please download this back test here from 2009 to 2021. It is a Quant Analyzer report that is very detailed.

I'm using the default settings but with "Multi-Symbol" set to true but, of course, it is using whatever tick data the MT5 tester uses.  I'm not sure where it gets it from - the broker maybe?  If so it's not a particularly low-spread broker so that could be the problem.

I've installed TickStory but its really slow getting data so I'll report back somewhat later when I've had a chance to test using that data!

PS.  Here's my test run from 2021-01-01 to date using the native MT5 test data!  Not good...

Hi David, I attached a setting file that gave this Graph from Jan 2021 to OCT 2021.  It looks alot different than the one you posted here.
Let me know if this setting gives you a better back test.

Thanks Scott, all is a bit clearer now!  My settings file was no different from yours other than 'auto-lot' being set on yours.  However, I have now taken the trouble to use a terminal on my actual broker (Pepperstone "razor" account) and get the following...

So, it seems that the MT5 terminal gets its native data from the broker rather than some Metaquotes source as I had assumed!  Now it has the nice low spreads all is fine :-).  Presumably if I carry on the rather tedious process of importing the Dukascopy data from TickStory I'll get similar results to yours - which I will do but could take a while!

Thanks again, David.

Hi Scott,

I just downloaded a copy of your EA and loaded it per your YT video and I guess now it's just running. So I can expect it to automatically open and close positions for me, correct?

Regards,

Hanoz

Hi Hanoz. Yes that is correct... What broker are you using? We want to make sure your Market watch time is correct... If it is not I need to send a setting file...

Hi Scott.

I'm using Pepperstone.

I think the Market Watch time is set correct. My local time is GMT+8 (Perth, AU), and the Market Watch time is 5 hours behind me, making it GMT+3, which is what you recommend. Would that be right? Is there a another way to confirm that the time is set correctly?

I attempted to join the telegram group multiple times, but the browser simply doesn't proceed when I click on "Join Group".

Regards,

Hanoz

Yes!!  That looks a lot better. Now remember when you download the ticks from the broker keep an eye on the tick quality after a backtest... The memory in your computer and HD space is important the further back you test. I have a laptop that only gets good quality back testing from IC markets when I test 6 months at time.. On My dedicated back test machine using Dukascopy I use 100GB or Virtual memory on a Solid state 1 Terrabyte drive. It gets 100% tick quality from 2009 to 2021.... 

I am glad you got the back test working much better!!

Thanks for sharing.

Scott

Scott is The Man!!

Well he might be if only he'd respond to comments!  I'm not sure at what release this happened, but the value of the "GMT Offset" parameter no longer makes any difference to test results  (this is certainly the case for V2.2 and V2.4.).  You would expect it to move the 2 hour trade opening window, but all the trades take place at exactly the same time irrespective of the offset setting.  This is an issue for me because I do have brokers with (currently) a 1 hour GMT offset.

I posted this fact on the MT4 comments board on 13th November but no response yet.

Well he might be if only he'd respond to comments!  I'm not sure at what release this happened, but the value of the "GMT Offset" parameter no longer makes any difference to test results  (this is certainly the case for V2.2 and V2.4.).  You would expect it to move the 2 hour trade opening window, but all the trades take place at exactly the same time irrespective of the offset setting.  This is an issue for me because I do have brokers with (currently) a 1 hour GMT offset.

I posted this fact on the MT4 comments board on 13th November but no response yet.

Well he might be if only he'd respond to comments!  I'm not sure at what release this happened, but the value of the "GMT Offset" parameter no longer makes any difference to test results  (this is certainly the case for V2.2 and V2.4.).  You would expect it to move the 2 hour trade opening window, but all the trades take place at exactly the same time irrespective of the offset setting.  This is an issue for me because I do have brokers with (currently) a 1 hour GMT offset.

I posted this fact on the MT4 comments board on 13th November but no response yet.