Assetto Corsa PC Mods General DiscussionPC 

  • Thread starter daan
  • 140,992 comments
  • 39,021,841 views
shi
Pineda v1.2

conversion from GTR2/GTL.
Fictional circuit in Spain.

View attachment 1135425
-CSP recommended
-34 pit/start
-AI, cam

Credits & Thanks;
Created for rFactor by entrevias. Thanks for creating this track and making it freeware.
Converted GTR2 by RacerM and Thank you for gave me permission
Converted GTL by der Dumeklemmer

AC Converted by @shi (shin956)
AI by Rainmaker (Up to v1.16)
AI, sidelines and ai_hints.ini by IMEAN
cam and ext_config by @CrisT86
.lua and font base by @gunnar333
Additional Pits Layout by @MeltFire
logo.png by @Fanapryde
cameraman, tree texture by kunos
Test, Feedback by @Breathe , @RMi_wood , @twobegreen

The readme for rF, GTR2, GTL and AC can be found in the _readme folder.
Enjoy.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
v1.15 changelog;
Change Castrol billboard.
Added some normal map.
Tweaked shader.
Adjusted the brightness of the light.
Spectators are now supported in camera_facting.ini.
Replaced the cameraman with one from kunos.
Reduced the saturation of the curbs.
Added normal maps for islands and hills.
Expanded sea area and adjusted shaders.
Adjusted the UI.
The blue areas were erased with treewall textures.

v1.16 changelog;
Tree was placed at the edge of Treewall. ( @Fanapryde Thanks for the report.)

v1.2 changelog;
Changed AI, sidelines and ai_hints.ini by IMEAN. (Thanks)
Changed crowd textures by Kniker97. (Thanks)
Updated some billboard logo textures.
Updated ext_config.ini.
Updated VAO-patch.
Replaced marshalls.

Pineda v1.2
The link is in the quote.

v1.2 changelog;
Changed AI, sidelines and ai_hints.ini by IMEAN. (Thanks)
Changed crowd textures by Kniker97. (Thanks)
Updated some billboard logo textures.
Updated ext_config.ini.
Updated VAO-patch.
Replaced marshalls.
 
Hello racing enthusiasts,

Thanks to F302, we finally got a missing car last year—not just any car, but a truly special one: the Mercedes-Benz W209 CLK DTM. While the car was already great, there were still many details that needed attention. This is where @eki03 and I came together. I’ve always had old pictures from the DTM era lying around, and I’ve always wanted to create some skins for it just like the pictures I have, so we decided to make it happen. But we didn’t stop there. With the help of TomSim, we’ve also made the following updates:

Improved the light materials for a more realistic look.
Adjusted LOD (Level of Detail) distances to optimize both performance and visual quality.
Redesigned the seat to reflect a more accurate design.
Updated both the driver and steering animations for better realism.
Added missing skins to reflect the various seasons in which the CLK raced.
Made several other detail improvements to further enhance the overall quality of the car.
Fine-tuned the vehicle physics to deliver a more authentic and immersive driving experience.
We welcome any feedback and hope you enjoy our work! For additional skins, including retro, prototype and testing versions—be sure to visit overtake.gg/sdmd13.


Wishing you all a great time on track and exciting racing ahead!

View attachment 1420957
Looks and feels like a completely different car! Really great job.
 
actually a big issue with them is to get them to proper default values, because they are also included in some emissive stuff like here the tvs at Brno:
View attachment 1420931

With setting sun they become really dark:
View attachment 1420932

and then if the tracklights going on they became bright and thats what does not really fit into a real logic, because why should they have the "backlight" off while day:
View attachment 1420933

So if they would have the backlight on also while day, it would work:
View attachment 1420934
View attachment 1420935

So all the problems come from the "old" AC too dim daylight logic where night and day were having the same brightness to be able to use a static exposure. But now with Pure you could think like in reality. So at day you need more power to view such LED screens.
Speaking of jumbotrons, is there a way to have them only show a particular camera_x.ini file too?
 

Attachments

  • 977f3672f57c75971fea493144d8ddad.jpg
    977f3672f57c75971fea493144d8ddad.jpg
    139.2 KB · Views: 1
  • 295060694_553753026292586_4043999037800054766_n.jpg
    295060694_553753026292586_4043999037800054766_n.jpg
    70.6 KB · Views: 1
  • image0.jpg
    image0.jpg
    38.9 KB · Views: 1
Just a heads up and PSA for everyone:

Maybe some of you keep up with the news better than I do... but long story short, I have an ASUS mobo and an i9-13900k and the default settings in the BIOS were unnecessarily aggressive and had essentially been setup for unlimited power (volts/watts/amps) and cooked my CPU. This has been an ongoing thing with the 13th/14th gen Intel chips, but I found out only after it was too late. I assume Assetto Corsa also played a factor in this because it's such a CPU intensive game and it's makes up about 75% of my game time. This CPU is less than two years old.

Anyone who isn't aware of this, or maybe is but doesn't think it will apply to them: Make sure to update your BIOS to the latest version and also be sure to implement the Intel recommended settings. Having 1.5v constantly coursing through your CPU while playing heavy load games like AC will destroy your CPU. Regardless of you Mobo manufacturer, if you have an i9-13000 or i9-14000 cpu, you are 100% at risk.

TLDR; My CPU just bricked itself and I had no idea there were any issues whatsoever.
Thanks again for the heads-up.
I updated my MB BIOS this morning after reading up about how necessary it is. My last BIOS was from mid-2023, so I'm wondering what damage might have been done in the meantime.
The update process wasn't entirely straightforward because of the usual ambiguity involved in navigating user-unfriendly menus to download the correct BIOS then actually update it in the BIOS.
These types of things are always expected to be done by casual luddites but always seem aimed at power users, and the potential for disaster always seems high.
Mine twice took a butt-clenchingly long time to update various firmware on first reboot, then booted straight to the BIOS again on the first 'clean' boot.
Here we go, I thought... but all seems OK now.
 
Could you try with an older CSP like 0.2.5p1 ? So if this is different i would need to search for a workaround

C13 has been my go-to filter since I switched to Pure, never had any problems with it lol
I tested Brno with following configs

csp 2.5 - Pure 2.37
csp 2.5 - Pure 2.38
csp 2.7 - Pure 2.37
csp 2.7 - Pure 2.38

And always the same dark jumbotrons :confused:
 
actually a big issue with them is to get them to proper default values, because they are also included in some emissive stuff like here the tvs at Brno:
View attachment 1420931

With setting sun they become really dark:
View attachment 1420932

and then if the tracklights going on they became bright and thats what does not really fit into a real logic, because why should they have the "backlight" off while day:
View attachment 1420933

So if they would have the backlight on also while day, it would work:
View attachment 1420934
View attachment 1420935

So all the problems come from the "old" AC too dim daylight logic where night and day were having the same brightness to be able to use a static exposure. But now with Pure you could think like in reality. So at day you need more power to view such LED screens.
As a guy who occasionally mods tracks and some of those tracks include jumbotrons, changing the way the night and day lighting is handled and forcing track makers to have to redo the jumbotron setups is a bad idea. That means every old track with a jumbotron needs a new config and what about doing tracks moving forward. Now modders have to decide who am I modding this track for, people who use new CSP\Pure combos or people (like me) who prefer old CSP\Pure\Sol combos. If I make the jumbotrons work for people like me, they are too dark for people using newer versions.

And no, i'm not going to use the rule that everyone should be using newer versions of CSP and Pure and mod just for them. If I had to guess, I would say more people are still using older versions. Maybe not the people here, but AC users overall.
 
Does anyone have a pitlane.ai for Southport Gold Coast (Nukedrop)? Cars bouncing all over the pitlane... A beautiful but un-useable track (for an offline racer). Surprising nobody's done anything about this... Tyrone? What's up?
 
As a guy who occasionally mods tracks and some of those tracks include jumbotrons, changing the way the night and day lighting is handled and forcing track makers to have to redo the jumbotron setups is a bad idea. That means every old track with a jumbotron needs a new config and what about doing tracks moving forward. Now modders have to decide who am I modding this track for, people who use new CSP\Pure combos or people (like me) who prefer old CSP\Pure\Sol combos. If I make the jumbotrons work for people like me, they are too dark for people using newer versions.

And no, i'm not going to use the rule that everyone should be using newer versions of CSP and Pure and mod just for them. If I had to guess, I would say more people are still using older versions. Maybe not the people here, but AC users overall.
Personally, since I don't like using a program that I can't use 100%.

To setting it to the small onions, I stay on the version lights-patch-v0.1.80preview115

Since there are only people who speak or write English fluently to understand this kind of program.

And that each update of CSP, it adds even more options to not understand anything.

So I say no thanks and stay on an old version of the thing.

I know I'm not going to make any friends by saying this. But when will there be an update to at least 30 languages translated for this program? Never, surely... :(
 
Just a heads up and PSA for everyone:

Maybe some of you keep up with the news better than I do... but long story short, I have an ASUS mobo and an i9-13900k and the default settings in the BIOS were unnecessarily aggressive and had essentially been setup for unlimited power (volts/watts/amps) and cooked my CPU. This has been an ongoing thing with the 13th/14th gen Intel chips, but I found out only after it was too late. I assume Assetto Corsa also played a factor in this because it's such a CPU intensive game and it's makes up about 75% of my game time. This CPU is less than two years old.

Anyone who isn't aware of this, or maybe is but doesn't think it will apply to them: Make sure to update your BIOS to the latest version and also be sure to implement the Intel recommended settings. Having 1.5v constantly coursing through your CPU while playing heavy load games like AC will destroy your CPU. Regardless of you Mobo manufacturer, if you have an i9-13000 or i9-14000 cpu, you are 100% at risk.

TLDR; My CPU just bricked itself and I had no idea there were any issues whatsoever.
I had a bit of luck with my new pc.
Right before throwing myself back into the whip'n'ballgag world of AC and reinstalling everything like a good dog, I bought one of those new-gen dumb-but-sexy shooter games.
This game has a very toxi...ehrm...active community and I accidentally stumbled upon some useful set-up tips, discovering that the bios of my new pc had super-aggressive overclocking tuning on by default making the said game a bit crashy.

So caveman tip: turn all the overclocking off unless you knowing something about it.
 
As a guy who occasionally mods tracks and some of those tracks include jumbotrons, changing the way the night and day lighting is handled and forcing track makers to have to redo the jumbotron setups is a bad idea. That means every old track with a jumbotron needs a new config and what about doing tracks moving forward. Now modders have to decide who am I modding this track for, people who use new CSP\Pure combos or people (like me) who prefer old CSP\Pure\Sol combos. If I make the jumbotrons work for people like me, they are too dark for people using newer versions.

And no, i'm not going to use the rule that everyone should be using newer versions of CSP and Pure and mod just for them. If I had to guess, I would say more people are still using older versions. Maybe not the people here, but AC users overall.
I actually thinking of getting something into it, to control it or tell the config, which "daylight" strength is present. So it would be automitcally adjusted then. But this is actually the point where things are different. To get a real lighting, such things must be adapted.
But idk why it is different now. So i will check more things out...

I tested Brno with following configs

csp 2.5 - Pure 2.37
csp 2.5 - Pure 2.38
csp 2.7 - Pure 2.37
csp 2.7 - Pure 2.38

And always the same dark jumbotrons :confused:
Thanks for checking it! But then idk what is the real cause here. Because Pure 2.37 is from mid December
 
Last edited:
As a guy who occasionally mods tracks and some of those tracks include jumbotrons, changing the way the night and day lighting is handled and forcing track makers to have to redo the jumbotron setups is a bad idea. That means every old track with a jumbotron needs a new config and what about doing tracks moving forward. Now modders have to decide who am I modding this track for, people who use new CSP\Pure combos or people (like me) who prefer old CSP\Pure\Sol combos. If I make the jumbotrons work for people like me, they are too dark for people using newer versions.

And no, i'm not going to use the rule that everyone should be using newer versions of CSP and Pure and mod just for them. If I had to guess, I would say more people are still using older versions. Maybe not the people here, but AC users overall.
Also, this Gamma vs LCS face-off where we now have to pick a side... your Instanbul updates look fantastic in Gamma, but with LCS the very first thing I noticed was oversaturated reds on the kerbs, which I'm 100% sure aren't how you want them to look.

LCS power users: should I be using a different PPF or something to avoid adjusting every single track config (not that it's a realistic option)? PureVR has stood me in good stead.... until now.
This is like a whole new twist on choice paralysis, but with goofy results.

Edit: tried C13AEGIS PPF.
Why is it so damn dark?
 
Last edited:
@Haunebu52
You should undervolt your Intel CPU.
I also had a 9900K that was scrapped due to high temperatures. I undervolted my current 14900K. At 5800 MHz, I have a maximum temperature of 60 degrees in AC and 70 degrees in Prime 95.

Here is a good explanation:
I have learned a valuable lesson here, and will be checking my default BIOS settings to make sure there isn't any overclocking, overvolting or any other shenanigans going on. I have a very powerful system, so I don't even need to be overclocking anything, but it was setup that way from the manufacturer. Thank you for the info.

Thanks again for the heads-up.
I updated my MB BIOS this morning after reading up about how necessary it is. My last BIOS was from mid-2023, so I'm wondering what damage might have been done in the meantime.
The update process wasn't entirely straightforward because of the usual ambiguity involved in navigating user-unfriendly menus to download the correct BIOS then actually update it in the BIOS.
These types of things are always expected to be done by casual luddites but always seem aimed at power users, and the potential for disaster always seems high.
Mine twice took a butt-clenchingly long time to update various firmware on first reboot, then booted straight to the BIOS again on the first 'clean' boot.
Here we go, I thought... but all seems OK now.
I was in the same situation, my BIOS were from mid-2023 when I bought the system and never thought there would be any problems. I did quite a lot of damage to the CPU running the default settings and playing games. I don't know if you built the system or bought it, but I would look into maybe trying to file a claim if you can. It would suck if your CPU eventually failed but it was too late to get a replacement.

Luckily, I have filed a claim and will be getting a replacement CPU free of charge, but my rig will be down for several weeks and I will have to install the CPU myself which is a bit intimidating. I haven't built a system since the early 2000's lol so dealing with a watercooler and all the advanced stuff in my system is just a little intimidating.

Also an additional PSA - I've noticed some folks mentioning microstutters and some choppiness in Assetto Corsa. Yes, this can be caused by numerous different things, but in my case, my microstutters were caused by CPU being overvolted and starting to fail. So, if you have a 13th/14th gen Intel CPU and are experiencing microstutters in Assetto Corsa and other games, the bad news is it could be something rather serious. You definitely want to file a claim and try to get a replacement CPU while they are still doing this. If your CPU fails next year, you may have to buy a replacement. Who knows how long they will be doing the free replacements.
 
Also, this Gamma vs LCS face-off where we now have to pick a side... your Instanbul updates look fantastic in Gamma, but with LCS the very first thing I noticed was oversaturated reds on the kerbs, which I'm 100% sure aren't how you want them to look.

LCS power users: should I be using a different PPF or something to avoid adjusting every single track config (not that it's a realistic option)? PureVR has stood me in good stead.... until now.
This is like a whole new twist on choice paralysis, but with goofy results.

Edit: tried C13AEGIS PPF.
Why is it so damn dark?
First, when using a new PPF make sure you set pure to default, then check the PP filters config and adjust it to your likings. I would recommend you try NVRealism or GarryReal as next ones. Especially GarryReal (I would recommend v1.13) as it has some pre-defined values you may choose from instead of moving sliders. I will never go back to Gamma since Peter eventually has stopped the development for it IIRC.
 
First, when using a new PPF make sure you set pure to default, then check the PP filters config and adjust it to your likings. I would recommend you try NVRealism or GarryReal as next ones. Especially GarryReal (I would recommend v1.13) as it has some pre-defined values you may choose from instead of moving sliders. I will never go back to Gamma since Peter eventually has stopped the development for it IIRC.
Ouch, Garryreal in VR? it's the most FPS consuming ppf on my long list. Also, it's the only one that does a proper job in LCS, i have to admit (but i never managed to make it work on old tracks).

I agree that i see nothing good in the 1.15 version, the 1.13 still has some use for me, but not so much on my vintage journey.

The problem with it is that it's the less versatile ppf i've ever seen. On the Nord? Perfect. But on many, many, many other track mods it's just "let's tweak the light, the whatever Light spec, the Luss option, the fog is buggy, oh no the cam_sun_face is bugged AGAIN". All at a 5-10% perf cost for some reason when there's a lot of cars, so basically worst than the best sets for Reshade (that would include Ambient occluson, cinematic DOF and all the other cool stuff). Once settled? Super good ppfilter, lots of great options (indeed the click once options are super nicely done and clear), but it gets rid of saturation a lot. I will absolutly steal the Daylight mult/Sun level slider.


Also, to be noted, the CSP link garry offers is an absolute nonsense and you shouldn't click it at any cost. Same for the Assetto video settings link.
 
Last edited:
Sharing a mod? Host it on GTPlanet Downloads. Free, public hosting for files up to 10GB in size.
Back