Only a small note.
I tried to use chisel.scm on samj's 2.10.2 pack, got one error on the parameter "VIRTUAL" used when calling plug-in-bump-map.

Simply replaced LINEAR with the equivalent value 0, and the filter completes the run without any additional error.

Pls note: I didn't deeply test it, but I tought this simple comment deserves a post, in case someone is tempted to use chisel.scm:
replace LINEAR with 0 at statement (filter line) # 148
so you can use it.

Yes that works nicely, thanks. Tried it in both appImage and flatpak. It didn't work before this simple modification.

Thank you, Dinasset. I tried to use Chisel and Carve and could not get it to work. Will try your fix.


Edit: I ran it several times after adding your fix. No problems at all!! Thank you so much!!!!

Using Windows 10. 64 bit Gimp 2.10 (Samj)

A friend of mine (running Gimp 32bits) told me that the mentioned simple change did not work (still getting errors on compatibility issues).
Hence I decided to replace those statements which have non-2.10 Language (FILL, MODE) and prepared an amended version, which was double-checked without errors.
Hence I post it here for those interested.

PS: remove the previous version before installing this one, because the registering function is the same (hence you would have a duplicated entry)
script-fu-register "script-fu-chisel"

Thank you so much Dinasset.

What would be real great, is a list of non-compatible commands along with the correct replacements. That way I can modify problem scripts.

Example:
LINEAR = 0

You can start GIMP with parameter:
gimp --pdb-compat-mode=warn

Then when GIMP is on run your script in question and it will give you a list of what's deprecated and by what to replace in the error console. You can then check the parameters of the procedure.

Dinasset, is your new version for 32 bit only or can it be used for 64 bit also?

It's OK for both 64 and 32 bits (I am on 64bits, I use it and it works)

Thank you Dinasset!