Posts by Cj24

Quote from Hobe

But somehow it needs to work, because in my exhample multiple different cars use the "vehicles_muscle_n_w_interior.ytd". Otherwise creating shared textures doesn´t make any sense.

You can assign multiple cars to the vehicles_muscle_n_w_interior texture, you just cannot assign multiple cars to the polshare texture and assign this polshare texture to multiple interiors as well. Multiple children can have the same parent, but a child can only have one parent.

Also, regarding the ytd size: It is not a useful metric for memory usage, as ytds are compressed similarly to zip archives to decrease disc space, the size of the dds textures themselves is what matters. Because of the ytd compression, it is possible that smaller textures with more varying content can result in a higher ytd size than larger but more repetitive textures, even though the smaller textures require less memory.

As each child can only have a single parent, I don't see how it would be possible to include different interior textures for different cars. Depending on how many shared interior texture each car uses and how many textures your polshare texture includes, it may still be advantageous to use the polshare while simply including the interior textures directly in the vehicles' ytd.

As far as I know, that's not possible, considering the polshare texture can only have a single interior texture as a parent.

It is not possible to overwrite the relationships for existing textures, in this case vehicles_muscle_n_w_interior. If you instead assign polshare to the vehicle and the interior textures polshare, it should work:

  <txdRelationships>
    <Item>
      <parent>polshare</parent>
      <child>lspd6</child>
    </Item>
    <Item>
      <parent>vehicles_muscle_n_w_interior</parent>
      <child>polshare</child>
    </Item>
  </txdRelationships>

I have recently started working on an LAPD inspired 2008 CVPI:

The first trailer has been released early:

Sounds like an improper hierarchy with either too many objects or with object ID conflicts caused by unrecognized object names. I recommend taking a look at the Hierarchy section in our ZModeler guide: https://www.modding-forum.com/guide/12-zmodeler-3-and-vehicle-mods/#b53384c6-hierachy

Rockstar Games has announced that the trailer will be released next Tuesday (5th December) at 9 AM ET: https://www.rockstargames.com/

We have added a SirenSetting Calculator with the following tools:

• Convert delta and start values from degrees to radians and vice versa
• Convert sequencers from binary to decimal and vice versa
• Calculate the optimal speed values for wigwags, halogen lights and strobe lights
• Calculate the optimal start values for flashing and steady coronas while syncToBpm is set to false

Here's a short video of some of the new DLSv2 features on the BCSO CVPI:

I have finished all the remaining equipment on the Detective CVPI:

Further bug fixes and small improvements are still necessary for all of the CVPIs, so please don't expect a public release in the very near future. These vehicles will all support DLS v2, which is currently in development. Since DLS v2 uses different configuration files and as it could still take some time until it's ready, the first release of the CVPIs may not include DLS vehicle configuration files yet.

Here are a few pictures of the Detective CVPI and the Code 3 Warrior. The car has a few different light options, the grill lights are optional, the headlight corner strobes can be changed from white to red and blue and the Warrior can either be steady red or split blue and steady red.

Based on the feedback I've gotten here and on Discord, I'll make the Havis console that's mounted underneath the dash with the same radio and the Mastercom controller I've used for the other cars.

In addition to the marked and slicktop CVPIs, I've also started working on a 2008 Street Appearance Package CVPI, intended as a detective or administrative car. It will have fewer lights, most likely a similar hideaway/grill light setup like the other CVPIs with a steady red or split red/blue Code 3 Warrior in the front and a short amber/blue Code 3 Wingman in the back.

I'm unsure about the interior equipment and I'm hoping for some feedback:

• Option 1: Use the standard CVPI seats rather than the civilian seat option and use the same console setup as for the other CVPIs, except without the ArrowStik controller.
• Option 2: Remove the default radio from the dash and mount a Motorola radio and a small light and siren controller such as the Code 3 Undercover Siren 3050 instead.
• Option 3: Model a console that's placed underneath the dash with the Motorola radio and a light/siren controller.
• Option 4: Like option 3, except that the default A/C and radio are moved from the dash down to the console, making it possible to mount the light/siren controller and radio in the dash instead.

I have added the mirror lights and a short version of the Wingman to the marked CVPI. These lights are set up as optional extras, whether the car spawns with or without either of them by default can be set in the vehicles.meta.

I have finished the LED X mirror lights:

A short video of the full light setup of the slicktop and unmarked cars:

Rockstar Games has announced that the first trailer for GTA 6 will be released in December: https://www.rockstargames.com/newswire/artic…-rockstar-games

Update: The first trailer has been released:

I'm finally back to modding and have managed to finish the Code 3 Supervisor and Wingman interior lightbars for the CVPI:

Quote from Cj24

We have added new user profile fields for Discord servers, Paypal Donation links and Patreon pages. These links and the links to your website and YouTube channel will be shown next to your files in our filebase and in your showroom threads.

In addition to the existing fields, we have added new fields for buymeacoffee.com and Ko-fi.

By using the move tool with the "Move Axes only" option enabled or by centering the axis to the object.

Those are the coronas ELS renders to make sure lights are still visible at higher distances. They're automatically placed at the axis of the extra, the color is chosen based on the color set for the extra in the VCF. You should move your axes to the position of the light itself. Note that even with properly placed axes, ELS coronas may be visible through mesh and pointing in the wrong direction, which is simply yet another shortcoming of ELS.