Assetto Corsa PC Mods General DiscussionPC 

  • Thread starter daan
  • 139,056 comments
  • 38,200,569 views
Hi Jari, isn't all that hidden detail just taking up unnecessary resources? We do all we can to get the model object/tri count down for better performance so I'm struggling to see what the point is in adding detail under the bonnet and in the boot. I know there are options in the showroom to open bonnets and doors but it's not like AC has a proper ForzaVista mode for gazing at tiny details. I'd much prefer a version of the car with all of that hidden stuff removed, TBH.

Totally agree!
 
I used 3DSimEd to edit all these tracks. If you want I can give you a detailed explanation in a pm how to add pits using this program :)
I'll take you up on that offer. I have the track opened in 3Dsimed now so I'll fool around with it but directions would be nice. Thank you.
 
Mate, I don´t know whats wrong with the sidekick app recently but I cannot run AC any longer with your app enabled. It just produces heavily stuttering. The only option for me is to disable it completely. Could it be the culprit to deactivate the second window you recently added to your app? Before it just was fine without any probs. It´s a pity since this app is the only one I think is really mandatory for AC.

Imo disabling the second row stops this massive stuttering, at least for me. I would like to have it enabled, as it looks nice and gives a lot of usefull additional informations, but I had no chance.
On the other hand, didn´t tested new version yet.

Would you two mind try it again with what ever setup causes the stuttering, and pm'ing me your sidekick config.ini and C:\Users\<your username>\Documents\Assetto Corsa\logs\py_log.txt?

I'm not experiencing any stuttering, and have not had any other reports, so hopefully the config and logs will have some clues as to what the problem is.

Also, some description if the frequency\duration of the stutters would help, and whether or not you are using CSP and\or SOL.
Thanks!
 
OK, I'm brand new to Blender. I created a LOD for a car but it's physically huge. I'm guessing I need to either scale when importing the fbx into blender or when exporting the kn5.
How do you do this, and what's the correct scale?
Thanks.
Edit: or maybe I need to set the correct units somewhere, eg imperial to metric?
Edit 2: I can select everything and click the 'scale' button, but there doesn't seem to be a dialogue box to enter a scale, just drag points.

Edit: Never mind, found the scale when exporting the FBX. Proper scale is 0.01.
If you set the world units in Blender to meters you can export FBX files from it using the same scale factor as you would on 3ds max ;)
 
...

edit : seems this 'thing' comes also fro URD
https://www.racedepartment.com/downloads/redbull-x2010.8443/

Actually, this 'thing' is just fantastic to drive - in VR is even better.

upload_2020-4-30_15-52-15.png
 
I'll take you up on that offer. I have the track opened in 3Dsimed now so I'll fool around with it but directions would be nice. Thank you.
Okay, so the procedure of adding pit boxes and start positions is not very complicated, but can be time consuming. It can also get a little bit repetitive, but I guess repetition is a vital part of racing, so nobody should complain about that ;)

Basically what you have to do is import the track to 3DSimEd and locate the pitlane. Check how the pit boxes are placed – they will usually look like cubes or flat arrows. Then find a place in which you would like to place your next pit box.

First, right click on the surface (ground) and select "Memorize XYZ". Then, right click on the last possible pit box, for example in Cadwell Park there were originally 18 pit boxes, which means the last possible will be named AC_PIT_17 (as the first one is always named AC_PIT_0). Right click on it, select "Object...", then "AC_PIT_17". A window called "Object instance edit" should pop up on your right. Select from it the "Clone object" option (the purple cross, like on Swiss flag), this should create a new object, in this example it will be called "AC_PIT_18". Then, select "Recall memorized vertex" option from the same window (it's shortened to blue MR letters). This option will move the pit box you just created to the coordinates you chose before.

Voila, you have a new pit box, where you want it. Then rinse and repeat, until you reach a number that satisfies you. Sometimes pit boxes created this way will be placed a little bit too high in the air or a little bit too low into the ground. Not to worry, what you need to do then is choose an original pit box, and copy it's Z Coord into all your new pit boxes. To copy, just highlight the Z Coord value, for example with double mouse click, ctrl+c, then select your new pit box, double click its Z Coord value, ctrl+v, and it should be right. It’s especially important not to place the pit box below the track level, as sometimes it might mean that the car will spawn under the ground and fall down into oblivion, probably not the best scenario for the race weekend.

Before you start adding pit boxes in 3DSimEd, I recommend that you first visit in Assetto Corsa the pitlane of the track you want to edit, just to see how much space in the pitlane you really have and where does the "ghosting" end (cars going through each other in the pitlane). For example the first time I edited a track this way, I added a pit box outside of the space where the "ghosting" happens, which resulted in collisions inside the pitlane, something you probably want to avoid :D

Also, sometimes there is something strange going on with the distances and dimensions with some tracks. For example, when I was editing Cadwell Park, I wanted to add one more pit box close to the pit exit, because it looked like there was space for it. When I loaded the game, it turned out that the car spawned on a pit wall, which was weird, because in 3DSimEd the wall looked like it was a few meters back than in reality. This is why it’s very important to check the pitlane before adding more pit boxes, because it can save you some time you would have to otherwise spend on fixing your own mistakes (happened to me more than I like to admit).

The procedure of adding pit boxes applies to start positons as well, which are called AC_START_number. Once again the first one is named as AC_START_0. One very important thing with start positions is not to place them too close to each other. If you do, AI cars on race start will slow down heavily just after the start of the race and possibly ruin your start in the process. If it happens to you, you will have to spread the start positions apart, which is not very difficult, but can be extremely annoying, because you will need to select all your start positions, place them on the side of the track, and then place them back onto the track, one by one, into their new, revised positions.

If you want to learn which distance between start positions is best, look for a track in Assetto Corsa that has a very smooth and rapid race start, load that track in 3DSimEd and check how the start positions are placed. Roughly measure the distance between them and try to implement that into your desired track.

One more thing about "ghosting effect" in the pitlane, that I mentioned before. On some tracks this effect doesn’t happen, which is not a good thing, because then AI cars will crash with each other in the pits and it will ruin the whole race weekend. You can identify it quickly by yourself in practice mode, because once your car loads into the game and you spawn in the pits, you should see the pit box info on the right of your screen (the table with tyres pressures, wings and repairs). If it’s not there, then it means that the pitlane is broken and "ghosting" doesn’t happen as well. This is the main problem with Anglesey Circuit for example, because if the pitlane worked as it should, then the player car would be “ghosted” when it’s in the pits and the AI cars would never crash into it.

Fortunately, there is an easy fix to this problem. Once again 3DSimEd comes to your help. Right click on the ground in the pitlane and select the object that covers the ground in the pitlane. It should be called nPIT (where n is any number except zero) for Assetto Corsa to recognize that it’s in fact the pitlane. It probably isn’t, so you need to rename it correctly. To make sure you are doing this right, once again look for a track in Assetto Corsa that has a working pitlane. Open it in 3DSimEd, check how the objects that form the pitlane are called. With this knowledge, come back to the broken track and rename the objects that form the pitlane in a similar manner to the objects in the track you just checked. It should work, if it doesn’t then try again, this time choose a different track and see how the pitlane is named in that instance.

Please let me know if you understood my instructions, english is not my first language, so I might have said something in a not precise way, for which I apologize.

This is the general rule of adding pit boxes and if you confirm that you understood everything, I will try to explain the more advanced way of adding pit boxes without editing the original track (it's not very complicated, but first you need to understand the basics).

Tagging @unpierrot , because he might find this helpful as well.

Also, sorry everyone else for creating this horrible wall of text, I probably should have done it in a private message.
 
Help please: Often (on different tracks with different car sets) on weekend mode in CM (after completing qualifying) the grid is set for race mode and when the cars pull out from the grid there is one car that stays put - blocking those behind. If you go around concluding the first lap, that car will still be blocking at the start and stay there for all laps to race end. This ruins the racing. This does not happen every single time. Since it appears to be a global issue, is there some setting in CM, perhaps, to disable this? Jump start disable doesn't do it.
 
Help please: Often (on different tracks with different car sets) on weekend mode in CM (after completing qualifying) the grid is set for race mode and when the cars pull out from the grid there is one car that stays put - blocking those behind. If you go around concluding the first lap, that car will still be blocking at the start and stay there for all laps to race end. This ruins the racing. This does not happen every single time. Since it appears to be a global issue, is there some setting in CM, perhaps, to disable this? Jump start disable doesn't do it.
One thing that sometimes works for me is restarting the session before the race begins. When qualifying ends and your car is placed on the grid, before you start the race, just click "restart session" in "SESSION CONTROL" tab and then start the race. Sometimes it works, sometimes it doesn't, but it helped me multiple times, so maybe it will help you as well.
 
Would you two mind try it again with what ever setup causes the stuttering, and pm'ing me your sidekick config.ini and C:\Users\<your username>\Documents\Assetto Corsa\logs\py_log.txt?

I'm not experiencing any stuttering, and have not had any other reports, so hopefully the config and logs will have some clues as to what the problem is.

Also, some description if the frequency\duration of the stutters would help, and whether or not you are using CSP and\or SOL.
Thanks!

Will try and test out. FYI: stuttering is from the beginning, once AC has been fired up. I use latest CSP (1.53 preview 4) and SOL 1.5.1 (have tested it with 1.6. as well). Will send you my logs and files very soon.
 
Foxeway:
Thank you. I will try that.
You have it happen, like me, and perhaps others too. Looks like it could be a general bug.
Maybe there is an AC exterminator out there who can squash this bug !
Again, thanks Foxeway.
 
Can someone share the data setting that determines brake pedal pressure and how quickly brakes lock up?:confused:
I'm working on a vintage car mod (sixties era) that seems to lock up the tyres immediately upon hitting the brake pedal, then of course if you enable ABS it doesn't stop at all, just thinks about it lol.
Similarly, what setting causes my Fanatec wheel to wobble left to right even when the car is stopped?:confused: That happens most frequently with older mods.
 
Last edited:
No problem, I hope it helps :)

For me it happens when an AI for some reason couldn't complete it's stint during Practice or Qualifying. What I mean is - for example during Practice, the AI car got hit by another car, crashed into the barrier and got sent back by the game into the pits. Then that car doesn't drive out again and in Qualifying it doesn't even set a time. Or sometimes it happens when an AI car already set a time in Qualifying with no problems, but during coming back into the pits it had an accident and once and it got sent back by the game to the pits.

Very often I am able to tell which AI car will probably not start the race and stay on the grid just by looking on what compound of tyres all cars are on - very often the "broken" AI car will have it's qualifying tyres on instead of the ones others use during the race (so for example it will be on Q tyres instead of M). When I see that, I immediately know I have to restart the session and most of the times it helps. Good luck!
 
Will try and test out. FYI: stuttering is from the beginning, once AC has been fired up. I use latest CSP (1.53 preview 4) and SOL 1.5.1 (have tested it with 1.6. as well). Will send you my logs and files very soon.

Found it. After disabling the "stereo odometer" app it works as a charm even with the second line enabled. So the sidekick app does not like this.
Maybe @slider666 this may work for you as well? Even the stutters after crossing the start / finish line are gone. Sweet and lovely.
 
Okay, so the procedure of adding pit boxes and start positions is not very complicated, but can be time consuming. It can also get a little bit repetitive, but I guess repetition is a vital part of racing, so nobody should complain about that ;)

Basically what you have to do is import the track to 3DSimEd and locate the pitlane. Check how the pit boxes are placed – they will usually look like cubes or flat arrows. Then find a place in which you would like to place your next pit box.

First, right click on the surface (ground) and select "Memorize XYZ". Then, right click on the last possible pit box, for example in Cadwell Park there were originally 18 pit boxes, which means the last possible will be named AC_PIT_17 (as the first one is always named AC_PIT_0). Right click on it, select "Object...", then "AC_PIT_17". A window called "Object instance edit" should pop up on your right. Select from it the "Clone object" option (the purple cross, like on Swiss flag), this should create a new object, in this example it will be called "AC_PIT_18". Then, select "Recall memorized vertex" option from the same window (it's shortened to blue MR letters). This option will move the pit box you just created to the coordinates you chose before.

Voila, you have a new pit box, where you want it. Then rinse and repeat, until you reach a number that satisfies you. Sometimes pit boxes created this way will be placed a little bit too high in the air or a little bit too low into the ground. Not to worry, what you need to do then is choose an original pit box, and copy it's Z Coord into all your new pit boxes. To copy, just highlight the Z Coord value, for example with double mouse click, ctrl+c, then select your new pit box, double click its Z Coord value, ctrl+v, and it should be right. It’s especially important not to place the pit box below the track level, as sometimes it might mean that the car will spawn under the ground and fall down into oblivion, probably not the best scenario for the race weekend.

Before you start adding pit boxes in 3DSimEd, I recommend that you first visit in Assetto Corsa the pitlane of the track you want to edit, just to see how much space in the pitlane you really have and where does the "ghosting" end (cars going through each other in the pitlane). For example the first time I edited a track this way, I added a pit box outside of the space where the "ghosting" happens, which resulted in collisions inside the pitlane, something you probably want to avoid :D

Also, sometimes there is something strange going on with the distances and dimensions with some tracks. For example, when I was editing Cadwell Park, I wanted to add one more pit box close to the pit exit, because it looked like there was space for it. When I loaded the game, it turned out that the car spawned on a pit wall, which was weird, because in 3DSimEd the wall looked like it was a few meters back than in reality. This is why it’s very important to check the pitlane before adding more pit boxes, because it can save you some time you would have to otherwise spend on fixing your own mistakes (happened to me more than I like to admit).

The procedure of adding pit boxes applies to start positons as well, which are called AC_START_number. Once again the first one is named as AC_START_0. One very important thing with start positions is not to place them too close to each other. If you do, AI cars on race start will slow down heavily just after the start of the race and possibly ruin your start in the process. If it happens to you, you will have to spread the start positions apart, which is not very difficult, but can be extremely annoying, because you will need to select all your start positions, place them on the side of the track, and then place them back onto the track, one by one, into their new, revised positions.

If you want to learn which distance between start positions is best, look for a track in Assetto Corsa that has a very smooth and rapid race start, load that track in 3DSimEd and check how the start positions are placed. Roughly measure the distance between them and try to implement that into your desired track.

One more thing about "ghosting effect" in the pitlane, that I mentioned before. On some tracks this effect doesn’t happen, which is not a good thing, because then AI cars will crash with each other in the pits and it will ruin the whole race weekend. You can identify it quickly by yourself in practice mode, because once your car loads into the game and you spawn in the pits, you should see the pit box info on the right of your screen (the table with tyres pressures, wings and repairs). If it’s not there, then it means that the pitlane is broken and "ghosting" doesn’t happen as well. This is the main problem with Anglesey Circuit for example, because if the pitlane worked as it should, then the player car would be “ghosted” when it’s in the pits and the AI cars would never crash into it.

Fortunately, there is an easy fix to this problem. Once again 3DSimEd comes to your help. Right click on the ground in the pitlane and select the object that covers the ground in the pitlane. It should be called nPIT (where n is any number except zero) for Assetto Corsa to recognize that it’s in fact the pitlane. It probably isn’t, so you need to rename it correctly. To make sure you are doing this right, once again look for a track in Assetto Corsa that has a working pitlane. Open it in 3DSimEd, check how the objects that form the pitlane are called. With this knowledge, come back to the broken track and rename the objects that form the pitlane in a similar manner to the objects in the track you just checked. It should work, if it doesn’t then try again, this time choose a different track and see how the pitlane is named in that instance.

Please let me know if you understood my instructions, english is not my first language, so I might have said something in a not precise way, for which I apologize.

This is the general rule of adding pit boxes and if you confirm that you understood everything, I will try to explain the more advanced way of adding pit boxes without editing the original track (it's not very complicated, but first you need to understand the basics).

Tagging @unpierrot , because he might find this helpful as well.

Also, sorry everyone else for creating this horrible wall of text, I probably should have done it in a private message.
I thank you immensely. Now that your fingertips are sore, go take a break. I'm going to process all of this and add it to my brain cells. Whatever is left.
 
Another quick question: which version of Hockenheimring is actual and more accurate? 2018 version or multi-layout?

The ACU version is a Codemasters rip from F1 2016 (?) I believe where the Tommy78 one is a scratch made one which is not that accurate. I would prefer the updated 2018 version.
 
I thank you immensely. Now that your fingertips are sore, go take a break. I'm going to process all of this and add it to my brain cells. Whatever is left.
Haha, no problem, the more people know how to do this, the more great content we will all have! :)

I will write the second part tomorrow on how to create a new layout with your new pit boxes and start positions. It's important to do it this way, because it guarantees that your pit boxes don't get overwritten when an updated version of the track comes out and also it makes it possible to play multiplayer with someone, who doesn't have the extra pit boxes and start positions.
 
The ACU version is a Codemasters rip from F1 2016 (?) I believe where the Tommy78 one is a scratch made one which is not that accurate. I would prefer the updated 2018 version.

Thx for answer!
I meand the version of Lorenzo Bonder (which was made by Tommy78) from RD (and a 2018 update for its version from INGV4RRCOREjZ), which is a rip from rFactor in comparison with "Hockenheim F1 GP 2018 - v.1.1 by patrikpat".
I still haven’t fully understood which one is better and accurate, in testing process. :)
 
Help please: Often (on different tracks with different car sets) on weekend mode in CM (after completing qualifying) the grid is set for race mode and when the cars pull out from the grid there is one car that stays put - blocking those behind. If you go around concluding the first lap, that car will still be blocking at the start and stay there for all laps to race end. This ruins the racing. This does not happen every single time. Since it appears to be a global issue, is there some setting in CM, perhaps, to disable this? Jump start disable doesn't do it.
What's more than likely happening is the rev limiter is being reached before the AI is being told to shift up from Neutral.
Go into data folder of car (extract that folder if necessary from data.acd), open up ai.ini and engine.ini. Look at engine.ini RPM limiter and then look at the up shift in ai.ini. I usually like to set the up shift to around 200 RPM below the engine limiter but anywhere underneath the RPM limiter will fix the problem.
Can someone share the data setting that determines brake pedal pressure and how quickly brakes lock up?:confused:
I'm working on a vintage car mod (sixties era) that seems to lock up the tyres immediately upon hitting the brake pedal, then of course if you enable ABS it doesn't stop at all, just thinks about it lol.
Your talking about MAX_TORQUE in brake.ini. Lower it down a bunch until you don't get lockup and then raise it back up to where they are on the cusp to start locking again. This also plays with brake temps that should be in the same file and parameters are missing in a lot of mod cars. Maybe make it so that first lap they will lock the first couple stomps and then when the brakes heat up, from there on just good squishy vintage brakes.
 
@GzeroD on your Mullenbach and GT variant of Nurb the grass is floating through the air:

upload_2020-5-1_0-45-52.png


It is connected to GrassFX and the ks_nurburgring.ini which has the config for grassfx. Can you please try to fix this?
 
Thx for answer!
I meand the version of Lorenzo Bonder (which was made by Tommy78) from RD (and a 2018 update for its version from INGV4RRCOREjZ), which is a rip from rFactor in comparison with "Hockenheim F1 GP 2018 - v.1.1 by patrikpat".
I still haven’t fully understood which one is better and accurate, in testing process. :)

Sorry I meant the patrikpat version - that should be better.
 
Sharing a mod? Host it on GTPlanet Downloads. Free, public hosting for files up to 10GB in size.
Back