"As you can see, they are suffering from some weird lighting issue."
could also be that ksAmbient and ksDiffuse are wrong, maybe use 0.2 and 0.3
could also be that ksAmbient and ksDiffuse are wrong, maybe use 0.2 and 0.3
TUTORIAL Build your FIRST track - BASIC GUIDE
- Thread starter luchian
- Start date
LilSKi
Well-Known Member
Trees should be using the proper object naming which makes the blender normals irrelevant.
http://www.racedepartment.com/threads/proper-technique-in-track-making-plus-tips.122794/#post-2397224
http://www.racedepartment.com/threads/proper-technique-in-track-making-plus-tips.122794/#post-2397224
oh alright, thanks
Pingypoker
New Member
Trying your script, it did not make a difference. Changing ksAmbient and ksDiffuse values also made no difference.
The only thing that 'fixes' my issue is using a different shader, such as KsGrass or KsPerPixelAT. Should I accept defeat and switch to a different shader?
The shadows seen in this picture are from the "top shadows for trees" tutorial. I am not worried about these, I know they are not causing my shading issue because it still persists when disabled.
Pingypoker
New Member
I think I figured it out. The mesh of my Y trees was all wrong. I had it in 2 parts instead of 3, if that makes any sense
.
Did you read the post earlier that suggests naming the trees correctly and setting their pivot points to the bottom? Its the only way they are going to look correct.
Pretender42
New Member
Hello,
First, thanks for the well explained guide, it's a huge help when building tracks !
I'm currently working converting an rF2 track to AC, I made almost everything working, but one thing I struggle with is pitbox orientation. I've read that object local Y must point up, and object local Z points forward. Currently, my AC_PIT_0 is sitting like this :
As it is, it is working fine in AC. But everytime I try to rotate it to make object local Z axis point the way I want, when I load the track in AC, my car crashes on the ground (or worse). I've tried moving the box up, down, many rotation angles, exporting with +Z Forward,... but I'm not able to make it work pointing the way I want.
Another (maybe related ?) issue I've saw is that, on the working version, when I go to pits, I can see the red markers delimting the edges of the pit box far, far away, like the pitbox is the size of a building !
If anyone as an idea what I'm doing wrong ?
First, thanks for the well explained guide, it's a huge help when building tracks !
I'm currently working converting an rF2 track to AC, I made almost everything working, but one thing I struggle with is pitbox orientation. I've read that object local Y must point up, and object local Z points forward. Currently, my AC_PIT_0 is sitting like this :
As it is, it is working fine in AC. But everytime I try to rotate it to make object local Z axis point the way I want, when I load the track in AC, my car crashes on the ground (or worse). I've tried moving the box up, down, many rotation angles, exporting with +Z Forward,... but I'm not able to make it work pointing the way I want.
Another (maybe related ?) issue I've saw is that, on the working version, when I go to pits, I can see the red markers delimting the edges of the pit box far, far away, like the pitbox is the size of a building !
If anyone as an idea what I'm doing wrong ?
Pretender42
New Member
Well... now I feel dumb, I spent an entire evening searching online a solution, and read many pages in this thread and others, but looks like i havn't searched hard and well enough
Anyway, thanks a lot for giving me the answer, it was indeed the issue, after scaling all my objects to 100, applying scale then exporting with Apply scaling FBX All set, now it works fine !
Once again, sorry for not finding what was already explained and many thanks !
Anyway, thanks a lot for giving me the answer, it was indeed the issue, after scaling all my objects to 100, applying scale then exporting with Apply scaling FBX All set, now it works fine !
Once again, sorry for not finding what was already explained
and many thanks !
I would not care if this shadow is not there in AC itself.
That's the problem. This shadow is also in the game.
set shadows for all the other stuff in your track, there is none
maybe that single shadow over you goes away then - just kidding, i have no idea where it comes from, but indeed you dont have shadows in your pic
if you use ksEditor, just edit your persistence file "...fbx.ini" and replace all CAST_SHADOWS=0 with CAST_SHADOWS=1
maybe that single shadow over you goes away then - just kidding, i have no idea where it comes from, but indeed you dont have shadows in your pic
if you use ksEditor, just edit your persistence file "...fbx.ini" and replace all CAST_SHADOWS=0 with CAST_SHADOWS=1
Oh, thanks. But now I have a problem. ksEditor takes too much time importing the fbx file.
you mean with shadows now on? but it loads the track or crashes?
It keeps loading the track a lot of time. It looks like if it never ends.
well then undo what you did, make it cast_shadows=0 again and only set it for the objects you want in ksEditor...
I mean that when I import the FBX file, it takes to much time. It doesn't load.
anything above 100MB per fbx maybe too much for ksEditor, you may have to split your objects into multiple fbx/kn5's
Share this page
Support the site
