OFS F2 FiboFade
Fully automated fade strategy for 1-minute charts: it trades against the approach to yesterday's fibonacci levels when the footprint shows exhaustion, with a fixed stop and target.
| Current version | 2.11.23 · 2026-10-29 |
| Compatibility | ATAS 8.0.14+ and ATAS X 8.0.14+ |
| Requirements | Windows 10/11 with classic ATAS or ATAS X, or macOS Tahoe and newer on Apple Silicon with ATAS X (the platform brings its own .NET 10 runtime), a 1-minute chart with cluster (footprint) data |
| Updates | All future updates included |
| Delivery | ATAS catalog (automatic) |
Description
OFS F2 FiboFade trades one specific moment: the instant an extended move meets a level that was drawn before the day even started - and the aggressive buyers pushing it there run out.
The map, drawn from yesterday
Every day the indicator measures yesterday's daily candle and stretches its fibonacci levels across that range. That map is fixed for the whole day - no repainting, no adjusting, nothing that moves once the day begins. Days with almost no volume (weekends, holidays, half sessions) are not stored, so a Monday always trades against a real Friday.
The touch, and why the entry is against it
When a 1-minute candle touches a level, the trade goes against the direction price came from: the strategy is fading the approach - it is not a breakout system. A touched level goes quiet until price has clearly moved away from it, so one level cannot fire again and again inside the same drift.
The evidence: exhaustion in the footprint
A touch alone is worthless, and this is the part that makes the strategy what it is. The footprint of the touching candle has to show exhaustion - several separate conditions, each with a measured threshold in the active setup and each of them a row in TUNE. The calibration is preserved bit for bit from the original research.
The brake
One more gate decides whether the day is traded at all: the 3-day brake skips the day when the 3-day background is too strong for a fade. Fading a market in an established trend is what kills fade strategies - in the original five-month research sample that single filter cut a population of 124 trades that lost 4,489 ticks between them.
The trade
Entry is a market order on the close of the signal candle. The bracket is deliberately simple: a stop at a fixed distance, and either a fixed target or - with the level target on - the nearest fibonacci level of the day in the trade direction that is far enough away, so the target knows where the next obstacle is. Everything is in ticks and editable in TUNE. The stop never moves away from the price; in the supplied setups it can only be pulled closer - by the NY Absorption Stop in PF21 and NET23 and by the Profit Stop in NET23. There is no partial exit and no scaling - so ANY quantity works, and the default is 1 contract. A trade that reaches neither side within the time stop (adjustable, or off) is closed at market, everything is flat by 15:58 Chicago time (22:58 in Bratislava in most weeks), entries are taken only between 17:05 and 15:45 Chicago time (00:05 - 22:45 in Bratislava in most weeks) - the trading day follows the CME clock - and never more than one position at a time.
The measured result
The shipped default is the PF21 setup. When it was selected on 19 months of MNQ tick tape (every exchange trade from March 2025 to September 2026, 1 contract, after 2 ticks of cost per trade) it measured 283 trades, 50.2% win rate, +22,490 ticks, profit factor 2.10, deepest equity dip 956 ticks, 17 of 19 months profitable. With the rules added since, on the tape extended to 9 October 2026 and read with the trades inside each candle: PF21 331 trades, 43.8% win rate, +26,489 ticks, profit factor 2.38, deepest dip 794 ticks, 18 of 20 calendar months profitable; NET23 303 trades, +33,752 ticks, profit factor 3.27, dip 644 ticks; WR55 345 trades, 54.5% win rate, +14,853 ticks, dip 1,044 ticks, all 20 months profitable. About 0.75 to 0.85 trades per trading day: this is a patient system, not a scalper.
Since 2.10.0 NET23 and PF21 also use the NY Absorption Stop: in trades entered during the New York session the stop moves to the entry plus 2 ticks when large orders in the trade direction stop moving the price. On the tick tape extended to 9 October 2026 it raised PF21 from 1,213 to 1,324 ticks a month with the deepest dip falling from 956 to 794 ticks, and NET23 from 1,316 to 1,435 ticks a month (dip 1,273 to 960). The backtest in TUNE shows it in the history when PRINTS is on.
Since 2.11.0 NET23 also uses the Flow Sieve and the Profit Stop: six more entry bans read from the order flow and the session around the touch, and a stop that is pulled closer in two steps once a trade is far enough in profit. On the same tape NET23 rose from 1,435 to 1,688 ticks a month (303 trades instead of 391, win rate 47.5%, profit factor 3.27) and its deepest dip fell from 960 to 644 ticks; both years were better. One of the bans reads large orders from the chart's trades, so the TUNE backtest shows it in the history only with PRINTS on.
Honest about its own limits: the setup was found on the same tape it is measured on - positive on both halves of the tape separately, but not a clean holdout - and the calibration is frozen exactly as it was validated - the thresholds are settings you CAN change, but the published numbers belong to these values.
The control panel
A panel at the top center of the chart is the cockpit, and it keeps a constant size instead of growing with its own text: a click-able ON/OFF button, the state of the incoming data (cluster data present, time and age of the last processed bar), the state of the level map (how many daily candles are loaded, today's 3-day move against the brake and whether today is tradeable at all), the live position, today's trades with their running result, and the built-in backtest - every signal the strategy would have taken on the loaded history is drawn on the chart with its full bracket, so you watch the strategy work before you ever switch it on.
Next to the title sit nine small buttons of equal width: NET23, PF21 and WR55 (the supplied setups), NET, WR and PF (the setups saved from the auto backtest, dim until something is saved), then FIBO (shows or hides the fibonacci levels), TUNE and ON/OFF. TUNE is a built-in strategy lab. It hard-disables trading and shows every rule of the strategy as a row of buttons, in two columns so the whole window fits a 1080-pixel screen: on the left ENTRIES for the quantity, the signal and the filters; on the right the exits, then a SWITCHES row with the on/off rules (blue = on) and the auto backtest. A click changes the live setting, the loaded history is replayed at once, and the STATISTICS block (three columns) sums it up over the whole loaded history: Total Trades (TT), Trading Days (TD), Gross Profit (GP), Net PnL, Long and Short with their win rates, Win Rate (WR), Profit Factor (PF), Max Drawdown (DIP), Worst Trade, Worst Day and Worst Run - all in ticks per contract, after costs. Three setup buttons sit in the header next to the title, as in the panel bar: NET23, PF21 and WR55 - complete packages found on the 19-month tick tape and named after what they measured there: NET23 the most net under a 1 300-tick drawdown, PF21 the best profit-to-drawdown ratio, WR55 a 55% win rate. With the rules added since, on the tape extended to 9 October 2026 (1 contract, after costs), NET23 leads on both net and drawdown: +33,752 ticks with a 644-tick dip; PF21 +26,489 ticks with a 794-tick dip; WR55 +14,853 ticks with a 54.5% win rate and all 20 months positive. Each button applies its WHOLE measured package - every row at once, including the level target where the setup uses it - and DEFAULT restores PF21 in one click.
AUTO BACKTEST
In the right column, below the exits and the switches, sits the AUTO row with RUN, X and GRID. RUN replays every combination of the selected values on the bars loaded in the chart - one contract, 2 ticks of cost per trade, the whole loaded history - in the background on all CPU cores but two, and finds the best setup for three goals at once: the highest net ticks, the highest win rate and the highest profit factor. GRID chooses what the run tries: press it and every row switches meaning - a click puts a value into the grid (blue) or leaves it out (dark), a switch in the SWITCHES row cycles off, on and both (half blue = both states go into the run), and NET23, PF21 or WR55 preset the grid to that setup, so you start from something proven and add only what you want to test. The default grid is 2 211 840 combinations. The AUTO row shows the percent while a run is on, and RUN INFO under the results table shows the grid size, the time left, the elapsed time and the combinations done, so you know what you commit to: every value you add multiplies the run, and a few extra rows turn minutes into hours or days - the auto backtest is meant for a powerful computer. X cancels at any moment and keeps the best result so far. MIN TRADES sets how many trades a winner must have: ANY picks the absolute best whatever the count, and a winner below your floor is marked BELOW MIN.
The results table on the right of TUNE compares the three winners side by side - NET, WR and PF: total trades, trading days, net, win rate, profit factor and drawdown (the best value in each row is green). Which value each winner uses is shown right on the buttons: every value in the rows carries small coloured marks - green for NET, amber for WR, blue for PF - and the table headers are underlined in the same colours. SAVE stores a winner as a saved setup; the NET, WR and PF buttons - in the TUNE header and on the panel - apply the saved setups through the same guard as the supplied ones (never during a live trade). Saved setups survive a restart and stay in the table (marked *) until the next run. Every RUN also performs a self-check: the live setup is replayed through the same path as the grid and compared with the live engine, and RUN INFO reports MATCH or MISMATCH - so the backtest is proven to count exactly what you see on the chart. A setup found on a few days is measured on the days it was found on: load months of history, set a sensible MIN TRADES, and judge a winner by its trade count and drawdown before you trust it.
What it does NOT do
It does not split the position, scale in, average down or reverse, and it never moves a stop away from the price. It does not read any external data feed, and it needs no subscription beyond ATAS itself - everything it uses is read from the chart in front of it. It does not repaint: levels are fixed when the day starts, and a signal is decided on a CLOSED candle and never moves afterwards. It does not hold overnight. And it does not trade at all while the TUNE window is open - that is a hard block, not a convention.
Execution: what happens on the account
The entry is a market order. The moment it fills, a stop and a target are placed from the REAL fill price, held as a manual OCO pair - the first to fill cancels the other. Beyond that, the execution layer carries a set of safeguards, each written after a specific incident on our earlier live relay: an order is never lost track of, even when the platform replaces it or one of its messages goes missing; stop prices always sit on the tick grid, so the broker cannot reject them for an off-grid price; the same fill is never counted twice after a reconnect; the stop size always follows the position as the broker reports it; where the broker supports it, a forgotten bracket can only ever reduce a position, never open one; and an independent guard checks every tick that no real position is left without a stop. Nothing survives a finished trade - every leg is cancelled and kept under watch until it is really dead. Any position left on the account after a trade ends is reported in red on the panel. A stop or target you move by hand is respected and adopted. A manual close or a flatten from the platform ends the trade on the account; the model keeps its own trade and closes it by its own rules, so that trade is not entered again and the next entry comes only with the next signal - the account mirrors the model, never the other way round, and the chart and the panel always show the model.
Every execution event is written to the ATAS log AND to the strategy's own file, %APPDATA%\OrderFlowSmith\logs\F2_<instance>_<date> (on macOS: ~/Library/Application Support/OrderFlowSmith/logs).log, so two charts running the strategy keep two separate files. Entries, stops, targets, fills, the end of the trade and every error state are recorded. Nothing is logged from the calculation path.
The license is re-checked once a minute while the chart runs, not only when the indicator loads, so a key that expires with the chart left open blocks new entries rather than trading on - a trade already open keeps its stop and target and is still closed by the time stop or at the end of the day, and renewing the key does not switch new entries back on by itself.
THE SETTINGS, GROUP BY GROUP
01 - License. Recommended Chart (read-only, states the timeframe: 1 minute). License Key - paste the key from orderflowsmith.com here.
05 - Session and Time. Time Zone - how times are shown and entered: New York by default, a list of zones with summer time, or a Manual Offset. It never changes when the strategy trades - the strategy is anchored to the market's own hours - it only changes how times read, and the DATA row on the panel says 'check Time Zone' when the bar time does not fit. Entry Window with its from and to times, Close At (the daily flat), Day Volume Min (a day below it is not stored as history, which keeps weekends and half sessions out of the level map), History Days Required, and two entry filter switches.
06 - Trading. Autopilot ON (default OFF - the strategy never trades until you switch it on, on the panel or here; the first ON shows the terms to accept; after accepting, the autopilot stays OFF, and the next ON shows a summary of the account, the instrument and every trading setting to enable - Enable automated trading; OFF blocks new entries, while a trade already opened by F2 is still managed to its end; after a restart the autopilot stays OFF unless Resume automated entries after restart is on and the enabled configuration is unchanged). Resume automated entries after restart (default OFF). Trade Quantity (default 1; any number works because the position is never split). Daily Loss Limit in ticks per contract and Max Losing Trades Per Day - the supplied setups carry their measured values, 0 disables either guard. Daily Profit Limit ($) (default 0 = off) is for prop-firm evaluations: when F2's profit today, open trade included, reaches it, F2 closes its trade at market and opens no new trade until the CME open.
07 - Strategy. Stop Loss, Take Profit, Time Stop (bars; 0 = off), Re-Arm Distance, Level Target Min Distance and the sweep exit - all in ticks, all pre-set by the active setup - plus the NY Absorption Stop and Profit Stop switches.
08 - Filters. The exhaustion thresholds, the 3-day brake and the other entry filters, including the Entry Sieve and the Flow Sieve. Every one of them is also a row in TUNE, and each supplied setup applies its own complete measured values.
09 - Display. Show Fibo Levels, level and key-level colors, line width, level labels with their position and pixel offsets - the line is drawn in two segments around the label so it never runs through the number. Today's Levels Only. Long and Short colors, entry, stop and target line colors, bracket line width, arrow size, and Show Historical Trades - the drawn backtest.
10 - Panel. Show Panel, position and pixel offsets, font size, Panel Background, TUNE Background and border - all colors with transparency.
11 - Alerts. Alert On Signal (default OFF) and the alert sound.
12 - Telegram. Bot Token, Chat ID, the test message and a switch for each event type - everything off by default.
13 - Auto Backtest. Saved NET / WR / PF Setup - the setups stored with SAVE, one line of text each; clear a field to free its button. MIN TRADES and the grid are set in TUNE.
WHAT WE RECOMMEND
Chart: 1-minute MNQ with cluster (footprint) data and at least two weeks of loaded history. The supplied setups use a one-stored-day minimum gate, and the drawn backtest still needs enough loaded history to show you a meaningful sample. Without cluster data it refuses to trade and says so on the panel, because it cannot read buyer exhaustion.
Check the DATA row on the panel: it shows the time and the age of the last processed bar in your chosen Time Zone. If it says 'check Time Zone', pick your zone in group 05.
Leave groups 07 and 08 alone if you want the published numbers - that calibration is frozen exactly as it was validated. The thresholds are settings you CAN change, and TUNE exists so you can explore them, but every published figure belongs to these values and DEFAULT puts them back in one click.
Keep the complete PF21 filter package if you want its measured configuration; use TUNE deliberately when studying alternatives. Leave alerts OFF unless you want them; they are off by design so the strategy is silent.
Start at quantity 1 and watch the drawn backtest and the panel for a few days before switching the autopilot on. Set the Daily Loss Limit to a number you can accept losing in one day.
Expect roughly 0.8 trades per trading day on MNQ, and expect quiet stretches: the strategy is deliberately selective, and days with no setup are normal, not a fault.
HOW MUCH TO TRUST THE NUMBERS
Everything published here is reproduced by the shipped engine, not copied from a research note. A parity test replays the original five-month research sample through the same engine on every release and must return exactly 75 trades and 6,759 ticks, trade by trade; the engine was also checked against the original research implementation and matched 72 of 72 trades on the overlapping data. More than five hundred and sixty automated checks run on every release, and every backtest run performs a self-check against the live engine.
What the numbers cannot tell you is the future. A setup found on the tape it is measured on is not a holdout, and the original five-month parity sample is modest. It is a fade strategy, so a strong trend is its natural enemy - that is what the 3-day brake is for, and it cannot catch every case. The entry sieve keeps only the few loss filters that held on both halves of the sample; the rest of the losses are the cost of the entry, not a fault to be filtered out.
Everything - the thresholds, the distances in ticks, the session times, the colors with transparency, line widths, font sizes and panel position - is editable.
Telegram notifications
Both automated strategies can report to your phone. Turn on the Telegram group in the settings and every REAL execution event lands in your Telegram within a second: the entry with the side, quantity and the ACTUAL fill price (never the drawn history), the live stop-loss and target prices from your account, every close with its reason and the result in ticks - and, most valuable of all, execution errors (a rejected order, a hanging bracket), so a problem finds you even when you are away from the screen. The same error repeats at most once per 10 minutes, and a Telegram outage can never delay or block a trade - sending runs in the background, fire-and-forget.
Activation takes two minutes: open @BotFather in Telegram, send /newbot and paste the token it gives you into Bot Token; write any message to your new bot; click Get Chat ID Now - the Chat ID fills itself; click Send Test Message. Done - notifications are off by default and each event type (entries, exits, errors) has its own switch.
Installation guide
2. Open or fully restart ATAS so the automatically delivered indicator becomes available in the indicator catalogue. Whenever an update is released through ATAS, fully restart the platform; ATAS downloads and loads the new version automatically. An update can change how the strategy or the execution behaves with the same settings - the changelog on the product page says when it did; read it before you keep the autopilot ON after an update.
3. If your ATAS account uses a different e-mail address than your OrderFlowSmith account, write to us at orderflowsmith.com/contact - we move the license to your ATAS e-mail and ATAS delivers the indicator automatically.
4. Add OFS F2 FiboFade to a 1-MINUTE MNQ chart with cluster (footprint) data and a connected trading account. Load at least two weeks of history so the drawn backtest shows a meaningful sample; the supplied setups themselves use a one-stored-day minimum gate.
5. Open settings, group 01 - License, and paste your key from orderflowsmith.com.
6. Group 05 - Session and Time: pick your Time Zone (New York is the default; the list includes zones with summer time). It only changes how times are shown and entered - the strategy is anchored to the market's own hours. If the DATA row on the panel says 'check Time Zone', the bar time does not fit the chosen zone.
7. Look at the chart. The fibonacci levels of every loaded day are drawn, and so is every trade the strategy would have taken, with its stop, target and outcome. Open TUNE for the statistics of the loaded history.
8. Before you switch ON: in the Chart Trader panel (classic ATAS and ATAS X) turn the ATAS SL/TP OFF - the indicator places its own stop and target on every fill, and with the platform SL/TP on ATAS would attach a second stop and target from the panel settings to the same fill. When you are ready: set your quantity (any number - the position is never split; default 1) and click ON on the panel. The indicator then places the entry, the stop and the target itself, closes on the time stop and flattens before the daily break. The first time you click ON, F2 shows the License terms and the F2 Automated Trading Addendum on the chart: page through them, save a copy if you wish and click Accept terms. The autopilot stays OFF. When you click ON again, a summary of the account, the instrument and every trading setting appears - click Enable automated trading. OFF blocks new entries only - a trade F2 has already opened is still managed to its end. After a restart the autopilot stays OFF until you click ON again, unless you switch on Resume automated entries after restart (group 06) and the enabled configuration is unchanged. Any change of a trading setting, a preset or an applied optimisation result asks you to enable the configuration again; a change made while a trade is open applies only after that trade ends.
9. OPTIONAL - Telegram notifications: in Telegram open @BotFather, send /newbot and paste the token into the Telegram group of the settings; write any message to your new bot, click Get Chat ID Now and then Send Test Message. Real entries, exits and execution errors then arrive on your phone; everything is off by default.
Changelog — version 2.11.23
- The hidden panel button shows a dot before the name: green while the autopilot is ON or FIBO is drawn, an empty grey ring when everything is off. The ON / OFF box beside the button stays.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.22 - ON / OFF CLICKED WHILE THE CHART LOADS IS REMEMBERED.
- A click on ON / OFF in the control panel, or in the ON / OFF box beside the hidden button, while the chart history is still loading is now remembered: the button shows what you clicked and the last click applies as soon as the history is loaded. ON then goes the usual way - the terms, the summary with Enable automated trading, or ON at once when the enabled configuration is unchanged; OFF stays OFF. Until now every click there counted as ON, a second click did not switch it off and the panel kept showing OFF; with Resume automated entries after restart on, the autopilot resumed even after you had clicked OFF.
- Without a click nothing changes: after a restart the autopilot stays OFF unless Resume automated entries after restart is on and the enabled configuration is unchanged.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.21 - EVERY TRADE COUNTED ONCE WITH TWO DATA CONNECTIONS.
- With two connections delivering market data for the same instrument (for example one for trading and one for order-by-order data), ATAS passes every trade twice. The live record of the candle - the prints and the big trades the rules work with - now recognises the copies from the second connection and counts every trade once. The data guard still sees every message, and the log says when copies start and end.
- Nothing changes with a single data connection. Trading rules unchanged.
2.11.20 - A TARGET YOU MOVE BY HAND ON RITHMIC STAYS F2'S TARGET, TOO.
- Like the stop in 2.11.19: when you drag F2's target and the platform replaces the order (Rithmic cancels it and sends a new one with the same comment), F2 takes the new order over as its own target at your price - no "unknown order" alarms.
- When your moved target fills, F2 cancels the stop at once. Until now the stop stayed live on the flat account for about a second, until F2 cleaned up after the flat position.
- Your price stays: F2 does not move a target you moved by hand. If the price touches it and the limit does not fill, F2 closes at market, as with its own target - counted from your move. A target you do not move works exactly as before.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.19 - A STOP YOU MOVE BY HAND ON RITHMIC STAYS F2'S STOP.
- On a connection that replaces an order when you drag it (Rithmic: the platform cancels F2's stop and sends a new one with the same comment), F2 now takes the new order over as its own stop at your price - the same as a stop moved by hand on other connections. Until now F2 treated it as an unknown order: error alarms ("unknown order with our comment", "unresolved order state" every minute, "part of the position is UNPROTECTED" in the moment between the two orders) and the stop was no longer part of the trade.
- Your price stays: F2 does not move a stop you moved by hand (Profit Stop and NY Absorb leave it as it is). When the stop fills, F2 cancels the target at once; when the target fills, F2 cancels the stop; the time stop, Close At, the daily profit limit and the virtual exit close the trade as usual.
- F2 takes over only its own stop: the exact comment of this chart's F2, your account and instrument, a stop on the closing side no larger than the position, sent right after F2's stop was cancelled outside F2. Anything else stays an unknown order and is reported as before.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.18 - DAILY PROFIT LIMIT FOR PROP-FIRM EVALUATIONS; F2 CLOSES ALSO AFTER A MANUAL STOP MOVE.
- New setting Daily Profit Limit ($) in 06 - Trading, off by default (0). When F2's profit today - its closed trades plus the open trade at the last price - reaches the limit, F2 closes its trade at market and opens no new trade until the CME open (18:00 New York). Made for prop-firm evaluations with a consistency rule, where one day may carry at most a set share of the total profit.
- It counts F2's own trades on that chart, before commissions: realized ticks per contract x Trade Quantity x the tick value from the platform (0.50 USD for MNQ). The market exit can slip a few ticks; the day stays closed even when the exit ends a little below the limit, also after a restart of ATAS. The virtual trades and the panel statistics do not change.
- Fixed: after you moved F2's stop or target by hand on a connection that replaces the order (Rithmic: the platform cancels it and sends a new one), F2 would not send its own closing order - the time stop, Close At and the rule-2 exit kept waiting for that order. F2 now cancels its replaced leg first and then closes.
- Fixed false error alarms on Rithmic, where the position update arrives after the fills: "protection is LARGER than the position" on an entry filled in two parts, "part of the position is UNPROTECTED" while F2 moves its own stop and when the stop fills, and "last close ended with an error" / "position still open" right after F2's own close. Real problems are still reported.
- With the profit limit off, trading and the autopilot profile are unchanged - after the update F2 continues as it was. Setting a limit changes the trading configuration: click ON and enable it, as after any trading setting.
2.11.17 - NEW CHARTS SHOW TIMES IN NEW YORK TIME.
- The default Time Zone of a new chart is New York, as in the other OFS indicators (until now UTC). It only changes how times are shown and entered - the strategy runs on the exchange's clock.
- Saved charts keep their Time Zone. A chart saved before August 22, 2026 (without the Time Zone row) keeps UTC and its entry window.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.16 - THE TIME ZONE ROW SWITCHES TO MANUAL AT ONCE.
- A non-zero Manual Offset (hours) switches Time Zone to Manual (display only - the strategy never moves with it). Until now the settings window kept showing the previous zone until it was reopened - now the Time Zone row shows Manual at once.
- Trading, the automation and the autopilot profile are unchanged - after the update F2 continues as it was.
2.11.15 - THE TRADING DAY FOLLOWS THE CME CLOCK IN EVERY WEEK.
- F2's trading day, entry window and Close At now run on the exchange's clock: the day starts when CME Globex opens (17:00 Chicago time). Until now they ran on Bratislava time, which is the same in most weeks - but for a few weeks in March and at the end of October, when Europe and the USA change their clocks on different days, the day started an hour late: the first hour of the new session counted into the previous day (so the next day's fibonacci levels came from a mix of two sessions) and Close At 22:58 fell into the CME daily break, so a trade open before the break was closed only after the market reopened.
- Outside those weeks nothing changes: on our 19-month NET23 tape every trade outside them is identical. Inside them 7 trades changed (+124 ticks in total) and no trade is held over the daily break any more.
- Time Zone and Manual Offset (hours) still change only how times are shown and entered - the strategy never moves with them. Session From, Session Until and Close At are shown in your selected Time Zone as they really are in that week (in Bratislava during such a week Session From 23:05 and Close At 21:58), and the chart saves them on the exchange's clock, so a chart saved in one week loads with the same times in any other week.
- Charts saved with an older version keep their times and the autopilot profile does not change - after the update F2 continues as it was.
2.11.14 - CONTROL PANEL AND HIDDEN BUTTON LINE UP WITH THE OTHER OFS INDICATORS.
- The buttons of hidden control panels of all OFS indicators on a chart line up side by side by themselves at the top centre, in the order of the chart's indicator list; open control panels at the same place stack below each other. A different position or offset in the settings keeps a button or panel in its own place.
- New default places, also on saved charts: Control Panel Position Top Center, Offset X 0, Offset Y 40; Hidden Button Position Top Center, Offset X 0, Offset Y 5.
- The control panel moved from the bottom to the top centre like every OFS control panel. The ON / OFF box beside the hidden button keeps its place in the row. FIBO (drawing only - the strategy uses the levels either way) is off by default for a newly added indicator. Trading, the automation and the presets are unchanged; the main ON stays off by default.
2.11.13 - THE NY ABSORPTION STOP WORKS LIVE THE SAME AS IN THE BACKTEST.
- F2 now records every single trade of the live candle. In a fast market the live record could miss the high or low of a candle, and the NY Absorption Stop then stopped for the rest of that trade - so live it moved the stop less often than the backtest. Now it moves the stop live in the same second as the model.
- A closed candle is evaluated as soon as all of its trades have arrived - normally within the same second.
- If the rule ever stops for a trade, the log says why.
- The autopilot profile does not change - after the update F2 continues as it was.
2.11.12 - LOG FILES SHOW ATAS OR ATAS X AND THE CHART.
- The log file name now says whether F2 runs in ATAS or ATAS X (F2_ATAS_... / F2_ATASX_...). The first line of each log file names the platform and its version, F2 and its version and the computer, and a chart: line names the instrument, the chart type and period and the account - so the logs of several F2 instances in two platforms and on different charts can be told apart.
- The panel message during a market data problem and the Notify Connection description no longer say 30 s: new entries wait until the data is fine again - 4 s after a delay, 10 s after lost data or a lost connection (since 2.11.11).
- The autopilot profile does not change - after the update F2 continues as it was.
2.11.11 - BACK TO TRADING FASTER AFTER A DATA HICCUP.
- After a short market data delay F2 allows new entries again after 4 s of healthy data (was 30 s); after lost data or a lost account connection after 10 s. The red panel frame and the Telegram message about the end of the problem follow the same rule. When a problem starts is unchanged (15 s without data or connection, or the data more than 5 s late).
- The autopilot profile does not change - after the update F2 continues as it was.
2.11.10 - TELEGRAM MESSAGES ARE NOT LOST WHEN THE INTERNET DROPS.
- A Telegram message that could not be delivered because the internet was down (for example the message about the outage itself) is now kept and sent as soon as Telegram is reachable again - tried every 30 s and right away when the market data is back, in the order the events happened, with the time of the event when it arrives more than a minute late. Messages that Telegram rejects (wrong bot token or Chat ID) are not repeated. At most 30 waiting messages, none older than 6 hours.
- The autopilot profile does not change - after the update F2 continues as it was.
2.11.9 - RED PANEL FRAME WHEN THE CONNECTION OR THE DATA DROPS.
- New: while the market data watcher reports a problem - the account connection (for example Rithmic) lost for more than 15 s, no market data for 15 s while CME is trading, or the data more than 5 s late - the control panel and the hidden panel button get a thick red frame; it returns to normal when the watcher reports the data OK again. The frame itself changes nothing - new entries wait during the problem as before. No alert and no sound. Setting Control Panel Outage Frame (on by default) in the control panel group.
- The autopilot profile does not change - after the update F2 continues as it was.
2.11.8 - THE CONTROL PANEL ZOOMS TO FIT A NARROW CHART.
- On a chart narrower than the control panel (a smaller monitor, several charts side by side) the whole panel now shrinks evenly - the same buttons in the same places, only smaller, down to font size 6 - instead of running out of the chart or over its own name. It grows back when the chart is wide again and does not jump back and forth near the limit. New setting Control Panel Zoom To Fit (on by default).
2.11.7 - LOG FOLDER.
- New Log Folder (13 · Log): the folder for the strategy's log files, for example D:\logs. The files go into a subfolder named after the computer, so two computers can share one synchronised folder. Empty = as until now. The autopilot keeps running after the update - the setting is not part of the trading profile.
2.11.6 - THE DATA WATCHER RECOGNISES THE CME BY ITS FULL NAME.
- The market data watcher of 2.11.5 now recognises the exchange also when the platform reports its full name (Chicago Mercantile Exchange). In 2.11.5 it therefore watched only the delay of the data and the connection state; now it also notices when no trades or quotes arrive for 15 seconds while the CME is open.
- Nothing else changed: the autopilot, the setups, the backtest and every setting stay as they were.
2.11.5 - F2 WATCHES THE MARKET DATA ITSELF: LATE OR MISSING DATA PAUSES NEW ENTRIES.
- New: F2 measures how late the market data from the broker arrives - the exchange time of every trade against the moment it reaches ATAS, corrected for the clock of your PC. When the data is more than 5 seconds late, or when no trades or quotes arrive for 15 seconds while the CME exchange is open, F2 opens no new trade until the data has been fine for 30 seconds. The autopilot stays ON and continues by itself; an open trade keeps its stop and target at the broker. The panel shows the reason.
- 12 - Telegram, Notify Connection: one message when the problem starts (connection lost, no market data, or data delayed - with the open F2 trade) and one when everything is fine again, with the length and the longest delay. Until now F2 relied only on the connection state shown by ATAS, which can stay Connected for half a minute after the data has stopped.
- Diagnostic Log: every DIAG line shows the current data delay.
Frequently asked questions
Which chart should I use?
Can I use it on other instruments than MNQ?
Why is the entry AGAINST the move?
Does it need GEXBot or any other subscription?
Why do I sometimes see no trades for days?
How does it manage a running trade?
Which supplied setup should I start with?
Can I see what the strategy would have done before switching it on?
Does it repaint?
Is there a daily stop?
How trustworthy are the published numbers?
What are the CALM CANDLE and SPARSE GRID buttons in TUNE?
Which settings should I change, and which should I leave alone?
Does it write a log?
How many trades should I expect?
Can the indicator send notifications to my phone?
How do I use the auto backtest, and does it count the same as the chart?
What are the CALM and SPARSE rows in TUNE?
Does OFS F2 FiboFade run on a Mac?
Are the live trades the same as the backtest?
Does F2 place real orders?
What does Autopilot OFF do?
Does saving an optimisation result start trading?
Are the presets selected for my account?
What happens after a restart or an update?
What happens when my licence expires or is revoked?
Why does F2 ask me to accept terms and to enable the configuration?
I changed a setting while a trade was open - what happens?
Why is there a thick red frame around the control panel?
Reviews
No reviews yet — be the first verified buyer to share your experience.