TUTORIAL Build your FIRST track - BASIC GUIDE

[quetillo]

Kseditor, load ai spline and use the camera tab at the bottom

I did so, but it does not mark the vertical lines that appear when you hit the pink line

 

[Johnr777]

I did so, but it does not mark the vertical lines that appear when you hit the pink line

Its a known issue... open the FBX in 3dsimed, save it as a different FBX... like quetillotrackforcameras.fbx

Use that instead, will work with the ai line again

 

[quetillo]

Its a known issue... open the FBX in 3dsimed, save it as a different FBX... like quetillotrackforcameras.fbx

Use that instead, will work with the ai line again

nothing does not work the cameras, I do not take the pink line
It only happened to me when I made this map in blender

 

[Johnr777]

nothing does not work the cameras, I do not take the pink line
It only happened to me when I made this map in blender

did you try my suggestion

 

[quetillo]

did you try my suggestion

Now, in the end I had to decompress the section in kn5 and it works for me with kn5conv, thanks

 

[quetillo]

which, being a path that crosses the camera, goes crazy

 

[Rob Pawn]

le Bluem made a app. https://www.racedepartment.com/downloads/caminfo.46609/
pretty nice. bit buggy tho. if you get stuck jumping to next cam position, i suggest copy paste manually several cam positions (counts) in the cameras ini and change position values. save, restart cm and go ahead with the app. I ended up with copy cam position via the app and write the ini manually...

 

[quetillo]

le Bluem made a app. https://www.racedepartment.com/downloads/caminfo.46609/
pretty nice. bit buggy tho. if you get stuck jumping to next cam position, i suggest copy paste manually several cam positions (counts) in the cameras ini and change position values. save, restart cm and go ahead with the app. I ended up with copy cam position via the app and write the ini manually...

I tried but there is not much about this app caminfo, I do not know where to start, the install I gave the + as it says and it goes lejos.no came to understand its operation, there is no tuto

 

[Rob Pawn]

There you go...

btw. @fughettaboutit
we already had a conversation about this bugs in:
https://assettocorsamods.net/threads/ai-spline-gremlins.3005/#post-20983

wouldn't you be down to invest bit time into your app, again?

I think a COPY button besides SAVE button for IN and OUT Point would be nice to have.
Maybe for UP and FORWARD, too...
But the main thing, the "automatic cam detection" is the big obstacle.
If it would be possible to get rid of that, the App could work quiet good i believe.
Everytime 2 cams are at the same position, i won't let you switch further to next cam in the app...

 

[fughettaboutit]

There you go...

btw. @fughettaboutit
we already had a conversation about this bugs in:
https://assettocorsamods.net/threads/ai-spline-gremlins.3005/#post-20983

wouldn't you be down to invest bit time into your app, again?

I think a COPY button besides SAVE button for IN and OUT Point would be nice to have.
Maybe for UP and FORWARD, too...
But the main thing, the "automatic cam detection" is the big obstacle.
If it would be possible to get rid of that, the App could work quiet good i believe.
Everytime 2 cams are at the same position, i won't let you switch further to next cam in the app...

aye, for making that long of a video and because your pain is really coming over, will take a look at "add" and same cam on same place w different camera files

 

[Rob Pawn]

your pain is really coming over

hahaha mission succesfully done... (force him to rework)
i could live with it on its actuall state - cause meanwhile i know how to workaround.
but for others and so...

to be honest, i was terrified as i saw the length of the tut...

 

[fughettaboutit]

"i was terrified as i saw the length of the tut..." same here

 

[fughettaboutit]

actually the app was not meant to make new cams, the "Add" button was meant only to insert a cam between two existing, not to add to current or empty cameras.ini
the AccExthelper app has a buggy implementation of "auto generating" cameras, i will update that too i guess

 

[fughettaboutit]

hahaha mission succesfully done... (force him to rework)
i could live with it on its actuall state - cause meanwhile i know how to workaround.
but for others and so...

to be honest, i was terrified as i saw the length of the tut...

So here a preview, i think it should work much better than before, some strange mistakes i made before; before i do a new update you might wanna try?

Rename attachement to only ...zip

CamInfo v1.4 preview
-redone "add" camera button, it will hoopefully behave better
-fixed being-near-existing-cam bug in free-cam
-fixed changing only first camera if more than 1 file have cams in same place
-new "add" cameras.ini button, some parameters in first lines of apps\python\CamInfo\CamInfo.py, not in UI, you must reload session anyway...
--based on fast_lane.ai and its borders
-added some sanity checks for cam-files on load and a label with log info
(edit: will add more to clipboard when "copy vals" later)

green: new

 

[Rob Pawn]

Sorry for the late response.
If we come to close to existing cams, the tool switch still automatically to this cam.
New added cams does not get the position we are right now. it seems to spawn always on first camera position.
By adding the 2nd cam (first add with tool) the positions get switched.
By adding outpoint for first cam (if there is just one camera position in ini file) the outpoint get set for inpoint as well.

Now where i tested v1.4 of CamInfo Tool... got damn, i found a quicker solution then i said in the tutorial before... There is no need to write anything manually (except header and first cam position)

works for both, 1.3 and 1.4

there is no tuto

 

[fughettaboutit]

Sorry for the late response.
If we come to close to existing cams, the tool switch still automatically to this cam.
New added cams does not get the position we are right now. it seems to spawn always on first camera position.
By adding the 2nd cam (first add with tool) the positions get switched.
By adding outpoint for first cam (if there is just one camera position in ini file) the outpoint get set for inpoint as well.

Now where i tested v1.4 of CamInfo Tool... got damn, i found a quicker solution then i said in the tutorial before... There is no need to write anything manually (except header and first cam position)

works for both, 1.3 and 1.4

...after adding a bunch (or only a few first) in the replay then just use play/pause to move the car, freecam to next cam pos, and use "save pos/fov" when the car is facing you, the app will then use that PoT of the car as IN_POINT

btw PoT = car's current "Point Of Track"

edit 31 jan 23: https://www.racedepartment.com/downloads/caminfo.46609/update/101634/

 

[quetillo]

I am doing tests with blender, I have a terrain with photogeometry, having so many polygons I have to divide it into several on the map, I divide it into 3, but when I load it later in AC it does not work. I create a models.ini file and I put the 3 kn5 there But it doesn't work, I split it into 8 and it's still the same. Is there a solution to this?

 

[Piereligio]

The entire mesh gets the increase - as per surfaces.ini

So I guess I could separate the surfaces around the ideal line and not, to emulate it building up in the ideal line zone?

 

[Johnr777]

So I guess I could separate the surfaces around the ideal line and not, to emulate it building up in the ideal line zone?

Sure

 

[Uniginius]

Hi to all
I'm new in Assetto corsa mod, I create my AB track in AC I have a problem or question.
When the car arrived to finish, how can stop the race? when the car arrived to end of the track the car not stop and go forward, and not stop the game! Someone have a solution??

Thank You!