Not difficult at all but is time consuming as now i have all three Skin Pack Addons to update again!
Skin pack add-ons shouldn't be affected to the point that they no long work, the cars in the packs should have their own veh.ini files.
The update has added a new line to the veh, or changed it to read
DefaultLivery="R8LMS_26.dds"
MaterialOverride="R8LMS_BaseMat.json" from
MaterialOverride="R8LMS.json" adding BaseMat to the line. It makes no sens at all why it was necessary to change the veh file names again. Really think it was done just to piss people off !!
NEW FLASH! Worked.
Ace King, You could go through and update all the veh files with the new line but as long as their still working I'd just leave it as is for now. Considering a lot off the cars in those packs haven't got a json & regions map.
The reason for the custom virtual ride skins are no longer working is the cars veh file names have changed yet again so all we need to do is create a VR from one off the new named cars and add that name to the rcd text file and they work again. Simple enough in our own installs but a pain if you've been continuing to share your work.
I had stopped adding cars for download when this first started a few months back. Had been updating all the older cars with the new json.ini and the regions_map DDS but haven't yet started to update them for download. Not planing to until this is all sorted out.
[Edit] Just a heads up. Shared car liveries are usually or should be set up in Mas. files. When a car is in a Mas. it still doesn't work with AI. Works as a driven car. But as per the correct way to share your skins in a Mas. If the windows are also in that Mas. they still don't work. Will if the windows DDS is outside the Mas as a open file. I'd suspect the driver and gloves would be the same as the windows.
Are you confused yet ???? hahaha..........