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!
The problem only occurs on Germany40 index!
I notice the problem only seem to occur on Multi timeframe systems!
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?!
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
Fourtunately this seem to only occur in backtest and not be affected by live ProOrder trades.
But this needs to be looked into asap.
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
Attached photo of it unless it is not understandable with text.
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
Hi! I’ve tested your system and it seems now this problem it’s solved.
No problem still remains you probably got lucky Ivan as you tested it on only 3 days.
Hi. I recommend opening a console so they can help you from PRT.
Regards.
JSParticipant
Senior
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)
The issue is not related to that JS, even with removing this the same issue appear!
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
