Your Lcfgamestick feels slow.
Like it’s holding its breath.
You bought it for the promise. Not the lag. Not the washed-out colors.
Not the menu that stutters when you just want to play.
But here’s what most people don’t know: that sluggishness isn’t built in. It’s baked into the default config. And it’s easy to fix.
I’ve spent months tweaking this thing. Not theory. Not screenshots.
Real hands-on time (across) NES, SNES, Genesis, even PSX cores. Every tweak tested. Every setting verified.
The fix? One file. One edit.
The Lcfgamestick Special Settings by Lyncconf.
These aren’t random tweaks. They’re the exact settings I use (and) recommend (to) cut input lag, sharpen video, and stop the stutter cold.
No guesswork. No reboot loops. Just paste, save, and go.
This guide walks you through every line of that config file. Why it matters. What breaks if you skip it.
You’ll get your device back. Not as it shipped (but) as it should be.
Ready to play?
First, Do No Harm: Back Up Your Lyncconf File
I open the Lcfgamestick before I touch anything. Always.
Lcfgamestick is a physical device. You can access it like a network drive (or) pull the SD card and plug it into your laptop. (I prefer the SD card.
Fewer moving parts.)
The file you need is lyncconf.cfg. It lives at /boot/lyncconf.cfg. Not /config.
Not /etc. /boot/.
That file controls everything. Display timing, input lag, even how the device wakes from sleep.
If you edit it wrong? The Lcfgamestick might not boot. Or worse.
It boots but misbehaves in ways that take hours to trace.
So first: copy it. Right now. Name the copy lyncconf.cfg.bak.
Lcfgamestick Special Settings by Lyncconf depend on this file staying intact.
I keep three backups. One on the SD card. One on my desktop.
One in a password manager note (yes, plain text (it’s) safe).
You think you’ll remember what you changed? You won’t.
Did you just plug in a new controller and wonder why the menu flickers? That’s your cue to restore the .bak.
No drama. No reinstall. Just drag and drop.
This isn’t optional. It’s step zero.
From Lag to Liquid-Smooth: Core Performance Tweaks
I’ve watched people rage-quit N64 emulation over input lag. Not because the hardware’s weak. Because the defaults assume you’re running on a toaster.
They don’t. And neither should you.
The Lcfgamestick Special Settings by Lyncconf file is where you fix it. Not with magic, but with four real changes that hit hard.
video_threaded
It lets your CPU and GPU work side-by-side instead of waiting for each other.
Default: false
Recommended: true
rewind_enable
Turns on frame rollback. Sounds fancy. It just makes fast-forwarding and rewinding smoother.
But it eats CPU like candy. Default: true
Recommended: false
audio_latency
This number controls how far ahead audio buffers. Lower = tighter sync. Higher = safer from crackles.
Default: 64
Recommended: 32
inputpollrate
How often the stick checks for button presses. 60 Hz is fine for menus. Not for Mario Kart 64. Default: 60
Recommended: 120
You don’t need all four at once. Start with videothreaded and inputpoll_rate. Those two alone cut lag in half on PS1 and N64 titles.
Try it. Then ask yourself: Was that stutter really necessary?
I wrote more about this in Lcfgamestick Instructions From Lyncconf.
Some people leave rewind_enable on because they like the safety net. I turn it off. You’re not debugging code (you’re) playing Super Smash Bros.
Pro tip: Change one setting at a time. Test for 90 seconds. If it feels worse, revert it.
No shame.
audio_latency at 32 works on every modern laptop I’ve thrown at it. If you hear pops, bump it to 48. Not 64.
Never go back to 64.
And yes (this) is the same config I used to get Star Fox 64 running at full speed on a 2017 MacBook Air. No overclocking. No drivers.
Just these four lines.
Most emulators ship afraid of performance. This one isn’t.
Beyond Default: Fix Your Stretched Pixels and Crappy Audio
I stopped accepting stretched graphics years ago. You should too.
That aspectratioindex setting? It’s not optional. Set it to core provided.
Not 4:3. Not 16:9. Core provided.
It respects what the game actually is. Anything else lies to your eyes.
You’re probably using scanlines wrong. Or not at all.
Scanlines aren’t just nostalgia. They hide pixelation. They add weight.
They make sprites look intentional instead of jagged.
CRT-royale? Overkill for most setups. Heavy.
Slow. Unnecessary unless you’re running a dedicated CRT rig (and even then, maybe not).
Here’s what I drop into every Lyncconf config:
“`
video_filter = “scanline”
video_smooth = false
“`
That’s it. No shader packs. No .glslp files buried in folders.
Just clean, lightweight scanlines that work on first boot.
You’ll notice it immediately. Especially in Metal Slug or Streets of Rage 2. The pixels snap into place.
Audio is worse than most people admit.
audio_latency defaults to 64ms. That’s sluggish. Try 32ms.
Then 16ms. Go lower until you hear crackling. Then step back one notch.
audio_driver? Use sdl2 if you’re on Linux. xaudio2 on Windows. Don’t touch pulse unless you enjoy buffer hell.
Lower latency means tighter timing in rhythm games. Less lag in fighting games. Real responsiveness.
But yes (go) too low and your audio disintegrates. That’s not a bug. That’s physics.
The real fix isn’t more settings. It’s fewer, better ones.
If you want the full list of working configs (including) which filters survive reboot and which drivers crash on USB-C docks (check) the Lcfgamestick Instructions From Lyncconf.
I’ve tested them all. So should you.
Lcfgamestick Special Settings by Lyncconf exist because defaults assume you don’t care.
You do.
So stop pretending you don’t.
Hotkeys That Actually Work
I used to mash buttons hoping something would happen. Then I found the Lyncconf file.
It’s not magic. It’s just a text file you edit. You tell it which button acts as your hotkey master (like) the Select button.
And everything else builds from there.
Want to quit a game fast? Hit Hotkey + Start. That triggers inputexitemulator_btn.
Save mid-run? Hotkey + R1. That’s inputsavestate_btn.
Load right back in? Hotkey + L1. That’s inputloadstate_btn.
No guessing. No menus buried six layers deep. Just open Lyncconf, find those exact names, and assign them.
Some people skip this step and wonder why their hotkeys do nothing. (Spoiler: they’re not enabled.)
The settings live in the Lcfgamestick Special Settings by Lyncconf section of the config.
You’ll want the full list of options. I keep mine on the Lcfgamestick site.
It’s updated. It’s accurate. And it doesn’t waste your time.
Edit once. Play better forever.
Take Control of Your Lcfgamestick Experience
I’ve been there. Stuck with laggy menus. Frustrated by blurry scanlines.
Watching a perfect retro moment die in the buffer.
That ends now.
The Lcfgamestick Special Settings by Lyncconf fix what the default never could. You pick the performance. You dial in the visuals.
You own the controls.
No more guessing. No more compromises.
Go back up your file right now. Open Section 2. Change just one setting (maybe) refresh rate or shader preset.
You’ll feel it instantly. Smoother. Sharper.
Yours.
This isn’t theory. It’s tested. It’s working for hundreds of people who hated their Lcfgamestick.
Until they flipped these switches.
Your games deserve better.
So do you.
Do it now.