UPDATE time, write here if you have problems!

[Dieter]

@anse33
I have the same problems

[fxDreema]

Guys, I can give you back the lost days if you say. If anyone lost time trying to battle with problems after the update, say to me and I will compensate. Those problems are my fault.

Can someone actually show that this block is not working as exoected? Because when I tried it, it worked normally. I will check it again, but...

[anse33]

@fxDreema
OK, let's approach to this problem step by step.
As I wrote, I extracted the ATR block as the relevant point, causing different results of the same EA compiled before and after the update. Of course, it's very simplified now. But I suppose, the error will occur here already.
Can you compile the extracted blocks one time with the current version of fxDreema and one time with the version before the last update and tell, wheather there are different results?

[miro1360]

@anse33 are you using candle ID 0 or candle ID 1 in that block?

[anse33]

@miro1360 It's starting with candle ID 0, the current candle.

[miro1360]

try with ID 1 ... because ID 0 can cause this ... maybe it is more metatrader issue ...

[anse33]

@miro1360 Using Shift "1" instead of "0" has the same effect:
The same EA without any changes, compiled after the update, gives different (worse) results than compiled before the update.

[miro1360]

not shift but Candle ID ...

[anse33]

@miro1360 It's the same here:

https://fxdreema.com/shared/k7s6vOlzc

[miro1360]

here is Candle ID

[anse33]

@miro1360 Unfortunately, I can not try this out.
Because I didn't activate that field for optimization in the former version I compiled before the update. So I have no possibility for comparation with this modified parameter before and after the update.

[miro1360]

yes thats true ... another true is, tester can give you different results when you use candle ID 0 ... I dont know this situation but I think this is caused by tester and metatrader (because now EAs are compiled with strict parameter and that ticks math modeling can be different in this mode - but I am not sure with this) ...

[anse33]

@miro1360
I only use "Every tick based on real ticks" in MT5 for backtesting. This should be very accurate and not as unreliable as the other tester modeling options.

Looks like only @fxDreema could help in this special case ...

[shafifie]

@fxDreema

[shafifie]

@fxDreema I remove it by reloading my template.

Reloading the EA and setting via template.

Nothing to worry right?

It run without any problem.

Thanks.

[anse33]

@fxDreema Did you find out something concerning the problem of different results before/after the update already?
https://fxdreema.com/shared/k7s6vOlzc

[ambrogio]

@fxDreema there is a problem: doesn't save .mq4 and .exe file
talk later

[CPBonzo]

@fxDreema I have the same problem. The EA compiles (or at least says it is doing so), but no "save as" dialogue appears so I can't save it as either an .mq4 or an .exe file.

[pffx]

I have the same problem with save .mq4 or .ex4 file(s).

[robertk]

Same problem here, cannot save the mq4 or ex file onto my harddrive