2.5.0 beta1 Post-Processor issue #8766
Comments
|
In your 3mf, there is no post-processing entry? If you need an output.gcode, then you'd have to use a script in between to switch parameters around. To get rid of "Invalid Data" I just check/uncheck the BRIM checkbox - annoying as hell, I know. |
|
Hi.
thank you for your response.
I keep trying to save it with that post-processor, but every time I
load it, it doesn't show up. Not sure why, not a big deal though.
The videos I've seen (and web pages I've visited) on this topic (using
arcwelder in PrusaSlicer) specfically state that no arguments are
recommended or required. I did post on the forums before filing this
bug, and specifically asked if I should using any arguments... and was
told 'no'.
I will take a look at this and attempt to leverage your advice when
I'm able to sit with it for a few moments.
Thanks again.
…-Chris
Quoting foreachthing ***@***.***>:
In your 3mf, there is no post-processing entry?
This is my line, in PS (2.5.0-rc1), of post-processing:
`"c:\dev\ArcWelderLib\x64\Release\ArcWelder.exe" -y -t=0.02 ;`
PS then adds the name of the gcode file at the end of that line.
That works very well on my computer ...
If you need an output.gcode, then you'd have to use a script in
between to switch parameters around.
Check `ArcWelder --help` for valid parameters.
--
Reply to this email directly or view it on GitHub:
#8766 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
|
Hello, Could you check the PATH? Try use |
|
That would set it to my home directory... it is not in my home directory... it is straight under /opt |
|
I cannot help but notice that your command isn't using arguments either. You have two switches that have nothing to do with positional parameters (which input and output are for the ArcWelder command).. and of course, you are using windows. It is possible that this problem doesn't manifest in Windows at all, it may just be in the Linux version. The other thing is that I do have the brim box unchecked... but it still happens. There is still something broken here, and I seriously doubt it has anything to do with ArcWelder. I'd be willing to try a simple script, if someone has one I can use, just to demonstrate that ArcWelder is not the culprit here. |
|
Hello, @m00nglum, I think that the problem will be caused by the incorrect PATH, missing permission, etc ... I already checked with my Ubuntu and latest PrusaSlicer on board - all works fine on my side. |
Yes, input output are the same in my case. If you need input output to be diffetent, you'll need a script in between to switch the positional arguments around. |
|
It isn't. Like I said, I can do this from the command line as my unprivileged user, and it works just fine (same user I run PrusaSlicer with)... and I'm using the beta, not the latest. I run it with the full path: /opt/aw/bin/ArcWelder -- no problems. It is only in Prusa Slicer that it doesn't work. It is not an ArcWelder issue. If your is working, what do you have in the post-processing text box? Where is your ArcWelder executable located? Under your home dir? @foreachthing |
|
I should probably also mention... I have tried this with other executables as well, like /usr/bin/xterm and /usr/bin/kwrite -- it does not matter what I put in the post processing text box -- it gives me the same error. I even tried just "echo". I've also tried this on 2.4.2 and the same thing happens. I only see one of two possilities here... a bug in the PS code, or I'm missing a package that PrusaSlicer is counting on... but I have no idea what that would be, if the latter was the case... |
@m00nglum (I also checked with 2.5.0 Beta1 - also works without problem) |
|
@Jan-Soustruznik I'm going to go out on a limb here, and guess that you are using Gnome, Cinnamon, or some other GTK desktop system, am I correct? I'm using KDE, so it is possible that this was packaged on a system with GTK libraries, and I'm missing one of them. I'm using KDE Neon, which is just Ubuntu with the latest KDE offerings. Can you confirm this please? Thanks. |
|
I think the fix is to change the default value for SHELL to "/bin/sh" instead of "sh" You can reproduce the issue just by using /bin/true as the post-processing script and setting the SHELL environment variable to "sh" vs "/bin/sh". |
|
I worked around this issue by creating a startup script for PrusaSlicer that exports that environment variable. Thanks to Jbauer for tipping me off to this issue. I couldn't have guessed that was the issue. |
|
I think the fix is to change the default value for SHELL to "/bin/sh"
instead of "sh"
Thanks, that makes sense. I don't know where I got that code snippet, I
suppose you are right.
po 29. 8. 2022 v 19:52 odesílatel m00nglum ***@***.***>
napsal:
… Reopened #8766 <#8766>.
—
Reply to this email directly, view it on GitHub
<#8766 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIZYVDZ66ZJWTXZWFODV3T2GZANCNFSM57W7HMWQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
thanks @jfbauer432 for pointing the problem out.
|
The issue should be fixed by 87a5116 in 2.5.0-rc2 (which will be released later today). @m00nglum , we will be glad if you retested it. @jfbauer432 , thanks for pointing the problem out. Closing. |
|
Thank you. I will!
Quoting Luká? Mat?na ***@***.***>:
… The issue should be fixed by 87a5116 in 2.5.0-rc2 (which will be
released later today). @m00nglum , we will be glad if you retested
it. @jfbauer432 , thanks for pointing the problem out. Closing.
--
Reply to this email directly or view it on GitHub:
#8766 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Description of the bug
I'm using Linux and just discovered ArcWelder. This is my first time using the post-processor option of Prusa Slicer. As instructed I put the full path to the ArcWelder executable in the post post-processing scripts section, like so:
/opt/aw/bin/ArcWelder
The script is executable, and I have permissions to it. My user can run arcwelder against a gocode file on the command line with no issues. But, when I try to use it as a post-processor I get this error:
execve failed: No such file or directory
This happens upon clicking "Export Gcode". The actual slice seems to be performed without any issue. I'm not sure when it tries to apply the post-script, but I assume it is upon export. It is upon export that the error occurs.
When the export fails, the "Export GCode" button label turns to "Invalid Data" and is unusable. I have to restart prusa sclicer to clear it.
.
Thank you.
Project file & How to reproduce
diameter_test.3mf.zip
I cannot export it... that is the problem, but attached is the 3mf. It would not allow me to upload a 3mf here (bug report system). I likewise could not zip the file, because it looks like it already uses a zip algorithm. When trying to do so, it says "nothing to do!". So I renamed the file. Just rename it back to 3mf (remove the zip extension).
This problem happens, however, no matter what I'm slicing. this just happens to be what I was doing.
It is worth mentioning that I'm using the AppImage version of 2.5.0 beta1
After renaming it, just open the attached 3mf in PS, then slice it and try to export it, you will see what i mean. I have the latest version of arcwelder, and like I said above, it works fine from the command line as the same user that is running prusaslicer. I don't think this has anything to do with arcwelder... I think it is probably a minor bug in the post-processor -- probably a space missed separating what should be script arguments from the full name of the path... something like that... so PS is trying to execute "/opt/aw/bin/ArcWelderPipedInFileFromPS outfile.gcode" instead of "/opt/aw/bin/ArcWelder PipedInFileFrom PS outfile.gcode" That's my guess anyway (but what do I know).
Thanks.
Checklist of files included above
Version of PrusaSlicer
2.5.0 Beta1
Operating system
Ubuntu Linux - latest
Printer model
mk3s +, no mmu
The text was updated successfully, but these errors were encountered: