Open proof0zone opened 3 months ago
Send me your G-Code File at : sb53systems@gmail.com
Got the same error when hitting the Generate button. Do you want me to send the unaltered g-code file, since there is no output yet, or is there?
Sorry for the late reply, you can send me by email the Original G-Code, I'll let you know if I discover anything.
Salim.
Restart your computer, or manually close the CMD console in Task Manager.
Is this problem still present?
Is this problem still present?
Sorry, I couldn't find the time to retest it, but I'm going to today and will report.
Know that a new version was released today :
https://github.com/sb53systems/G-Code-Flow-Temperature-Controller/releases/tag/V1.1Beta
I just got the issue myself today
@Nathan22211 This problem occurs with the integration of Klipper_Estimator with this script, you have to reboot your computer or close manualy all CMD Consol in the Task Manager.
Let me know if you manage to resolve this issue.
Best regards,
Salim
killing the console host nor rebooting fixed it.
I do get an error about a float needing to be an int in french before this occurs though
I do get an error about a float needing to be an int in french before this occurs though
I thought this error is fixed in the current version of the script!
If you are on the latest version and this problem persists, send me the original G-Code and a screenshot of the error message.
I'll do my best to resolve this essue.
Best reguards,
Salim
@Nathan22211 Another script modified the G-Code before this one, the Script is not yet optimized to avoid comments added in the same line.
Try one of these solutions temporarily:
I will try to solve this problem soon in the future updates. If you need more support, contact me in Discord: sb53systems
Best reguards,
Salim
yeah just tried it straight out of orca slicer with it being the only post script and it still errors. I am a few versions behind and on a fork so maybe I should try to use mainline
@Nathan22211 Another solution: use flow compensation integrated into Orcaslicer
yeah just tried it straight out of orca slicer with it being the only post script and it still errors. I am a few versions behind and on a fork so maybe I should try to use mainline
@Nathan22211 Yeap, Forked version can cause essues, i recommend you use an official version.
yeah just tried it with the latest mainline beta and still the same issue when running it from orca, and I'm pretty sure I turned verbose off so there shouldn't be as much of a comment issue. also it doesn't seem to find the extruder and used filament in the g code
yeah just tried it with the latest mainline beta and still the same issue when running it from orca, and I'm pretty sure I turned verbose off so there shouldn't be as much of a comment issue. also it doesn't seem to find the extruder and used filament in the g code
Send me the original G-Code with the error screenshot
From where (which parameter) this comments come from !
I'm using Orcaslicer v2.2.0-beta2!
verbose gcode if I recall correctly. must have left it on by accident, though some other post scripts need it turned on so there's already a conflict there.
turning verbose off fixes it but I'd definitely make it practically ignore anything after a ; in a line within the gcode blocks. some scripts, such as gradient infill, need it turned on to work properly
@Nathan22211 I will try to prepare an update as soon as possible, thank you for your contribution.
Let me know if you found otherthing to improve.
Hey, tried with a simple benchy, and keep getting this