Featured TUTORIAL Build your FIRST track - BASIC GUIDE

If I find some time, I'll explain more in detail the groove thingy .
Until then, looking forward to see what you're cooking.

 

Hi sorry for the delay, a bit busy with work these days. Anyhoo, here's what I know:

1/ You can assign LODs inside the editor. Just right clic on the object you'd like to use LOD, and at the bottom in Object tab, you will see LodIN and LodOUT. For the highest detailed object you will have lods something like 0 to X meters, for the second one from X to Y, and so on. The LodOUT of previous object will be the LodIN of the next object.
Also the good part is that you can preview this in realtime, inside the SDK Editor

2/ You can load into the editor the AI path that you have recorded (if you've recorded one).
And you can use this path, to visually adjust the IN and OUT point of a specific camera.
In my example below, I've made one camera called TEST_CAMERA - and I've used the IN_point the position where you see the markers, and OUT_point another one, selected farther away. Play a little with it and should become easy.



3/ You are probably speaking about driver animation - you can find almost all the info in the document Kunos provided in \STEAM\steamapps\common\assettocorsa\sdk\dev\car-pipeline-1.03

4/ You don't usually need to use it, unless your recorded AI path needs readjusting. However, a) I am not very accustomed with it and b) it would be a pain to explain without video .

5/ No, not so much - just scattered information. There is a thread that might help you on the main forum. Some of the information might be obsolete, but still, I guess it will answer some questions.

6/ There is no skydome in AC tracks. If you are simply speaking about illumination, you can modify sun pitch and angle in lighting.ini, in your data folder.

7/ If it's a normal object, you cannot modify it (afaik). If you are speaking about objects with alpha (like trees for example), you can modify the fidelity it in the shader settings ksAlphaRef


But I think a shadow being too dark/light is more about the settings of the material the shadow projects to (the ground in my example) than the original object itself (the tree). Play a little with Ambient and Diffuse. The more distance you have between them, the more "dramatic" the shadow.

8/ No (would be cool though).

 

In what mode are you trying to run ? (Race, Race Weekend, ?)
If you start in race mode, the AI will work with only "fast_lane.ai" in your AI folder, because they will spawn at AC_START_x positions.
If you start in Race Weekend, AI will spawn at AC_PIT_x positions. And in this case, they need the "pit_lane.ai" in order to find their way out of pits .

It should work with the files inside \yourtrack\data\sfx folder. It used to work like this at least, didn't test in the latest updates of AC. Let us know if ok or not please .
To link the audio sources, just create a file called "audio_sources.ini" in the data folder, and inside add something like this:

Code:

[AC_AUDIO_1]
VOLUME_SCALE=20
VOLUME=0.9
FILENAME=content/tracks/_YOURTRACK_/sfx/my_sound_file.wav

[AC_AUDIO_2]
VOLUME_SCALE=20
VOLUME=0.9
FILENAME=content/tracks/_YOURTRACK_/sfx/my_next_sound_file.wav

You can customize volume and volume scale of course. Just play with them to fit your needs.

What software are you using ? (if Blender, you need to add 90 rotation on X axis, but then DON'T make "Apply" or it will be lost. For 3dsmax it's the same, but only rotate the pivot point.

 

What I mean is after some modifications on an object (scale, position, etc) you usually "apply" those modifications (pressing CTRL+A >> Apply) in order to make'em default.

For example, let's say you've changes the scale of an object so now it would be something like 2.3, 4, 1 instead of the "true" scale 1,1,1. If you choose Apply scale, the object's scale properties will be back to 1, 1, 1.

In any case, for your rotation to the objects you should NOT apply the modification, so you should be good .
Please see Troubleshooting for more info.

 

Hi there @ckbucu . Had a look at your log file.
Looks like you have some objects named as physical surfaces (by mistake I believe) but they miss the surfaces keys in the surfaces.ini.

Do note, that ANY object that starts with a number other than 0, WILL behave like a physical object. So not only 1ROAD_blah_blah will act as a road; but also 3DDRZEWKO02_SUB1, for example.

What can you do:
1/ rename the objects that you don't want physical properties for to something that will make them graphical only. Example: rename 3DDRZEWKO02_SUB1 to 0DDRZEWKO02_SUB1 or simply delete the number in front DDRZEWKO02_SUB1, or whatever.

2/ if you'd actually like this object to have some physical properties (to act like a surface) add a key for it, in the surfaces.ini file. Key should be something like:

[SURFACE_1]
KEY=DDRZEWKO02
FRICTION=1
DAMPING=0
WAV=
WAV_PITCH=0
FF_EFFECT=NULL
DIRT_ADDITIVE=0
IS_VALID_TRACK=1
BLACK_FLAG_TIME=0
SIN_HEIGHT=0
SIN_LENGTH=0
IS_PITLANE=0
VIBRATION_GAIN=0
VIBRATION_LENGTH=0

Do this for ALL the objects named starting with a number that should act as a surface.

 

Can't seem to spot another error in the logs.
Can you post a screenshot of your folder hierarchy ?
A screenshot fo your track in KSEditor ?

In what mode are you starting your track ?

Does your AC work with other tracks ?

 

All seems ok..
Maybe another screen with the hierarchy in the 3d software you are using ?

And, what happens exactly ?
- you start AC
- see your track in the menu, select it
- select practice mode
- hit drive
- ...and ? PC is blocked ?

Maybe try and clear your log folder (delete or move all files in it), do a clean run, and then attach all the files. Maybe the the problem lies somewhere different.

Also, are all you textures dds or png ?

 

kn5 file will not really help me (especially since I am not at my main PC) .
But the track in a 3d format (fbx ?) would be ok.

Screen of object naming hierarchy in the 3d program (3dsimed ?).