EA not taking trades or taking false trades

[coinmaster]

Hello. I have an indicator that has a filter which causes it to sit at the 'zero' value for long periods of time.
This indicator has a moving average attached to it for triggers.
However when the indicator sits at zero value it is very buggy on crossover triggers.

The Data window shows that the indicator line and the moving average line are behaving normally, but the crossover logic ignores the data values and gets buggy.

When I try to throw the indicator MA values into variables and output them as text I get inconsistencies between what the data window says and what the variable says.

Those 0.0 values don't exist in the data windows

I've tried using "when indicator is visible' blocks but it is buggy and inconsistent within the strategy tester unless I run the strategy tester in 'visual' mode. I'm guessing the objects don't render in the same way in the tester?

Does anyone know why this happens and what the workaround might be?

Since the data window is correct I assume the issue lies with FXdreema and not the indicator correct?

Would greatly appreciate the help.

[TipsyWisdom]

Sounds like you ought to abandon that indicator my friend.

I dont experience that with indicators in Dreema. I frequently use comment blocks displaying many various things and its only 0 if I jacked something up.

[coinmaster]

Nah, I need this indicator. I put a lot of time and money into its development. I need to do whatever it takes to make it function.

The data window numbers are valid.
But the indicator data captured from FXdreema is not always valid.

I'm trying to figure out why it is failing. I can't tell if it is a bug in the indicator or in FXdreema.

Using triggers from objects only works in visual mode of backtest.

When not in visual mode it takes the wrong trades or skips many trades

Is there a way for me to capture the data from the data window and use that as a trigger? I don't understand how the data from FXdreema variables can be different from the data window. Aren't they extracted from the same source?

[TipsyWisdom]

@coinmaster if you want help, the best thing will be to share that indicator.

[coinmaster]

So you are implying that this is a bug with the indicator and not FXdreema?

What I want to know is if it's possible for the data window to have different data than the indicator buffer.
It seems strange that FXdreema variables would show a different value than the data window since the data window gets its values from the indicator and the data window is showing correct values, this makes me think it is a bug within fxdreema no?

[l'andorrà]

@coinmaster Initially I would agree with what Tipsy says. Most of custom indicators are repainting and this is the reason why they don't work in fxDreema. If you paid for it, I understand you don't want to share it, but if you want some serious help to fix the issue we need at least a link to the EA. Do not share the indi if you do not want, but we can only guess what happens in the project if you don't share the project.

[djlaserman]

I can't say for sure but I suspect this all comes from the delay placing trades by fxd. It's difficult to get it to place trades at the very beginning of bars correctly. Most just miss the mark.

compared to other ea builder

Someone needs to debug the core fxd web application... I hope the owner is still actively doing so.

[TipsyWisdom]

@djlaserman said in EA not taking trades or taking false trades:

I can't say for sure but I suspect this all comes from the delay placing trades by fxd. It's difficult to get it to place trades at the very beginning of bars correctly. Most just miss the mark.

compared to other ea builder

Someone needs to debug the core fxd web application... I hope the owner is still actively doing so.

You might be confusing slippage in real time VS backtest.

this trade opened perfectly at candle open after some significance around the 62 fib for example.

[coinmaster]

@l-andorrà

The indicator does not repaint so that is not a concern.
I had a direct hand in its development, I simply erred by not testing it within an EA before handing over the payment to the developer.

The test is done by a simple line cross indicator
https://fxdreema.com/shared/SBHKZRwPc

However I have also tested many other styles of line cross using other blocks to create the same logic and also using the 'arrows' option within the indicator as a trigger.

The only time I managed to get it working was when I used the arrows as a trigger when the backtester was in 'visual mode'.

The other methods are usually somewhat improved within the visual mode backtesting as well.
However, outside of visual mode, nothing works properly.

[l'andorrà]

@coinmaster The logic of your example is correct. This means the issue must be in other places. Did you try to select candle ID 0 instead for the crossings? I do not recommend, but maybe it helps.

[tempol]

@coinmaster said in EA not taking trades or taking false trades:

Nah, I need this indicator. I put a lot of time and money into its development. I need to do whatever it takes to make it function.

The data window numbers are valid.
But the indicator data captured from FXdreema is not always valid.

I'm trying to figure out why it is failing. I can't tell if it is a bug in the indicator or in FXdreema.

Using triggers from objects only works in visual mode of backtest.

When not in visual mode it takes the wrong trades or skips many trades

Is there a way for me to capture the data from the data window and use that as a trigger? I don't understand how the data from FXdreema variables can be different from the data window. Aren't they extracted from the same source?

I have been looking for a way to use info from data window NOT the rounded out data from fxdreema. They are too often different, even for basic indicators like MAs, kelter channels etc. Data window has the precise value, fxdreema rounds it out, making it impossible to calculate where indicator TRULY increased or decreased or changed. Still looking for a solution on my end.

[jstap]

@tempol Have you tried storing in a variable, using NormalizeDouble(variable,1); in a custom code block, the 1 being number of digits past . this may make the numbers match.

[coinmaster]

@tempol
What do you mean?
As you can see from my first post the variable values of the indicator are not rounded at all.

[jstap]

@coinmaster So if the indicator has a value and this is what you are using, store in a modify variables block the value, use the custom code block to round, use this variable to compare.

[coinmaster]

@jstap
Why would I want to round it? That would make it less accurate.
Also I've already tried using the variable values as a crossover trigger. I've tried as many funky workarounds as I could think of and they all give the same result.

The only time it worked was when I used the arrows as triggers and I had the backtester in 'visual mode'.
Outside of visual mode nothing works.

[jstap]

@coinmaster Just trying to help, you said you can't get values to match because 1 is rounded, tried to show you a way to round the other and maybe make it match.

[tempol]

@coinmaster I know, sorry for the confusion. Was just adding that other indicators, in different ways, also have fxdreema use different output other than what we get in data window... Would be so useful if there was a way to simply state, use data window data AS IS.

[tempol]

@jstap said in EA not taking trades or taking false trades:

@tempol Have you tried storing in a variable, using NormalizeDouble(variable,1); in a custom code block, the 1 being number of digits past . this may make the numbers match.

Thanks jstap, yes I have, and still does not come out with precise data window numbers. Impossible to correctly identify rise or fall from 1min to 1min. And I am talking about simple MAs on mt5. Using the data on closed candles of course, or commenting it out on the chart, no matter if in adjusted variable or not... It just never outputs the same precision I get in the data window. At least not the 1000000 times I tried a few weeks ago.

Sorry didnt mean to hijack your thread @coinmaster !

I really hope you find a solution !

[jstap]

@tempol This is true as amazing as FXDreema is it has some floors, there is code to reference the data window, been a long time since I tried and didn't work for what I needed but could be worth looking at.

[coinmaster]

@jstap
That wasn't me that said that. It was Tempol.