@luisjunior1224 said in when I put 50 is calculating me 5 pips in the backtes, why?:
@l-andorrà I finally know why, that happens when the account is cent
Vaya, supongo que tenía que ser por algún motivo lógico. Al menos lo encontraste y no era por causa de fxDreema. Me alegro. 
I forgot to tel that I was on MT4. I will take a llok on your link, roar, but I don't understand why the program 'thinks' that right now for the first time after so many, many years of backtesting. 
This is the first time I find that a backtesting stops abruptly (i.e. before finishing the programmed testing period) for no apparent reason. Let me explain.
I'm working on a hedging EA that is programmed to work on two different timeframes at the same time, M15 and M1. If all conditions are on the same timeframe, it works fine. However, the inferior timeframe conditions are activated, it crashes so the reason must be there. Let's say a buy/sell is open on M15, if price moves back and reaches a specific ATR distance in pips from open price (in loss), the hedging part is activated and an opposite trade is open. I confirm my broker allows hedging.
Here is when the inferior timeframe is activated. It is programmed that if the close price of M1 bar is below o equal to that ATR distance, then the opposite trade is open. And it is exactly when this happens that the backest crashes and simply stops. Never happened to me before.
I used two ways to do this hedging part, but both failed. Initially I specified all relevant blocks as M1 on the available display within them. Then I used a 'Set current timeframe for next blocks' on top of the tree. Now I ran out of ideas.
Any hint?
Not personally. Could you please share it?
Yo can try to add or remove zeros before the one. Maybe it works.
Did you contact the admin via this support page?:
I think I answered your question in your previous thread.
What do you exactly mean by 'news time'? Maybe fundamental's info? If so, I think this is not possible AFAIK.
Could you please share your project to take a look at it?
How many orders and trades will be active at the same time? One trade and one pending order only, maybe?
This is a question for real progammers. This is the log file for those of you who can understand mql language:
GQ 0 18:58:57.209 Startup MetaTester 5 x64 build 2265 (06 Dec 2019)
QD 0 18:58:57.279 Server MetaTester 5 started on 127.0.0.1:3000
EO 0 18:58:57.282 Startup initialization finished
RM 0 18:58:57.511 127.0.0.1 login (build 2265)
KK 0 18:58:57.549 Network 4372 bytes of account info loaded
MM 0 18:58:57.549 Network 1482 bytes of tester parameters loaded
GH 0 18:58:57.549 Network 17084 bytes of input parameters loaded
IO 0 18:58:57.863 Network 86845 bytes of symbols list loaded
LE 0 18:58:57.864 Tester expert file added: Experts\Advisors\Kbot v1.0.ex5. 394820 bytes loaded
FG 0 18:58:57.864 Tester program file added: Indicators\HiLo Escadinha.ex5. 10617 bytes loaded
KP 0 18:58:57.881 Tester 1884 Mb available, 23 blocks set for ticks generating
IK 0 18:58:57.881 Tester initial deposit 1000.00 BRL, leverage 1:1
HS 0 18:58:57.885 Tester successfully initialized
LD 0 18:58:57.886 Network 467 Kb of total initialization data received
NN 0 18:58:57.886 Tester AMD A6-3420M APU with Radeon HD Graphics, 5610 MB
JL 0 18:58:58.237 Symbols WDO@N: symbol to be synchronized
II 0 18:58:58.238 Symbols WDO@N: symbol synchronized, 3720 bytes of symbol info received
NQ 0 18:58:58.238 History WDO@N: history synchronization started
GK 0 18:58:58.273 History WDO@N: load 25 bytes of history data to synchronize in 0:00:00.003
GM 0 18:58:58.273 History WDO@N: history synchronized from 2018.01.02 to 2019.12.03
DR 0 18:58:58.433 History WDO@N,M1: history cache allocated for 311454 bars and contains 133264 bars from 2018.01.02 09:00 to 2018.12.28 18:14
CS 0 18:58:58.433 History WDO@N,M1: history begins from 2018.01.02 09:00
NH 0 18:58:58.437 Tester WDO@N,M1 (XPMT5-PRD): every tick generating
RO 0 18:58:58.437 Tester WDO@N,M1: testing of Experts\Advisors\Kbot v1.0.ex5 from 2019.01.01 00:00 to 2019.06.20 00:00 started with inputs:
MS 0 18:58:58.437 Tester Mostrar_Indicador_HiLo=true
IE 0 18:58:58.437 Tester HiLo_Deslocar=-1
NP 0 18:58:58.437 Tester Ordem_Limite=false
CD 0 18:58:58.437 Tester Ativar_Operacoes_de_Venda=true
JL 0 18:58:58.437 Tester Ativar_Teto=false
KR 0 18:58:58.437 Tester Teto_Automatico=false
FE 0 18:58:58.437 Tester Periodo_Teto=1
CQ 0 18:58:58.437 Tester Valor_Teto_Manual=5000
QF 0 18:58:58.437 Tester TimeFrame=0
QE 0 18:58:58.437 Tester HiLo_Periodo=3
QQ 0 18:58:58.437 Tester HiLo_Metodo=0
RJ 0 18:58:58.437 Tester HiLo_Pontos_Acionar=200
PI 0 18:58:58.437 Tester Volume_Contrato=2
PM 0 18:58:58.437 Tester Ativar_Traling_Stop=false
PF 0 18:58:58.437 Tester SL_HiLo_Distancia=50
PM 0 18:58:58.437 Tester Stop_Loss=1000
NO 0 18:58:58.437 Tester TakeProfit=800
PD 0 18:58:58.437 Tester Ativar_Alerta_Celular=false
DO 0 18:58:58.437 Tester Hora_Inicial=9
MI 0 18:58:58.437 Tester Minuto_Inicial=1
HD 0 18:58:58.437 Tester Hora_Finalizar=17
MS 0 18:58:58.437 Tester MInuto_Finalizar=0
GG 0 18:58:58.437 Tester Hora_Fechar_Operacoes=17
JS 0 18:58:58.437 Tester Minuto_Fechar_Operacoes=0
GN 0 18:58:58.438 Tester Ativar_Telegram=false
GG 0 18:58:58.438 Tester Ativar_Stop_Gain=true
CO 0 18:58:58.438 Tester Stop_Gain_Lucro=300
KE 0 18:58:58.438 Tester Stop_Gain_Pontos=50
PM 0 18:58:58.438 Tester Ativar_Realizacao_Parcial=true
QN 0 18:58:58.438 Tester RP_Lucro=500
QI 0 18:58:58.438 Tester RP_Porcento=50
LQ 0 18:58:58.438 Tester Derrapagem=100
QM 0 18:58:58.438 Tester MagicStart=1465
JD 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
PJ 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
QK 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
DO 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
ML 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
HL 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
IQ 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
LP 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
ER 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
PE 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
QF 2 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
DJ 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Indicator not handled. (handle=-1 | error code=4002)
IF 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 fxDreema: Block "3" goes ON
IS 0 18:59:15.193 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 fxDreema: Block "7" goes ON
CS 0 18:59:15.348 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:00:00 Error: Cannot get value from a custom indicator. (handle=10 | error code=4806)
DQ 2 18:59:15.467 HiLo Escadinha (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
FH 0 18:59:15.467 HiLo Escadinha (WDO@N,M1) 2019.01.02 09:00:00 Failed to get the handle of MA
ID 2 18:59:15.468 HiLo Escadinha (WDO@N,M1) 2019.01.02 09:00:00 cannot load indicator 'Moving Average' [4002]
GE 0 18:59:15.468 HiLo Escadinha (WDO@N,M1) 2019.01.02 09:00:00 Failed to get the handle of MA
...
QR 0 19:10:09.260 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
CQ 3 19:10:09.261 Tester stopped by user
CK 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
RD 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
OG 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
FS 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
KR 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
JN 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
GM 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
NJ 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
CH 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
RI 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
OD 2 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 cannot load indicator 'Moving Average' [4002]
FD 0 19:10:09.261 Kbot v1.0 (WDO@N,M1) 2019.01.02 09:01:06 Error: Indicator not handled. (handle=-1 | error code=4002)
RH 0 19:10:09.261 test Experts\Advisors\Kbot v1.0.ex5 on WDO@N,M1 thread finished
QR 0 19:10:09.510 127.0.0.1 prepare for shutdown
¿Quieres decir que no opere durante un periodo concreto de tiempo?
I can't imagine the reason right now. Could you please share your project to take a look on it?
I'm afraid that's programmer territory, not my field of expertise, I'm afraid. Someone could help?
Just select the bar range to be scanned and the use this:
Do you mean that your fxDreema EAs can't be compiled on your MT4 platform?
Both trailing stop blocks should be disconnected from both buy/sell pending orders. They need to work independently from all other conditions.
Does the problem happen in forwardtesting demo too?
You need to adjust the pip size rules. I guess you are not testing it on forex, right?
