Trend surfer DAX modified

Forums ProRealTime English forum ProOrder support Trend surfer DAX modified

Viewing 15 posts - 16 through 30 (of 46 total)
  • #66011

    I tried this :

    but still doesn’t work…

    #66012

    How about below, also try including volume also?

     

     

    #66016

    Ok, I finally made it work my way, then I added your code (+5% win ratio), then I added volume, it didn’t change much, same thing for volatility.

    I’ve got good %win ratio but awful win/loss ratio, any idea how to improve this ?

    #66022

    What about adding a momentum indicator, e.g. Chande Momentum Index or similar; RSI maybe??

    #66039

    OK, eventually I filtered it with supertrend extended (see attached), looks better now, I’ll try to push it.

    Here’s the code :

    a = 89 (sl)

    b = 28 (tp)

    c = 20

    d = 1

     

    chears !

    #66041

    i just saw that i tested it on 10 000 bars, its still good thow, but not so good…

    #66042

    Again, it doesn’t do what I want, which also means it can be even more profitable.

    See picture attached, any suggestions are welcome.

    #66078

    I cooked another one that seems to work : ut 2min, trades on TDI overbought/oversold.

    Neutral trades are in fact winners of 1 pip (spread + 1)

    1 user thanked author for this post.
    #66190

    Here is an other one, much more profitable, based on moving avegerage 50 and 500 (optimized) crossing.

    Sometimes, the simpler, the better. I can’t go back further 3 months thow…

    2 users thanked author for this post.
    #66209

    Even better if we make it swinng trading.

    1 user thanked author for this post.
    #66942

    Hi again !

    I’m trying to make some tweaks on the last code I posted, but I need help…

    I took nicolas’ trailing code here https://www.prorealcode.com/blog/trading/complete-trailing-stop-code-function/

    I’m keeping the break even part, but I want the trailing step to be the last high or low (if we go short or long) of “n” or “m” periods (n and m being different for long or short and to be optimized).

    here’s what I changed, but it doesn’t seem to work :

     

    #66946

    It is defined to 39, I missed it when I copied/pasted the code, I edited the post to correct that, sorry

    #66948

    Aha I thought my eyes were deceiving me so I nipped in and deleted my comment re the Trailingstart! 🙂 🙂

    Have you use GRAPH to see what the value of tradeprice (lowest[m](low)) is?  Because if it is > Trailing start then it wouldn’t work anyway??

    #66950

    ok I am going to look closer, I ‘ll report back when I shall find the error.

    Meanwhile, I added pyramiding code I founded in nicolas’ advanced training videos,

    I tweaked it so that position size increases also after a win (and not just deacreases after a loss).

    Win/loss ratio jumped from 4,73 to 5,71.

    here’s the code to put at the begining :

     

    #66951

    Please could you put your latest full code on here and then I can see if I can offer any improvements, but doubt I will as you are doing great on your own … your code has done me well today!

    Thank You
    GraHal

Viewing 15 posts - 16 through 30 (of 46 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login