- 12
- Australia
Assetto Corsa PC Mods General DiscussionPC
- Thread starter daan
- 142,974 comments
- 39,982,239 views
- 962
- Belgium
How rude!
And to answer your question, no I am not using pirated mods...
If you look up what pirated means, you will find this on a first google hit :
So unless Peter would be asking money for his releases (which I don't think is the case) , any leaked beta can not be seen as a pirated mod, since Peter does not stand to loose income from this leaked beta.
If anything it will gain him valuable feedback from us lot testdriving it.
And if I put some time in creating skins and share them, it's up to you to ignore them if you don't want them.
The number of likes on my posts sharing skins tell me not everyone must feel that way, so try and tone it down.
Say to yourself : "my opinion is my own, and not necessarily the right one"
Putting your opinion on everyone else, and telling me to shove my skins where the light doesn't shine , isn't that a bridge too far?
Last edited:
- 247
- Ukraine
The tribunal of the fundamentalists is watching you 
This is my way to ajust the height of the car (in showroom and in game)
Heigth in showroom:
And in game:
Go to suspension.ini and note the values of static_camber for the front. Launch the game, then check if you get the same value for the front camber. if not the parameter to adjust is rod_length. Stop the race, go to suspension.ini and set rod_length. if in game the camber was lower than the value of static camber in suspension.ini, rod_length must be increased. conversely if camber was greater than static_camber. For the values, obviously you take into account the - sign.
Of course, this operation will require several trips back and forth in game.
Do the same for the rear.
Have fun, nice week end.
Mike
Edit: keep in mind these operations could modify the TOE parameters.
This is my way to ajust the height of the car (in showroom and in game)
Heigth in showroom:
And in game:
Go to suspension.ini and note the values of static_camber for the front. Launch the game, then check if you get the same value for the front camber. if not the parameter to adjust is rod_length. Stop the race, go to suspension.ini and set rod_length. if in game the camber was lower than the value of static camber in suspension.ini, rod_length must be increased. conversely if camber was greater than static_camber. For the values, obviously you take into account the - sign.
Of course, this operation will require several trips back and forth in game.
Do the same for the rear.
Have fun, nice week end.
Mike
Edit: keep in mind these operations could modify the TOE parameters.
Last edited:
- 583
- Netherlands
- Rivanov
Thank you very much! Will give this a try!OK, so what's happening here?
When you generate a preview with the "Use CSP for final preview render" Content Manager setting UNCHECKED (aka CM previews)...
View attachment 1434705
CM uses the current skin that it's/you're viewing, or have selected in a list, and the current KN5, and fires up it's internal renderer to make a preview image using the selected preview preset.
The settings in /data, data.acd, the car's /extension/ext_config.ini, the skin's individual ext_config.ini are NOT applied. So none of the KN5's added in skin-specific ext_config's for wings, winglets, number-plates etc are rendered. And if the model is encrypted with "clumsy-mode" encryption, you get blue crystals.
When you have "Use CSP for final preview render" checked (aka CSP previews), CM will actually launch AC in the background and get CSP involved. NOW the settings in /data, data.acd, the car's /extension/ext_config.ini, the skin's individual ext_config.ini ARE all applied. And just like when you check "Align with data", the ride height (amongst everything else) is visible.
Since encrypted cars HAVE to be decrypted to be viewable in-game, even that hurdle is removed, and we can have nice previews.
Finally, CSP generates the render from the "modified" KN5.
And looking at all the folks who have reported that their previews are fine and dandy, this is exactly what they have done.
Now. If you're brave and have a backup of the KN5 (CM makes one, but belts AND braces, right?) you can, having applied "Align with data", use the "Update model" button at the bottom of the same panel. This updates the current KN5 with the current-in-use data settings (/data or data.acd) and saves it (with a backup, 'cos as Ilya as well knows, "stuff" happens...)
Now, when you make a CM Preview, the effects of /data or data.acd are "baked" into the KN5.
WARNINGs:
1. Many things may change, not just the ride height. I've found modders (even good ones) to be shockingly sloppy with this. The data settings and the saved KN5 in some instances differ wildly. Wheels move, wheelbase inaccuracies are revealed, camber is suddenly applied, wheels are spacered because Graphic adjustments etc.
2. Sometimes you'll mess up the ambient shadows by doing this, and have to update them. After updating the model, navigate to the left-most tab in the CM showroom parameters panel, with the left arrow icon, and click "Update Ambient Shadow". Select your prefs or accept defaults, and update the shadows.
3. I'd be especially careful with complex code-heavy mods like those from RSS and even more so, VRC. Backup, backup.
Good luck, fellow traveller
Last edited:
- 856
- Spain
- 583
- Netherlands
- Rivanov
Sorry for coming back to you about this.. but I don't see an Update Model button. (CM Showroom)OK, so what's happening here?
When you generate a preview with the "Use CSP for final preview render" Content Manager setting UNCHECKED (aka CM previews)...
View attachment 1434705
CM uses the current skin that it's/you're viewing, or have selected in a list, and the current KN5, and fires up it's internal renderer to make a preview image using the selected preview preset.
The settings in /data, data.acd, the car's /extension/ext_config.ini, the skin's individual ext_config.ini are NOT applied. So none of the KN5's added in skin-specific ext_config's for wings, winglets, number-plates etc are rendered. And if the model is encrypted with "clumsy-mode" encryption, you get blue crystals.
When you have "Use CSP for final preview render" checked (aka CSP previews), CM will actually launch AC in the background and get CSP involved. NOW the settings in /data, data.acd, the car's /extension/ext_config.ini, the skin's individual ext_config.ini ARE all applied. And just like when you check "Align with data", the ride height (amongst everything else) is visible.
Since encrypted cars HAVE to be decrypted to be viewable in-game, even that hurdle is removed, and we can have nice previews.
Finally, CSP generates the render from the "modified" KN5.
And looking at all the folks who have reported that their previews are fine and dandy, this is exactly what they have done.
Now. If you're brave and have a backup of the KN5 (CM makes one, but belts AND braces, right?) you can, having applied "Align with data", use the "Update model" button at the bottom of the same panel. This updates the current KN5 with the current-in-use data settings (/data or data.acd) and saves it (with a backup, 'cos as Ilya as well knows, "stuff" happens...)
Now, when you make a CM Preview, the effects of /data or data.acd are "baked" into the KN5.
WARNINGs:
1. Many things may change, not just the ride height. I've found modders (even good ones) to be shockingly sloppy with this. The data settings and the saved KN5 in some instances differ wildly. Wheels move, wheelbase inaccuracies are revealed, camber is suddenly applied, wheels are spacered because Graphic adjustments etc.
2. Sometimes you'll mess up the ambient shadows by doing this, and have to update them. After updating the model, navigate to the left-most tab in the CM showroom parameters panel, with the left arrow icon, and click "Update Ambient Shadow". Select your prefs or accept defaults, and update the shadows.
3. I'd be especially careful with complex code-heavy mods like those from RSS and even more so, VRC. Backup, backup.
Good luck, fellow traveller
/edit: Guess it's because an encrypted mod? With a standard Kunos car I do have the Update Model option.
Last edited:
- 1,801
- Chicago, USA
- 178
- Germany
modifying the basey is a very bad idea because it also changes the behavior of the car, you can adjust the height in car.ini with the line: GRAPHICS_OFFSETThe tribunal of the fundamentalists is watching you
This is my way to ajust the height of the car (in showroom and in game)
Heigth in showroom:View attachment 1434731
And in game:
Go to suspension.ini and note the values of static_camber for the front. Launch the game, then check if you get the same value for the front camber. if not the parameter to adjust is rod_length. Stop the race, go to suspension.ini and set rod_length. if in game the camber was lower than the value of static camber in suspension.ini, rod_length must be increased. conversely if camber was greater than static_camber. For the values, obviously you take into account the - sign.
Of course, this operation will require several trips back and forth in game.
Do the same for the rear.
Have fun, nice week end.
Mike
Edit: keep in mind these operations could modify the TOE parameters.
- 2,295
- MI
This is the right answer. Do not adjust BASEY unless you are trying to change the physics and driving characteristics of the car. That value is not a height adjustment value even though that's what it looks like it does in the showroom.
- 178
- Germany
It's release Friday!
This time with the last track of my WIP portfolio, Bern Alpenring, a nice made fantasy track located in Switzerland.
This fantasy track was made by Edoardo Bottin (edobot) for rFactor in 2012. It was converted to Assetto Corsa by Rainmaker.
Features:
-working AI
-replay cameras by DaBaeda
-working track map
-support for hot lap mode
-support for time attack mode
-26 pit boxes with working pit lane
-DRS zone
-nights lights
-vao patch
-added option to removed 2d crowds: open the ext_config.ini in the extension folder scroll down to last ";remove 2d crowds" and set ACTIVE = 1
Known issues: thin hair lines in the background
DOWNLOAD
View attachment 1434170
View attachment 1434171
there is already a version of this track almost identical to yours? what's the point of creating a duplicate?
there are much more beautiful mountains on the other version, the original one needs to be changed it's too low poly and old textures.
spectators are also much prettier than the original ones
Last edited:
- 887
- Italy
I use a bit of CSP AI rubberbanding because I like opponents to bite my bottom but you guys bring it to the next level.
- 46
- Finland
A lot of car.ui.json errors lately. Both among free old mods and brand new paid mods like URD and RSS. CM does not offer fix even it has done that sometimes. Running the newest version as RSS Mustang asked for it. They seem to be so critical that non-MP race crash the game. Any ideas?
- 618
- Germany
I made my version before ACTK released his version. The mountains look much better if you have the correct settings. You can disable the spectators in my version if you like.
- 178
- Germany
is this an update then? I thought it was a new release, but for the mountains you can use all the settings you want, the problem comes from textures with a much too low resolution, no setting can erase that..
the solution would be to move the horizon further away, so that it is less close and the defects less visible
Last edited:
- 6,898
- The Bunker
Nice car - thanks for the heads up. I wish the Chivas GT cars were as nicely finished in the cockpits.
Does anyone have any issues with disappearing wheels on cars ahead? Seems to be a LODs issue or model swap problem somewhere?
- 1,759
- Sherbrooke, Québec,
- 178
- Germany
Yes, one of the latest on both. I'll try to combine older versions if this can solve the problem.you have a recent version of CSP and pure? there must be a problem of incompatibility between the 2, otherwise soon the elephants Rose CSP?
Thanks.
Similar threads
