I am no coder, but from reading the thread I would think there were some very important changes from 1m to 1q that may impact performance.c1borg wrote:Ok thanks for the info might try and fit your settings into the 1q version if there is any benefits code wise.
IMHO one should always try to work with the latest versions because they are least bug prone. But also because it shows appreciation for the work of all excellent coders here working tirelessly in an effort to improve the EAs.
BUT ...if you have a profitable old version, one should IMHO always - over a period of two weeks and at least 100 trades -, run a new version parallel with the old version until convinced that you can replicate or improve on the profitable old version (with adapted set file when needed).
But back to Awesome:
One very important change would be that the issue of trades closing on the first opposite FB (instead of close on opposite FB ONLY WHEN SS agrees), was solved in 1o. The details are described in the thread.
I do not say that this fix improves results (I did not yet test conclusively myself). The 1o fix made Awesome close trades as originally designed, but this behavior would be differently from the behavior from versions before the 1o fix (as with 1o the setting about 'only close when SS agrees' in the setfile is no longer ignored).
Hence you need to adapt the set file if you want same behavior as before 1o.
According to the AwesomeOriginal thread there were also changes in 1q with respect to the minimum pip distance between trades.
My testing has not been able to keep up with the changes, so I can't yet report on how the changes impact performance.