I recently upgraded to Corona 14 from Corona 13…what is this strange loop when I start the IR?
This scene was created with Corona 13 HF2…
Latest Cinema4D
Latest Corona 14
MacBook Pro M1 Max
Latest MacOS
I recently upgraded to Corona 14 from Corona 13…what is this strange loop when I start the IR?
This scene was created with Corona 13 HF2…
Latest Cinema4D
Latest Corona 14
MacBook Pro M1 Max
Latest MacOS
it’s unbelievable that anyone have not this issue…for me Corona 14 still useless.
Any tips?
Is it only this scene or every scene? Can you send in the problematic scene via ticket at https://support.chaos.com/hc/en-us/requests/new ? Can you specify which versions are involved, rather than saying “latest”, as sometimes people think they have the latest, but they don’t and it avoids any possible confusion if you specify the version. Thanks!
Sure…let me send the scene…
Anyway Is reported on our Cinema4D forum too and my co-workers here on my office has the same issue with old scenes.
The version is Corona 14 as wrote on my topic.
Cinema4D 2026
Macos 26.1
Mac Book M1 Pro Max
Anyway I will prepare files for the support…
Thanks Tom
Thanks for the extra info! I know that can be frustrating to dig up all the numbers, when something is already going wrong and getting in the way of things for you, so I appreciate you taking the time to do that. TY in advance for the ticket and scene too so we can dig into things more specifically.
It’s a pleasure to help you, I know how hard is to develop a software for many platforms and versions. Anyway don’t worry I downgraded to Corona 13 until news about this issue.
Have a good evening (here is evening now).
Alex
Good to know you are up and running so not held up with any of your work. Also, thank you for your understanding as we try and figure this one out and get it fixed for you!
This is handled in support ticket #444547, is reproduced, and reported to our devs. We will need some more time for the investigation.
same, IR loop with start and stop..
anyone tried ‘renewing’ the cam. tag?
I tend to do that first on such occurrence ~ ain’t the first time nor the only engine behaving this way w/ old scenes
Yes. I tried a new cam, new render settings but need to investigate more.
Usually I love to catch bugs but I’m so busy on my office so I can’t try more ![]()