@roar
WOW!!!
This finally worked!

Thanks my dear
This has solved the issue.

@Lacone Yes, dear. I use terminal values.

I might try to embed them in the code instead and see the results.

Thank you!

@l-andorrà thanks, my dear for the advice.

I will redo the expert without copy-pasting any block, and watch for the results.
I will try that and tell you, hopefully, the good news.

Have a nice day!

@Lacone
Yes, I use constants and variables in the MT5 Fxdreema project.

@l-andorrà Thanks so much for your response. Yes, I am using the same data.
Moreover, I do not believe that the issue is with the broker but in the bot.
I have made alerts for each action that it takes, and it gives me actions/alerts as if it has gone through a different pathway.
It is like the code itself is faulty, or not viable when it comes to demo/live testing.

Do you have more insights regarding this for I have put so much effort in it, and it contains over 1100 blocks with so much calculations and scenarios, and it is frustrating to see so much work going in vain?

Thanks in advance!

My issue is that the code does not simply follow the pathway designed in the Fxdreema project
It goes through wrong pathways and execute their actions.
And this never happens while testing.
And it keeps happening again and again, not just a one-time thing.

MT5
Backtesting on "ticks based on real ticks" / strategy depends on price
PC is working fine (I use it along with my VPS for years without these issues)
I use the same broker for years
Strategy depends on price
Trades are opened/closed every few hours

I would like also to add that, it does not do the same thing each time.

For example, the EA is supposed to open two different trades once initiated.

One time it does so, and another time it only opens one of the two trades.

Hello all,

I have been working on a complicated EA that works on Gold.

Once it became flawless (by revising all the log files in backtesting, the numbers, different scenarios), I launched it on a Demo account.

To my surprise, it is making mistakes when it comes to Demo testing.

For example, it skips opening some trades, and it opens trades that is not indicated in the right Fxdreema project pathway.

I would like to stress again that the EA never behaves like this in backtesting log files.

Is it normal to see this, because if it is, this renders the Fxdreema code useless.

Thank you!

Hello all,

I would like to address an issue that I have here, and I would very much appreciate an answer.

I have three areas/functions:

• Area 1: When there are no positions open, and the Max Consecutive Losses is less than a specific number (identified by an input), it activates

• Area 2: When there are no positions open, and the Max Consecutive Losses is more than a specific number (identified by an input), it activates

• Area 3: After Area 2 is activated, it waits until the Max Consecutive Losses becomes less than the input value (once a win trade happens), then Area 3 is activated, changing values before entering to Area 1 again.

My issue is that sometimes, after Area 2 ends, Area 1 activates before Area 3.

I have done the block numbering correctly, however, the ordering does not happen always according to the numbering.

Here's an example for the above situation:

shared/5OCWgzbbd

Thank you!

Thanks, Jstap!