Triple spline
by Eric Kinkead · in Torque Game Builder · 04/26/2007 (4:18 pm) · 9 replies
Private forums?? I've been posting all my crap about my questions in the public forums.. lol. sorry about that. I'll moved it here...
This used to be just 1 path working nicely. Somehow my path trippled itself.
It still works nice. but its so strange, placing an object on those boxes now I have the unwanted choice of placing it on 2 boxes and it has 3 lines coming out of it.
Might be kind of hard to see in the picture, but you can see it. Those arent 3 different path objects, its one path that has the properties of containing 3 paths in-itself. Not a serious error because the paths are pretty simple to make and set up. I can just delete it and create a new one.
But I am curious as to why it did this and figured I should report it.
This used to be just 1 path working nicely. Somehow my path trippled itself.
It still works nice. but its so strange, placing an object on those boxes now I have the unwanted choice of placing it on 2 boxes and it has 3 lines coming out of it.
Might be kind of hard to see in the picture, but you can see it. Those arent 3 different path objects, its one path that has the properties of containing 3 paths in-itself. Not a serious error because the paths are pretty simple to make and set up. I can just delete it and create a new one.
But I am curious as to why it did this and figured I should report it.
#2
04/29/2007 (8:40 am)
Hmm... i can try, but remember i am a designer/artist so i will probably suck at this. what .cs file should i be looking in for this line? 
#3
04/29/2007 (10:54 am)
The data/leves/levelName.t2d file that the level is created -- to find it easier, give the path a name in the Edit tab under Scripting, and it will look like this:new t2dPath(PathName)
{
....
};
#4
yea, here it is.. to big to put here totally... but it looks like a heck more nodes than it needs...
05/03/2007 (2:04 pm)
Quote:
new t2dPath() {
pathType = "CATMULL";
pathModeEnum = "WRAP";
canSaveDynamicFields = "1";
position = "-147.097 -360.122";
size = "75.197 66.164";
Layer = "1";
MountRotation = "107.096";
AutoMountRotation = "1";
mountID = "23";
node0 = "-184.487335 -380.229248 0.000000 10.000000";
node1 = "-165.885620 -393.017944 0.000000 10.000000";
...
node99 = "-184.278946 -358.180481 0.000000 10.000000";
nodeCount = "160";
object0 = "17 7 6 10.000000 1 1 0.000000 -1 WRAP";
objectCount = "1";
};
yea, here it is.. to big to put here totally... but it looks like a heck more nodes than it needs...
#5
the first 2 nodes are so close together, it's not even funny ... ;)
looks like a bug to me ... unless you have code in your scripts that works with the nodes themselves, that could have somehow duplicated them ... code in your scripts can affect the scene in level builder when you exit the 'test play' .... which is an unfortunate side effect of test playing, at least with the 1.1.3 and below versions ... 1.5 does not have this issue, to my understanding ...
05/04/2007 (7:50 am)
Eric -- according to the editor screenshot you posted, you only have two nodes ... and your code has 100 ;)the first 2 nodes are so close together, it's not even funny ... ;)
looks like a bug to me ... unless you have code in your scripts that works with the nodes themselves, that could have somehow duplicated them ... code in your scripts can affect the scene in level builder when you exit the 'test play' .... which is an unfortunate side effect of test playing, at least with the 1.1.3 and below versions ... 1.5 does not have this issue, to my understanding ...
#6
We noticed some similar issues when we moved some of our levels over from 1.1.x to 1.5. Deleting the extra nodes and saving the file again is about as good a solution we came up with.
05/22/2007 (12:38 pm)
Eric; Are you using 1.5?We noticed some similar issues when we moved some of our levels over from 1.1.x to 1.5. Deleting the extra nodes and saving the file again is about as good a solution we came up with.
#7
05/22/2007 (1:03 pm)
No i am using v1.1.3 or yea x in this case.
#8
05/22/2007 (1:08 pm)
It may be something in 1.1.3 that is the main issue (just that we didn't notice it until we moved to 1.5). In either case, just wanted to mention I've seen this happen too. So, yeah, it's a bug somewhere, not entirely sure WHERE though since it only seem to happen quite rarely. 
#9
1.1.3 had a very unfunny bug which cloned the path along with the parented object which perhaps happened here as well.
05/22/2007 (11:36 pm)
In 1.1.3: Did you have something mounted to the path and copy that mounted thing?1.1.3 had a very unfunny bug which cloned the path along with the parented object which perhaps happened here as well.
Associate David Higgins
DPHCoders.com