Posts by Cj24

The game will always force 8 characters, the only way to change the format is to use external scripts such as this one: https://www.gta5-mods.com/scripts/license-plate-changer

The color of license plates is set in the carcols for each license plate by the FontColor value. It's a hex code starting with 0x and the opacity, which should be fully opaque (FF) for license plate text.

In the future, as per our forum guidelines, please make sure to choose comprehensible titles for your issues.

Your file list are the default DLCs by the game, this is absolutely correct and intended. Many mod authors set up their addon vehicles to use a DLC, in that case it'll be enough to copy the DLC and its folder to the dlcpacks folder and add its name to the dlclist.xml. Note that the name of the DLC folder has to match the name set in the DLC, which is usually provided by the mod author.

You just need to assign these lights to the vehicle_lightsemissive shader without any light type ID set. They will automatically turn on whenever the engine is on.

According to the error message, the .yft file is too big. It is not affected by textures. However, considering the reported file size is absurdly high, there is likely a different reason, such as a corrupted file for example.

You have too many hierarchy elements, the limit is 128.

Rotating the dummy will not work.

As I said before, it's an ELS bug. If the dummy has a positive Z-axis position, the light will point to the rear. This cannot be changed, you can just move the dummy somewhere behind the axis as Sova said.

As you're using an extra, I'm assuming you're talking about ELS? If so, it's an ELS bug that happens whenever the dummy is positioned in the front of a car (negative Z-axis) and cannot be avoided.

When copying emissives from other lights, it'll be necessary to set the ID to 0 to make sure it's no longer affected by the original light. If by flickering you mean z-fighting, make sure that your new emissive is slightly in front of the original one.

Other than that, there shouldn't be any differences compared to any other lights.

As far as I know, those scripts are typically set up to switch between modkits for each digit. I'm unable to help with that, as I have no experience using modkits at all, but you may be able to find other tutorials on how to create those.

That could be the model, but it could also be caused by an incorrect sirensetting in the carvariations or carcols. I'd recommend making sure the car works without crashing before continuing work on the lights. If the metas aren't right, it's likely that the lights aren't going to work anyway.

Crashes are rarely caused by the model or texture files, but usually rather by the metas.

The hierarchy doesn't appear to have any issues. The only thing to consider is that both the standard and the hi.yft files have the exact same file size, which indicates an importer export of the LODs, but as long as at least an L0 and an L1 are present, this shouldn't cause any crashes.

To clarify for anybody who still has this question: Vice City mods are not compatible with Vice City Stories.

The glow is caused by coronas, you'll have to create a new light block with an unused ID in a carcols.meta and set to the taillightCorona size and intensity to 0 and assign the ID in the carvariations.meta.

Quote from Keith

I hate coronas, As I only use ELS. I change my corona texture itself to eliminate them altogether.

mods\update\update.rpf\x64\textures

Change the corona texture for a black one

That isn't advisable, the game absolutely needs coronas for far distances, otherwise lights will will simply disappear. This has nothing do with ELS either.

I'm guessing you mean the coronas, rather than the light meshes? They are set in the lightsettings in the carcols, you'll likely have to create a new lightsetting with your intended setting and then assign that setting in the carvariations.

I'm currently on a modding hiatus, so there won't be any news in the near and possibly even the far future. I was planning to update the marked CVPI to support 32 sirens (requiring SirenSetting Limit Adjuster) and use the additional sirens to add (optional) mirror lights and lights on the rear deck. This has been on hold due to my hiatus, though all the existing lights have already been converted to separate sirens for SSLA and the new pattern showcased in the video above.

This 32 siren version of the marked CVPI is in a state that's likely ready for release, but won't be officially released until the additional lights have been added. However, as I have no idea when I find the time and motivation to get back to it, I've decided to release it as a prerelease version. It has the updated patterns and uses more than 20 sirens, therefore requiring SSLA for all lights to work properly, and it is otherwise identical to the last released version.

With the steadily growing number of development resources posted on Modding Forum, we have decided to make some changes to the labels to allow easier filtering:

• The "Emergency Vehicle Equipment" label has been replaced with many new labels for specific equipment types.
• We have added vehicle labels for the most common vehicles.
• From now on, accessories to specific parts (such as mounts) will be labeled like the original part, for example an emergency light mount will be added to the "Emergency Lights" label.

Labels of existing threads have been updated. If you notice any threads with incorrect or missing labels, feel free to report them.

It looks very well made, but I'm not sure I'd agree with calling it optimized. For a part of this size, you could easily get away with a fraction of the poly count, a normal map for the slot, and a much lower texture resolution.

The guidelines for all showroom categories, including for development resources, have been updated to include the following rule:

• Showroom threads may not be used for advertising. Links to websites, Discord servers or YouTube channels are only permitted in the respective profile fields, which are automatically shown next to the first post of the thread.

Advertising commercial Discord servers in showroom threads has always been against our terms of use. However, the distinction between commercial and non-commercial can be difficult, which is why Discord server links have been tolerated in the past. To prevent having to make this distinction and to prevent threads from cluttering up with advertisements and unrelated links, we have decided to add this new rule.

Instead, we encourage authors to add these links in the respective profile fields, which have been exempt from the commercial advertising rule ever since they were introduced. They will automatically be displayed in the profile and next to showroom threads or files in the filebase, which we believe to be a fair compromise.