Posts made by l'andorrà

@sam83014 Plese don't duplicate threads. I provided the answer in your first thread.

@sam83014 I already answered to that same issue in your previous thread. Please don't duplicate threads.

@01punchman Not that way. If toy need the green colour of the indicator to be used, it needs to be available as a buffer in the indicator itself. This is not the case for the indicator offered by default in fxDreema. You have two options here: a) try to find a custom indicator with those buffers or b) you still can use the one in fxDreema but changing the condition to select --> Candle ID1 value > Candle ID1 value. This second options is what the indicator does when plotting agreen line.

@kepler What is the exact compilation issue? Can you please provide a screenshot? O the other side, Riera9 is right. Be very careful with those 'miraculous' pattern solutions you can find on Youtube.

@sam83014 In general fxDreema cannoy identify MQ5 buffers correctly. Sadly this is a reccurrent problem here in the forums. I confirm this is the issue in your project. You will need a programmer to 'rebuild' the indicator in the way fxDreema works.

@nasru What's the point of using so many 'loop' blocks with 999999999 times to pass?

@econsulttt Can you please confirm all trades share the same SL level? Any can you please confirm no trade moved beyond 100 pips in profit individually?

@iqbalazmi Then honestly I have no idea. Any programmer here providing some help?

@fabiobioware I can confirm swap and comissions are NOT included in the calculation. It is not a bug, this is how the block was designed.

@juanjo Apparently the buffers are correctly identified by fxDreema. However I don't see the values that are stored. I recommend you to use the 'comment' block to vislaulize those values. I guess the problem is there.

@piptheripper You're welcome.

@dannysetiawan You're welcome.

@itadila I'm not saying it is a wrong choice. I just say you won't be able to backtest it.

@kestra No. I say you should remove all those 'once per bar' blocks and substitute them for this one: 'once per trade/order'.

@vonmunchy Honeslty I don't know. Can anyone else help here?

@mateus_f I see you aleady asked that in another thread. Please don't duplicate threads.

@fabiobioware This block is using the average price of all open trades right now. Not sure it is a good idea to combine it with a martingale.

@itadila That has a problem. You will never be able to backtest that EA because it will be connected to the source of news to get its info, and that cannot be emulated via backtesting.

@miki Please don't use the supertrand indicator. IT REPAINTS!!! You backtest will never be realiable if you use that indicator!!!

@kestra It doesnt work because all those 'For each trade' blocks are searching for the same open trades every single tick. Limiting each tree to 'once per trade' as I suggested will stop that to happen once every condition is met. This way the next tree will be executed.