FiveM Modding Tutorial
This is a tutorial on how to get textures under 16MB uncompressed without too much effort.
What do you need?
In this tutorial I use the
hevo, this is a GTA5-mods vehicle (GTA5-mods).
When I start the vehicle I get the following message in the console:
166 MB physical memory is more than 10 times as it is supposed to be.
How to make a texture dictionary under 16MB?
.ytd file in OpenIV
2. Export all textures as
.dds | Click
Export all textures bottom left of OpenIV
I will export them in a folder inside my vehicle called textures
3. Wait until all textures are exported | Bottom left number of items matches OpenIV number of textures from step 1.
4. Open XnResize
5. Drag all
dds files exported by OpenIV and drop them in XnResize
You should now see alle exported
dds files in XnResize
6. Configure XnResize
- Set the
Widthto 50% and
Heightto 50% (will resize all textures to 50% of there original size)
Screenshot of settings:
Folderto a destination your prefer (I created a second folder called
texturesin vehicle resource)
DDS - Direct Draw Surface
Screenshot of settings:
Convert in XnResize
After a couple of seconds XnResize is finsihed and you will see a small report like:
8. Delete now the existing texture dictionary we are fixing (hevo.ytd)
9. Create a new texture dictionary in OpenIV with the same name as we deleted in step 8
Remember: In order to create a new texture dictionary you need to have Edit mode in OpenIV enabled
Give it the same name as the texture dictionary we deleted
10. Open our new Texture dictionary and press the Import button
11. Select all
dds files from the folder you have given in step 6.2 (set
Folder) and press
The following files are not imported
dds files aren’t importable after resizing in XnResize, we will use then the original files exported in step 2, press
ok and import those original files
13. Save our new Texture dictionary by pressing
Now we have reduce the size of our Texture Dictionary
|Description||(original) Texture Dictionary||(resized) Texture Dictionary||Times Better|
|Compressed Size||11.8 MB||1.23 MB||9.6x|
|Uncompressed Size||164 MB||11 MB||14.9x|
|Virtual Memory||0.05 MiB||0.05 MiB||–|
|Physical Memory||166.00 MiB||10.69 MiB||15.5x|
Our resized texture dictionary is almost 10% of its original compressed size and 6.5% in game’s Physical Memory, overall is our texture dictionary 10 times better
14. Final results (screenshots)
- My textures are glitching:
It is possible that textures will glitch when they are resized to 50%. Do not resize them but leave it in the original size (100% instead of 50%). If these textures still glitch, replace them with the original .dds file.
- Quality is disappointing:
You can always replace a texture back with the original .dds file, try to resize as many files as possible using XnResize. If you have a car with e.g. liveries and the quality is disappointing, put the original liveries in XnResize and don’t adjust the size (keep 100%). If the quality is still disappointing, replace it with the original .dds file (NOTE: can increase the file size again).
Keep in mind that this is a way to reduce textures more easily and optimize your server. Textures can lose quality or change their appearance. First try to convert the file again but don’t change the size, If it remain bad, then replace it with the original file.
ThymonA // Tigo
Also read my comments below:
Nov 8, 2020 3:47 pm
Nov 10, 2020 10:30 am
Original source: https://forum.cfx.re/t/how-to-optimize-texture-size-fixing-oversized-assets-bring-any-texture-dictionary-under-16-mb-physical-memory/1764640