Posts made by roar

You can delete the SL from existing trade the same way you delete it from a new trade: set the SL level at 0.

@adentist you must remove the "once per bar" block (or put it before the loop) and do the counting like this

@fifeivkbdedwcf the code checks if all conditions are True at the same instant. Indicator cannot be above 70 and below 70 at the same instant.

Nevermind, you are correct actually

@cmuphyfx I haven't

You could use some arrays and loops, but I think the more "robust" solution is just to get a custom indicator that has the MA built-in.

https://fxdreema.com/shared/JMTGEGlMd

Basically this

@Ecowith try this

@p3ym4n you need a modified, custom indicator for that.

Well moving averages have a little loophole, you can just multiply the period by 48 because there are 48 5-minute bars in one 4h bar. So 10-MA on h4 is the same as 480-MA on 5-minute.

@seb-0 the "TP or SL trigger choice problem" might not be the reason here, as there is supposedly always min 20 pips difference between those levels.

I am very interested in this, but purely from the point of figuring out where the tester goes wrong, in what detail does the devil hide...

@Julianrob your mt5 backtest shows much larger "largest loss trade" while the mt4 backtest seems to have a fixed SL, largest being the same as average. -55 vs -6. So there is some different trading logic going on.

Let me guess: the dynamic TP is the one factor that is utmost important for the EA. The moment you test using fixed stops, the EA plummets?

@cmuphyfx You can replace the default indicator with a custom indicator, then it compiles normally.

https://fxdreema.com/shared/0pXpK1Cre

@cmuphyfx it seems to happen on a fresh project with only one condition with TEMA. So it is clearly some typo in the MDLIC_indicators_iTEMA class.

I cannot fix the source code of fxdreema itself (unfortunately lol), so there's little I can do here. Maybe just get a custom indicator that works the same way as the default TEMA in fxdreema.

@Julianrob I could run some backtests, sure

Seeing that your trades last only some minutes, and you modify the stops during that time, the results are probably skewed due to the tester limitations. Have you made a mt5 version?

Alright, maybe its a mistake for me to throw my opinions and talk off topic, but well this is the general section and it feels wrong to stay silent, so here goes:

https://www.telegraph.co.uk/world-news/2023/10/28/iranian-girl-dies-allegedly-beaten-by-morality-police-hijab/

In Iran, another young girl has been beaten to death, by authorities, for not wearing her hat properly. For such a country, being called poor is the absolute least of problems. This truly makes me sick.

@cmuphyfx I dont know why fxdreema recognizes some buffers and some not, but you can always add more buffers manually from the "New" button. Color and name are irrelevant, only the buffer number (position in list) matters.

@kbt I doubt the purpose of this post is to specifically talk about Iran. The fact is that the average person in country a has more purchase power than the average person in country b (and fxdreema or any other business cant do much about this inequality).

Anyway 30% of Iranian households live in poverty, so it is not very outrageous to call it a poor country in general, in my opinion.

@mee-air the button is created in the On Init tab

@cmuphyfx Currently the time functions seem to have some bugs. But you can employ some mql5 functions to do the same stuff.

https://fxdreema.com/shared/n8h15ql6b

@PauloSouza just create a constant, lets say "lotsize", and modify the code in my picture to

lotA = lotsize;

Now you can adjust it from your EA inputs.