- 514
- United Kingdom
No problem - happy to help!
Co-sign, it's one of my biggest pet peeves. 8K skins, even on a 90 class GPU, is totally unnecessary and an explosion in file size for materially zero visual improvement in Photo/CM Showroom mode and a pure degradation when racing due to lower frames/LOD management. All for detail you couldn't even notice if you paused the game, hit F7 for free cam and zoomed right up to another car.Don't usually do things like this, but I just spent the better part of the last two days wasting my time re-sizing and re-saving car skins and i'm a bit frustrated.
Do car skin makers understand the concept of files sizes and GPU memory?
I noticed in MSI Afterburner that I was pushing past my 8gb of GPU memory and thought it was something I did when modding a track. Turns out it was the car skins and I wasn't even using that big of a field. Only about 25-30 cars. I started to look through the skins folders and noticed some really huge file sizes for the textures used in most of the skins. Some of it was due to larger than needed texture resolutions for silly things like chasis AO's, tyre blur textures, NM files, etc. Most of it was due to choosing the wrong dds format when saving. There were files saved in a dds format that made the file size 4 times bigger than it should be. Thankfully after a massive amount of time spent, i'm back down to 5-6gb of GPU memory for a field of 30-32 cars.
OK, rant over.....
Likewise, I almost always resize car mod skins.Don't usually do things like this, but I just spent the better part of the last two days wasting my time re-sizing and re-saving car skins and i'm a bit frustrated.
Do car skin makers understand the concept of files sizes and GPU memory?
I noticed in MSI Afterburner that I was pushing past my 8gb of GPU memory and thought it was something I did when modding a track. Turns out it was the car skins and I wasn't even using that big of a field. Only about 25-30 cars. I started to look through the skins folders and noticed some really huge file sizes for the textures used in most of the skins. Some of it was due to larger than needed texture resolutions for silly things like chasis AO's, tyre blur textures, NM files, etc. Most of it was due to choosing the wrong dds format when saving. There were files saved in a dds format that made the file size 4 times bigger than it should be. Thankfully after a massive amount of time spent, i'm back down to 5-6gb of GPU memory for a field of 30-32 cars.
OK, rant over.....
The reason hasn't been clearly articulated by RSS, but here's the TL;DR I was able to piece together, cos I was also interested. The trend is spreading btw, the HSS Matra launched in early access with PNG skins.
Waaaaayyyy back in the day (yes I'm old), DDS was introduced because it was faster for the game engines to read than other formats, although I don't recall PNG being a common format back then, it was more JPG and BMP in particular. ACC works on PNGs if I recall, although it does have transparency because you create 3 seperate images which combine together on the car if I recall?The reason hasn't been clearly articulated by RSS, but here's the TL;DR I was able to piece together, cos I was also interested. The trend is spreading btw, the HSS Matra launched in early access with PNG skins.
Pro: PNG's can be much smaller, simpler to work with, and in some cases avoid artifacting (like striation). Also, as textures get ever bigger, Photoshop (the fat Adobe crumbling tower) and whichever 3rd-party extension is chosen to make it work with DDS, on the vast majority of painter PCs, is being pushed to the edge, esp in large DDS saves.
Con: PNG doesn't support alpha channel (which is apparently responsible/capable of effects like chrome, matte and the second coming, and while I do understand the mask, I have yet to find someone who can explain that clearly, without marketing-speak), so transparency needs to be incorporated directly into the image.
Sidebar.Here's a interesting trick. Create a PNG, and then just edit the extension to DDS.
AC will convert that to an uncompressed DDS, on the fly, and use it (ymmv)
Hi, I really like your work but isn't this R8 Ultra already made by KS on the base game? I personnally don't see the point of making another one knowing we also have CF's extension for it that gives us almost every single wing configuration etc...
Don't usually do things like this, but I just spent the better part of the last two days wasting my time re-sizing and re-saving car skins and i'm a bit frustrated.
Do car skin makers understand the concept of files sizes and GPU memory?
I noticed in MSI Afterburner that I was pushing past my 8gb of GPU memory and thought it was something I did when modding a track. Turns out it was the car skins and I wasn't even using that big of a field. Only about 25-30 cars. I started to look through the skins folders and noticed some really huge file sizes for the textures used in most of the skins. Some of it was due to larger than needed texture resolutions for silly things like chasis AO's, tyre blur textures, NM files, etc. Most of it was due to choosing the wrong dds format when saving. There were files saved in a dds format that made the file size 4 times bigger than it should be. Thankfully after a massive amount of time spent, i'm back down to 5-6gb of GPU memory for a field of 30-32 cars.
OK, rant over.....
and also sometimes there are multiple versions of a car number, eg 3 skins with number 1 , 3 with number 2 , etc.
@echo offsetlocal enabledelayedexpansionecho Starting the processing of folders...for /d %%F in (*) do ( echo processing folder %%F mogrify -format dds -define dds:mipmaps=0 -define dds:compression=dtx5 "%%F\*.dds")echo Done processing all folders.pause
What are the differences with the current version of the BMW 320i STW and Audi A4 STW that are available from PM3DM
www.gtplanet.net
What are the differences with the current version of the BMW 320i STW and Audi A4 STW that are available from PM3DM
BMW 320i STW BTCC
The car and skins aren't made by me. All credits to the original creators of the car and skins. This is an updated version of the PM3DM car with a new interior (made by FSR?). Some time ago I've updated this version for me. I added all skins...
Don't usually do things like this, but I just spent the better part of the last two days wasting my time re-sizing and re-saving car skins and i'm a bit frustrated.
Do car skin makers understand the concept of files sizes and GPU memory?
I noticed in MSI Afterburner that I was pushing past my 8gb of GPU memory and thought it was something I did when modding a track. Turns out it was the car skins and I wasn't even using that big of a field. Only about 25-30 cars. I started to look through the skins folders and noticed some really huge file sizes for the textures used in most of the skins. Some of it was due to larger than needed texture resolutions for silly things like chasis AO's, tyre blur textures, NM files, etc. Most of it was due to choosing the wrong dds format when saving. There were files saved in a dds format that made the file size 4 times bigger than it should be. Thankfully after a massive amount of time spent, i'm back down to 5-6gb of GPU memory for a field of 30-32 cars.
OK, rant over.....
In that particular example you probably find its different skins for each series, so Le Mans, WEC and then IMSA, all that changes is the number plate banner.and also sometimes there are multiple versions of a car number, eg 3 skins with number 1 , 3 with number 2 , etc.
If I do a quickrace , I don't want to have multiple opponents with the same number...
An example is the ts_peugeot908_hdi_alms_lms , with a whopping 1.6GB skins folder ,
I kept 1 of each and got the skin folder down to 400 MB that way.
Still able to enjoy the mod... even more so now!
And I don't blame the modder / creator for sharing all the skins btw, just saying that's another way to save you some space
Running this in the skins folder will go through each skin folder and do dtx5 compression and remove mipmaps.
EDIT:
This saves diskspace , not gpu ram though... so actually all this is not really relevant to your posts.
Hi,
unsure if the following helps... need to make an 'activation' choice. I chose the last option and all is OK.
it was clearly articulated on their discord. There are no compression artifacts so you get better quality.The reason hasn't been clearly articulated by RSS, but here's the TL;DR I was able to piece together, cos I was also interested. The trend is spreading btw, the HSS Matra launched in early access with PNG skins.
Pro: PNG's can be much smaller, simpler to work with, and in some cases avoid artifacting (like striation). Also, as textures get ever bigger, Photoshop (the fat Adobe crumbling tower) and whichever 3rd-party extension is chosen to make it work with DDS, on the vast majority of painter PCs, is being pushed to the edge, esp in large DDS saves.
Con: PNG doesn't support alpha channel (which is apparently responsible/capable of effects like chrome, matte and the second coming, and while I do understand the mask, I have yet to find someone who can explain that clearly, without marketing-speak), so transparency needs to be incorporated directly into the image.
Sidebar.Here's a interesting trick. Create a PNG, and then just edit the extension to DDS.
AC will convert that to an uncompressed DDS, on the fly, and use it (ymmv)
