Warning
This is a public beta release. While it has been tested and is considered stable enough for regular use, some features may still behave unexpectedly and there may be cosmetic issues.
This beta will receive updates only within the beta branch. Once the final 1.4.2 release is published, you’ll need to reflash using the final release image to switch back to the stable update channel. Your Forge-X settings, user configuration, and calibration data will be preserved when switching to the beta and back — no recalibration is needed.
Even so, I strongly recommend creating a backup with TAR_BACKUP before installing the beta and downloading that backup to your computer as well, just in case.
By installing this version, you acknowledge that it is beta software and use it at your own risk. No guarantee is made that everything will work perfectly on every printer or configuration.
Highlights
- Fixed the “Timer too close” issue that could cause MCU shutdowns during heavy prints. With the current fix, previously problematic G-code files no longer reproduce the error in testing.
- Added a new Advanced Recovery mode for troubleshooting and recovery directly on the printer.
- Added Adaptive Pressure Advance, backported from Klipper 0.13, allowing Forge-X to use adaptive PA generated by recent Orca versions.
What’s included
- Improved Forge-X camera streamer with lower memory usage.
- Live camera effect tuning with automatic saving and restore after reboot.
- Faster printer boot process.
- Feather can refresh the bed mesh before starting a print and ask whether to save the new mesh afterward.
- A new Forge-X firmware installer with support for firmware packages directly, reducing the delay before the actual firmware image starts.
- The installation image is now about 15 MB smaller than in 1.4.1
- Many smaller bug fixes and improvements.
Help shape the future of Forge-X
Recently, we started talking about bringing Forge-X / Feather to other printers, so I made a few polls to get a better idea of how much real interest there is.
Before organizing any fundraising, I’d first like to understand whether moving in this direction makes sense for the community.
The basic idea is simple: to support another printer, I need access to the hardware first. But buying the printer alone doesn’t mean a full port will appear immediately — the biggest limitation is development time.
For some perspective, Forge-X 1.4.2 has already taken me around 250 hours of work. For a completely new printer, I’d roughly expect 2–3 months of focused development, possibly more, depending on the platform and how much needs to be adapted.
So there are really two separate parts: funding the printer itself, and ongoing support that would allow me to spend enough time developing, testing, and maintaining the port.
For now, I just want to measure interest:
FlashForge AD5X:
https://strawpoll.com/e6Z2A1G08gN
FlashForge Creator 5 (Pro):
https://strawpoll.com/Dwyo3Oxz0yA
Forge-X development support:
https://strawpoll.com/kjn1D1P0LyQ
Please also share these polls with friends, other communities, or anyone else who might be interested. A large part of the potential user base probably won’t see this post directly, so wider participation will make the results much more useful.
For now, this is only about understanding the level of interest. If there’s enough support, we can figure out the next step from there.
P.S. Join the discussion topic for announcements/news/next steps: #81