1
[C4D] General Discussion / Re: Ai Enhancer Upload Error
« on: 2025-08-14, 11:09:56 »
Thanks again! Great support!
2025-09-18, 05:21:00
News:
Having trouble verifying your license? If you are seeing a license verification message or are unable to access your Chaos products, please follow these simple steps to fix sign-in issues. If you have already tried this and are still unable to access your Chaos products, please contact Support.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
[C4D] General Discussion / Re: Ai Enhancer Upload Error
« on: 2025-07-24, 18:55:11 »
Hello Maru,
thank you for your reply. I had already suspected that no one was responding because we’re probably the only ones (so far) experiencing this issue.
The PCs are exactly the same, we’re working with the same servers, and no, there is no antivirus program or firewall in place.
At the moment, it just doesn’t make any sense — it works perfectly on my machine, but not on the other one.
In the coming days, we’ll completely reinstall Windows on that PC, and I’ll report back if there are any updates.
If anyone has any suggestions in the meantime, feel free to share them here.
Tuami
thank you for your reply. I had already suspected that no one was responding because we’re probably the only ones (so far) experiencing this issue.
The PCs are exactly the same, we’re working with the same servers, and no, there is no antivirus program or firewall in place.
At the moment, it just doesn’t make any sense — it works perfectly on my machine, but not on the other one.
In the coming days, we’ll completely reinstall Windows on that PC, and I’ll report back if there are any updates.
If anyone has any suggestions in the meantime, feel free to share them here.
Tuami
3
[C4D] I need help! / Re: AI Enhancer > how to use it
« on: 2025-07-24, 11:02:54 »
Hey, I found a workaround to use Takes along with the AI Enhancer afterwards. Maybe this solution will help you — just make sure not to close C4D in the process.
4
[C4D] General Discussion / Re: Ai Enhancer Upload Error
« on: 2025-07-21, 19:02:19 »
Can no one help us with this issue?? I've already tried the following:
Completely reinstalled Cinema 4D 2025 (including deleting all files from the AppData folders)
Completely reinstalled Corona and all Chaos products (including deleting all related files from the AppData folders)
Checked Windows updates (everything is up to date)
Verified all drivers
Tested various simple scenes → always results in an upload error
Checked the network and confirmed the internet connection is working
Searched the forums to see if others are experiencing the same issue
EXR files are correctly created in \AppData\Local\Temp\collaboration
The only thing that works is a regular upload (without using the AI Enhancer to the cloud).
Unfortunately, no error messages are shown in the console.
The computer is identical to another one where everything works. It’s on the same network with the same DNS settings and same servers — the only difference is the internal IP address, which I’ve already tested and ruled out.
The only real hardware difference is the GPU: mine uses an NVIDIA card, the other system has an AMD GPU — but that really shouldn’t be the issue, since the AI processing runs on Chaos' servers, not locally.
We also have two licenses, both of which are recognized correctly. There are no issues regarding licensing.
Any help or suggestions would be greatly appreciated. Thank you!
Completely reinstalled Cinema 4D 2025 (including deleting all files from the AppData folders)
Completely reinstalled Corona and all Chaos products (including deleting all related files from the AppData folders)
Checked Windows updates (everything is up to date)
Verified all drivers
Tested various simple scenes → always results in an upload error
Checked the network and confirmed the internet connection is working
Searched the forums to see if others are experiencing the same issue
EXR files are correctly created in \AppData\Local\Temp\collaboration
The only thing that works is a regular upload (without using the AI Enhancer to the cloud).
Unfortunately, no error messages are shown in the console.
The computer is identical to another one where everything works. It’s on the same network with the same DNS settings and same servers — the only difference is the internal IP address, which I’ve already tested and ruled out.
The only real hardware difference is the GPU: mine uses an NVIDIA card, the other system has an AMD GPU — but that really shouldn’t be the issue, since the AI processing runs on Chaos' servers, not locally.
We also have two licenses, both of which are recognized correctly. There are no issues regarding licensing.
Any help or suggestions would be greatly appreciated. Thank you!
5
[C4D] I need help! / Re: TEAM RENDERING ISSUE - PLEASE HELP!
« on: 2025-07-17, 20:27:45 »
@maru
We also encountered an issue where the Team Render clients in Cinema 4D showed an error message claiming there wasn’t enough RAM available.
It turned out, however, that the real problem was simply that the Team Render clients weren’t logged into Corona. (I find this behavior quite odd—there was no indication on the clients themselves that they were not logged in.) Only after briefly launching the Corona Image Editor did the licensing prompt appear. Once we logged in, Corona worked normally and the RAM issue disappeared.
Maybe this information helps. It would definitely be better if Corona showed a proper error message—something like a licensing issue instead of a misleading RAM error. Also, I think the Team Render integration could use much more attention; there are quite a few problems that still need addressing.
We also encountered an issue where the Team Render clients in Cinema 4D showed an error message claiming there wasn’t enough RAM available.
It turned out, however, that the real problem was simply that the Team Render clients weren’t logged into Corona. (I find this behavior quite odd—there was no indication on the clients themselves that they were not logged in.) Only after briefly launching the Corona Image Editor did the licensing prompt appear. Once we logged in, Corona worked normally and the RAM issue disappeared.
Maybe this information helps. It would definitely be better if Corona showed a proper error message—something like a licensing issue instead of a misleading RAM error. Also, I think the Team Render integration could use much more attention; there are quite a few problems that still need addressing.
6
[C4D] General Discussion / Ai Enhancer Upload Error
« on: 2025-07-11, 13:07:21 »
hi, We are using Corona 13 and c4d 2025, and uploading does not work on one of our computers when using ai enhancer. We have completely reinstalled Corona and temporarily disabled the firewall as a test, but we still keep getting an "Upload Error" in the Corona VFB. Uploading images to Collab works fine in general, but not when using the AI Enhancer.
7
[C4D] I need help! / Re: AI Enhancer > how to use it
« on: 2025-06-23, 13:55:04 »
Hello,
we’re using Cinema 4D’s Take System to render multiple images in a single batch. Currently, the next rendering process starts immediately after the previous one finishes, which prevents us from using the AI Enhancer between individual renders.
Is there a possible workaround to avoid this issue? Alternatively, is there a way to apply the AI Enhancer to the rendered images afterward?
we’re using Cinema 4D’s Take System to render multiple images in a single batch. Currently, the next rendering process starts immediately after the previous one finishes, which prevents us from using the AI Enhancer between individual renders.
Is there a possible workaround to avoid this issue? Alternatively, is there a way to apply the AI Enhancer to the rendered images afterward?
8
[C4D] Previews (Daily Builds) / Re: Mixture Shader and some other Issues with Corona and Team Render
« on: 2025-06-16, 11:42:42 »
It seems to be working now with Corona 13 Final.
9
[C4D] Bug Reporting / Re: Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
« on: 2025-06-16, 11:40:55 »
That would be great. I hope you understand the urgency, as we’re currently unable to use render slaves.
10
[C4D] Bug Reporting / Re: Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
« on: 2025-06-16, 09:46:55 »Reproduced and logged (Report ID=CC4D-1028). It looks like Corona Bitmap doesn't render through Team Render at all, not only when used as opacity.
Thank you very much, and hopefully the fix can somehow be included in Corona 13.
11
[C4D] Previews (Daily Builds) / Mixture Shader and some other Issues with Corona and Team Render
« on: 2025-06-06, 12:25:51 »
Hi everyone,
I've been running into ongoing issues when using Team Render with Corona Renderer. The rendering behavior is noticeably different compared to local renders, and in this particular case, the Mixture Shader is not working correctly when rendered over Team Render. Locally, everything looks fine.
I've been using Corona since the early Alpha days (back when it was still free), so it's been around 8–9 years now. Unfortunately, I’m seeing more and more issues related specifically to Team Render.
Please also check my previous threads on this topic – I haven’t received any response there yet.
At our studio, we have six high-performance Team Render machines running locally, but due to the issues described, we currently can't use them. This seriously impacts our timeline and workflow, as we're now forced to render everything locally just to make sure results are correct.
I kindly ask you to take a closer look at this issue. We're definitely not the only ones experiencing these problems – and some of them have existed for quite a long time now. I always try to describe everything in as much detail as possible and provide clean test scenes to help track down the issue.
The current problematic scene is attached. I hope this can be investigated further.
Best regards,
Tuami
2025.2.1
Latest Daly 02.06.
Other current problems
Problems with CXR when renderings via Team Renderer
https://forum.corona-renderer.com/index.php?topic=44128.0
Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
https://forum.corona-renderer.com/index.php?topic=44204.0
See also last post from BigAl3D
From metanerd
I've been running into ongoing issues when using Team Render with Corona Renderer. The rendering behavior is noticeably different compared to local renders, and in this particular case, the Mixture Shader is not working correctly when rendered over Team Render. Locally, everything looks fine.
I've been using Corona since the early Alpha days (back when it was still free), so it's been around 8–9 years now. Unfortunately, I’m seeing more and more issues related specifically to Team Render.
Please also check my previous threads on this topic – I haven’t received any response there yet.
At our studio, we have six high-performance Team Render machines running locally, but due to the issues described, we currently can't use them. This seriously impacts our timeline and workflow, as we're now forced to render everything locally just to make sure results are correct.
I kindly ask you to take a closer look at this issue. We're definitely not the only ones experiencing these problems – and some of them have existed for quite a long time now. I always try to describe everything in as much detail as possible and provide clean test scenes to help track down the issue.
The current problematic scene is attached. I hope this can be investigated further.
Best regards,
Tuami
2025.2.1
Latest Daly 02.06.
Other current problems
Problems with CXR when renderings via Team Renderer
https://forum.corona-renderer.com/index.php?topic=44128.0
Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
https://forum.corona-renderer.com/index.php?topic=44204.0
See also last post from BigAl3D
Quote
Interesting. I had reported this Team Render issues a long time ago, maybe 4 or 5 years. Team Render behaves similar to Save with Assets. In my case, textures, at least from third party materials sets, when collected would change the name of the texture file to some random numeric name, but not the inside the path so they would all be missing from the render. In my case it was a material set from The Pixel Lab. I will try your workaround with a C4D node sitting in there.
For me, I haven't used Team Render in a long time, but this issue would be a problem if you want to use a render farm too.
From metanerd
Quote
I’m following up on this again. Just like with Tuami, we can reproduce the same behavior here.
Everything works as expected up to version Cinema Version 2025.0.2.
Starting with version 2025.1 and up to the current version 2025.2.1, files imported from the Asset Browser that either use the Bitmap Shader or are set up as Shared Materials no longer work in Team Render. Both V12-Hotfix 1 and V12-Update 2 work correctly under version 2025.0.2, but not from version 2025.1 onwards.
For us, this means we can no longer install any C4D updates, which is extremely inconvenient.
12
[C4D] Bug Reporting / Re: Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
« on: 2025-04-11, 09:38:37 »
Hi @bnji,
I’ve discovered something interesting:
As long as the native Cinema 4D Bitmap shader is still loaded in the Node Editor (but not connected to anything), the scene works correctly with Team Render.
However, as soon as the C4D Bitmap shader is completely removed, it no longer works.
Could you please set up your scene like this:
1. Add the black & white opacity map to the Asset Browser.
2. Create a Corona Bitmap shader (make sure no C4D Bitmap shader is active in the Node Editor).
3. Drag the image from step 1 into the Node Editor and copy the asset path (IT HAVE TO BEGIN WITH assetdb:///) and paste it into the corona bitmap shader
4. Important: Delete the image you just dragged into the Node Editor, so that only the Corona Bitmap shader remains.
5. Connect the Corona shader to the Opacity input of the Physical Material.
Run a local test and a Team Render test.
Thanks!
Best regards,
Tuami
I’ve discovered something interesting:
As long as the native Cinema 4D Bitmap shader is still loaded in the Node Editor (but not connected to anything), the scene works correctly with Team Render.
However, as soon as the C4D Bitmap shader is completely removed, it no longer works.
Could you please set up your scene like this:
1. Add the black & white opacity map to the Asset Browser.
2. Create a Corona Bitmap shader (make sure no C4D Bitmap shader is active in the Node Editor).
3. Drag the image from step 1 into the Node Editor and copy the asset path (IT HAVE TO BEGIN WITH assetdb:///) and paste it into the corona bitmap shader
4. Important: Delete the image you just dragged into the Node Editor, so that only the Corona Bitmap shader remains.
5. Connect the Corona shader to the Opacity input of the Physical Material.
Run a local test and a Team Render test.
Thanks!
Best regards,
Tuami
13
[C4D] Bug Reporting / Re: Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
« on: 2025-04-09, 15:12:36 »
Hello bnji,
Thank you very much for your help in resolving the issue.
We are using Teamrender on Windows 11 machines with the latest version of Cinema 4D and the daily build, connected via a 10 Gbit Ethernet network, and the data is hosted on a separate server.
I've done some more testing, and in our case, we are using an opacity map. The issue occurs as long as no native Cinema 4D Bitmap shader with the same texture is loaded in the scene. Once the Cinema 4D Bitmap shader is loaded (it doesn't have to be connected to the material), it works fine. The problem seems to be specific to the Corona Bitmap shader (all paths are exactly the same). It appears that the Corona Bitmap shader has trouble when using Teamrender, with the data located on a server and loaded through the Asset Browser.
I'll try to provide a scene in the coming days.
tuami
Thank you very much for your help in resolving the issue.
We are using Teamrender on Windows 11 machines with the latest version of Cinema 4D and the daily build, connected via a 10 Gbit Ethernet network, and the data is hosted on a separate server.
I've done some more testing, and in our case, we are using an opacity map. The issue occurs as long as no native Cinema 4D Bitmap shader with the same texture is loaded in the scene. Once the Cinema 4D Bitmap shader is loaded (it doesn't have to be connected to the material), it works fine. The problem seems to be specific to the Corona Bitmap shader (all paths are exactly the same). It appears that the Corona Bitmap shader has trouble when using Teamrender, with the data located on a server and loaded through the Asset Browser.
I'll try to provide a scene in the coming days.
tuami
14
[C4D] Bug Reporting / Re: Issue with Mixture Shader in Corona Version 13 Daily Build – March 5, 2025
« on: 2025-03-25, 09:25:51 »
Thank you!
15
[C4D] Bug Reporting / Re: Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
« on: 2025-03-24, 12:42:29 »
The issue is still present in the current Corona daily build. The assets are stored in the Asset Browser and were created by us there. As mentioned, the setup worked both locally and with older versions of Corona. However, with newer versions, it no longer works over the Team Renderer, only locally. So far, we've only encountered this issue with this specific material, though it’s possible that other materials could also cause problems when using Team Renderer.
There seems to be some issue with the native Corona Bitmap Shader, the Asset Browser, and the Team Renderer. This combination appears to be causing the problem, as it works locally but fails when using the Team Renderer with newer Corona versions.
The issue does not occur with the C4D Bitmap Shader, but we almost always use the Corona Bitmap Shader. It seems that the problem arises specifically when using the Corona Bitmap Shader in combination with the Asset Browser and Team Renderer.
There seems to be some issue with the native Corona Bitmap Shader, the Asset Browser, and the Team Renderer. This combination appears to be causing the problem, as it works locally but fails when using the Team Renderer with newer Corona versions.
The issue does not occur with the C4D Bitmap Shader, but we almost always use the Corona Bitmap Shader. It seems that the problem arises specifically when using the Corona Bitmap Shader in combination with the Asset Browser and Team Renderer.