Cineversity

Hi there,

I recently found out that you can set up relative paths to renders.  For example ‘./Output/render’ creates a render directory in the current c4d folder called Output and renders to that.  Great.

But i need to create that output folder on one level up.  So using ‘.././Output/render’ worked fine in the picture viewer.  However when using the render queue it gives an invalid path error.  I also tried ‘../../Output/render’ but no luck either

Anyone know how to go about getting this working?

Thanks

Hi Rich,

I can’t find any general [platt-form-independet] information about it.

I get a file written [Mac] above the “Scene File Folder” while using “..//” [no quotes of course], but no folder at all (new or in existing).

All path conventions which I have tried are collected in the WIKI here (… it is of course not a MAXON collection :o):
https://en.wikipedia.org/wiki/Path_(computing)

However, since the Picture Viewer works and the Render Queue not in the way you describe it, I have the impression that there is a reason for it. I might be wrong, as this should work with Team Render and platt-form independent, hence my idea that there is a reason, or many reasons! The support will know it much better than I do.
http://www.maxon.net/support/support-questions.html
The Render Queue gives a very good feedback if it wont work with a clear ERROR message.

My suggestion, perhaps use the Take System to manage your folder locations, or place the scene one level up, to have more control (Brainstorming here—tests are needed)

As mentioned, check directly with MAXON, or request a tutorials here, to have that subject discussed with examples and in depth.

All the best

Thanks for looking into it, Dr Sassi. 

Have lodged a question with support.  Will update this if i find out a workaround. 

Cheers for the help : )

You’re welcome, Rich.

I wish I had found more of course. Yes, please share any findings, thanks in advance!

My best wishes.

Just to close off this thread, i spoke to maxon.  This is a current issue with relative paths in the render queue at the moment.  Hence why it only works in picture viewer.  They’re looking to fix it in a future update

Thanks

Thanks, Rich, very nice of you.

I saw that only mentioned for the AEC file, so far. So, not great that it isn’t fixed by now, but any report will certainly add to it.

It certainly sould be better documented (Do I miss something?)

Hopefully we will see a quick tip about it here. ;o)

Have a great weekend and thanks again!

Just had this problem. Found this thread. Apparently they never fixed it in R17. Phooey.

Hi luke.letellier,

The r17 and R18 help content tells me this:
When using relative paths, place periods at the beginning of the path name:

./xy/beauty saves a file named beauty to the xy folder in the scene file’s save path.
../xy/beauty jumps up one level in the directory - from the location at which the scene file is saved. In this example, a file named beauty will be saved in a parent folder named xy.

If I do exactly this, I get the results I’m after. I even tried to add the ../ in the Queue.It goes up one level. Though: It does not go up two levels. I tried the PV as well.

I can only share what works, I have no option to work on stuff that doesn’t work.

==========

if it doesn’t work by now is not nice, I agree.

This here is Cineversity, if you have a technical problem, please check with Maxon directly.

Perhaps via support:
https://www.maxon.net/en-us/support/how-can-we-help/

I mentioned it above, and I can only repeat, I’m not supposed to deal here with technical things that the Maxon Support would do.

All the best.

I completely understand! And I don’t expect you to fix it.

I was just updating the status of the issue here so that if another user found this thread, they’d be able to get an update themselves.

Thanks for understanding, luke.letellier, but I certainly wish I could!

I have updated my post above, checking all things I can do with R17 and R18 (Mac versions here only, hence my suggestion as well to check with the support, they have so much more options)

Thanks for updating the status. Which made me look again into it. However, this is not the fastest way to get the developer’s attention. The support has the “Red Phone” to call them. I certainly do not like to play the “go here and now go there” game. But if it is software or hardware: the support is the best place.

On the other hand: How things work for the artists, and how to get something set-up with the package, I’m certainly happy to dive into it. Stuff, on the other hand, that needs work on the inner core, well that is for the team who can put ideas and dreams into code-lines. If we mix those realities up, I guess no one will be happy …

So, it works for me and not for you, which means, we have made a little bit progress, but there is obviously something else that needs attention. Fingers crossed.

My best wishes and sorry again about the trouble!