Best posts made by cmuphyfx

Update - was able to make it work by utilizing the count and start positions fir iLowest and iHighest with the start index as today.

Thank you for the help!

And this will automatically connect to the buffers that the indicator has declared. If so, that's VERY helpful!

Thank you

I added the additional buffers as shown above, and then in an ugly comment printed them out and it all appears to be working!

@sktsec Found out it was the build version. Build 4040 works well, the latest demo build 4057 has a terribly slow strategy tester.

I ended up finding the issue - something I've never seen before. I have 4 once per bar blocks that execute and they were out of order and this is somehow causing my trades 'once per bar' to execute twice? I re-ordered them and this solved the issue. Still a VERY strange issue considering I disable the flags after a trade is place, at the top of my 'once per bar' I have a number of positions check to make sure it's less than 1, and 'on trade' I disable the flags also.

Sorry - thought I fixed the issue with the above renumbering, but it was actually this block... I didn't realize it goes down the logic path two times in this scenario.

I turned off the 2nd condition and I no longer get double trades. Dummy.

I use the strategy tester in MT5 for all my data - it gets the data from the broker where I also run the EAs. Data is very important - I've found optimizing from broker to broker is VERY different and should be avoided. If you test and tune on a specific brokers data, you should also run the EA there.