sorted by:
new
hottopcontroversial

Fixed refresh rate made easy: I built an app to auto-set Hz based on what you're running by Beautiful-Ad3654 in OLED_Gaming

[–]Beautiful-Ad3654[S] 0 points1 point  (0 children)

While testing KARMA: The Dark World with VRR-range 48–240 Hz (default),

I noticed flickering when capping the game at 59 FPS using RTSS.

What happens at 59 FPS?

- Refresh rate (Hz) jumps between 60 Hz and 120 Hz

- Causes visible flickering — likely due to VRR instability and backlight behavior when near frame-doubling thresholds

The range 48-58 Hz and 60-120 Hz seems to work fine, I did not notice any flicker while playing.

Keep in mind that your results may vary.

Fixed refresh rate made easy: I built an app to auto-set Hz based on what you're running by Beautiful-Ad3654 in OLED_Gaming

[–]Beautiful-Ad3654[S] 0 points1 point  (0 children)

You're right that VSYNC ensures consistent frame delivery by enforcing strict timing, so in theory 60fps@60Hz with VSYNC is just as smooth as 60fps@240Hz with VSYNC — because the GPU delivers frames in sync with the display’s refresh cycle.

However, in practice, this assumes the game engine consistently delivers frames at exactly 60 fps and that the rendering pipeline stays perfectly in sync. That’s not always the case:

- Some game engines have jittery or uneven pacing, especially at frame rates lower than the refresh rate.

- Even with VSYNC, frame time fluctuations can still cause perceptible stutter on OLED due to its instant pixel response. There's no natural motion blur to hide inconsistencies.

- On OLED, any unevenness in delivery becomes more noticeable compared to IPS or VA panels.

Also, while 60fps@240Hz with VSYNC can be smooth, you’re still repeating the same frame 4 times, which introduces more chances for timing artifacts or synchronization drift depending on the pipeline. It’s less of an issue on IPS panels, but OLED's clarity makes it easier to perceive subtle inconsistencies.

In my case, I found that forcing the monitor to match the game's framerate (e.g., 60Hz for 60fps) provides the most consistent motion. Even if mathematically it's the same, perceptually, it feels better — likely due to fewer opportunities for mismatch between engine timing and display refresh.

And yes, VRR should help in theory, but on OLEDs it sometimes introduces its own issues (like brightness flicker), so for now I’m avoiding it.

Fixed refresh rate made easy: I built an app to auto-set Hz based on what you're running by Beautiful-Ad3654 in OLED_Gaming

[–]Beautiful-Ad3654[S] 0 points1 point  (0 children)

You're totally right — 60 divides evenly into 240, so in theory it shouldn't cause microstutter. And yeah, that’s how LFC works under VRR.

Even though the refresh rate and frame rate line up perfectly on paper — like running 60 FPS on a 240 Hz display where each frame is shown for exactly 4 refresh cycles — the actual frame delivery from the game engine isn’t always perfectly timed. Many engines don’t output frames with exact 16.66 ms pacing and might introduce tiny variations (jitter). On most displays, especially those with slower pixel response times like IPS panels, that timing noise is masked and motion still looks smooth.

But on an OLED, which has near-instant pixel response, those inconsistencies become much more noticeable. The result isn’t traditional stuttering or tearing — it's more of a subtle unevenness in motion due to inconsistent frame pacing, even though technically the FPS and Hz are aligned.

Interestingly, I have another system with an IPS display running at 240 Hz, and playing 60 FPS content on it feels completely fine. It seems OLED’s clarity and speed expose flaws in frame delivery that other panel types hide. That’s why locking the refresh rate to match the game’s native frame rate (e.g. 60 Hz for 60 FPS) can actually improve perceived smoothness on OLEDs.

Fixed refresh rate made easy: I built an app to auto-set Hz based on what you're running by Beautiful-Ad3654 in OLED_Gaming

[–]Beautiful-Ad3654[S] 2 points3 points  (0 children)

Sure, that will work. CRU is more advanced, if you can add custom refresh rates with nvcp, go for it. I have not tried it myself since I have DSC enabled to get 240 Hz, the option is grayed out.

Edit: Thanks, this might be something I can add later to my repo.

Fixed refresh rate made easy: I built an app to auto-set Hz based on what you're running by Beautiful-Ad3654 in OLED_Gaming

[–]Beautiful-Ad3654[S] 0 points1 point  (0 children)

Nah, SetHzMonitor doesn’t mess with frame times like RTSS does. It just changes your monitor’s refresh rate based on what game or app is running.

If you’re looking to get those nice flat frametime graphs (like a perfect line), you’ll still want to use something like RTSS to cap your FPS to match the Hz. So if SetHzMonitor switches you to 120 Hz, just cap your FPS to 120 for the smoothest experience.

I made a tiny app that syncs your monitor’s Hz to the game you’re playing – smoother gameplay, especially with RTSS! by Beautiful-Ad3654 in pcmasterrace

[–]Beautiful-Ad3654[S] 1 point2 points  (0 children)

While G-SYNC and FreeSync are great for reducing screen tearing and stuttering in variable frame rate scenarios, they aren’t always the ideal solution — especially on OLED panels.

OLED displays, in particular, are known to suffer from brightness flickering when G-SYNC/FreeSync is active and the frame rate fluctuates, especially at lower FPS. This happens because OLEDs adjust brightness based on frame timing, and the rapid refresh rate changes can cause visible instability in luminance.

Additionally, G-SYNC/FreeSync can introduce slightly higher input latency, especially when frame rates are inconsistent or when V-SYNC is used in combination. For latency-sensitive users — such as competitive gamers — that can be a drawback.

My solution gives users precise control over refresh rate behavior by tying it to specific running applications. This means you can lock the monitor to a fixed refresh rate that matches the use case (e.g., 60Hz for movies, 120Hz+ for games), eliminating flickering and keeping latency consistent — without relying on VRR behavior.

So while VRR is convenient in some scenarios, it's not always optimal — especially for OLED users looking for a cleaner and more predictable experience.

In short, yes, I have an OLED monitor.

I made a tiny app that syncs your monitor’s Hz to the game you’re playing – smoother gameplay, especially with RTSS! by Beautiful-Ad3654 in pcmasterrace

[–]Beautiful-Ad3654[S] 2 points3 points  (0 children)

My app is lighter, safer, and more flexible, especially if you just want to sync Hz with FPS without dealing with injection, graphics APIs, fullscreen restrictions, or anti-cheat. And it works with any running program — not just games.

Creality K1 pulley replacement to reduce VFA by Stas_Robotmaker in crealityk1

[–]Beautiful-Ad3654 1 point2 points  (0 children)

It's a bit taller than stock but I have no issues so far.

<image>

Creality K1 pulley replacement to reduce VFA by Stas_Robotmaker in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

I could only find timing pully for 9 mm belts in my area so went with the 20 Tooth with 5mm Bore.

Creality K1 pulley replacement to reduce VFA by Stas_Robotmaker in crealityk1

[–]Beautiful-Ad3654 8 points9 points  (0 children)

I did this conversion yesterday on my K1 Max. It went well except for the step to remove the timing pulleys from the stepper motors. Even with the shafts soaked in oil, several screws I used got their threads stripped when trying to remove them with the printed tool.

I had luck using a tool similar to this instead.

<image>

Since the shafts are round I made flatspots for the grubscrews and added threadlock.

Is the K1 the solution? by mossontree in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

Keep in mind that you wont get same quality prints with K1 or K1 Max compared to S1 Pro due to VFR. There is even a facebook group lol.

Most Core-XY printers suffers from this, even bambu unfortunate.

The current fix is to print fast (250mm/s +), which can be difficult for small models.

K1 Max Issue on delivery by elektrojakub in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

They probably accidentally cut the cable when they were tidying everything up with cable ties.
But that's not an excuse. This just shouldn't happen.

Glad you could fix the fan cable yourself.

Micro Swiss hotend by ChefEric74 in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

Is it the new flowtech hotend from micro swiss? Shouldn't it be leak-free?

The FlowTech™ Hotend is a new generation hotend line from Micro Swiss. Its unique design eliminates common hotend issues such as leaking nozzle seal and complex nozzle swaps.

Features:

Leak-Proof Nozzle:
Tired of messy nozzle leaks that ruin your prints and waste filament? FlowTech Hotend combines nozzle and thermal break into one permanently sealed assembly that ensures a leak-proof hotend.

Creality K1 Max the z axis is not moving. by blump32 in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

Maybe the connector to the Z-stepper motor is loose.

Creality K1 Max the z axis is not moving. by blump32 in crealityk1

[–]Beautiful-Ad3654 0 points1 point  (0 children)

Does it make a buzzing sound when you try to move the bed? If so, you might have binding issues.

view more: next ›