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.


Messages - tiglat_agora

Pages: [1]
1
Hi Ben,

I changed the setting, but it didn't change the result, see the video in the attachment.
A question for everyone reading this. Am I the only one with this problem?
I'm also attaching my start file and my layout. Maybe the error is somewhere here?

greetings tiglat

2
Hi Beanzvision,

how do you open the VFB?

The synchronization only works for me if I first open the C4D image manager (image step 1) and then open the Corana VFB in the image manager (image step 2). If I open the VFB via the Corona menu (Figure 3), the camera tag does not synchronize.

Greetings


3
Ok Beanzvision,

Thank you, I will install and test the hotfix again. I'll let you know.


4
Hey Beanzvision,

you're doing exactly the opposite of what I meant. I think the majority of users change the exposure in VFB and not in camera tag. I don't want to open 2 windows to change the exposure of the current camera. Whatever has worked so far in all previous versions.

greeting

5
I´m on C4D 2024.4 and Win11

6
Hello everyone,

I just tested chaos-corona-11-c4d-hotfix 2.

The Corona VFB and the Corona camera tag still do not synchronize.
Am I the only one with this problem?

Has anyone tested whether the asset browser and texture paths issue has been resolved?
I'm back to Corona 10 hotfix2.

greeting

7
Good morning Luis,

I have the same problem. You have to wait forever to open a scene. I tested it with a scene created in Cinema4d 2024.3.2.
The loading time in corona 10 (hotfix2) according to the task manager built into C4D is 0:00min and in the current daily 1:17min for the same file (see attachment). If you have a big scene, it may take some time.

I think it has something to do with the Corona materials and the Corona proxies. If I delete all materials and convert all proxies, the file loads normally.

Maybe everything will work if you start a completely new project. But I don't have time for more tests.
I'm back in Corona 10 (hotfix2) because I have to constantly work with "old" files.

In general, there is currently a problem with Corona materials in cinema. As already described elsewhere in the forum, Corona materials always lose the connection to the textures when you save them in the Cinema4D Asset Browser and then reinsert them into a project.

My system: AMD Ryzen Threadripper 3970X with 128GB RAM, RTX2080 SUPER and Win11 23H2
I'm working with Cinema4D R26, 2023.2.2 and 2024.3.2

I wish everyone a good start into the week.

8
[C4D] Bug Reporting / Re: Corona 11 bug ?
« on: 2023-12-08, 11:37:47 »
Hello Beanzvision,


it's the same problem like in this thread: https://forum.corona-renderer.com/index.php?topic=41468.0

or in this one: https://forum.corona-renderer.com/index.php?topic=41425.0

Greeting


9
Hello Beanzvision,

nice to hear that the team is working on solving the problem.

Greetings and a good start into the week!

10
hello rafaz,

I think it's the same problem as in my post.

https://forum.corona-renderer.com/index.php?topic=41425.0

Good to hear that I'm not the only one having this problem.
The changes made in the VFB are not adopted in the current camera.

Greetings and have a nice day

11
Hello everyone,
I have now tested RC3. Same behavior. If I open the Coroana VFB via the icon, the current camera is not synchronized. What I found out is that if I first open the native image manager (shift + F6) and then the Corona VFB there, then the current camera and VFB are synchronized.
I have attached 2 videos for the behavior.

Greetings
Bastian

12
Hello everyone,

I tested the release candidate data RC 1 and 2 and noticed that the VFB and the corona camera tag do not communicate with each other. If I change the tone mapping settings in the VFB, they are not adopted into the camera tag.
So I have to re-enter the tone mapping settings every time I re-render.
I'm back in daily from 2023-11-09, it works there.
I'm working on a PC AMD Ryzen Threadripper 3970X (128Gb RAM) with Cinema4D 2024 and Win11.

best regards
Bastian

13
Hi Le Sill,

have you tried the option in my attachment?

regards
Bastian

14
[Max] Bug Reporting / Re: The Cosmos Browser wont open
« on: 2023-06-08, 08:42:08 »
Hi maru,

had the same problem in Corona 10 RC 1 and Cinema 4D 2023.2.1 in Win11. Your hint works for me.

regards

15
[C4D] Daily Builds / Re: v9 More Interactive Crashes
« on: 2022-11-12, 17:58:31 »
Hi,

the IPR crashes every time if I change the name of a object in the object manager .
I´m on a Ryzen 9950X (64GB RAM) and an Ryzen 3970X (128GB RAM) both machines with win11, cinema 4D 26 and 2023.1 and it happens ín corona 9 and 10(daily build Nov 3, 2022).
No crash dumps and bug reports.

Best regards,
Bastian

Pages: [1]