Simplify3D User Forum

idcrook

Using the method that captures self STDOUT and STDERR of bash script I was able to determine what was causing the problem with V5. It appears to be a macOS system permissions issue with respect to Screen Recordings permissions and its interaction with GetWindowID utility. That is why the "(null...

idcrook

I've determined one issue. In V5, identifying windows belonging to app on macOS from post-processing script run returns "(null)". But on command line and in V4 execution, it returns "AppName licensed to..." It is using utility https://github.com/smokris/GetWindowID I guess a poss...

idcrook

I found a way for the bash script itself to capture its own output. This is basically what I was looking for to help debug. # capture stdout+stderr from this script running # https://stackoverflow.com/a/314678 exectrace="${INSTALL_DIR}exectrace" exec > "$exectrace" exec 2>&1 ...

idcrook

It may help to review this recent thread: https://forum.simplify3d.com/viewtopic.php?p=63885#p63885 It gives an example showing how to prove the scripts run correctly. We have already tested that process on several operating systems and it worked on each one, so it should be a good place to start. ...

idcrook

It's really difficult to figure out what is failing if STDOUT is not available from the post-processing script. Simple file-based debugging has already confirmed script on v4 works to completion, but exact same thing in v5 fails to complete. Here's a github issue that tracks this: Simplify3D: Postpr...

idcrook

now we're getting somewhere. I added an additional debug trace output file that gets created near end of script execution when it is ready to insert the thumbnail encodings. in v5 this debug file is not getting created which implies script is not reaching that point on v5. in v4 this debug file IS g...

idcrook

and one additional note, there is some internal debugging that produces files that help to tell if script was run and what the filename argument is. $ grep '^' runtimestamp args workdir gcode args:/Users/dpc/projects/3dprint/s3d-thumbnails/PLA_Front_Bay_Adapter-Part_1_of_2-Chassis.gcode workdir:/var...

idcrook

By the way, the way it "modifies" the .gcode is that it prepends (concatenates) a comment section with .gcode path passed as an argument to a temporary file, and then moves that file back on top of original .gcode file it was provided. cat "${WORKDIR}base64.txt" "$GCODE"...

idcrook

It looks like the Process settings migrated correctly from v4 process for the [Scripts][Post Processing] section. Just to be sure in the Post-processing panel I manually copied the text again in case it was some weird migration issue.. /Users/dpc/projects/3dprint/s3d-thumbnails/generate_S3D_thumbnai...

Search found 9 matches

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1

Re: [BUG] Postprocessing script not being executed on S3D v5.0.1