Messages

1

[C4D] Bug Reporting / Re: IPR rerenders with any tonemapping setting changed-stil in v12update2

« on: 2025-06-02, 14:02:39 »

Hi,

I'd simply like to emphasize how annoying this is. This issue with parsing the scene after any changes in tonemapping is just horrible especially when working on large projects. It was reported many months ago, yet there is no solution to this problem. Kindly look at this thoroughly and attempt to resolve the issue. Thank you.

2

[C4D] Bug Reporting / COSMOS - Connection refused

« on: 2025-06-02, 13:47:21 »

Hi Guys,

I have installed the most recent Corona version and am having difficulties launching Cosmos. I receive the message: CONNECTION REFUSED. Any ideas on how to fix this?

Thanks

3

[C4D] I need help! / Re: Cinema 2025 does not provide options when saving an image

« on: 2025-06-02, 13:37:47 »

After reinstalling Cinema 2025, everything works fine.

4

[C4D] Bug Reporting / Re: Corona Sky / Volume effect causing glith

« on: 2025-05-26, 16:11:47 »

Ohhh...OK...thanks. I have it active. I will deactivate the clouds.

5

[C4D] I need help! / Cinema 2025 does not provide options when saving an image

« on: 2025-05-26, 15:46:31 »

Hi guys,

I'm using Cinema 2025, and when I want to save a PNG or TIFF image, I can't choose whether to save it in 8 or 16 bit format, or if I want to keep the alpha channel. This choice is not displayed, as the image is saved directly as 8bit with alpha. Nonetheless, it works fine in Cinema 2024. Did anyone else have the same issue?

Kind regards

6

[C4D] Bug Reporting / Corona Sky / Volume effect causing glith

« on: 2025-05-26, 15:31:51 »

Hi Guys,
When using Corona Sky with the VOLUME EFFECT ON, a glitch occurs in which a white background appears from around 60% of the image height. It cannot be overridden with the SCENE ENVIRONEMT option.
Did anyone else have the same problem?
Thank you for any reply.

7

[C4D] General Discussion / Re: Multiplied alpha

« on: 2025-04-04, 10:37:49 »

I tried saving the image as 16-bit EXR (it's a shame we can't save CXR 16-bit from VFB) and opening it in Photoshop with the EXR IO plugin, but it always opens as 32-bit, so any conversion to 16 or 8-bit affects the colors. It is a little irritating. Is there a workaround?

8

[C4D] Bug Reporting / Re: Scene still parsing

« on: 2025-04-04, 10:30:13 »

I disabled the LEGACY WHITE BALANCE option and then started the interactive rendering. As soon as I alter the SIMPLE EXPOSURE setting, the parsing restarts!!! It's very bothersome.

9

[C4D] General Discussion / Re: Cryptomatte pass for animation

« on: 2025-03-21, 22:34:43 »

Thank you for the reply. I have seen that video before, but it is only about the static image saved from VFB.

I first tried saving CXR for passes. It did not save any files, and I received a notice stating that it can only store single images, not animations. Passes cannot be saved as CXR for animation. I could save the REGULAR IMAGE in CXR format for animation. The issue is that it is saved as 32bit, and I am unsure of the color space. As a result, the colors of the beauty pass are unusable in DaVinci Resolve, and repairing them is difficult with unpredictable results. Second, I can't import a CXR file sequence into DaVinci Resolve timeline. I was able to open CXR in the Fusion tab.

The only way to fix this is to save the REGULAR IMAGE as a CXR sequence for the CRYPTOMATTE pass and save the passes as PNG. Passes are saved with linear gama, which can be easily converted to gama 2.2 in DaVinci. Thus, the VirtualBeauty pass can be used as the REGULAR IMAGE.
The problem with storing a standard image as CXR is that it stores all of the passes Corona has to provide. So there are a lot of passes I don't need, and the file is large.

It would be ideal to save the regular image as PNG and the passes as CXR.

10

[C4D] General Discussion / Re: Cryptomatte pass for animation

« on: 2025-03-20, 10:03:24 »

Hi,

I've recently discovered that it is also possible to save image sequences/animation in CXR format. I assumed that was a format available just in VFB. I tried saving CRYPTOMATTE using ordinary EXR format, but it didn't work. Now I've checked whether DaVinici Resolve can open CXR format for Cryptomatte masking, and to my surprise, it can. Unfortunately, Photoshop does not support CXR format.

Kind regards

11

[C4D] Bug Reporting / Re: Scene still parsing

« on: 2025-03-20, 09:00:19 »

Hi,

I am running the most recent daily build, and as soon as I complete rendering an animation, I will try to delete the LEGACY WHITE BALANCE controller, even though I believe I did it a few weeks ago and it did not resolve the issue.

Kind regards

12

[C4D] Bug Reporting / Render instances and Motion blur randomly change the position of the instances

« on: 2025-03-14, 12:18:20 »

Hi guys,

I had an imported STP model with several parts, including INSTANCES set to RENDER INSTANCE. When I activate MOTION BLUR in the options, some (or all) of the instances appear in the VFB render at random positions. When I set the instance mode of the INSTANCES to INSTANCE, the objects remained in their correct places.

Kind regards

13

[C4D] General Discussion / Cryptomatte pass for animation

« on: 2025-03-13, 15:08:41 »

Hi guys,

Is it feasible to save the Cryptomatte Pass for animation? It is stated that you must save it from VFB as CXR and alter the extension to EXR. Well, it works for stills, but what about animation? I tried saving a few frames as EXR, but it did not work.
Any suggestions?

Thank you

14

[C4D] Bug Reporting / Scene still parsing

« on: 2025-03-12, 16:15:20 »

Hi guys,

When I modify the material or adjust some light parameters in the lightmix window, the scene begins to parse. Is it normal? When a scene is large enough, it can take a long time to parse. I am spending more time waiting than working.
Any idea what's causing this? I use the latest CORONA 13 daily build.

Kind regards

15

[C4D] General Discussion / Re: Randomizer issues

« on: 2025-03-05, 11:23:48 »

I intentionally picked this texture with substantial seams to test how the rondimzer works. Thank you for confirming that the seam issue is due to a non-seamless texture, which the randomizer cannot address.