Topics created by BHuff04

Aside from memory and resource woes, generally it's better to mod on the latest game version, since mods tend to use new content from recent DLC, like engine sounds etc.

For scripting, it should not matter which version you are running, but the latest game version usually has the best support, though exceptions apply.

Exceptions:

When the game just updated, ScriptHookV will need to be updated. In these cases it's better to wait for ScriptHookV to update before updating your game/letting it update. Some script mods use natives that Rockstar removed from the game. Usually these are updated fairly quickly, but others are never updated. Read the comments to prevent script crashes. Some scripts (most of mine, ScriptHookVDotNet) hard(ish)-code some structures to read or change values not accessible via natives. This can break fairly quickly after a fresh update. These scripts are usually also updated quickly after the author gets their hands on an updated ScriptHookV, so you might need to wait a while longer. As usual, try bugging the author.

@BHuff04
You are referring to replacing the model ('.yft') of the car, not just the textures. Well, you are replacing both but it's a little confusing to refer to the whole car as a texture just so you know (that's probably why you haven't had a response to this yet).
Use Ctrl+F3 in OpenIV to search for the car ('adder.yft' etc. Search 'mods folder only' in dropdown so you don't see any of the game folder cars) & then replace the adder you find in the highest numbered 'patchday##ng' folder structure. Alternatively, place the car's '.yft' & '.ytd' in the 'vehicles.rpf' of the highest 'patchday##ng' you have installed (even if it is not there already).
Note: Be aware that if Rockstar update the car in question in a higher patchday your car will revert to default. You then just move your files & replace the new car with your custom replace to get it back.