From: Magne D. <ma...@gm...> - 2010-09-28 20:41:21
|
Hi, I did a little test with adjusting the start positions in The Island by adding an empty with the properties "start" and "position" with a string value of 4. Unfortunately, all karts now face backwards when starting the track. Any idea on what went wrong? Thanks for the help. |
From: Magne D. <ma...@gm...> - 2010-09-30 13:55:44
|
On 28. sep. 2010 22:41, Magne Djupvik wrote: > Hi, I did a little test with adjusting the start positions in The > Island by adding an empty with the properties "start" and "position" > with a string value of 4. Unfortunately, all karts now face backwards > when starting the track. Any idea on what went wrong? > > Thanks for the help. Okay, got this answered on IRC, thanks a lot! Now it works, but I face these kinds of errors: Warning: quad has wrong orientation: p0=4.487787 -0.494440 -8.999015 p1=-1.023237 -0.505088 -7.073626 The quad will be swapped, nevertheless test for correctness - quads must be counter-clockwise oriented. The minimap gets messed up as well, and it might answer why AI is driving particularly silly, too. What's the easiest way to fix this situation? And, btw, I tried adding a Blender camera with the property 'fixed' and the property 'start'; I see no difference at all. Must the camera be placed closer to the track, and/or how do I specify the area it affects? Thank you. |
From: Joerg H. <jo...@lu...> - 2010-10-01 01:21:45
|
Hi, ... > Okay, got this answered on IRC, thanks a lot! Now it works, but I face > these kinds of errors: > Warning: quad has wrong orientation: p0=4.487787 -0.494440 -8.999015 > p1=-1.023237 -0.505088 -7.073626 > The quad will be swapped, nevertheless test for correctness - > quads must be counter-clockwise oriented. We have already found and fixed that problem - there was a duplicated vertex causing havoc everywhere. The latest version of the track exporter now shows a popup window with a warning, and prints details on the console which should make it easier to diagnose those problems. > The minimap gets messed up as well, and it might answer why AI is > driving particularly silly, too. Yes, indeed. > What's the easiest way to fix this situation? > > And, btw, I tried adding a Blender camera with the property 'fixed' and > the property 'start'; I see no difference at all. Must the camera be > placed closer to the track, and/or how do I specify the area it affects? You have to set the 'type' property to 'fixed' (or 'ahead'), and the 'start' property to the radius of the circle where you want it to get activated. Cheers, Joerg |