Potential Redshift Render Token bug? (C4D 2026.1)
Hi everyone,
I am trying to determine if I am missing something obvious or if the Redshift Render Token system is currently bugged (2026.1)
The Problem: I typically bypass the standard render output window in favor of the Redshift AOV output. However, Redshift is refusing to render EXRs to the folder when using tokens.
Token used: Render/$prj/$prj_
Symptoms: Frames render in the Render View, but files are not generated. Right-clicking to "Show in Explorer" triggers no action. Even manually pasting the Windows Explorer path into the field fails. A search on windows explorer yielded zilch.
Troubleshooting & Support: A Maxon rep recommended changing the string to $filepath$filename_$pass, but this also failed. Their final advice was to revert to the standard render output workflow.
On December 15th, they closed my ticket with the following statement:
"We will be closing this Support ticket, but it does not mean that we are closing the bug ticket... we are unable to offer any dates or time frames on product releases, updates, or bug fixes."
For a sanity check, I ran the same workflow in Octane with the exact same token. It worked perfectly. Same scene, only diff are the obviously the materials, lights, camera etc.
Has anyone else faced this? I would appreciate it if someone could test this on their end or suggest a workaround that allows me to keep using the AOV output window.
System: Windows 11, RTX 4090 x2, Threadripper 7970X, 256GB RAM.
16 views
Log in to join the conversation.
Hey Andy,
I cant say I've run into this one before. I personally rarely use AOVs (except cryptomattes) as I prefer to just do a little color correction in resolve only, not the whole multipass workflow.
However when I do, I always use the
DIRECT AOVmethod and the tokensRENDER/$prj/$prjso renders always go to a relative RENDER folder.I use this as my AOV base:
$prj_AOVI have all this set up in my default C4D scenes (and all redshift project files here) if you want to take a look at my settings.
For your particular setup it may well be a bug, 2026 is full of them!