TUTORIAL Build your FIRST track - BASIC GUIDE

[DrPenguin]

Thanks Dave! Does Blender provide a persistence file or do I need to amend the generated one from RTB with the name changes from Blender?

 

[Johnr777]

No.. but if you haven’t changed any material names, your shaders should be intact, and the mesh names shouldn’t really matter, except if maybe you have the physical objects set to render = false, then you need to redo that for the new mesh names.

 

[Patrice COte]

Perplexing question: has anyone ever had objects (or even entire fbx) showing perfectly in editor and not showing at all in game?
Really weird, only made another update (to an already working in-game fbx), and somehow I'm not able to get it in-game anymore, despite trying some work-arounds.
Could it be related to new CSP settings (version 245)? They have KsGrass shader.
With vanilla settings same results (no CSP). I guess that's no it.

I've checked the other obvious stuff such as .kn5 names called in models.ini, no luck.
It's been 2 days, no fix found yet despite looking "everywhere". (I hate looking like a noob... but getting a bit desperate)

All my tree walls in the editor ... gone in game. Any advice welcome!

 

[luchian]

Did you maybe played with the persistence file ? Like renaming it or renaming the fbx ?

Something similar-ish happened to me, and I needed to delete the persistence and redo all materials. I think it was one of the "is transparent" options that would not stay saved, no matter what.

 

[Johnr777]

Perplexing question: has anyone ever had objects (or even entire fbx) showing perfectly in editor and not showing at all in game?
Really weird, only made another update (to an already working in-game fbx), and somehow I'm not able to get it in-game anymore, despite trying some work-arounds.
Could it be related to new CSP settings (version 245)? They have KsGrass shader.
With vanilla settings same results (no CSP). I guess that's no it.

I've checked the other obvious stuff such as .kn5 names called in models.ini, no luck.
It's been 2 days, no fix found yet despite looking "everywhere". (I hate looking like a noob... but getting a bit desperate)

All my tree walls in the editor ... gone in game. Any advice welcome!
View attachment 4037

GrassFX guesses what is KsGrass and automatically hides it...

One way to disable this auto guessing is to insert a line in the ini that tells GrassFX what to actually hide:

ORIGINAL_GRASS_MATERIALS= "your old 3d grass material goes here"

 

[Patrice COte]

OK, looks like the CSP auto grass remover is to blame. Thanks for the advice guys!
I switched to KsTree and everything is back.
However I do prefer the look with grass shader.
Is there a way to tell CSP to ignore specific objects or material for grass FX? Seems to have something similar with other settings. (no other 3D grass at the moment, I suppose could create a dummy / decoy one so CSP can remove it and leave my trees alone)

 

[Johnr777]

OK, looks like the CSP auto grass remover is to blame. Thanks for the advice guys!
I switched to KsTree and everything is back.
However I do prefer the look with grass shader.
Is there a way to tell CSP to ignore specific objects or material for grass FX? Seems to have something similar with other settings. (no other 3D grass at the moment, I suppose could create a dummy / decoy one so CSP can remove it and leave my trees alone)

The line I wrote above

 

[Patrice COte]

What I meant, can we tell CSP what NOT to hide?

While on topic, since the grass FX is the future, is it even worth while to go thru the trouble of making custom 3D grass in the first place?

 

[Johnr777]

What I meant, can we tell CSP what NOT to hide?

While on topic, since the grass FX is the future, is it even worth while to go thru the trouble of making custom 3D grass in the first place?

One more time , this line

ORIGINAL_GRASS_MATERIALS= "your old 3d grass material goes here"

it will make grass-fx ONLY hide that material.

Making manual grass or not is really up to you... some of us have some projects that are going to be released soon, and grass-fx is still very buggy and IMO not looking that good, so we are still going old school, for now.

 

[Patrice COte]

OK, sorry if I looked slow, I just didn't have any 3D grass at the moment. Thanks for your patience!!!
I'll go the old school way for release version. Meanwhile, the FX shader gives a glipse of what it could look like, which is good to keep motivation.

 

[Johnr777]

OK, sorry if I looked slow, I just didn't have any 3D grass at the moment. Thanks for your patience!!!
I'll go the old school way for release version. Meanwhile, the FX shader gives a glipse of what it could look like, which is good to keep motivation.

It’s really good practice, I enjoy doing it the old way

 

[DrPenguin]

I've been working on my AMP project lately, but it's been months since I've brought a new version in-game. I don't know what I messed up, but when I load the game up and I'm at the session start screen the camera is part way through the map and things are swaying gently side to side. Click drive and I'm barrel rolling slightly above the circuit. I've spent the past few hours reading around the forums and I've tried the spawn cubes at various heights, checked scale, rotation, naming etc and I'm still having the same issue. I'm sure it's something simple, I just can't figure it out haha. The map loads the same way in ksEditor and I have to PgUp to come back above the surface.

 

[fughettaboutit]

seem like spawn point is at 0,0,0
this happens when ac cant find your ac_objects
you named the things correct?

AC_HOTLAP_START
AC_START_0
AC_START_1
...
AC_PIT_0
AC_PIT_1
...

and set correct count in
"ui\ui_track.json" ?
...
"pitboxes": "24",
...

ok the pic shows that at least AC_PIT_0 is ok

 

[MGMetroDave]

Hi @DrPenguin do you have a hotlap start object in your game? Does it do the same if you try to start from the pit lane too?

 

[DrPenguin]

Thanks for the replies guys. I have 2 pit objects, 2 start objects and L/R timing objects at start finish. My ui_track.json has 2 pit boxes. I don't have a hotlap start object. I'm loading from CM in practice mode, start from pits selected.

 

[fughettaboutit]

i have had some problems with those things too sometimes
i ended up copying them from other tracks
maybe read this https://assettocorsamods.net/threads/build-your-first-track-basic-guide.12/
starting with
"These objects can be simple CUBES..."
and make sure you click the spoiler...

 

[MGMetroDave]

Does it happen if you choose a different car, especially a Kunos one?

I've encountered problems in the past if the objects aren't rotated correctly. The X, Y and Z don't point where you'd normally have them in blender. I can't currently recall which way they're supposed to point.

 

[DrPenguin]

I've been over that guide a ton today. I've tried with the RSR GP3 car and a Kunos car, the Evora GX. I've attached a screen in blender. I've tried heights from .01m above ground through to 2m above ground. In the screen they're a bit less than 1m above the pitlane surface. Taking that in game with the GX when I hit drive the front end slowly dives for a few seconds, then resets and does the same again.

With Z at 0 as in the troubleshooting post from Luchian in the first track guide the car loads up facing the wrong direction. I've looked at the FBX export settings and matched them to the recommended as well.

 

[DrPenguin]

I'm thinking it's likely something silly I'm missing with tired eyes and brain. I'll have another look over tomorrow and if I can't figure it out I'll pull in the objects from the older working cut and test that. MG, fughettaboutit, thanks a lot for your help this evening!

Edit- Could the 'Set Origin To-' setting being wrong be causing these issues? I've noticed on some of my objects the little yellow dot is centered in the object, on others it shows in the area where the in game screenshot I posted is. I haven't learned much about origin yet so I haven't intentionally used 'Set Origin To', but it's certainly possible I've accidentaly changed it.

 

[MGMetroDave]

Hmm, I'm sure we'll get to the bottom of this

Yes good idea to set origin to geometry in most cases. That could indeed be the problem if your car seems to start at 0,0,0 despite your pit object being elsewhere. Try selecting the pit object then ctrl-alt-shift-C I think then choose origin to geometry.
Whenever you apply position to an object it sets the origin of that object to 0,0,0. Maybe that's what's happened.