you are very funny ,but the one who makes most laugh is you and unlike you I know what I’m talking about
First of all, thanks for the reply.
Wow, super detailed explanation, thank you so much Andre!I wanted to help you, but Suzuki saw your preview, and now they have a restraining order on me....
Seriously, that is a bit extreme .
OK, unpack the data, and rename data.acd to something like data.acd.bak
In the data folder you've just unpacked, open suspensions.ini
In [FRONT] look for BASEY. Now, mind your maths, and add whatever change you've made in the CM showroom (in this case 100mm or 0.1m cos the data in suspensions is in meters. Take care with the sign. The stock Suzuki Cup car is BASEY=-0.220. Add 0.1 = -0.120 yeah?
Do the same for the rear.
Now. Many, many people in this forum, will tell you this is a dumb idea. Because it is. BASEY is related to the CoG of the car.
A 100mm adjustment will almost certainly trash the handling, setups etc. beyond redemption.
In my experience, BASEY can be used safely for small adjustments, but 100mm (4 inches) yoink will require more suspension-ken to do properly.
Further down in suspensions.ini you will find [GRAPHICS_OFFSETS]
This is where you can move the tyres inward/outward, this time relatively free from consequence.
Have the showroom open and a text editor open with suspensions.ini so that you can see both.
Adjust the eight values (again, mind the signs, they're opposite on each side of the car). A wheel and a suspension are a pair, and the values for each pair should be the same, else, for example, the brakes will show through the rim.
When you save the suspensions.ini (just save, not close) the changes appear immediately in the showroom.
When you're happy, save an close suspensions.ini, and in the parameters pane in CM Showroom at the bottom of the "Car Params" panel (where you gave basey an all-mighty whack) There's a button to Update model. CM will make a backup of the KN5 and "burn" your changes "permanently". This will then be visible anywhere you view the car.
All of this stuff will certainly not be usable online.
Good luck.
Edit: "Update model" uses data.acd first and if not found, the unpacked /data folder. Changing the sliders in CM does not change it in either, which is why the "Update model" does not seem to "take". You have to actually change the data first ^^.
I like Marco17's skins for the RSS cars. If I understand correctly, he's basically an RSS team member who - on release days, usually, already - releases some of the top real-life liveries for the RSS cars as "unofficial" add-ons.
yes, the CF model and details visually are quite good. I was more speaking to how it drives.
I have had CM crash my File Explorer in Windows multiple times over the past few weeks. I have seen that there's been more than a few updates, so I'm sure he's aware. Something has gone amiss with it recently, I'd say.
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.....
