Please find attached a simple TRIX indicator EURUSD on 15 min time bars (based close & bid price) calculation.
If you run it on JForex2 Local Run and JForex3 Local Run you see it produces different results.
The difference might be low if you start it later in the week (like now when I wrote this post), but it is very high on a Sunday when the markets starts.
Example given:
Do a Historical Tester run from Sunday 2017-01-08 on both platforms and you will see the difference immediately.
JForex2.45.65
2017-01-11 21:03:52 trix = -0.009622293992805897 at 08-01-2017 22:45:00.000 GMT
2017-01-11 21:03:52 trix = -0.010362616995940321 at 08-01-2017 22:30:00.000 GMT
2017-01-11 21:03:52 trix = -0.011048734967755713 at 08-01-2017 22:15:00.000 GMT
2017-01-11 21:03:52 trix = -0.011721022921562518 at 08-01-2017 22:00:00.000 GMT
JForex3.0.16
2017-01-11 21:04:40 trix = -0.01612478451243904 at 08-01-2017 22:45:00.000 GMT
2017-01-11 21:04:39 trix = -0.016003175668055647 at 08-01-2017 22:30:00.000 GMT
2017-01-11 21:04:39 trix = -0.015647086565251378 at 08-01-2017 22:15:00.000 GMT
2017-01-11 21:04:39 trix = -0.015037404668871712 at 08-01-2017 22:00:00.000 GMT
This problem is very serious as many strategies use indicators like this.
It affects also JForex2 strategies running in Remote Run!
If you remote run strategies on JForex2 it gets executed on a JForex3 engine, see support answer on
https://www.dukascopy.com/swiss/english ... 65&t=54602Please help! Should we (JForex API users) change the indicator call (so JForex3 won't be downwards compatible) or will you change JForex3 so it gets downwards compatible?