Hey all,
Ran into this error today that I've never seen before:
Has anyone ever experienced this before?
I've tried to reproduce it on two different systems (OSX Mojave, and Win 10). This was originally experienced on an OSX El Capitan (don't have access to that computer right now so I don't have the exact version number).
Can't seem to find anything pertaining to this error on the forum. Gonna do some troubleshooting tomorrow.