Paths causing TGB to crash

#1 Can you post example script please so I can repro this?

#2 The problem seems to go away when I define the path in code with the %path = new t2dPath function, rather than drawing them in the editor. That'll work fine - I was just using the editor drawn path for testing anyway.

#3 Sounds odd. How are you deleting your objects?

(By the way, TGB 1.5 added path callbacks!)

#4 Gah - I spoke too soon, it's happening again.

I'm deleting my objects in the onWorldLimits callback with %this.safeDelete();

Will the new TGB be able to import and run current projects?

#5 @ Neo : here's the function where I create my wave of enemies and their path:

function levelManager::spawnPathWave(%this, %waveNumber, %numberOfEnemies, %delayTime, %node0, %node1, %node2, %node3)
{
	// create the wave of enemies
	
	%newWave = new t2dSceneObject()
	{
		class = enemyWave;
		numberOfEnemies = %numberOfEnemies;
	};
	
	// create the path for them to follow
	
	%newWave.Path = new t2dPath()
	{
		scenegraph = $pDrone.scenegraph;
		pathType = "catmull";
	};
	
	%newWave.Path.addNode(%node0, 0);
	%newWave.Path.addNode(%node1, 1);
	%newWave.Path.addNode(%node2, 2);
	%newWave.Path.addNode(%node3, 3);
	
	
	// create the enemies in the wave
	
	for (%i = 1; %i <= %numberOfEnemies; %i++)
	{
		%newWave.enemy[%i] = %this.spawnEnemyChopper(%newWave);
		%newWave.enemy[%i].parentPath = %newPath;
		%newWave.enemy[%i].setPosition(800, 0);                       
		%newWave.enemy[%i].schedule((%i -1) * %delaytime, "attachToPath", %newWave.Path, 3); 
	}
		
	%this.wave[%waveNumber] = %newWave;
}

and here's how I attach them to their path:

function enemy::attachToPath(%this, %targetPath, %endNode)
{
	%targetPath.attachObject(%this, %this.speed, 1, 0, %endNode, "wrap", 1, true);
}

#6 K looking into it

#7 I created a spline path and mounted a sprite to it, setting its world limit to kill made sure that the path would take it outside its world limit. Works fine, sprite goes outside world limit and is removed.

I suppose I should have asked what version you are using as I am testing with beta 3 and this might have been fixed if youre using an older version?

#8 Thanks for looking in to it Neo - I'm using TGB 1.1.3

The problem seems more complex than I first thought. I'm spawning a wave of 4 enemies who travel along the spline. If I shoot and kill the first 2 enemies then TGB crashes, or if I let them wander off the screen into their world limits, crash. However, if I shoot the 2nd two enemies and let the first 2 hit their world limits, the game does not crash. Unfortunately I can't use any echo commands to debug as it's just crashing with the standard windows 'send error report' crash. Perhaps I need to look into running a debug build of TGB and stepping through the code. I was hoping I wouldn't need to resort to that yet :-(

#9 Any particular reason you're sticking with 1.1.3 and dont want to move to beta3?

My guess is that it might be related to the bug where objects being updated after they were destroyed which causes a crash.

I'll look into it and let you know how it goes.

#10 Neo - I'm just getting started with Torque, this is my first program, so I thought I'd stick with the released version as the documentation would be more accurate than the Beta version. I guess I'll switch to the new version once it's ready.

#11 I have this same problem, but no fix. I think it has to do with deleting an object attached to a path and the path not *realizing* it... which would be a great theory, if it happened every time- except that if your bug is like mine, it is consistent only in that it always eventually occurs.

What you may want to do, and what I haven't had time to, is give each object on the path a reference to the path and in their OnWorldLimit callback have them explicitly detach themselves from the path before they delete themselves. I believe that deleting the path as well (and adding a or cloning a new path with each object instantiation) may also solve the problem, but again, I have been working on other things and have not had time to try it out.

Lemme know if it works!

#12 Samuel - I tried detaching the objects from the path before deleting them, but the crash happened exactly as before.

I've given up on paths and have got around the problem by using a combination of MoveTo and mounting with a weak mount force to get smooth movement. If paths are more stable in the new version (and it sounds like they are) then I'll probably revisit them then.

#13 Sounds good. If I manage to figure out a fix (don't hold your breath) I'll post it somewhere or other.

#14 Deleting of a object in onReachNode callback isn't such a good idea.
Becuase the way how the engine walks through an attached objects, so even if you detach object and delete them before the callback returns you get a crash(probably). Solution is simple. Use schedule function with time 0 and delete your object in another function. (you should detach object first in callback though)

#15 Thanks Igor, I'll give that a shot next time I use paths.