Error reading resource Line 1

Boony2000

Hi everyone!

I am currently in the process of moving a plugin into a new environment and starting a very reduced version of it up gives me an error on startup:

Error reading resource
file
'[PLUGINDIR]\res\c4d_symbols.h'
Line 1

I am still on R20, in case this is relevant.

I am a little stumped as to what this error is trying to tell me, since the first line of the file are just comments and even if I only put a dummy element in there the error appears (even though the plugin then breaks).
I am confused as to why the plugin seems to run fine after I click ok, since the file contains the pluginIDs necessary to register the plugins. How do I get rid of that error message?

I don't know if this is related at all, but I also always get this in the maxon console:

ZeroConf error: Couldn't get bonjour version [sys_bonjour.cpp(1726)]
Warning: Team Render is deactivated in -parallel mode
[...]
ZeroConf error: Couldn't get bonjour version [sys_bonjour.cpp(1726)]
ZeroConf error: nullptr
CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]
CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]
Optout defined by Installer / Updater.

It's probably not related, but in case it is I thought I'd mention it.

m_adam

Hi could you provide us c4d_symbols.h? And describe your "new environment and a very reduced version" does mean.

If you could link the whole project this would be even better.

On a side note the issue about

CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]
CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(499)]

This is a known issue when you have the Take Manager open in your default layout. Removing it from your startup layout should remove these warnings. Note that they are unrelated to your original issue.

Cheers,
Maxime.

Boony2000

After a LOT of testing around I finally found the culprit.
The header file was encoded UTF-8 with BOM. I finally figured it out after noticing that two versions of the header file that worked or didn't work had a 3 byte difference in file size. No idea how that snuck in there, but now it finally works.
Also now it makes sense that the error was pointing to line 1.