Record your installed build and symptom first. Compare one setting at a time; for Steam crashes or missing textures, verify the installation. Back up saves before mod changes. The checked 1.0 notes do not promise an FPS target or a universal performance fix.
Turn a vague bug into a useful report.
Choose your situation for matching checks. Add only what you observed, then copy or download the draft. No automatic scan. No submission.
JavaScript enables editing. This site does not save or send this draft. Copy or download it before leaving.
Draft privacy · Sending the downloaded file is your choice. Remove personal information first.
What the developer actually confirmed
The 1.0 changelist describes model and texture optimization and lower overall memory use. The launch FAQ also describes optimization work. Neither source supplies a per-GPU benchmark, a Steam Deck FPS target or a guarantee that an existing shop cannot stutter.
On our review, the checked official announcement showed 1.0, 1.01 and 1.02 sections. We did not find a later developer build in the listing we checked. That is a dated observation, not a promise about future updates. Build 1.02 documents gifts, achievement counting and a possible tournament-progress fix; it is not labeled a general FPS repair.
Record a clean baseline
Write down the game build you actually see, your storefront, device, resolution, graphics settings and optional mods. If an update is downloading or pending a restart, finish that normally first. A version number in a website headline is not proof that your installed copy matches it.
Choose a repeatable scene and test interval. For example, compare the same view of the same shop before and after changing one graphics option. Note the time of day, whether customers are present and whether the symptom starts only after loading a save or entering a duel. This comparison method is our diagnostic advice, not a developer benchmark.
Use the report builder to keep the conditions beside the observation. Leave an FPS field blank when you did not measure it; an estimate from another player’s machine is not your baseline.
Low FPS and stuttering
| What you see | Useful comparison | Do not conclude |
|---|---|---|
| Consistently low FPS | Retest the same view at a lower resolution or a lower graphics option actually present in your build. | A change alone does not identify a specific engine defect. |
| Short freezes or uneven movement | Record when each pause happens, what you were doing and any background downloads or recording. | A smooth average FPS does not describe every pause. |
| Only a busy shop slows down | Compare a quiet and busy moment in the same shop; keep the camera/settings as consistent as practical. | This does not prove a specific customer, decoration or pathfinding bug. |
| Only a duel or bracket stops | Check whether the picture still animates while an action or round is unavailable. | A rules or tournament-progress issue is not automatically low FPS. |
Keep a note of every changed setting and restore it if the test does not help. Do not delete furniture, empty your collection or overwrite your working save just to imitate an unverified optimization tip. Use the published PC requirements as context, not a guarantee of a particular frame rate.
Crashes or missing textures
For a Steam installation, follow Steam’s installation check: open the game in your Library, choose Properties → Installed Files → Verify integrity of game files. Let it complete before launching another test. Verification checks installed game files; it is not a recovery tool for your shop save.
Steam notes that some local configuration files can fail verification normally. A message about a file does not, by itself, establish save corruption. Record repeated errors and the exact point where the game stops: before the menu, while loading a save or after entering the shop.
Steam’s general launch guide also covers current OS/drivers, system requirements and conflicting non-essential software. Use the operating system or hardware vendor’s normal update tools. Do not download random DLLs, run an unknown FPS-booster executable or turn off security protection because a forum post suggests it.
Mods and save safety
Before changing a mod or loader, close the game cleanly and preserve an unchanged save backup using your platform’s supported options. Record the mod names and versions, then follow their authors’ removal or compatibility instructions. Do not assume uninstalling a mod undoes changes it already made to a save.
If you can test an unmodified setup safely, use a separate test slot rather than overwriting your only working shop. A game update, mod update and device-driver change should not all happen inside one comparison. Otherwise, you will not know which change affected the result.
The developer confirms that 0.70 saves carry forward to 1.0. This does not establish that a newer save can be downgraded to an old branch, that a modified save can be repaired, or that console saves transfer to Steam. Read the save and backup guide before trying recovery instructions.
Steam Deck and console boundaries
For Steam Deck, record SteamOS, the selected compatibility setting, resolution and any power or FPS limit. For an Xbox or Nintendo device, record the console model and installed game version. Do not apply Windows-only driver, executable or PC-mod instructions to another platform.
A source describing Steam fixes does not establish when each console receives them. The sources checked for this guide also do not establish a universal handheld preset, DLSS/FSR availability, a particular Deck verification rating or a “classic 1.0” rollback procedure. Use only the options that your current installation actually offers and ask the developer about an unsupported branch change.
Send a useful report
A good report separates what you observed from what you have not tested. Include the platform/build, exact hardware, settings, affected scene, mod status, steps to reproduce, expected versus actual behavior and the result of each change you actually tried. Add a screenshot or short clip only after checking it for personal information.
The report builder keeps suggested next checks in a different section from completed tests. It does not detect your hardware, inspect your save, diagnose a root cause or submit a ticket. Copy or download the text, review it, and use the support/community routes linked from the official game listing. Do not post credentials, account IDs, personal file paths or an entire unredacted save folder.
Good questions. Clear answers.
Did 1.02 fix every FPS problem?
No such claim appears in the checked notes. Build 1.02 covers Ascension gifts, TCG Arcade counting and a possible tournament-progress fix.
Should I start a new save for the 1.0 update?
The official FAQ says 0.70 saves carry over, so a new save is not required just to receive 1.0. Preserve your working save while investigating a separate problem.
Does file verification restore my cards or shop?
No save-restoration behavior is promised by the installation check. Keep save backups and game-file verification as separate tasks.
Can the report builder detect my hardware or guarantee a fix?
No. It formats your own observations and suggests checks by platform and symptom. It does not scan, save or send a report automatically.
Where is the confirmed classic or legacy 1.0 branch tutorial?
The current launch announcement and FAQ checked for this page did not establish such a procedure. Do not downgrade your only working save based on an unverified branch name.
Source-reviewed . Recommendations are editorial guidance, not in-game benchmark results.
OPNeon Games — 1.0 optimization notes and post-launch addenda Source reviewed September 19 in a live browser; the parent article is dated September 14. Lists model/texture optimization and reduced memory usage. The visible addenda run through 1.02, without independent dates. No newer developer build was found in the checked announcement listing; no per-device FPS targets, URP switch, classic-branch procedure or universal fix is established.
OPNeon Games — official 1.0 Update FAQ Reopened September 19: 0.70 saves carry forward to 1.0; console-to-Steam cross-save is not offered; model/memory optimization is described. This is not a save-recovery, downgrade-compatibility or measured-FPS promise.
Steam Support — Verify Integrity of Game Files Platform guidance reviewed September 19: Library → Properties → Installed Files → Verify integrity of game files for installation checks. Steam notes that some local configuration files can fail verification normally. This is not a TCG-specific save repair or an FPS guarantee.
Steam Support — Games do not run after Preparing to Launch Platform troubleshooting reviewed September 19. Covers checking requirements, OS/drivers, installation files and non-essential software; distinguishes Windows and Linux. Our safe comparison checklist is editorial guidance, not independently playtested game fixes.