Common errors in Filter Foundry, a plugin for creating custom Photoshop-compatible filters, often stem from syntax mistakes in formulas or compatibility limitations with modern 64-bit systems. Troubleshooting involves checking for simple mathematical typos or environment mismatches. Common Errors & Easy Fixes Likely Cause “Preview does not match output” Input datasets or execution flags are mismatched.
Verify input datasets correspond to those in Rule Editor and ensure the shouldMatchContourExecutionBehavior flag is set to true. Plugin Won’t Load
Incompatible file types or bit-depth (e.g., trying to load FFP files).
Use only 8BF files created by Filter Factory or unprotected Filter Foundry files. FFP (FilterMeister) files are currently unsupported. Syntax/Formula Errors
Using unsupported commands or missing required text metadata.
Stick to basic Filter Factory commands. If metadata (Author, Copyright) is missing, manually add it using a text editor. Visual Glitches
Outdated or bugged integrated graphics drivers (especially Intel).
Update your graphics drivers directly from the manufacturer’s site (e.g., Intel) rather than relying on Windows Update. “Receiving end does not exist” The extension service worker has gone idle.
Restart the application or run a reconnect command (e.g., /chrome in some environments). Advanced Troubleshooting Steps
Safe Configuration: If the application fails to launch or behaves erratically, launch in a Safe Configuration (disabling all third-party modules) to rule out external conflicts.
User Data Reset: Persistent loading hangs can often be fixed by deleting the Sandbox system directory in your User Data folder. You can find this by right-clicking the app icon and selecting “Browse User Data”.
Cross-Filtering Issues: If filters aren’t applying across tabs in complex setups, ensure the “cross-filtering” checkbox is marked in settings and that the filterSet values are identical and case-sensitive. Troubleshooting reference – Foundry Rules – Palantir
Leave a Reply