fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    1. Home
    2. rumesh
    3. Topics
    R
    • Profile
    • Following 1
    • Followers 0
    • Topics 8
    • Posts 8
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by rumesh

    • R

      payment issue
      Bug Reports • • rumesh

      2
      0
      Votes
      2
      Posts
      305
      Views

      l'andorrà

      Did you pay with crypto? I know those payments are slower than usual.

    • R

      Previous price level bellow open trade
      Questions & Answers • • rumesh

      2
      0
      Votes
      2
      Posts
      634
      Views

      fxDreema

      I don't have easy solution for this. I think that custom code needs to be written 🙂

    • R

      loop direction set
      Questions & Answers • • rumesh

      2
      0
      Votes
      2
      Posts
      1338
      Views

      fxDreema

      This?
      0_1541014139867_68b71bba-7624-400a-88cb-1a041eb1c946-image.png

    • R

      if close last trade buy next trade sell
      Questions & Answers • • rumesh

      2
      0
      Votes
      2
      Posts
      453
      Views

      fxDreema

      There is a block "Check type (last closed)". In the desktop version I think it was named "Check last closed type".But if you have 0 closed trades, which is the case in the backtester, you probably need to create one initial trade

    • R

      back test and real
      Questions & Answers • • rumesh

      6
      0
      Votes
      6
      Posts
      1690
      Views

      fxDreema

      The lowest timeframe is M1. For each M1 Candle you have 4 price levels - Open, High, Low and Close. There is no data for the ticks inside those candles, nothing more that those 4 prices exists.

      The first thing that the Tester does is to generate ticks. It reads the information from M1 (or other timeframes) and based on that information it uses some algorithm to create ticks. By the look of each candle it decides how ticks would travel within that candle. Candle's Volume is probably used to decide how many fake ticks to put in that candle. It's the same as if I give you one candle and ask you what was the path of the ticks inside.

      If you have candle with height of 10 pips, then fake ticks will be generated for the path of those 10 pips within that candle. But what if you create a trade with stops of 5 pips? If that trade is created and closed within that candle, how accurate will the result be?

      It's another story if you for example create a trade in the first tick of the candle and then close it at the first tick of another candle. Those are the Open prices and they should be accurate. Or if you have stops much bigger than the biggest M1 candle.

      The problem with Trailing Stop and similar functions is that in most cases they react on small movements. The price moves with 1 pip and Stop-Loss is set somewhere, which means that Stop-Loss is also fake, because it is based on fake ticks.

      Here is more to read:
      https://www.mql5.com/en/articles/1511
      https://www.mql5.com/en/articles/75 (this is for MT5)

    • R

      using hekin ashi
      Questions & Answers • • rumesh

      2
      0
      Votes
      2
      Posts
      730
      Views

      fxDreema

      I don't remember exactly, but I think that the way to detect white-red and red-white transitions was by detecting crossover of High and Low values. Because these swap over time.

      Here somebody wrote about this indicator long time ago: viewtopic.php?f=2&t=1782&p=1830&hilit=heiken+ashi#p1830
      And I posted some example also long time ago: https://fxdreema.com/shared/JvDgZliqc

    • R

      Maximum trade count
      Questions & Answers • • rumesh

      2
      0
      Votes
      2
      Posts
      786
      Views

      fxDreema

      http://prntscr.com/9rcxlz
      http://i.imgur.com/6X6qG0b.png

    • 1 / 1