T3D MIT Trigger Bug

I am having some unusual problems with the Triggers in the current release of T3D MIT.

When creating triggers in the mission editor as usual, only some of them are working. My triggers are all the exact same, with the exception of the position. Same datablock, same scale values, etc etc.
I have six triggers in the level, and I can only get four of them to work, at best.

Implementing the fix described here: (in post 4)
https://www.garagegames.com/community/forums/viewthread/135658

Did nothing until I also made the same change in the "ConsoleSetType" function here:

U32 numArgs = dSscanf(argv[0], "%g %g %g %g %g %g %g %g %g %g %g %g",
                         &origin.x, &origin.y, &origin.z,
                         &vecs[0].x, &vecs[0].y, &vecs[0].z,
                         &vecs[2].x, &vecs[2].y, &vecs[2].z,//here
                         &vecs[1].x, &vecs[1].y, &vecs[1].z);//and here

This cause the two triggers that were previously not working to start working again, but... the four that were working stopped working...

This is clearly an issue with the winding order of the polys being used to build up the trigger object. What seems to be happening is that sometimes a trigger is created with reversed polys, causing it to fail.
I have tried creating the triggers in script, copying working triggers, etc, but to no avail.
My trigger code is very simple:

datablock TriggerData(LowCoverTrigger)
{
   tickPeriodMS = 100;
};

function LowCoverTrigger::onEnterTrigger(%this,%trigger,%obj)
{
			echo("ENTER: " @ %obj);
}

function LowCoverTrigger::onLeaveTrigger(%this,%trigger,%obj)
{
	echo("EXIT: " @ %obj);
}


   new Trigger() {
      polyhedron = "-0.5000000 0.5000000 0.0000000 1.0000000 0.0000000 0.0000000 0.0000000 0.0000000 1.0000000 0.0000000 -1.0000000 0.0000000";
      dataBlock = "LowCoverTrigger";
      position = "8.38168 0.249492 238.899";
      rotation = "1 0 0 0";
      scale = "4 1 5";
      canSave = "1";
      canSaveDynamicFields = "1";
       triggerOff = "0";  
   };

As I said, there are six triggers, all identical to the one above except for the position, only four (or two) work.

I'm not sure where to go to solve this, but I'm fairly confident in calling it a bug, I can't see anything I could have done that would cause this.