Log in to reply
 

combining dlc mods



  • hi guys
    when am combining addons to a folder i put the mod files into the vehicle mods but they dont work


  • MODERATOR



  • put tuning rpf into dlc pack folder where i combine all my addons. cars all work but the tuning parts for most cars dont.
    mods,update,x64,dlcpacks,myfile,dlc.rpf vehiclemods

    everything is uptodate



  • @conjames23
    Try one of the pre-made add-on folder mods, that way your 'content.xml' file & folder structure is already setup correctly & all you have to do is chuck the files into the correct locations defined in the mod instructions.
    Should only be a 5 min job :thumbsup:





  • @a63nt-5m1th
    yeah i have the realcars one from fyto . put them in vehicle mods but some dont work. ill tryt the other one



  • @conjames23
    Engine Upgrades Working?:
    If you are unable to apply engine tuning to the cars (check this), you have a ModKitID conflict & that is why your tuning is not working.
    See more info & the basics of fixing a modlit ID conflict here if that is the case.

    Engine Upgrades Good. Just Visual Tuning/Upgrades Broken:
    Remember to edit 'content.xml' manually for each & every 'vehicle-name-here_mods.rpf' ('16challenger_mods.rpf' etc) you add to the 'vehiclemods' folder :thumbsup:
    You have to do that with F7YO's Multiple Base DLC Packs For Combining DLC'S & it is also required if you are now using Reyser's Add-On/Replace Base Folder [Vehicles | Weapons | Textures] v8.0 (All-In-One) or visual tuning will not work.

    From Reyser's 'content.xml':

    
    	<!-- Use these lines below for every "vehicle_mods.rpf"
    	<Item>
          <filename>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/VEHICLE_mods.rpf</filename>
          <fileType>RPF_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	-->
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/handling.meta</Item>
            <Item>dlc_FOLDERNAME:/data/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carcols.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carvariations.meta</Item>
            <Item>dlc_FOLDERNAME:/data/dlctext.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/anim/clip_sets/clip_sets.xml</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehicles.rpf</Item>
            <!-- Use this line below for every "vehicle_mods.rpf"
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/VEHICLE_mods.rpf</Item>
            -->
    	  </filesToEnable>
    	  <txdToLoad />
    	  <txdToUnload />
    	  <residentResources />
    	  <unregisterResources />
    	</Item>
    

    So the 'content.xml', once edited, would end up looking somewhat like this for multiple cars:

    Example:

        <Item>
          <filename>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/16challenger_mods.rpf</filename>
          <fileType>RPF_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
        <Item>
          <filename>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/06saleen_mods.rpf</filename>
          <fileType>RPF_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
        <Item>
          <filename>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/66fastback_mods.rpf</filename>
          <fileType>RPF_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/handling.meta</Item>
            <Item>dlc_FOLDERNAME:/data/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carcols.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carvariations.meta</Item>
            <Item>dlc_FOLDERNAME:/data/dlctext.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/anim/clip_sets/clip_sets.xml</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehicles.rpf</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/16challenger_mods.rpf</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/06saleen_mods.rpf</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/66fastback_mods.rpf</Item>
    	  </filesToEnable>
    	  <txdToLoad />
    	  <txdToUnload />
    	  <residentResources />
    	  <unregisterResources />
    	</Item>
    


  • @QBit07 thanks for that see if a vehicle has handling.meta, vehicles.meta, carcols.meta, carvarations.meta, dlctext.meta, vehiclelayouts.meta ? do you add all these or just handling vmeta carcols carvariations . meta



  • @conjames23
    Generally, you take the block/s of data for a vehicle from within their respective '.meta' files & add them into the files, 'handling.meta', 'vehicles.meta', 'carcols.meta' & 'carvarations.meta' that already exist within your combined add-on dlc.
    'dlctext.meta' doesn't needed to be edited as this relates to the add-on dlc & not the vehicles it contains, so it already has all the info it will ever need.
    'vehiclelayouts.meta' contains a lot of different sections & is tricky to combine into one file, so it's probably best & easiest to rename the files to their respective vehicle names & add entries for them in 'content.xml':

    Example (confirmed to work):

    16challenger_vehiclelayouts.meta
    06saleen_vehiclelayouts.meta
    66fastback_vehiclelayouts.meta
    

    & then add new sections to 'content.xml' pointing to the new separate layout files:
    Example:

      <dataFiles>
      ...~
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/16challenger_vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/06saleen_vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/66fastback_vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	  ...~
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/handling.meta</Item>
            <Item>dlc_FOLDERNAME:/data/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carcols.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carvariations.meta</Item>
            <Item>dlc_FOLDERNAME:/data/dlctext.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/16challenger_vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/06saleen_vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/66fastback_vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/anim/clip_sets/clip_sets.xml</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehicles.rpf</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/VEHICLE_mods.rpf</Item>
            </filesToEnable>
    

    OR (perhaps this might work too, but unconfirmed):

      <dataFiles>
      ...~
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/16challenger/vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/06saleen/vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/ai/66fastback/vehiclelayouts.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	  ...~
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/handling.meta</Item>
            <Item>dlc_FOLDERNAME:/data/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carcols.meta</Item>
            <Item>dlc_FOLDERNAME:/data/carvariations.meta</Item>
            <Item>dlc_FOLDERNAME:/data/dlctext.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/16challenger/vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/06saleen/vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/ai/66fastback/vehiclelayouts.meta</Item>
            <Item>dlc_FOLDERNAME:/data/anim/clip_sets/clip_sets.xml</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehicles.rpf</Item>
            <Item>dlc_FOLDERNAME:/%PLATFORM%/vehiclemods/VEHICLE_mods.rpf</Item>
            </filesToEnable>
    

    Will this 'content.xml' approach work for all '.meta' files?:
    It may be possible to use this 'content.xml' route with all '.meta' files, but I haven't tried it, so can't confirm it will work for all of them. There are distinct advantages if it does though.

    Example (only 'vehicles.meta' used in this example, but should work for all '.meta':

      <dataFiles>
      ...~
    	<Item>
          <filename>dlc_FOLDERNAME:/data/16challenger_vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/06saleen_vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/66fastback_vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	  ...~
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/16challenger_vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/06saleen_vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/66fastback_vehicles.meta</Item>
            </filesToEnable>
    

    OR

      <dataFiles>
      ...~
    	<Item>
          <filename>dlc_FOLDERNAME:/data/16challenger/vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/06saleen/vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	<Item>
          <filename>dlc_FOLDERNAME:/data/66fastback/vehicles.meta</filename>
          <fileType>VEHICLE_LAYOUTS_FILE</fileType>
          <locked value="true"/>
    	  <disabled value="true"/>
    	  <persistent value="true"/>
    	  <overlay value="true"/>
        </Item>
    	  ...~
      </dataFiles>
      <contentChangeSets>
    	<Item>
    	  <changeSetName>FOLDERNAME_AUTOGEN</changeSetName>
    	  <filesToDisable />
    	  <filesToEnable>
            <Item>dlc_FOLDERNAME:/data/16challenger/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/06saleen/vehicles.meta</Item>
            <Item>dlc_FOLDERNAME:/data/66fastback/vehicles.meta</Item>
            </filesToEnable>
    

    Note: The two 'content.xml' approaches above are untested for files other than 'vehiclelayouts.meta' (only very top example is confirmed to work for 'vehiclelayouts.meta'), so no guarantees, but should be easy enough to test & I can't see why they wouldn't work.
    The big advantage, if they do, is that adding new vehicles to the dlc in future will be much quicker & easier with less chance of a silly mistake than copying & pasting all info into one set of '.meta' files.

    If you try the 'content.xml' route for other files as well, let me know how you get on, I've been meaning to get around to testing it for the noted advantages.
    Best of luck, any issues, give me a shout :thumbsup:


Log in to reply
 

Looks like your connection to GTA5-Mods.com Forums was lost, please wait while we try to reconnect.