Assetto Corsa PC Mods General DiscussionPC 

  • Thread starter Thread starter daan
  • 146,806 comments
  • 43,692,896 views
no worries sorry for not putting the link up in the upload i should of done it would of saved you scratching your head
I applied the patch and I still get this gran turismo sticker on top of your skin, is there any way to remove it? Or maybe it's just some CM showroom thing?
 

Attachments

  • __custom_showroom_1752776680.png
    __custom_showroom_1752776680.png
    390.7 KB · Views: 1
Interesting experiment with Kunos F2004 in Kunos Nurburgring, with CSP last stable version 0.179.

AI 100 (Schumacher), driver aggression 25.
AI 97 (Raikkonen) driver aggression 12

Qualifying, ai

Both constantly drove to the gravel in the Valvoline curve. Every single time.

I switched to VRC 2007 tyres.ini there and bang... all issues were gone. And suddenly the AI cars are performing consistently in every track and even drive better than default Kunos.

Maybe not a surprise to anyone, huh?
 
Last edited:
Interesting experiment with Kunos F2004 in Kunos Nurburgring, with CSP last stable version 0.179.

AI 100 (Schumacher), driver aggression 25.
AI 97 (Raikkonen) driver aggression 12

Qualifying, ai

Both constantly drove to the gravel in the Valvoline curve. Every single time.

I switched to VRC 2007 tyres.ini there and bang... all issues were gone. And suddenly the AI cars are performing consistently in every track and even drive better than default Kunos.

Maybe not a surprise to anyone, huh?
Tires are very responsible for many performance params. very small changes on some parameters make big differences (even to ai)
Aero is also a big factor btw, esp drag coefficient (which can be used for top speed and acceleration tuning. If all power, gears and tires are correct and the top speed, or time to top speed... tweaing the aero is the next step )
 
I applied the patch and I still get this gran turismo sticker on top of your skin, is there any way to remove it? Or maybe it's just some CM showroom thing?
This is what i see, i have just checked the download and the ext_config is there so it should be removed if you are in "showroom" and not "cm showroom"

cm showroom does not apply all the bells and whistles it is only applied in "showroom" or out on the track

Screenshot (1009).png
 
Last edited:
Hi All. Does anyone know how to make the headlights on the URD Mercedes CLR LM shine on the track and light up the track at night. The headlights come on but don’t throw any light on track. Many thanks.
 
Hi All. Does anyone know how to make the headlights on the URD Mercedes CLR LM shine on the track and light up the track at night. The headlights come on but don’t throw any light on track. Many thanks.
I remember we had this topic last year, see here:

 
Hello everyone! Do you know what this track is? I can't find him anywhere. Maybe it doesn't exist at all.
 

Attachments

  • track.jpg
    track.jpg
    106.4 KB · Views: 3
Tires are very responsible for many performance params. very small changes on some parameters make big differences (even to ai)
Aero is also a big factor btw, esp drag coefficient (which can be used for top speed and acceleration tuning. If all power, gears and tires are correct and the top speed, or time to top speed... tweaing the aero is the next step )

Does anyone know that some cars respond much stronger to AI rating?

For example the F2002 car based season and the VRC's 2005 and 2007 (all skin based, the base car is the same) are amazingly accurate. 2002 Schumacher gets 80% of all poles in the season which is pretty much accurate. Hamilton and Alonso (at rating 100) get all AI poles in the 2007 season. Not once they were out of top-3 unless they have that random crash in the session.

But when you do the exact same AI settings for some other cars, the results vary a lot. In some QF sessions the highest rated (skin) car (like ai driver 100) can be 3 seconds slower (despite not having any traffic issues).

Is there some random variable in the car data? You know... perhaps the skin based "fabricated cars" choose to drive with maximum rear wing or something?

Just like sometimes AI car decides to pit twice with no reason and the others choose one pitstop. Is there a way affect these variables?

Say, you set the ai cars' max starting fuel sufficient for like 14 laps. And the ai car pits at lap seven and then they might pit again at lap 19 in a 20 lap race (even they have plenty of fuel left). These are very annoying things that you can't set up (I guess).
 
Last edited:
OK, I tried the NVIDIA Preview driver for Smooth Motion activation on a 4090.


It needed a profile inspector upgrade too and I found a link to the 590.x preview without needing to go into the Nvidia developer forum (where it is seemingly impossible to find the preview drivers.)

My base set-up is a Nvidia 566.36, CSP 2.10, Pure, FSR 87% using HP Reverb VR via OpenXR using a Narrow FFR.
I get constant 90 FPS day and night with this, great clarity with all graphics settings maxed.

Any benefit I was going to be put toward a wider FFR or RainFX which generally drops frames unless I compromise on other settings.
No improvement is essential, but I thought I'd give it a go.

The result was with the upgraded driver and smoothing on, a decrease in frames to 75FPS, seemingly the new driver tanked performance, I also tried CSP 2.12 at this same time which may also have generated an issue. I'll try again without the CSP upgrade, try with/without FSR and report, but on the first go round, it wasn't immediately beneficial over the optimised base.
 
ACU Interlagos.

Add another amazing track that no longer works with CSP 0.2.11

Well it works. It races ok. But when the ai cars have time to pit, they drive staight to the concrete wall that is on the left of the pitlane 250 km/h.May they all rest in peace.

Tested version ACU 1.0. I tried another pitlane.ai from some other version. No difference. All crash.

Well I'm not an expert and can't say it's definitely the CSP. But a lot of tracks no longer work like they used to. It can be something else too. The cars pitted and raced without any problems for years at ACU Interlagos. Now they crash when pitting. I don't know what it is... but the old saying "don't fix what ain't broken" applies to CSP/CM/physics/whatever it is. :)
@Apocalypse211 I'm having the same issue with Mosport 2021 ver.3.0 from JohnR. AI cars can no longer leave the pits, they drive straight into the pit wall and keep doing this for the entire race. CM 0.2.11
:banghead:
 
@Apocalypse211 I'm having the same issue with Mosport 2021 ver.3.0 from JohnR. AI cars can no longer leave the pits, they drive straight into the pit wall and keep doing this for the entire race. CM 0.2.11
:banghead:

Yeah. Something is really going on. Good old Sepang stopped working too (not ACU Sepang that always had erratic pit, which erases one full lap from pitting AI cars) but the other version. However I managed to find older version which works. I don't know if it's CSP or Content Manager but something that wasn't broken has been "fixed". :)

Another issue... the exact one that you mention... is that occasionally cars that leave the pits start crashing like maniacs on the pitlane. This happens with 0.1.79 last stable version so it's definitely not CSP issue. Then when you restart the race and CM (like 5 times), it suddenly works normally.

I have two gaming machines. The other one always has the latest CSP and the actual playing machine has 0.1,79.

Here is a video of this issue. Probably the same that you have. It's not track related or car related. Happens on ACU interlagos and Fuji MTS with several cars. But when you restart the race many times, it start workings. Super weird. Definitely something got screwed in the CM settings probably.

 
Last edited:
New CSP makes visor of ACSPRH disappear...
1752821702679.png



New CSP un-unalive disabled objects in the KN5 so now they appear in game even though I disabled them in kseditor
1752821894664.png


The new KN5 Loader makes every helmet use the default helmet skin when enabled
1752821956906.png



Idk i'm tired of csp, having to bring workaround to fix bugs introduced with each new update that have been flooding my mailbox with 'help i have this issue' and not knowing what csp version to recommend is annoying.
 
Some of the physics issues are not CSP related. I have played some track/car combos for years. Like Monaco 2017 with VRC 2005 and 2007 cars. Suddenly they have a fastlane issue where they crash on the left side wall at La Rascasso with the same CSP 0.1.79 version. That never, ever happened before. Fastlane hasn't been altered and the CSP version hasn't changed.

Same for that pitlane madness that Kurt Woods mentioned. It's a new issue and happens with the 0.1.79 suddenly. Never happened before.

Could it be that there is something on the CM that was adjusted and majorly screwed things up?
 
Last edited:
I remember we had this topic last year, see here:

Fantastic. Thanks for that.
 
@Apocalypse211 I'm having the same issue with Mosport 2021 ver.3.0 from JohnR. AI cars can no longer leave the pits, they drive straight into the pit wall and keep doing this for the entire race. CM 0.2.11
:banghead:
ACU Interlagos.

Add another amazing track that no longer works with CSP 0.2.11

Well it works. It races ok. But when the ai cars have time to pit, they drive staight to the concrete wall that is on the left of the pitlane 250 km/h.May they all rest in peace.

Tested version ACU 1.0. I tried another pitlane.ai from some other version. No difference. All crash.

Well I'm not an expert and can't say it's definitely the CSP. But a lot of tracks no longer work like they used to. It can be something else too. The cars pitted and raced without any problems for years at ACU Interlagos. Now they crash when pitting. I don't know what it is... but the old saying "don't fix what ain't broken" applies to CSP/CM/physics/whatever it is. :)

Click to expand...
Try selecting "Disabled" under "Settings/CSP/general patch settings/Physics experiments/Awake physics in pits"
 
Try selecting "Disabled" under "Settings/CSP/general patch settings/Physics experiments/Awake physics in pits"

I just checked and this is activated as default in the 0.2.11. If that is what is creating this issue, it's absolute insanity to leave it activated as a default setting.

HOWEVER... this same thing happens with 0.1.79 too. I can't check my other machine at the moment if that option was already there. Doubt it. So maybe this is not the guilty setting.

But will investigate. Thanks man.
 
Last edited:
I just checked and this is activated as default in the 0.2.11. If that is what is creating this issue, it's absolute insanity to leave it activated as a default setting.

HOWEVER... this same thing happens with 0.1.79 too. I can't check my other machine at the moment if that option was already there. Doubt it. So maybe this is not the guilty setting.

But will investigate. Thanks man.
New features (which sadly are often ill-conceived, badly-implemented or seemingly untested) are regularly set to on by default in CSP updates. It's maddening, and often leaves you scratching your head wondering why something that has worked perfectly for years is suddenly broken.
 
I just checked and this is activated as default in the 0.2.11. If that is what is creating this issue, it's absolute insanity to leave it activated as a default setting.

HOWEVER... this same thing happens with 0.1.79 too. I can't check my other machine at the moment if that option was already there. Doubt it. So maybe this is not the guilty setting.

But will investigate. Thanks man.
I kind of understand ija pov, that new csp are technically "beta" and if you want a bug free experience you should go back in a recommended version. And that not a lot of people would activate these options leading to these options to not be really tested and give feedback. But treating the whole user base as beta tester by forcing these options to gather data in the way CSP is released is actually mad.

Idk why actually CSP follow this development path. Normally for softwares, you have stable release and beta release. Difference being that stable get an update every 2-3 months, and nightly/beta get an update much more frequently. And in the end you get 1.0, 1.1 beta 1, 1.1 beta 2 leading to 1.1


But CSP treat itself as constantly being in beta. Pushing updates increasing the counter without reaching 1.0, and with that you get experimental features at each update. And then retroactively a version of CSP that has found to be "mostly stable" get the recommended tag in Content Manager. The more annoying fact being that each version fix bugs from the previous version but brings more experimental features that brings more bugs. I would just wish if he release a stable version that is just bug fix.

Instead of pushing stable and beta version, he just push beta version and retroactively mark them as stable. Weird path to go on.
 
FCA Pinerolo Race Autodrome v1.0

Screenshot_bmw_m3_e30_dtm_pinerolo_r_a_18-6-125-18-40-34.jpg

Fictional circuit in Italy.
Conversion from rFactor.

-CSP Recommended
-2 layouts (Mountain/ Club)
-42 pit/start
-AI, cam

Credits & Thanks;
Original rFactor Track by Edobot
-I have tried to contact him but have not been able to. I thank him for his work.

AC converted by @shi (shin956)
Crowds texture by Kniker97
Pit tent base from F1-S-R's 1994 Track Pack (rF1)
marshall and some textures by kunos
"Toyota Land Cruiser" (https://skfb.ly/MyHv) by Renafox is licensed under Creative Commons Attribution-Noncommercial (http://creativecommons.org/licenses/by-nc/4.0/).

Enjoy.
 
Hi. I'm using Pain.net to modify a skin, but I don't know how to remove the sponsor stickers, race number, writing, etc. I know how to add stickers, but I don't know how to remove the original ones. Can someone explain this to me? Thanks a lot. 🙏
for me you should never try to modify an existing skin.....especially with AO......try to recreate it as a new standalone one from scratch
 
The idea that because he says 1.79 is recommended, its functionally working is sadly cobblers. There are issues with 1.79 which are addressed with the patreon builds, and obviously new stuff that's broken.

But there is still nothing like AC, aside from if i wanted to fully get into beamng, which i don't, AC is like a warm blanket and i learn new stuff modding wise everyday.

But yeah, the whole CSP / Pure gravy train got old a long time ago for me.
I must say i'm sure that about 2 years ago everything looked better. But then again why in Gods name do i still need to be playing a decade old sim racing game.....
 
I kind of understand ija pov, that new csp are technically "beta" and if you want a bug free experience you should go back in a recommended version. And that not a lot of people would activate these options leading to these options to not be really tested and give feedback. But treating the whole user base as beta tester by forcing these options to gather data in the way CSP is released is actually mad.

Idk why actually CSP follow this development path. Normally for softwares, you have stable release and beta release. Difference being that stable get an update every 2-3 months, and nightly/beta get an update much more frequently. And in the end you get 1.0, 1.1 beta 1, 1.1 beta 2 leading to 1.1


But CSP treat itself as constantly being in beta. Pushing updates increasing the counter without reaching 1.0, and with that you get experimental features at each update. And then retroactively a version of CSP that has found to be "mostly stable" get the recommended tag in Content Manager. The more annoying fact being that each version fix bugs from the previous version but brings more experimental features that brings more bugs. I would just wish if he release a stable version that is just bug fix.

Instead of pushing stable and beta version, he just push beta version and retroactively mark them as stable. Weird path to go on.
That because he is in fact a mad scientist!!

Dress Up Doc Brown GIF by Nickelodeon
 
Some of the physics issues are not CSP related. I have played some track/car combos for years. Like Monaco 2017 with VRC 2005 and 2007 cars. Suddenly they have a fastlane issue where they crash on the left side wall at La Rascasso with the same CSP 0.1.79 version. That never, ever happened before. Fastlane hasn't been altered and the CSP version hasn't changed.

Same for that pitlane madness that Kurt Woods mentioned. It's a new issue and happens with the 0.1.79 suddenly. Never happened before.

Could it be that there is something on the CM that was adjusted and majorly screwed things up?
There's was a quote sometime ago, if I remember correctly from @peterboese that CSP 179 even though it says recommended, newer versions have been but not stated as is 211.
 
Sharing a mod? Host it on GTPlanet Downloads. Free, public hosting for files up to 10GB in size.
Back