BIG CALL FUNCTION PROBLEM

Forums › ProRealTime English forum › ProRealTime platform support › BIG CALL FUNCTION PROBLEM

Viewing 15 posts - 1 through 15 (of 33 total)
1 2 3
  • 06/05/2025 at 7:50 PM #247974
    deleted23092025

    Hi. I need help with this REALLY FAST.

    I have been using CALL fucntion as normal like condbuy1, condbuy2 = CALL “indicator name”

    Now when I am backtesting thoose systems with calling for the indicator the backtest is totally wrong. I have tested multiple systems. Is there something wrong with ProRealTime at the moment? Or have I missed something, I am currently in panic. Please someone help!

    06/05/2025 at 7:52 PM #247975
    deleted23092025

    The problem only occurs on Germany40 index!

    06/05/2025 at 7:57 PM #247976
    deleted23092025

    I notice the problem only seem to occur on Multi timeframe systems!

    06/05/2025 at 8:15 PM #247978
    deleted23092025

    For example

    DEFPARAM CUMULATEORDERS = false
    defparam preloadbars = 10000

    timeframe (1hour)
    ma1 = average[150,7](typicalprice)
    cb1 = ma1>ma1[1]

    timeframe (default)
    cb2 = average[200](close)

    if cb1 and cb2 then
    buy 1 contract at market
    set stop %loss 1
    set target %profit 0.1
    endif

    VS

    DEFPARAM CUMULATEORDERS = false
    defparam preloadbars = 10000

    timeframe (1hour)
    cb1, ignore = CALL “indicator21”

    timeframe (default)
    ignore1hourtimeframe, cb2 = CALL “indicator21”

    if cb1 and cb2 then
    buy 1 contract at market
    set stop %loss 1
    set target %profit 0.1
    endif

    and indicator

    ma1 = average[150,7](typicalprice)
    cb1 = ma1>ma1[1]

    cb2 = average[200](close)

    return cb1, cb2

    Gives 2 different results. Never seen this, this is a big issue. I have tested multiple accounts aswell. Only on DAX40. Anyone else?!

     

    06/05/2025 at 8:30 PM #247979
    deleted23092025

    I have had the systems running for years. But with calling indicator now gives wrong results on backtest. But system seems fine on live because on live I have the same results as backtest without the calling. But I have imported the system long time ago to another account.

    Can someone also look at this please

    06/05/2025 at 8:59 PM #247980
    deleted23092025

    Fourtunately this seem to only occur in backtest and not be affected by live ProOrder trades.

    But this needs to be looked into asap.

    06/05/2025 at 10:58 PM #247981
    deleted23092025

    Actually I noticed this occur on every system with multi-timeframe calling indicators. No matter the index. This just needs to be looked at ASAP

    06/05/2025 at 11:14 PM #247982
    deleted23092025

    Attached photo of it unless it is not understandable with text.

    06/05/2025 at 11:34 PM #247984
    PeterSt

    Hi,

    Unfortunately, because of the chaotic structure of these forum boards I can not find it back, but in the past 7 days one of the Market Place vendors announced the very same. While addressing Nicolas for this, Nicolas did not respond, BUT for this Market Vendor (there are just 2 or 3 out there) this problem was solved (estimate : 3 days ago) by a means he did not tell about.

    I really hope this helps you.
    Peter

     

    1 user thanked author for this post.
    avatar Iván
    06/06/2025 at 8:00 AM #247991
    Iván

    Hi! I’ve tested your system and it seems now this problem it’s solved.

    06/06/2025 at 8:02 AM #247993
    deleted23092025

    No problem still remains you probably got lucky Ivan as you tested it on only 3 days.

    06/06/2025 at 8:32 AM #247998
    Iván

    Hi. I recommend opening a console so they can help you from PRT.
    Regards.

    06/06/2025 at 9:44 AM #248002
    JS

    Hi,

    When using different price constants (such as TypicalPrice and Close) in your indicator, you need to specify them in parentheses in your “Call” statement…

    cb1, ignore = Call "indicator21"(TypicalPrice)

    ignore, cb2 = Call "indicator21"(Close)

    06/06/2025 at 10:29 AM #248007
    deleted23092025

    The issue is not related to that JS, even with removing this the same issue appear!

    06/06/2025 at 10:33 AM #248008
    deleted23092025

    The only way to go arround the bug is doing timeframe (1hour, updateonclose).

    But this have not been a problem for over 7 years.  So it needs to be fixed by ProRealTime

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 33 total)
1 2 3

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
“big difference between positions in backtesting and live trading.
2 pole oscillator by big beluga
big increase in price
help >> function close not working (it does not check price levels properly)
highest function in for loop
htf indicator call bug in backtest code
looking for a function, which can tell if there is an event happend in the last
margin call rates functions in prt
mystup, mystdown = call “orderflow”
nice setup for a big short

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