Macros not generating?

[Shizutea]

I've noticed since the most recent update, the macros will stop generating partway through, or not generate at all at the beginning. Restarting the craft does not fix this, nor does restarting the client or switching classes/crafts.

[WorkingRobot]

Do you mean for the synth helper, or elsewhere? Do you have a screenshot or recording I could look at, too?

[Roflskippy]

I believe they mean the Synth Helper. This has happened to me too, starting a craft leaves the Synth Helper blank, and nothing gets it going, not Retry or quitting and starting the craft again.

[Shizutea]

Yup, that's exactly what I meant! Sorry I didn't get back sooner, but it had stopped happening for a little bit, and then it started again this morning.

[WorkingRobot]

Which recipes does this happen on, and what are your stats and settings? Do you see any craftimizer errors when you open /xllog?

[Shizutea]

11:19:32.858 | ERR | [WindowSystem] Error during Draw(): Craftimizer Synthesis Helper###CraftimizerSynthHelper
System.NullReferenceException: Object reference not set to an instance of an object.
at Craftimizer.Simulator.SimulationState.get_HQPercent() in /work/repo/Simulator/SimulationState.cs:line 27
at Craftimizer.Windows.SynthHelper.DrawMacroInfo() in /work/repo/Craftimizer/Windows/SynthHelper.cs:line 414
at Craftimizer.Windows.SynthHelper.Draw() in /work/repo/Craftimizer/Windows/SynthHelper.cs:line 264
at Dalamud.Interface.Windowing.Window.DrawInternal(DalamudConfiguration configuration) in C:\goatsoft\companysecrets\dalamud\Interface\Windowing\Window.cs:line 346

This is the error I found in the log. The recipes seem random; when it happens it's on ALL of them, across all classes. But I noticed if I select an ability manually, it gets it going again. Stats are (generally) Craftsmanship 4936, Control 4837, CP 611

[Nitrousoxide]

I have this happen on the first time I use it after logging in. Manually clicking on the "retry" button gets it working for the rest of the login session, but the issue repeats next new login.

If this is the intended behavior can you add a "retry" command so it can be macro'd up? It's a bit of a pain if you're on a controller and have to start the mouse simulator to click that retry button every new login.