This MUST get fixed

Viewing 15 posts - 1 through 15 (of 31 total)
  • Author
    Posts
  • #246577 quote
    deleted23092025
    Participant
    New

    This absolutely must be fixed. It’s 2025, yet ProRealTime still enforces outdated and highly restrictive rules around timeframe compatibility. These limitations are not just inconvenient — they actively hinder the performance and reliability of trading systems, especially those built on higher timeframes like 4 hours.

    The inability to mix timeframes freely — for example, running a 4-hour system while managing stop-loss or breakeven logic on a 1-minute timeframe — is a major flaw. It makes risk management tools like breakeven and trailing stop-loss nearly useless in practical terms.

    Consider this: a position might gain over 1,000 points during a 4-hour candle, but if the trailing stop is only allowed to update every 4 hours, that gain can vanish completely before the next update. This isn’t just inefficient — it’s unacceptable in real trading environments where precision and timely execution are critical.

    There’s a simple and obvious solution: allow systems to maintain their primary logic on a higher timeframe while managing stop-loss and breakeven mechanisms on a faster one. Yet ProRealTime’s current requirement that timeframes be multiplicative blocks this entirely. This restriction severely handicaps anyone building serious trading systems and effectively punishes users for using higher timeframes.

    This is not a small issue — it is a fundamental design flaw that is costing traders real opportunities and exposing them to avoidable risk. It needs to be addressed with urgency.

    #246582 quote
    GraHal
    Participant
    Master
    Yet ProRealTime’s current requirement that timeframes be multiplicative blocks this entirely.
    I guess from above you know about Multi-Timeframe … run your main code on 4 hours (or whatever TF) and run your stop loss on 1 minute TF?
    #246583 quote
    deleted23092025
    Participant
    New
    You can not run main code on 4 hours and stoploss on 1 minute TF. It has to be reverse, or-else it´s not working.
    #246585 quote
    GraHal
    Participant
    Master
    I am running Algos with main code on 1 hour TF and Trailing Stop on 1 minute TF. Have you tried … what problem do you experience / what error messages do you see?
    #246586 quote
    deleted23092025
    Participant
    New
    Chart is set to 1 hour. As I said it must be multiplictives with default timeframe. Timeframe (default) Entry Conditions Timeframe (30 minutes)  //any minute that is lower than 1 hour won´t work. trailingstopcode
    pp.png pp.png
    #246588 quote
    phoentzs
    Participant
    Master
    Probably a bug in the code? I code signals on many higher timeframes and execute the code in 1 minute. It works great.
    #246589 quote
    deleted23092025
    Participant
    New
    Timeframe (default) IF NOT LongOnMarket AND time = 160000 THEN BUY 1 CONTRACTS AT MARKET ENDIF Timeframe (1 minutes) if time = 170000 then sell at market endif What´s wrong here? Or here Timeframe (1 hour) IF NOT LongOnMarket AND time = 160000 THEN BUY 1 CONTRACTS AT MARKET ENDIF Timeframe (1 minutes) if time = 170000 then sell at market endif
    #246598 quote
    JS
    Participant
    Senior

    Why do you want to turn it around, what do you think is the benefit of this…?

    #246599 quote
    deleted23092025
    Participant
    New
    I explained that in the topic “Consider this: a position might gain over 1,000 points during a 4-hour candle, but if the trailing stop is only allowed to update every 4 hours, that gain can vanish completely before the next update.”
    #246600 quote
    JS
    Participant
    Senior

    The trailing stop is not only allowed on the 4 hour time frame but can be used on the 1 minute time frame… (as everyone does here)

    #246601 quote
    JS
    Participant
    Senior

    These are your (strategy) examples, which work without a problem…

    (nothing has to be fixed)

    Scherm­afbeelding-2025-05-01-om-10.17.59.jpg Scherm­afbeelding-2025-05-01-om-10.17.59.jpg
    #246603 quote
    GraHal
    Participant
    Master
    What´s wrong here? Or here
    There is nothing wrong, but the Chart Timeframe (TF) has to be the lower of the 2 TF’s, i.e. 1 minute. The Chart TF needs to  divide into any higher TF’s used in the code, i.e. 1 minute divides into 1 hour. However, we couldn’t use 8 minute (as Chart TF) and have 1 hour TF in the code as 8 mins does not divide into 1 hour / 60 mins.
    #246606 quote
    deleted23092025
    Participant
    New

    The default timeframe must be multiplicative. You cannot run a system on a 1-hour timeframe with a trailing stop on 1 minute, but it works the other way around, as you demonstrate – I’m aware of that.

    The problem occurs when running a system on a 4-hour timeframe, and the stop loss only updates every 4 hours, which is not what I want.

    #246607 quote
    deleted23092025
    Participant
    New
    @GraHal and this is exactly the problem. The Chart timeframe must be higher for it to work. If you run a 4h timeframe system, you are forced to use trailingstop on 4h (OR HIGHER). Which is terrible.   I want to have the entry conditions on a higher timeframe for ie 4 hours. And I want the trailingstop to be updated more than every 4 hours as anything, I want to be able to set the trailingstopcode to anything I want. And this is exactly what I see as a problem.
    #246613 quote
    JS
    Participant
    Senior
    Yes, you can run a system on a 1 hour timeframe with a trailing stop on 1 minute… Timeframe(1 hour, UpdateOnClose) Main code Timeframe(1 minutes) Trailing Stop
Viewing 15 posts - 1 through 15 (of 31 total)
  • You must be logged in to reply to this topic.

This MUST get fixed


ProOrder: Automated Strategies & Backtesting

New Reply
Author
Summary

This topic contains 30 replies,
has 5 voices, and was last updated by phoentzs
9 months, 3 weeks ago.

Topic Details
Forum: ProOrder: Automated Strategies & Backtesting
Language: English
Started: 04/30/2025
Status: Active
Attachments: 2 files
Logo Logo
Loading...