November 25, 20196 yr Newbies I have just updated to Plastic 3.2 and am getting a Plug-in Initialization error. Expected a -1 separator byte, but received 0. This probably indicates that the parent did consume the entire message. What do I need to do? Thanks, Tom
November 25, 20196 yr hello, Plugin initialization errors are usually caused by an issue with the support files that get downloaded the very first time the plugin is initialized. Please follow the instructions here to manually download and install them. If the issue persists, please follow the instructions at the bottom of that page under the heading Temp Logs to send us the initialization logs. You can send those logs to [email protected] and that will open an official support case for your issue. Reference this thread in your email.
November 25, 20196 yr Author Newbies Thanks. I ended up configuring the plug-in and then registering it. Next time I opened FMP, Plastic initialized. Tom
Create an account or sign in to comment