No date has been published and no scope. A developer has named four things being looked at, in forum replies. There are no patch notes, no known-issues list, and the pinned Q&A thread is still empty.
No date and no scope have been published. A developer has named ultrawide support, frame generation, upscaler persistence and controller glyphs as things being looked at, in forum replies — and beyond that there are no patch notes, no known-issues list, and a pinned developer Q&A still sitting at zero replies.
Where this is being asked · Behind every display and performance complaint on the Steam board, and directly in threads that exist purely to ask for a timeline. Those are unanswered too.
Evidence
The answer, broken into claims
A grade describes sourcing, not truth. Inferred means we concluded it and the reasoning is shown; unverified means someone asserted it and nobody stands behind it.
OfficialUltrawide support and frame generation are targeted for fixes.
Sam [developer], bug thread page 3, 3 August 2026 at 7:04pm. No date and no scope were given.
OfficialThe upscaler reverting to FSR1 on restart is confirmed as a bug.
Sam [developer], bug thread page 4, 3 August 2026 at 8:13pm.
OfficialThe latest version named in public is 1.0.6.
The availability announcement on the publisher’s Steam news hub, read 2026-08-05.
InferredNo patch date or scope exists in public.
Our check on 5 August 2026 of the news hub, the pinned Q&A at zero replies, the publisher’s support route and the discussion board. Nothing carries a date.
UnverifiedTwo threads on the Steam board exist purely to ask for a patch timeline, and both are unanswered.
Our own read of the discussion board on 5 August 2026. The two threads were logged without their URLs, so we cannot link them and you should weigh this as our word rather than as something you can check in a click.
§01
What has actually been said
Four things, all of them in replies inside the launch bug megathread rather than in an announcement.
Ultrawide support and frame generation are targeted for fixes — Sam [developer], 3 August at 7:04pm.
The upscaler reverting to AMD FSR1 on every restart is confirmed — Sam [developer], 3 August at 8:13pm.
The controller glyph mismatch is acknowledged in the same thread.
No date is attached to any of them, and no order.
§02
What "being looked at" is worth
It is a statement of intent from someone on the team, typed into a forum thread during a launch week. That is genuinely more than nothing — it establishes that the team knows about these four things and does not consider them working as intended. It is not a commitment to a release, a scope or an order, and the distance between "we are looking at ultrawide" and shipped ultrawide is not something anyone outside the studio can measure. Treat all four as acknowledged, none as scheduled.
§03
What was checked
A patch date would appear in one of these places, and it is in none of them.
The publisher’s Steam news hub: seven posts, the most recent being the availability announcement naming version 1.0.6. No patch notes and no known-issues list among them.
The pinned developer Q&A thread, opened 3 August promising to be filled out over the first day: zero replies on 5 August.
support.fictions.com, the publisher’s only published support route: it returns 403 to automated fetching, so we cannot tell you what it carries.
The Steam discussion board, where the threads asking for a timeline sit unanswered.
§04
The number to watch
The latest version named in public is 1.0.6, in the availability announcement. That is the figure to compare against when something does ship — if your client reports 1.0.6 you are on the launch build, whatever has been said in a thread since.
Expiry condition
What would have to change for this answer to be wrong
An answer about a live-service game without this is an answer with a hidden expiry date.
The publisher posts patch notes, a known-issues list or a date. The Steam news hub is where it would appear first and it carries none of the three today, so a single post there answers this page.
Citations
Every source, with its date
A complaint posted before 30 July 2026 describes the playtest, not the game you bought, and a source whose publication date nobody captured cannot show that it postdates launch either. Both are flagged rather than quietly mixed in.
That Sam [developer], 3 August at 8:13pm, confirmed the upscaler reverting to AMD FSR1 on every restart. A confirmation that the behaviour is a bug, not a commitment to fix it by a date.
That the developer has acknowledged the controller glyph mismatch in the megathread without naming a date or a fix. The page and timestamp of that reply were not captured, so it is cited to the thread rather than to a post. Read 2026-08-05.
That the developer pinned a Q&A thread on 3 August promising to fill it out over the first day, and that it still showed zero replies on 5 August. Cited for the absence of a published timeline.
That the publisher’s news feed carries seven posts, the latest being the availability announcement naming version 1.0.6, and that none of them is a patch note, a known-issues list or a roadmap. Read 2026-08-05.
That the publisher’s only published support route returns 403 to automated fetching, so it could not be checked for a patch timeline from here. Recorded as a check that could not be completed rather than as one that came back empty. Read 2026-08-05.
Related questions
No date has been published. The developer has named four things being looked at in forum replies and attached no timeline to any of them.
