RustForge Patch Notes - Version 3.9.6.0 "The Precision Sleep Engine Revamp!"

Transmission from RustForge 🎙️

The next evolution of the RustForge engine has arrived. Version 3.9.6.0 focuses entirely on raw performance and timing accuracy. I have officially overhauled the core timing logic to bypass the limitations of the Windows OS scheduler, ensuring that your painting speed is no longer held back by system clock "micro-naps."

From the new Hybrid Wait Logic to the total elimination of the "15.6ms Trap," this update delivers the most linear and responsive painting experience to date. Whether you are pushing the limits with Turbo speeds or running on mobile hardware, the engine now adapts to your CPU cycle for frame-perfect execution.

Revamping the Precision Sleep Engine

Standard "Windows Thread Sleeping" is notoriously unreliable. If you tell Windows to sleep for 5ms, it might decide to take 15.6ms instead. When painting 100,000+ pixels, these delays result in hours of wasted time. The new engine uses a tiered approach to bypass these limitations.

• The 15.6ms Trap: Previously, faster settings (Turbo/Fastest) were hitting the Windows Scheduler wall. If the app asked for a 10ms delay, the OS would round it up to the nearest "clock tick" (15.6ms), causing stuttering and uneven lines. This has been eliminated.

• The 15ms Threshold (Safety Buffer): We no longer use Windows Thread Sleeping for anything under 15ms. By keeping the thread "awake" for Turbo and Fastest settings, we bypass the OS scheduler entirely for raw millisecond precision.

• Hybrid Wait Logic: For Turbo/Fastest, we use a high-performance "hot loop" that keeps the CPU core locked on the operation, ensuring the mouse moves the exact nanosecond the timer hits zero. For Normal/Fast, we use a partial sleep to keep CPU usage low but wake the thread early to finish with high-precision timing.

What this Means for Users

• True Speed: "Fastest" is now actually 2x faster than "Normal."

• Zero Jitter: Mouse movement is now perfectly linear. No more "clumping" of pixels or "dropped pixels" left unpainted due to missed timing. This will only happen when you try to run speeds that are too high for your machine to handle, or lag caused an input stutter.

• Input Buffer Stability: By controlling timing at the CPU cycle level, we stay within "OS Input" limits, preventing input drops even at Turbo speeds.

Compatibility & Hardware Notes

Because the new engine utilizes high-performance loops for accuracy, users should be aware of how their hardware handles the load.

• CPU Usage: Turbo and Fastest settings use a "Hot-Thread" to achieve accuracy. You will notice higher CPU usage on a single core during the painting process, this is intentional for frame-perfect timing.

• Hardware Scalability: If you are on an older laptop or a dual-core CPU and experience "system heaviness" or Discord lag, switch to Normal or Fast. These settings still use partial sleeping to give your hardware room to breathe.

• Thermal Throttling: On low-end mobile hardware, high-precision loops may cause heat. If your laptop throttles (slows down to cool), your painting speed will become inconsistent. Stick to Fast (15ms) or Normal (20ms) for the best results on mobile hardware.

Bugfixes & Stability

Color Selection Fix: Resolved a race condition that prevented RustForge from clicking the first color in a painting operation. This fix applies to both default and adaptive palettes, ensuring a color is always selected or pasted at the start of a session. This bug was introduced in the last update, and it's finally tracked down and fixed!

Input Stability Buffer: Added a new Safe Painting Mode in the settings. If you experience "specks" or "tearing," enabling this adds microsleeps between each mouse input operation for extra stability on specific hardware configurations.