Repository navigation
Replies: 2 comments
|
Hello cheurteen, thanks a lot for taking the time to write all of this up. I've read both threads, and I really appreciate the detail and the testing you did. I like many of your suggestions and plan to adopt them. I'll go through each point carefully over the next few days and reply properly then. Some quick news in the meantime: FOV: My latest build already has a field-of-view option. Linux: I'm planning a native Linux build in about two weeks, so Proton should become optional after that. Since you're already testing on Linux, I'd be glad to have your help trying it out. |
|
Hi cheurteen, I've reviewed your requests. I wanted to let you know that I've released the Linux version version 0.1.7, so you no longer have to use Proton. Take a look at it if you can, and let me know how it goes. I've given you credit in the changelogs for the reports and improvements you suggested |
Uh oh!
There was an error while loading. Please reload this page.
Hi, and thanks for the port — it runs beautifully under Proton on Linux too. Following up on
discussions/4 (disc image prompt on Proton/Wine), here
are ideas for things the port could offer, ordered by how small the change looks. Please treat each as optional and
independent; happy to test any of them on Linux.
1. Disc image through a command-line argument or an environment variable (smallest, high value on Linux)
Something like a
--iso "Z:\path\to\dump.rvz"argument or aCORRUPTION3_ISOvariable the port reads once at start.The benefits, against what we saw with the dialog under Proton:
through Wine, so the whole shell-path family of problems disappears rather than being worked around;
For precedent in the same RecompLauncher catalog, Odrannnn's Metroid Prime Port does exactly this with
MP_DISC(plus
MP_NO_DISC_DIALOG=1for headless runs), and Echoes Unbound stores a plaindisc_pathin its usersettings.cfg.2. A typed/pasted path field in F1 > Diagnostics, next to Select disc image
A small "disc image path" text box with an empty-state hint, storing the same
iso_pathvalue. Anyone who hits anodd dialog — the This-PC shell path on Windows, Wine quirks on Linux — can paste the real path in game instead of
editing the TOML by hand, and there is one consistent place that shows what will be checked.
3. Make the disc-check dialog say which of the three cases failed
Today one message covers three root causes ("could not be opened (read-only)…"). When the image does open but the
game ID is wrong (
RM3P01,RM3D01, Trilogy), a line like "found RM3P01 — this port only runs RM3E01 (USA)"would stop players from re-picking the same wrong dump and keep Discussions free of symptoms that look like bugs.
The exact same dialog could also skip ahead to the prompt when the path is missing, instead of failing and restarting.
4. Document the
game/folder next to the executable as a no-dialog fallbackThe exe message tells players to "Copy your own dump … into the 'game' folder next to the executable", but the doc
does not mention it. This is the most cheese-proof path under Proton: the folder is on the Linux side, a symlink to
the dump works (no drive mapping, no
Z:), and the prompt never appears at all. One paragraph in the Common issuessection would cover it.
5. Longer-term, what the sister ports offer that this one could grow into
Said with full respect for one-dev scope: savestates (F9/F10 in both Odrannnn ports), an FOV option and ultrawide
handling, and eventually RetroAchievements hardcore for leaderboard players (README says casual only today). No
urgency implied on any of these — they are what makes the ecosystem great for everyone, listed so they end up on your
radar for some future beta.
The troubleshooting entry proposed in discussions/4 is still ready to merge
(branch) whenever PRs are back on.
Happy to run any experiment on Linux — including making a fresh test run with a debug build if that helps ground
items 1–3.
All reactions