Phantom Moving Average
-
For a reason I don't understand, a 100 bars moving average appears when backtesting this EA:
https://fxdreema.com/shared/DZGmOsPSd
As you can see, no such MA is programmed at any block. Why did that appear?
-
Hmm I only see 300 and 1000 MA in my BT
-
Really? Could you please try a short backtest? You will see a 100 MA acting as a moving SL. That's the weirdest thing I've seen so far.
This EA was originally designed for a 100 MA. I bactested it and results were bad. Then I changed all blocks for a 300 MA but the original one still remains somehow.
-
EURUSD M30, every tick:
Really strange if you get different results.. Do you have these default inputs?
-
Yes, I'm using the same default imputs, but things are worsening. I don't know why, but now the EA doesn't run at all. This is what is shown at the logs.
Any suggestion?
-
I would rebuild the entire thing in a new project and that should get rid of the phantom moving average.
-
I can confirm the problem is within the EA. I tested other EAs on the same chart, TF, etc and it works perfectly. I will have to rebuild it from scratch and try it again.
Dear fxDreema, could you please check out everything is going right on your mq5 part of the platform? This is the third problem I found in a row
-
I don't see 100 MA line, I only see 300 and 1000. But you said that you used 100 before, so I think it could be some kind of cache.
That Access violation problem... maybe you ran out of RAM. I have never seen such error before, but I have 32 GB of RAM and most of the time I don't think about it. I also never investigated how EAs are filling the RAM, so I'm not sure from where these 4626 MB are coming from.
MQL5 is very weird sometimes. The thing is, in order for me to fix some problem, I need to somehow replicate that problem here on my PC, so I can do tests and everything else
-
I created a new project from scratch and it works fine. Apparently there was some cache, as you suggested. Additionally I am using a different lapto with more RAM and I can confirm the error is no more. Once again the more RAM the better.
