Virtual / Physical Memory for Assets

[Apostol]

Hey Guys,

New server builds have introduced some nice checks, but I still don’t know how much virtual/physical memory is considered OK for assets. Anyone has any idea?

Asset goldwing/goldwing.yft uses 16.3 MiB of virtual memory. - is this informational?

a8lw12.ytd uses 62.0 MiB of physical memory. Oversized assets can and WILL lead to streaming issues (models not loading/rendering, commonly known as ‘texture loss’, ‘city bug’ or ‘streaming isn’t great’) - is this wrong and if yes, what values (I guess in MiBs) are considered normal?

Thanks a lot!!!

[nta]

Around what an equivalent asset type R* made uses in “strmem” on the client.

[Apostol]

Thank you very much, sir.

[TigoDEV]

To fix your Oversized assets you can follow this guide (bring any asset under 16MiB:

[How-to] Optimize texture size | Fixing oversized assets | Bring any texture dictionary under 16 MB physical memory

This is a tutorial on how to get textures under 16MB uncompressed without too much effort. What do you need? OpenIV | download XnResize | download 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: [physical memory oversized] 166 MB physical memory is more than 3 times as it is supposed to be. How to make a texture dictionary under 16MB? 1. Open .ytd file in OpenIV [OpenIV Texture Dictiona…

[naoestu]

@TigoDEV Same error is happening with less than 48mb used by physical memory,
so your tutorial does not solve the issue.

“Asset p1/p1.ytd uses 34.0 MiB of physical memory”

Maybe this is the real solution?
“the texture size should be no larger than 1024x1024”

[TigoDEV]

@naoestu What my message said is fixing Oversized assets

Asset p1/p1.ytd uses 34.0 MiB of physical memory

If you want to get the message gone, you should make the asset under 16.00 MiB of physical memory.

Sze	Description	Message Color
< 16.00 MiB	Best for FiveM and won’t show you a message	None
< 32.00 MiB	Your almost there, try to get it under 16.00 MiB	Blue
< 48.00 MiB	Your asset is big, but isn’t responable for your texture losses	Yellow
> 64.00 MiB	This asset isn’t fivem optimized and should be fixed or replaced	Red

If you don’t want to get a message, you should bring your assets under 16MB

In my tutorial I used a 166.00 MiB physical memory vehicle and after “fixing” it was under 11.00 MiB physical memory and those messages were then gone.

[naoestu]

yeah you’re right buddy, i misunderstood.
I already solved the “physical memory” message with your tutorial
The current problem is different:
"Could not make hard link for /home/testserver/FXServer/server-data/resources//[cars]/p1/stream//p1.yft <-> /home/testserver/FXServer/server-data/cache/files/p1/stream_cache/z21c224f3b799a6881e285b24095c9c7762fd8091.
Asset p1/p1_hi.yft uses 23.8 MiB of virtual memory.
Asset p1/p1_hi.yft uses 23.8 MiB of virtual memory.

do you know how solve it?

[SonOfKoKoBo]

Hey, I know this is a bit late but I hope you can help me.
I’m having trouble with it.
When I started the server I checked the YTD files and they’re all was below 16Mb but the console shows different.
I used splitting but that has nothing to do about it because I succeeded in getting them below 16Mb.
I’ve posted about it and It would be really awesome if you could help me there.

Files Splitting Problem. Console says wrong size values

I Got European Roads installed and I tried fixing the 16Mb stream limit by splitting the big files. And I’ve done it after long hours, but still, when I ran the server the big Red stream limit warning in the console disappeared but the yellow ones came out. I was confused because I checked the YTD files and they’re all was below 16Mb but the console shows different. For example, I checked a YTD file and it was 8Mb but when I looked at the console it says19MiB(20Mb) The file: [image] The c…