Fusion outputting G1 F0. and No Rapid Moves

[zachariah.lyle.cavish]

After an update in Feb, my fusion is outputting NC code littered with F0.  Below I have the beginning of a program where the difference can be seen.

BEFORE UPDATE

M5
T9
S24000 M3
G54
G0 X4.275 Y-1.625
Z0.35
Z0.3
G1 Z0.085 F50.
G18 G3 X4.15 Z-0.04 I-0.125 K0. F100.
G1 X4.
X0.
X-0.15
G3 X-0.275 Z0.085 I0. K0.125
G0 Z0.3

AFTER UPDATE

M5
T9
S24000 M3
G54
G0 X4.275 Y-1.625
G1 Z0.35 F0.
Z0.3
Z0.085 F50.
G18 G3 X4.15 Z-0.04 I-0.125 K0. F100.
G1 X4.
X0.
X-0.15
G3 X-0.275 Z0.085 I0. K0.125
G1 Z0.3 F0.

As you can see in the new pgm, all rapids after the first one look to be replaced by G1 (xyz) F0.

Both programs are using the exact same setup, geometry, toolpaths, and post processor. The only difference is that one file was created before Feb, and the latter I just created today. Also note, I can go to the old file, post that program again, and it comes out fine. The problem only exists in new files. 

Is anyone else experiencing this issue, or have a good solution? Right now I am just posting and then replacing all F0. with F500. Not a huge issue, but annoying nonetheless.

Thanks

[seth.madore]

Would you be able to share your Fusion file here?
File > Export > Save to local folder, return to thread and attach the .f3d/.f3z file in your reply.

[zachariah.lyle.cavish]

I got you

Attached is the file before/after

[seth.madore]

What post processor are you using?

[seth.madore]

With the Haas NGC post processor, I'm not seeing the issue, everything is coming out with an F100. or F50.

If I turn on "Use High Feed" for the G0's, it gives me a G1 xx F650.

[zachariah.lyle.cavish]

Here is the post I use

[seth.madore]

If you respond by email, attachments do not come thru, you need to respond via the forum.

[zachariah.lyle.cavish · Accepted solution]

Oh, now I see the problem. Under "built-in", all my new files are set to use high feed instead of preserve rapid. IDK if I mistakenly changed this or if it was update that changed the default, but anyways, putting it back to preserve rapid solves my problem. 

Thanks for your attentiveness regardless

have a good day ✌️