Can G-CodeExplorer change my file?
No. The open document is always read, never written. Exports and inserted pauses or filament changes produce new files, wherever you choose.
Support and assistance
Welcome to the G-CodeExplorer support page. In the app, Help › G-CodeExplorer Support leads here. If your question isn’t answered below, write to us: we read every message.
Support
No. The open document is always read, never written. Exports and inserted pauses or filament changes produce new files, wherever you choose.
No. It shows a simulated preview, without infill or real speeds, and offers to send it to your slicer; the exported G-code is then offered in the window.
It shouldn't be: “Estimated time” uses the time announced by the slicer when the file contains it. The “With acceleration” row is a second calculation, made by the app with the acceleration of the chosen printer; it is mostly useful when the file announces nothing. If the printer in the “Studio” tab isn't yours, this calculation is off: choose the right one.
Prusa's compressed format isn't read. Export a regular .gcode file from PrusaSlicer.
Only the first one is replayed, and the “Summary” tab says so. Export each plate separately from Bambu Studio to replay them all.
The file doesn't indicate its move types (wall, infill, bridge), or it is an STL. The other risks are still analyzed. Most slicers write these types by default: check that the option hasn't been turned off.
The thresholds are cautious, and your machine may do better. Set up the “Custom” profile in the settings, “Risk analysis” tab, then choose it in the “Material” menu of the “Analysis” tab.
It appears only if the analysis has found at least one critical risk: with no critical risk, it would have nothing to stop at.
Check that the printer is on and on the same network as the Mac, that the address in the settings is right (including the port for Moonraker if needed), and that you allowed local network access when macOS asked. You'll find this setting in System Settings, under Privacy & Security, Local Network.
The app compares the name of the open file with the one the printer is printing. Open the same file, under the same name, as the one sent to the printer.
No. Live follow is read-only, by design: the app sends no commands to the printer.
On this Mac: the settings in the app's preferences, the workshop journal in a file in its data. Nothing is sent anywhere else.
To help us reproduce the problem as quickly as possible, please include in your message: