In the 1.60 update, we have introduced the Improved Material System for selected trucks for both Euro Truck Simulator 2 and American Truck Simulator. And today, we bring you a look behind the scenes at how this feature came to life!
The two main people working on this feature are our colleagues Daniel and Martin, who were and still are implementing the system for trucks in both games, and also for cars in the upcoming Road Trip project for American Truck Simulator.
"I've been working at SCS Software for over thirteen years. I started as a 3D Generalist, then worked as a 3D Vehicle Artist and Vehicle Team Lead. Today, my role is the Vehicle Technical Leader.
My work bridges the gap between the graphical and technical aspects of development. I collaborate with programmers to implement vehicle features into the engine, while also helping artists establish efficient workflows. I also design new tools and technical improvements.
My task on the improved material system was to identify the problem, propose a solution, and collaborate with programmers on its implementation into the engine. Next, we needed to set up a practical workflow for the vehicle team so that the system could be used consistently across other vehicles. The programmers created the necessary support in the engine and shaders. The graphic designers then converted and fine-tuned the materials for specific trucks."
"I work as a Senior 3D Graphic Designer specializing in vehicles. I also worked as Head of Content for the Road Trip project. I participated in selecting the vehicles and their specific variants, handled research and pre-production, provided expert consultation, and subsequently worked on the actual creation of the vehicles. I also helped Dan fine-tune changes to the material system.
Cars have been a long-standing passion of mine, especially sports cars and classic cars - particularly American ones. Thanks to this, I was able to bring my own experience and knowledge of American automotive culture, history, and the technical development of individual models to the project.
My main task was the 1967 Ford Mustang and everything related to its visual and content preparation. I was involved in selecting the specific car and its variant, conducting research, gathering references, consulting during data collection, and the actual creation of the model and materials.
During the development of the new material system, I prepared and fine-tuned the individual surfaces on the Mustang. Together with Dan, we used this car to verify how the new technical solution behaved in practice and which values provided the most accurate results."
How did this project start?
"Development began while we were working on the Road Trip project. The interiors of passenger cars are smaller and darker than those of trucks, so the shortcomings of the original system were more noticeable in them.
Aside from direct light, the original system had no way to render light within the interiors. In the real world, a large portion of the visuals consists of so-called indirect, or reflected light (GI). However, the game did not work with this concept at all and was not designed for it. We knew we needed to change this somehow.
The second problem was that the interiors of the trucks contain many different materials, such as fabric, leather, plastic, painted surfaces, metal, and glass. The original system was unable to render them accurately, especially under indirect lighting; everything looked very flat.
"Road Trip provided us with a suitable, isolated environment for development and testing. From the start, however, we designed the system so that it could also be used for trucks," says Daniel.
What did you have to do before actually starting to implement the improved system?
"We needed to map out the actual vehicles and the materials used in their interior in detail through extensive research. I studied magazines, photographs, available documentation, and individual trim levels. While gathering data, we had the opportunity to see the specific car in person, speak with its owner, and document its construction and appearance in detail.
It wasn't enough to simply determine that a certain part of the interior was made of, for example, plastic, leather, or metal. We also had to examine the surface texture, the degree of gloss, the way the material reflects light, its wear and tear, the color shade, and the differences between individual parts.
This research laid the foundation upon which we could later assess whether the materials in the game corresponded to the actual vehicle," Martin told us.
"We also had to decide which direction to take. One of the key requirements was maintaining performance, so we looked for approaches that didn't require complex computational operations and sought techniques that would achieve good results with minimal changes to computational complexity. I believe the result of our efforts is a noticeable improvement in graphics with minimal impact on performance," Daniel shared with us.
How did the process of bringing the new system into the game look?
"We needed to implement changes to the engine regarding how the game loads and handles reflective textures. A reflective texture is essentially a cube where each face shows a reflection in a different direction relative to the player. Using it is significantly more efficient than calculating actual light reflections using ray tracing. We made several changes to the code to gain direct access to individual mipmaps. A mipmap is a scaled-down copy of the original image, typically used when a textured object is farther away from the player to eliminate unappealing texture aliasing. In our specific case, however, a lower resolution automatically results in a softer reflection, which can be used for materials that do not have a 100% glossy surface but rather a physically rougher surface, causing the reflection on the material to be more diffuse.
This way, we created several different levels of reflection smoothness, ranging from perfectly glossy surfaces like chrome, through smoother reflections such as those found on leather seat materials, to rough, nearly non-reflective materials like fabrics, where one side of the reflection cube is only 2x2px. In our case, it replaces the Iradience map, which means it primarily serves to project the surrounding light palette onto the given material (color cast). The game was already calculating the mipmaps themselves, which means this change costs us practically nothing in terms of performance - and that is the main reason we decided to use this approach.
Along with the material changes, we also needed to rebalance the contrast and lighting throughout the game to eliminate extremely dark areas and achieve a more realistic sense of lighting.
Unlike the original solution, where reflective textures were used only for highly reflective materials, particularly metals, the revised system applies a reflective texture to every single material in the vehicle's interior. However, they differ in how strongly the reflection is visible in the final image and in the softness of the reflection applied. This ensures that even less reflective materials - especially plastics - convey a sense of reflected light, color cast, and improved contrast, particularly in shaded areas of the interior. Players will now notice that the entire interior actually reacts to the truck's surroundings; for example, when driving past trees, the part of the interior near the windows takes on a subtle green tint. This makes the game feel much more realistic than before, even without the computationally expensive global illumination (GI) calculation.
Once the technology was ready, we needed to determine how to adjust the individual materials under the new conditions. Since each material now includes a reflective component, we had to completely rebalance all the settings for each material. To ensure that existing textures would function correctly with the new settings, we also had to rebalance their color and specular components to the standard values we had established during our extensive testing.
The final step for system-wide deployment was to create a material library so that we wouldn't have to configure each material type separately for every vehicle," Daniel explains.
What were the biggest challenges in implementing the system?
"The biggest challenge was the diversity of the vehicles. The individual trucks were created at different times and used different source data, textures, and rendering methods. There is no single conversion that works for all trucks. Each completed interior has its own structure and requires a customized approach," says Daniel.
"Also, the individual properties of materials influence one another. Changing the reflectance or roughness might improve the appearance of one surface, but at the same time cause the material to behave poorly in a different lighting situation. Or a material that looked right in direct daylight might be too shiny in a dark interior or react unnaturally while driving at night. It was therefore necessary to constantly strike a balance between realism, visibility, and consistent behavior. The goal was not to make all surfaces more prominent or shinier, but to accurately capture the differences between them.
We reworked many of these steps several times during development. However, the result was not just materials for one specific car, but also experience and guidelines that will significantly facilitate work on future vehicles.
The process wasn't straightforward. It wasn't enough to simply set a few parameters according to a pre-prepared table. We had to figure out many of the values ourselves, and together with Dan, we tested them repeatedly right in the game," Martin added.
How did you manage to do the changes without affecting performance?
"Our players use a wide range of hardware. We didn't want to create visual enhancements that would significantly reduce the game's performance or even make the game unplayable for some players. Therefore, the system is not based on a new, resource-intensive lighting simulation. It extends the existing rendering pipeline and utilizes already available data more efficiently.
Performance was continuously profiled during development. The goal was to achieve a visible improvement with minimal impact on the graphics card and memory. Furthermore, the system is configured to function with a certain trade-off even when set to medium or low - in such cases, while reflections are not rendered in real time and some benefits, such as realistic color cast from the vehicle's surroundings, are lost, the materials themselves still look realistic and can be distinguished from one another," says Daniel.
So far, we've implemented the improved material system on four trucks across ETS2 and ATS. Rather than making the community wait until every truck has been updated, we'll continue rolling out the improved material system for other trucks gradually, allowing you to enjoy the improvements on some vehicles already while we complete the rest. As Daniel explains here:
"Each truck requires individual adjustments, a visual inspection, and testing of all variants in daylight, at night, in the rain, and in cloudy weather. Therefore, it was not possible to update the entire fleet at once. This smaller initial group will allow us to verify the entire production process, maintain quality, and gather feedback from players."
We hope you have enjoyed this in-depth look at how we work on the improved material system. Make sure to also add the Ford Car Pack and the RAM & Dodge Car Pack to your Steam wishlist, so you can enjoy this feature on cars when we release them.
Don't forget to give our X/Twitter, Instagram, Facebook, Bluesky, TikTok, and YouTube a follow, as you'll receive updates about our games straight to your feed! Or subscribe to our newsletter to stay informed. Until next time, safe travels!
Changelog
================================================================
Wana boot and install OS through network (PXE)? Welcome to my new project iVentoy.
About iVentoy https://www.iventoy.com/
iVentoy is an enhanced version of the PXE server.
Extremely easy to use
Many advanced features
x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI and ARM64 UEFI mode supported
110+ common types of OS supported (Windows/WinPE/Linux/VMware)
Turn any PC, laptop, server, NAS, or Raspberry Pi into a PXE server instantly!
......
Windows Installer
Windows No Installer (zip)
macOS - Universal
Linux - deb, AppImage or rpm
Windows intel x32 releases are marked -ia32-
ChangeLog:
Docker images have been built and pushed:
Docker Hub:
Log inalexta69/metube:latestalexta69/metube:2026.07.24GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.07.24
The Stable channel has been updated to 150.0.7871.186/.187 for Windows and Mac and 150.0.7871.186 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 4 security fixes. Please see the Chrome Security Page for more information.
[N/A][518237034] High CVE-2026-16807: Out of bounds write in Codecs. Reported by Google on 2026-05-30
[N/A][522064153] High CVE-2026-16806: Use after free in WebMCP. Reported by Google on 2026-06-10
[N/A][523292588] High CVE-2026-16805: Use after free in Blink. Reported by Google on 2026-06-12
[N/A][524721670] High CVE-2026-16804: Use after free in Input. Reported by Google on 2026-06-16
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome
General
API
Media-Over-QUIC
WebRTC
RTSP
HLS
SRT
Dependencies
Binaries are compiled from source code by the Release workflow, which is a fully-visible process that prevents any change or external interference in produced artifacts.
Checksums of binaries are also published in a public blockchain by using GitHub Attestations, and they can be verified by running:
ls mediamtx_* | xargs -L1 gh attestation verify --repo bluenviron/mediamtx
You can verify checksums of binaries by downloading checksums.sha256 and running:
cat checksums.sha256 | grep "$(ls mediamtx_*)" | sha256sum --check
Note
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
If you've been following our rework projects in American Truck Simulator, you may be wondering what's next after our recent focus on Route 66. Today, we're excited to share the answer! Our next major undertaking will be the Nevada Rework Project, where we'll give the Silver State a complete overhaul.
As part of this next phase, our map designers will focus on the entire state of Nevada, reworking all of its existing cities and road networks to bring them up to the quality standards of our latest content. Since Nevada was one of the original states released with American Truck Simulator, this rework will allow us to rebuild many locations from the ground up while preserving the character and atmosphere that make the state so unique.
In addition to refreshing familiar places, we're also taking the opportunity to expand Nevada with locations and road connections that were missing from the original version. One example is the city of Fallon, located east of Carson City. Alongside it, we'll also add the missing sections of US-95 that pass through Fallon from south to north, creating a more complete and authentic driving experience.
Throughout the state, you can also look forward to a variety of brand-new custom depots, offering more diverse delivery destinations and making freight transportation across Nevada feel even more immersive than before.
This is just the beginning of the Nevada Rework Project, and we're looking forward to sharing more previews from development as work progresses. Be sure to follow us on X/Twitter, Facebook, Instagram, TikTok, Bluesky, and YouTube, or sign up for our newsletter so you don't miss any future updates. Until next time, keep on truckin'!
Ever since we introduced the idea of a community-powered device database at State of the Open Home 2025, our goal has been clear: create a “Wikipedia of smart home devices” based on real-world usage. In February, we took the first step by inviting Home Assistant users to voluntarily share anonymized device data to help us build it.
The Stable channel has been updated to 151.0.7922.47/.48 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.
You can find more details about early Stable releases here.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome
Thank you for your donations:
One-time
Monthly
url()/@import from <style> blocks in the sanitizer (#457)LOGIN_SHOW_TOTP and LOGIN_SHOW_VERSION config flags (#520)NEXT_PUBLIC_LOCALE_PREFIX build argumentui.rerenderFetchedEmails method (#668)onEmailsFetched and onSearchResults hooks and getSomeEmails JMAP methodonRecipientChipsChange hookwebauthn.getOrCreate API methodui:download-file consent permission)target/rel on links in plain-text message bodies and open signature links in a new tabmailboxIds replacementspf=none from downgrading a MAIL FROM spf=pass (#650)dompurify to 3.4.12 and next-intl to 4.13.3
Our wheels keep turning, and today we’re ready to share a teaser of another U.S. state currently in development for American Truck Simulator. Let’s see how good your guessing game is!
We are pleased to announce the third 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-rc3 or preview tags.v12.0-rc2)README.md by @kaunkrishna in #17382Full Changelog: v12.0-rc2...v12.0-rc3
We are pleased to announce the third 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-rc3 or preview tags.v12.0-rc2)assign-in expression by @timreichen in #7073Full Changelog: v12.0-rc2...v12.0-rc3
The Stable channel has been updated to 150.0.7871.181/.182 for Windows and Mac and 150.0.7871.181 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 12 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$500][527930356] High CVE-2026-16420: Type Confusion in WebAudio. Reported by Found by XBOW and triaged by Brendan Dolan-Gavitt on 2026-06-26
[$500][528276487] High CVE-2026-16421: Inappropriate implementation in WebAudio. Reported by Found by XBOW and triaged by Brendan Dolan-Gavitt on 2026-06-26
[N/A][517359779] High CVE-2026-16413: Out of bounds write in ANGLE. Reported by Google on 2026-05-28
[N/A][517651910] High CVE-2026-16414: Insufficient validation of untrusted input in Chromecast. Reported by Google on 2026-05-28
[N/A][519244446] High CVE-2026-16415: Insufficient validation of untrusted input in Extensions. Reported by Google on 2026-06-02
[N/A][520172356] High CVE-2026-16416: Integer overflow in Chromecast. Reported by Google on 2026-06-05
[N/A][521491024] High CVE-2026-16417: Uninitialized Use in Skia. Reported by Google on 2026-06-08
[N/A][522125255] High CVE-2026-16418: Stack buffer overflow in V8. Reported by Google on 2026-06-10
[N/A][523435970] High CVE-2026-16419: Out of bounds read and write in ANGLE. Reported by Google on 2026-06-13
[N/A][533515002] High CVE-2026-16422: Insufficient validation of untrusted input in Certificate. Reported by Google on 2026-07-10
[N/A][534582496] High CVE-2026-16423: Use after free in UI. Reported by Google on 2026-07-14
[N/A][534858939] High CVE-2026-16424: Use after free in GPU. Reported by Google on 2026-07-14
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome
Important
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
TRUSTED_HOST value must not be quoted in docker-compose file, both in documentation and messages (#1453)Full Changelog: v2.13.3...v2.13.4
Important
The NVIDIA SDK was updated to version 13 in this release. This means that the minimum supported driver version is now 570. If you experience any issues with NVENC, please ensure that your GPU driver version is fully up to date.
OBS-Studio-32.2.0-Sources.tar.gz: a26a5da53964a8c38741c613f14f93cc37d95354e5225a07b6618152cdfcec1c
OBS-Studio-32.2.0-Ubuntu-24.04-x86_64-dbsym.ddeb: 650dc0f064b96a02238b0f328263b221abca3a246456ea379e2d7729ac48adba
OBS-Studio-32.2.0-Ubuntu-24.04-x86_64.deb: 4b691bef1eabba502e6d7592f87d09049af56d00d83f06087a7b447cc7c19d98
OBS-Studio-32.2.0-Ubuntu-26.04-x86_64-dbsym.ddeb: f0b0962bda0e5739250e903c61d536c5db3746f23902a7c142f1521c8c386d4d
OBS-Studio-32.2.0-Ubuntu-26.04-x86_64.deb: 82a74954f7fad626480b20fa6ab50c48245d604962b5c57c68a5dfe0e55fcb0a
OBS-Studio-32.2.0-Windows-arm64-PDBs.zip: a5b673de8e198b2db1d8d974043661bb64ee3f5b9ddcae33a3c9aa48604e8bd4
OBS-Studio-32.2.0-Windows-arm64.zip: 5c819148cf916d8621449633f55fa8b80eaf7d51bd5d5afa984d509105484047
OBS-Studio-32.2.0-Windows-x64-Installer.exe: e85f7cc39129c4c1999d84765fde8dade4c9a9800972f78d752ad218e7c50302
OBS-Studio-32.2.0-Windows-x64-PDBs.zip: dfa28cb12311e61b432b63d7dc5308365542ca8703a67a3f0d262825171b1aef
OBS-Studio-32.2.0-Windows-x64.zip: 793c8866796f94b907646c63ac73b9d0df7e98dcdab5b6bfd5baebf153e1ed92
OBS-Studio-32.2.0-macOS-Apple-dSYMs.tar.xz: 0b1c0380cc6d37ba3966518e9d8b9ad56ca92989255fd010f404d834bb5cd970
OBS-Studio-32.2.0-macOS-Apple.dmg: e4bed7f871efa8f2bb5b31d1bbdbde1d0b1016062050f5eab03fd16d44f7a04d
OBS-Studio-32.2.0-macOS-Intel-dSYMs.tar.xz: 4927c042adddf67955deff437560c81906f94316a1ebbc720db8e16ead099f56
OBS-Studio-32.2.0-macOS-Intel.dmg: 7c8cccd19db5771aaa3a803124534b2e9dbf0ebe5ce1c7cee78baaa54c2e21da
Windows Installer
Windows No Installer (zip)
macOS - Universal
Linux - deb, AppImage or rpm
Windows intel x32 releases are marked -ia32-
ChangeLog:
Team members with the Member role now have read-only access. They can continue to view team resources and configuration, but can no longer create, update, delete, deploy, start, stop, or otherwise modify resources. Review your team roles before upgrading and promote users who still require write access.
State-changing API endpoints now require POST. Legacy GET requests return 405 Method Not Allowed. Update API clients and deploy webhooks that use these endpoints:
/enable/disable/deploy/servers/{uuid}/validate/applications/{uuid}/start/applications/{uuid}/restart/applications/{uuid}/stop/databases/{uuid}/start/databases/{uuid}/restart/databases/{uuid}/stop/services/{uuid}/start/services/{uuid}/restart/services/{uuid}/stop/services/{uuid}/applications/{app_uuid}/start/services/{uuid}/applications/{app_uuid}/restart/services/{uuid}/applications/{app_uuid}/stopforce=false deployment requests from incorrectly forcing cache-busting rebuilds. (#9909)POST for state-changing API operations such as start, stop, restart, deploy, enable, disable, and server validation; equivalent GET requests now return 405 Method Not Allowed.Related issue references:
Today, we take you on a preview journey to beautiful Rapid City, one of the cities you will find when driving through our upcoming South Dakota DLC for American Truck Simulator!
Rapid City is located in a picturesque landscape surrounded by some of South Dakota's most popular natural attractions. Heading west opens the way to the Black Hills National Forest and the iconic Mount Rushmore - the reason Rapid City is also known as the Gateway to the Black Hills. Traveling east along Interstate 90 takes you toward the rugged landscapes of Badlands National Park.
Beyond its surroundings, Rapid City has a rich heritage, as it celebrates its 150th anniversary this year. It has grown from a small settlement into a thriving regional hub while preserving the character that makes it unique. Today, tourism is one of the cornerstones of the local economy, with visitors drawn not only to the beauty of the region but also to the historic streets, distinctive buildings, and local landmarks.
Our asset and map designers have recreated plenty of these buildings and structures to bring Rapid City to life. Among them are two hotels, one of which is located in the heart of downtown, known for its appearance and history dating back to the 1920s. Driving further, you will also find another historic building that once served as the fire station and is now transformed into a local winery.
Some of the landmarks can be seen from a distance yet are instantly recognizable, such as the large white "SMD" letters displayed on the hillside above the city. Created by students as a tribute to the South Dakota Mines school and community, it has become one of the symbols of Rapid City. Another smaller landmark you may notice is the gateway entrance to Memorial Park, located in the center of the city along Rapid Creek.
You will also find many more landmarks as you explore Rapid City, from larger ones such as the city hall and administration buildings to smaller ones like a roadside windmill, a statue in the downtown, and others. Each of these elements has been recreated to help capture the atmosphere and identity of the real place.
And if you are visiting not only for sightseeing but also to take on a job, you will find plenty of depots to choose from. These include a cement works, a gas and chemical distribution facility, a sawmill, a warehouse, a home store, waste management, and even a custom-made grain elevator depot, all ready to load up your trailer.
We hope you are excited to discover Rapid City and everything else the Mount Rushmore State has to offer. If you do, make sure to add the South Dakota DLC to your Steam wishlist!
Also, remember to follow us on Twitter, Facebook, Instagram, Bluesky, and YouTube for all the latest news from not only this map expansion, but also other American Truck Simulator projects, or sign up for our newsletter to stay informed. Until next time, safe travels!
High Dynamic Range (HDR) video playback is now available on Windows - this feature needs HDR mode enabled for the display in Windows Settings - Display. Laptop displays that only offer "HDR video streaming" are not supported at this time. Some videos recorded on phones in certain orientations are currently not shown as HDR.
Containers let you keep separate parts of your online life (work, shopping, personal, banking) logged into different accounts in the same browser window, but keep your cookies and ad tracking isolated inside each container.
Share any open page with a QR code. Right-click a tab, select Share > Generate QR Code. Great for posters, invitations, banners, and other printed materials.
It is now possible to merge multiple PDFs by dragging a PDF into the PDF sidebar.
It is now possible to add images as new pages within PDFs using the Firefox PDF editor.
Quickly pick and copy a color from any page by typing "pick color", "color picker", or "eyedropper" in the address bar and selecting the "Pick a color" quick action.
Added support for Apple's system-wide full-screen keyboard command (Globe-F).
Firefox now verifies and displays Qualified Website Authentication Certificates (QWACs) in accordance with eIDAS regulations.
Added improved support for videos with overlays so users can more easily access video actions from context menus.
Firefox now highlights the location permission icon in red whenever a website has access to your location. The permission icon is also now visible on search results pages where it was previously hidden.
This feature is part of a progressive roll out.
Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.
Firefox Labs can now be opened quickly by typing "labs" or "experiment" in the address bar and selecting the Open Firefox Labs quick action.
Firefox now offers experimental support for the new JPEG XL image format, which generally provides better compression than WebP, JPEG, PNG, and GIF and is designed to supersede them. You can enable it from the Firefox Labs panel in Settings.
Various security fixes.
Extensions can no longer access local files by default. Users can grant or revoke this access via the new "Access local files on your computer" permission, separate from "Access your data for all websites".
Local Network Access restrictions are now enabled by default for all users. Firefox requires websites to request permission before connecting to devices on your local network or to apps and services on your device.
Outdated cookie settings have been removed from the Settings UI. Users still in that mode should switch to default behavior "Isolate cross-site cookies". More information
You can find information about policy updates and enterprise-specific bug fixes in the Firefox for Enterprise 153 Release Notes.
A new "Local Mode" setting in the options panel allows developers to load local directories via custom origins. This simplifies testing for APIs that do not function over standard file:// URLs, removing the need to run a local web server. Multiple directory mappings are supported.
Firefox now supports a limited subset of the non-standard ::-webkit-scrollbar pseudo-element to improve web compatibility:
width/height disable overlay scrollbars for the affected container.display: none on ::-webkit-scrollbar behaves like scrollbar-width: none, hiding the scrollbar.@supports selector(::-webkit-scrollbar) now evaluates to true.The vertical-align property was converted into a shorthand for baseline-source, alignment-baseline, and baseline-shift in Firefox 149. Now, alignment-baseline supports the new keywords alphabetic, ideographic, central, mathematical, and hanging, extending the variety of baselines to choose for alignment.
Implemented the new popover=hint spec, which removes a series of inconsistent and unexpected behaviors.
The newly added Error.stackTraceLimit property allows to set the maximal depth of the captured JavaScript error stack as a performance optimization.
Developers can now use the text import attribute to import text files using the module system.
The Picture In Picture API exposes a way for web developers to make use of user agent Picture-In-Picture functionality.
The Intl.LocaleInfo proposal adds the ability to query Locale information, such as week data (first day in a week, weekend start day, weekend end day), text direction and hour cycle used in the Locale.
The MediaCapabilities.decodingInfo() and MediaCapabilities.encodingInfo() methods now accept the "webrtc" configuration type. This allows a site to query whether a given audio or video configuration can be decoded or encoded for WebRTC and whether doing so will be smooth and/or powerEfficient.
HTTP Compression Dictionaries is enabled via rollout in 153, it will be made permanent in a future release. This can greatly reduce network traffic size for sites that use it.
This feature is part of a progressive roll out.
Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.
With the release of Firefox 153, we are pleased to welcome the developers who contributed their first code change to Firefox in this release, 15 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:
Docker images have been built and pushed:
Docker Hub:
alexta69/metube:latestalexta69/metube:2026.07.21GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.07.21
