Tool Orientation bug?

[GalenYMW8K]

Since latest update, I keep having issue where my post is not posting the correct tool orientation. in fact, it isn't posting TWP / DWO at all. I have never had this issue until now. 

CAM has tool orienation, everything looks correct, posted program just ignores it. I am trying to find why, when I have 5 toolpaths with same tool, one will randomly not post. I think it may be because I am not always selecting all axes, (selection may have "no selection") even though appearance in CAM is correct. Otherwise no idea. Usually happens when I have like 2d contours followed by drilling and the drilling doesn't post right. This has worked in the past but the only thing I can think of why it wont work. If I post from the incorrectly posting toolpath forward, it will post fine. 

I've been doing this many times daily and never had any issues until latest update. Now at least once each program I post my tools are trying to plunge through my table. I think is bug. 

[seth.madore]

What post processor are you using, and do you have a Fusion file you can share that is exhibiting this behavior?
Are you on Mac or PC?

[GalenYMW8K]

Heavily modified fanuc post. Never had this issue until very recently, it was working just fine before last update. Every time I drill with tool orientation, it always cancels TWP (G69) , regardless if next tool path is using G68.2 or not. The next tool does not post a G68.2 because it for some reason does not realize it was canceled with a G69. 

The issue happens in my post here:

if (words.length > 0) {

writeBlock(words.length); //I temporarily added this line to see what it was doing, and it would always output a 1
writeBlock(gMotionModal.format(0), gAbsIncModal.format(91), gFormat.format(properties.useG30 ? 30 : 28), words); // retract
writeBlock(gAbsIncModal.format(90));
writeBlock(gRotationModal.format(69)); //I added some unique code at one time here to identify it in the g code program, this is the G69 that is posting that often times shouldn't
forceWorkPlane(); //I added this to work around the issue as a temporary fix}