That stuttering Super Mario Bros. run again?
You know the one. Where the jump feels off. Or the screen stretches weird.
Or the audio crackles like a bad cassette.
It’s not your imagination. The Lcfgamestick Special Settings by Lyncconf exist for this exact reason.
Global settings are useless when every game needs something different.
I’ve tweaked hundreds of titles on this device. Seen what breaks. Know what fixes it.
Lyncconf isn’t just another config menu. It’s the only way to set per-game resolution, input lag, aspect ratio (without) touching the core system.
No guesswork. No reboot loops. Just real control.
This guide walks you through each step. No fluff, no assumptions.
You’ll learn how to build custom profiles for any title in under five minutes.
And yes. It works on the ones that always glitched before.
Lyncconf: Your Game’s Personal Rulebook
I used to think all config files were the same. (Spoiler: they’re not.)
The Lyncconf file is a per-game override. It lives inside each game’s folder on your Lcfgamestick. It tells the system how that one it should run.
Not every game.
That’s different from the global config. That one sits at the root and applies to everything. Think of it like house rules.
Everyone follows them unless you write an exception.
A Lyncconf is that exception. Like handing one guest a special permission slip to use the pool after dark. (Yes, I’ve done that.
No, I won’t say which game.)
You need this when a game stutters, crashes, or refuses to load menus. Editing the Lyncconf fixes it. Without breaking anything else.
Most people ignore it until something breaks. Then they panic. Don’t be most people.
The Lcfgamestick docs explain where to drop the file and what settings actually do. Read them before you start tweaking.
This is how you get Lcfgamestick Special Settings by Lyncconf working right.
One line. One game. One fix.
It’s not magic. It’s just configuration done properly.
Safety First: Don’t Panic, Just Copy This One File
I’ve watched people freeze up before editing their Lcfgamestick.
They stare at the screen like it’s a live grenade.
It’s not.
One backup step makes everything reversible.
That’s it.
Open your Lcfgamestick’s file system. You can do that two ways: plug the SD card into your computer, or access it over your local network (Samba share works fine).
Get through to /boot/config/retroarch/.
Find retroarch.cfg.
That’s the only file you need to touch.
Right-click it. Choose “Copy.” Paste it in the same folder. Rename the copy to retroarch.cfg.bak.
Lcfgamestick Special Settings by Lyncconf assumes you did this. It doesn’t warn you. It just expects it.
Don’t skip the .bak. Ever.
I’ve lost count of how many times that single file saved someone’s night.
You think you’ll remember what you changed? You won’t.
Your future self will open that .bak file and whisper thank you.
No fancy tools. No cloud sync. Just one clean copy.
Done wrong? You’re stuck. Done right?
You’re free to experiment.
So go ahead (break) something.
Just make sure you can undo it in two seconds.
Lyncconf Settings: Stop Guessing, Start Saving

I launch the game first. Always.
No shortcuts. No assumptions. If you’re tweaking SNES games, fire up Super Mario World.
If it’s Genesis, load Sonic. You need the actual ROM running.
That’s when I hit Select + X.
RetroArch pops up. The menu appears. It’s not magic.
It’s just a button combo. (And yes, it changes if you remap controls (check) your input settings first.)
Now I go straight to Core Options. Or Video Settings. Or Controls.
Depends what I’m fixing. Aspect ratio? Video.
Input lag? Core Options. Button mapping?
Controls.
I change one thing at a time. Not five. Not ten.
One. Because if it breaks, I know exactly what broke it.
Here’s where most people fail.
They tweak and exit.
I wrote more about this in Lcfgamestick Instructions From Lyncconf.
They think “save” means “it stuck.”
It doesn’t.
You have to save it as a game-specific override. That’s how Lyncconf works. That’s how the .lconf file gets made.
So after changing aspect ratio from 4:3 to 16:9 for Chrono Trigger, I scroll down to Configuration > Save Current Configuration as Autoconfig.
Then I pick Save Game-Specific Override.
RetroArch asks: “Save override for chronotriggersnes.zip?”
I say yes.
Boom. A file named chronotriggersnes.lconf appears in /configs/retroarch/config/Lyncconf/. Not in the root.
Not in saves. In that exact folder.
That file now owns those settings. Only for that game. No other ROM touches it.
No global config overwrites it.
This is why you don’t get weird glitches on Donkey Kong Country just because you fixed EarthBound.
The naming is literal. Lowercase. No spaces.
No special chars. Just the ROM filename minus extension, plus .lconf.
Lcfgamestick Special Settings by Lyncconf builds on this. But with hardware-level tweaks baked in.
If you’re using the Lcfgamestick, you’ll want the Lcfgamestick instructions from lyncconf to line up firmware and override paths.
I’ve seen people rename files manually. Don’t. Let RetroArch do it.
It knows the rules.
One more pro tip: backup your .lconf files before updating RetroArch. Updates sometimes reset override paths. It’s happened to me twice.
Both times I had backups.
You want consistency? Save once. Test twice.
Ship the .lconf.
That’s it. No philosophy. No fluff.
Just press, change, save, go.
Lyncconf Fixes That Actually Work
I’ve spent way too many hours fighting emulator quirks. So let’s fix three things that break your flow.
First: PS1 games running like molasses. I switch the core to SwanStation for most of them. Not globally (just) for that game.
Right-click the title > “Edit Game Settings” > pick SwanStation > save as a Lyncconf file. Done. No more waiting for Metal Gear Solid to load.
Second: Arcade games with wonky controls. MAME and FBNeo don’t always map buttons right out of the box. You can remap just for Pac-Man Championship Edition, for example.
Go into input settings, assign keys or controller buttons, then save it as a game-specific override. It won’t touch Street Fighter II. Good.
Third: N64 glitches (screen) tearing, missing textures, black bars. Change the video plugin only for that title. GlideN64 often fixes Star Fox 64.
Save it. Don’t force it on everything.
These aren’t guesses. They’re what I use daily. The Lcfgamestick page has pre-built configs (including) Lcfgamestick Special Settings by Lyncconf.
If you’d rather skip the trial-and-error.
Fix Your Retro Games. For Real.
I’ve been there. That moment when a game you love just won’t boot. Or it runs slow.
Or crashes mid-level. Frustrating as hell.
You don’t need more hardware. You don’t need to downgrade emulators. You need control.
Lcfgamestick Special Settings by Lyncconf gives you that. Not guesses. Not presets.
Actual settings (tuned) per game.
Change one thing. Save it. Watch the game run right.
Most people wait for someone else to fix it. You’re done waiting.
Pick one game that’s been giving you trouble. Right now. Open the settings.
Apply what you learned.
Your perfect retro experience isn’t coming someday. It’s waiting for you to hit save.
Do it.


There is a specific skill involved in explaining something clearly — one that is completely separate from actually knowing the subject. Ryvel Durnhaven has both. They has spent years working with competitive gaming gear reviews in a hands-on capacity, and an equal amount of time figuring out how to translate that experience into writing that people with different backgrounds can actually absorb and use.
Ryvel tends to approach complex subjects — Competitive Gaming Gear Reviews, Team Meta Analysis in HCD Arenas, Hot Topics in Gaming being good examples — by starting with what the reader already knows, then building outward from there rather than dropping them in the deep end. It sounds like a small thing. In practice it makes a significant difference in whether someone finishes the article or abandons it halfway through. They is also good at knowing when to stop — a surprisingly underrated skill. Some writers bury useful information under so many caveats and qualifications that the point disappears. Ryvel knows where the point is and gets there without too many detours.
The practical effect of all this is that people who read Ryvel's work tend to come away actually capable of doing something with it. Not just vaguely informed — actually capable. For a writer working in competitive gaming gear reviews, that is probably the best possible outcome, and it's the standard Ryvel holds they's own work to.
