Split 16Mb car textures problem

FiveM Resource Development & Modding Discussion
1

I wanted this car on my server : https://www.gta5-mods.com/vehicles/mazda-rx-7-super-tuning-add-on
I realized that YTD file is 28Mb and I need to split textures by : https://forum.cfx.re/t/how-to-split-vehicle-ytd-files-to-avoid-16mb-stream-limit-no-texture-compression/142734
I didn’t know how because it has in vehicles.meta under relationships this:

  </InitDatas>
  <txdRelationships>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_generic</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_interior</child>
    </Item>

I dont know how to deal with vehshare… I tried this but it does not work

  <txdRelationships>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_generic</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_interior</child>
    </Item>
    <Item>
      <parent>mrx71</parent>
      <child>mrx7</child>
    </Item>
      <parent>mrx72</parent>
      <child>mrx71</child>
    </Item>
      <parent>vehicles_race_generic</parent>
      <child>mrx72</child>
    </Item>

Does anybody know how to help me please?

Thanks in advance

2

:thinking:

      <child>mrx7</child>
    </Item>
      <parent>mrx72</parent>

This part is incorrect; you have forgotten to begin the succeeding texture relationship by inserting <Item> after the preceding texture relationship (or before the succeding one), ending with </Item>, and it should look like this instead.

      <child>mrx7</child>
    </Item>
    <Item>
      <parent>mrx72</parent>

Typically you want to hierarchically organize the texture relationships (to avoid confusion), and so your aforementioned example should actually look like the following one.

The reason why I’m mentioning this is because you should also sequentially name your split texture dictionaries in order to avoid confusion, and so the texture dictionary mrx7 for example could be expanded into—

• mrx72 and mrx73 if there are two additional parts, and
• mrx72, mrx73 and mrx74 if there are three additional parts, and so forth.

You don’t even have to use these particular names or the ones that were supplied to you; you should be able to use whichever names for the texture dictionary files (and relationships) that you choose, and so mrx7 for example can be—

• m1 or
• 1m, or whatever you’d like to choose for the filename.

A two-part texture dictionary relationship with mrx7 would look like this.

    <Item>
      <parent>vehicles_(vehicle)_interior</parent>
      <child>mrx72</child>
    </Item>
    <Item>
      <parent>mrx72</parent>
      <child>mrx7</child>
    </Item>

In this case, mrx7 is the child (the first half of the .ytd file) where it is parented to the parent itself (the second half of the .ytd file); mrx72.

You also wouldn’t modify the vehshare_, _generic and/or _interior texture relationships if they exist already, and you should only concern yourself with the actual structuring or hierarchy of the split texture dictionary relationships themselves.

If you’d like to have any additional assistance with this particular matter, please feel free to respond to this post.

3

Hello, thank your very much for the reply.
I firstly tried this:

  <txdRelationships>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_generic</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_interior</child>
    </Item>
    <Item>
      <parent>mrx71</parent>
      <child>mrx7</child>
    </Item>
    </Item>
      <parent>mrx72</parent>
      <child>mrx71</child>
    </Item>
    </Item>
      <parent>vehicles_race_generic</parent>
      <child>mrx72</child>
    </Item>

I did not even spawn, so i tried this:

  <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_generic</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_interior</child>
    </Item>
   <Item>
      <parent>vehicles_(vehicle)_interior</parent>
      <child>mrx73</child>
    </Item>
    <Item>
      <parent>mrx73</parent>
      <child>mrx72</child>
    </Item>

I also modified and splitted the mrx7 to mrx72 ,3 and 4.
It spawned but it had some bad textures… no lights, windows etc. bugged textures

I would be really glad for your reply again. I would love to have this car on my server.

Thank you very much in advance.

4

Please pardon the delay in my response.

I revised my previous post.

I’ve also downloaded the add-on you’d provided in your initial post and realized that we have apparently misinterpreted the actual name of the texture dictionary file, being mrx7.ytd.

However, after downloading the actual add-on itself, I took the liberty of manually splitting the existing texture dictionary file, mrx7.ytd, into three respective files—

mrx7.ytd
mrx72.ytd
mrx73.ytd

Shown in the following image are the files themselves.

image
image960×520 44.7 KB

And those are the files that would be inserted into the \stream\ folder.

So, since the aforementioned methods you’d mentioned have not actually been successful (and had been written on the basis of my misinterpretation of the actual texture dictionary filename itself), you should attempt this particular method of splitting the file and managing the texture relationships in the vehicles.meta file instead.

And, so, in attribution to the aforementioned files that have been split, your texture relationships in the vehicles.meta file should appear as such.

  <txdRelationships>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_generic</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_race_interior</child>
    </Item>
    <Item>
	  	<parent>vehicles_race_generic</parent>
      <child>mrx73</child>
    </Item>
    <Item>
	  	<parent>mrx73</parent>
      <child>mrx72</child>
    </Item>
    <Item>
	  	<parent>mrx72</parent>
      <child>mrx7</child>
    </Item>
  </txdRelationships>
5

Thank your very much for your help :slight_smile:

You are a GOD.

Thank you.

1 Like