THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 27/06/2004 at 10:23, xxxxxxxx wrote:
Cinema 4D Version: 8.5
Language(s) : C.O.F.F.E.E ;
I've got a scene with several coffee tags all which use a common .coh include file. This include file is in the same directory as the .c4d scene. From the editor, the coffee runs fine. However, when I render to frames, the coffee stops working. Apparently, it can't see the include any longer.
Also of note, if I open the scene from my most recently used list. The coffee does not work. If I open the file using the file browser, it works.
So, the question is, how do I make it find the include consistently? Is there a PATH statement or other C4D config that I can set up? In the mean time, I'll try hard coding the path ... but I should be able to use a relative path.
On 30/06/2004 at 21:39, xxxxxxxx wrote:
It seems to me like C4D searches all directories in the working directory for C.O.F.F.E.E. includes. I cannot confirm the render specific part of the bug.
Possibly using includes in C.O.F.F.E.E. tags isn't supported. A workaround would be to insert the included file into the code directly. I'll report the behaviour as a bug.
On 01/07/2004 at 00:05, xxxxxxxx wrote:
Yeah, as the document is cloned during rendering this might lead to problems probably.
On 01/07/2004 at 01:58, xxxxxxxx wrote:
I got it confirmed from the programmers that include isn't supported in C.O.F.F.E.E. expressions. So you'll have to either rely on the fragile support there is, or use the workaround.
On 07/05/2009 at 22:22, xxxxxxxx wrote:
I have a similar problem... I'd like to "include" a common function library into a variety of plugins I'm working on- each in its own directory, but I can't specify a path (or can't figure out how to.)
Mikael mentions above that "C4D searches all directories in the working directory for includes", but as soon as I move my common library out of any given folder, that plugin fails to load with
(125) Error in 'include'
Creating aliases for the include file doesn't work (makes sense), so do I really need to keep a copy of this common library (still a work in progress) and replace every copy in each plugin's folder everytime I do a minor update during development? Please let me know if there is some way to specify a path for the include or if I'm doing something else wrong.
On 11/05/2009 at 07:50, xxxxxxxx wrote:
Have you tried absolute paths, something like include "c:\myincludes\myheader.h" ?
On 11/05/2009 at 13:18, xxxxxxxx wrote:
I've not tried absolute paths of that style, just the relative "../CommonFile.col" to get the parent directory that Robert suggested. I'll try to start with a clean GeGetRootFilename and will post what happes.
On 11/05/2009 at 16:47, xxxxxxxx wrote:
I've tried some of the above, and nothing has worked so far.
I'll move details for this conversation over to the more specific thread under
"Coffee include path?"
On 13/05/2009 at 12:46, xxxxxxxx wrote:
Success from Lennart. See path above for details: