FiveM Sollumz 2.8.1 Fixes Asset Exports for Servers

Asset developers building custom maps, props, and vehicles for GTA V received a series of stability fixes on 8 February 2026. The release of fivem sollumz 2.8.1 addresses asset corruption, Blender import errors, and export failures across multiple file formats used by custom communities on the FiveM Server List.

Published on GitHub by the Sollumz project, version v2.8.1 serves as a maintenance release following larger overhauls to mapping workflows. For community managers who previously tracked the FiveM Sollumz update rebuilding YMAP tooling, this patch focuses on eliminating exporter crashes and texture pipeline hitches in Blender.

Texture Pipeline and Asset Management

Texture handling gains workflow options that streamline how artists store textures alongside geometry.

Packed Textures on Import and Export

Creators can now export assets with packed textures directly, alongside support for pack and extract modes during texture imports. This workflow change prevents texture paths from breaking when moving files between directories. In addition, Sollumz no longer copies embedded textures during native export tasks, and an issue causing errors when writing external textures into the target export directory has been corrected.

Asset Library Integration and Shaders

For drawable dictionaries (ydd), the update introduces support for 'Import to Asset Library'. Shader conversions also retain their embedded status accurately on ydr drawables, while an issue preventing the proper creation of the spec_decal shader has been resolved.

Fixes for Vehicles, Cloth, and Map Definitions

The update resolves several crashes that interrupted model conversions across varied GTA asset categories.

Vehicle Glass and Fragment Cloth

Vehicle modders working on yft files previously encountered shattermap failures whenever the blue channel of vehicle glass was entirely black. That check now processes without throwing errors. In addition, fragment cloth plane bounds import and export issues across collision files (ybn) have been corrected, alongside a fix for a typo in discard_formats that previously interrupted vehicle exports.

Entity Sets and Archetype Extensions

In map archetypes (ytyp), artists can now toggle the visibility of entity sets within the Blender interface. The release also repairs fatal export crashes triggered when saving ytyp definitions that incorporate either Spawn Point or Explosion extensions.

Performance Gains and Exporter Optimisations

Processing speeds during asset compilation have seen targeted improvements across complex models. Drawable exports combining a single LOD with numerous models are now optimised, accompanied by performance boosts in the vertex builder export and mesh builder import routines.

To help modders monitor these changes, the command line interface introduces sz_perf_ie, allowing developers to measure exact import and export execution times. Under the hood, the release upgrades core project dependencies to szio 1.1.0 and pymateria 0.1.1, while resolving underlying memory allocation crashes.

Impact on FiveM Server Owners

The changes in v2.8.1 occur entirely on the creator side inside Blender and do not alter server runtime binaries. Server administrators using tools such as FiveM txAdmin 8.1.0 do not need to apply server configuration adjustments or restart hosts.

Existing streamed assets do not need to be recompiled unless creators previously encountered the specific bugs addressed in this release, such as missing spec_decal shaders, duplicated material slots, or broken vehicle glass shattermaps. If modified assets are updated by model developers, administrators simply replace the corresponding resource files in their server data folders and restart that individual resource.

What Players Will Notice

Because this is an external authoring patch, players will not experience immediate mechanical changes upon joining a server. However, servers streaming newly exported vehicles and map props should exhibit fewer visual anomalies. Vehicles authored with fixed shattermaps will shatter their glass correctly without graphical artefacts, and complex MLOs exported under the corrected ytyp rules will properly trigger intended explosion and spawn behaviours without dropping props.