Development Build
Below are development builds for testing purposes.
Latest development build: 2.8.0.49 (August 22nd 2026)
Latest stable release build: 2.8.0
https://github.com/clsid2/mpc-hc/releases/tag/2.8.0
Below are development builds for testing purposes.
Latest development build: 2.8.0.49 (August 22nd 2026)
Latest stable release build: 2.8.0
https://github.com/clsid2/mpc-hc/releases/tag/2.8.0
Today, we're excited to share a brand-new gameplay preview from our upcoming South Dakota DLC for American Truck Simulator! Get a closer look at some of the beautiful roads, landmarks, and industries our map team has been recreating.
In the gameplay preview below, you'll follow a journey that begins in the Black Hills before passing by the scenic Pactola Lake and crossing the Spring Creek Memorial Bridge. Along the way, we'll drive through several settlements, including the beautiful city of Hot Springs and part of the historic town of Deadwood, before completing our delivery at a wood processing depot.
This route is just a small preview of what South Dakota has to offer, featuring winding mountain roads, charming communities, and diverse scenery. Whether you're taking in the views or making deliveries across the state, there's plenty to discover behind the wheel.
We hope you enjoy this gameplay preview and the stunning scenery South Dakota has to offer. As always, please keep in mind that everything you see is still a work in progress and subject to change during development.
If you like what you see, be sure to add the South Dakota DLC to your Steam Wishlist. Don't forget to follow us onΒ Twitter,Β Facebook,Β Instagram,Β Bluesky, andΒ YouTube, orΒ sign up for our newsletter. Until next time, happy haulin'!

Fixed Firefox becoming unresponsive when clearing browsing history, which could also result in site data being lost. (Bug 2059647)
Reference link to 153.0.3 release notes.
β
This new alpha build introduces 8 new effects, fixes some crashes and other glitches, fixes compatibility with some old plugins, and adds some debugging options to assist with the WINE effort.
You can read more about 5.2 and what it includes by reading the release notes for the first alpha.
The new effects will be discussed more in the final release notes for 5.2, when the time comes, but here are some previews for now. Each new effect is also available for plugins to use in their Direct2D effect graphs.
Original Image
![]()
Linocut
![]()
Mosaic
![]()
Pointillism
![]()
Stained Glass
![]()
Ordered Dither
![]()
Spherize
(This isnβt actually a very good image to use for showcasing this effect. Iβll have a better example for the final release notes.)
![]()
Waves
Here are several examples for this one, which has many different modes you can experiment with:
![]()
Halftone
![]()
Change Log
Changes since 5.2 Alpha (build 9688):
Download and Install
This build is available via the built-in updater as long as you have opted-in to pre-release updates. From within Settings -> Updates, enable βAlso check for pre-release (beta) versions of paint.netβ and then click on the Check Now button. You can also use the links below to download an offline installer or portable ZIP.
![]()
You can also
download the installer here (for any supported CPU and OS), which is also where you can find downloads for offline installers, portable ZIPs, and deployable MSIs.
β

We are pleased to announce the fifth release candidate preview release of Jellyfin 12.0!
This is a preview release, intended for those interested in testing 12.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Starting with this release, we are dropping the preceding 10. from our versioning. Thus, 10.11.x -> [10.]12.x = 12.x. The reason is simple: at this point in the project, we don't envision a hard break in the API like we planned way back in the early days, and this version scheme was causing a lot of confusion amongst users about what a "major" release was. For more information, please see the RC1 release notes.
The main goal of this release has been performance. 10.11.0 dropped a major backend rewrite, and while it was broadly functional, it had a lot of rough edges. This release seeks to polish out most of those rough edges and bring better performance to all users.
There are many other small fixes, improvements, changes, and translations. See our draft release notes here or below for the full list of pull requests. You can also view the Server side changelog here.
Note: You must be on Jellyfin 10.10.7+ or 10.11.x (ideally, 10.11.11) before upgrading! If you are not, the upgrade will fail. Ensure you upgrade to one of these versions first!
Note: The initial load of Jellyfin 12.x will run a few migrations and will take several minutes. Please be patient and do not interrupt the process. You can leverage the (newly improved!) startup UI on your local network to see specific progress, or off-network to see general progress, by visiting the server URL in your web browser during startup.
Note: If you install the RC, you should disable all external plugins and reinstall using the unstable plugin repository, or plugins may fail to load and cause unintended side effects.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
12.0-rc5 or preview tags.v12.0-rc4)Full Changelog: v12.0-rc4...v12.0-rc5
We are pleased to announce the fifth release candidate preview release of Jellyfin 12.0!
This is a preview release, intended for those interested in testing 12.0 before its final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Starting with this release, we are dropping the preceding 10. from our versioning. Thus, 10.11.x -> [10.]12.x = 12.x. The reason is simple: at this point in the project, we don't envision a hard break in the API like we planned way back in the early days, and this version scheme was causing a lot of confusion amongst users about what a "major" release was. For more information, please see the RC1 release notes.
The main goal of this release has been performance. 10.11.0 dropped a major backend rewrite, and while it was broadly functional, it had a lot of rough edges. This release seeks to polish out most of those rough edges and bring better performance to all users.
There are many other small fixes, improvements, changes, and translations. See our draft release notes here or below for the full list of pull requests. You can also view the Web side changelog here.
Note: You must be on Jellyfin 10.10.7+ or 10.11.x (ideally, 10.11.11) before upgrading! If you are not, the upgrade will fail. Ensure you upgrade to one of these versions first!
Note: The initial load of Jellyfin 12.x will run a few migrations and will take several minutes. Please be patient and do not interrupt the process. You can leverage the (newly improved!) startup UI on your local network to see specific progress, or off-network to see general progress, by visiting the server URL in your web browser during startup.
Note: If you install the RC, you should disable all external plugins and reinstall using the unstable plugin repository, or plugins may fail to load and cause unintended side effects.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
12.0-rc5 or preview tags.v12.0-rc4)Full Changelog: v12.0-rc4...v12.0-rc5
Warning
After upgrade, you need to run php bin/console doctrine:migrations:migrate (or equivalent) as webserver user after upgrade.. If you are running a docker container, use sudo docker exec --user=www-data partdb php bin/console doctrine:migrations:migrate, or sudo -E inside the docker container, to ensure that the migrations are applied to the correct database.
Important
Since this version Part-DB can enable foreign key checks for SQLite: it is recommend to do this, but it requires some manual intervention. See this announcement on how to do it: #1486
Note
If you are using Part-DB it would be helpful if you fill out this short survey on your usage of Part-DB (Google Forms): https://forms.gle/Q15twx3YYq3qCNfe8
Full Changelog: v2.14.1...v2.15.0