Messages

1

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-05-06, 14:26:52 »

hello frv,
you are right that they are there for testing purposes. we lost a lot of time clearing up the problem and the error with the asset browser because we didn't know that this error existed.

i have already reported the problem several times and always tested the latest versions. i just can't listen to this “can you send us a test scene” anymore, because i have already been in active exchange with the corona team and it should be clear by now how the errors can be reproduced.




this was my last mail from march to corona team as an example

---------------

here is the summary again



Computer 1 (My computer)

On this PC is installed
Cinema 4D version 2024.2.3 (latest)
Corona 10 Hotfix 2 from September 2023

The following problems are no longer present when Corona 10 Hotfix 2 from September is installed
- Xref problem
- Long loading times when opening scenes

The following problems are still there
- Problems with Asset Browser (Corona materials are reset)



Computer 2 (computer of a colleague)

The following is installed on this PC
Cinema 4D version 2024.1.0
corona-12-c4d-daily-2024-03-11 (latest)

The following problems are no longer present when Cinema 4D version 2024.1.0 is installed
- Problems with Asset Browser (Corona materials are reset)

The following problems are still there
- Xref problem
- Long loading times when opening scenes


Forum Links

Assets Browser Problem
https://forum.corona-renderer.com/index.php?topic=41775.0

Long Loading Problem
https://forum.corona-renderer.com/index.php?topic=42282.0

Xref Problem
apparently fewer people use xref but the problem still exists


Greetings
Thomas

2

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-05-06, 09:05:27 »

Hello there,

Thank you for all your feedback.
Have any of you already tried the latest Daily build? (23.4)
Does the issue persist?
Could any of you share a previous scene so that we can use it to reproduce the issue on our end?
Looking forward to hearing from you.
Have an amazing weekend ahead.

Is there anything new?
I already reported the error 2 months ago. Beanzvision was on my computer about a month ago and I showed him the error (plus other errors that are currently being discussed in another thread). i don't understand why they are asking for test files again. somehow there seems to be something wrong with your internal communication.

i also invited him in this thread on 2024-04-05, 12:44:06 to send test files again, that was a month ago and no one has responded. Now you are asking for test files.

i have already sent them to the support, i posted some tickets two months ago also with the reference to the corresponding forum posts and here still no connection is recognized or looked at properly. is there a programmer with whom you can contact directly?
Either the wrong configuration environments are being used or the communication with the programmer does not seem to be correct. please send me a private message if you have any questions about this or post in the thread so that others can also benefit from it.

3

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-04-29, 13:00:33 »

Since there was a Hotfix to Corona 11 and also the new 2024.4 had some promising new feature, I've installed both and tried out our beloved little bugs. Seems like the bug somehow changed . Now, the color stays after re-loading it from the Asset Browser (most of the time), but the Bump value still is replaced with the full 100%, instead of the previously set value before loading it into the database. Just for a quick update on the topic from my side.

This still seems very uncertain and I keep wondering why nothing has been fixed yet. I think it's partly due to corona and partly due to maxon. Maxon tells me to contact corona. Somehow it all seems very uncertain to me, it's a fundamental mistake that can lead to whole days of work being lost because you think everything is correctly stored in the library. We have to set up three workstations here so that either cinema4d (asset problem with corona) or corona (extremely slow loading of files that contain Corona Bitmap shader) works and that is just extremely nerve-wracking if nothing changes. I posted the error over 2 months ago and so far either the things couldn't be traced or you only get the feedback that it will be passed on. On the other hand, unimportant new functions are added instead of focusing on ensuring that everything works smoothly. Man, I'm really pissed off, sorry, but this needs to be heard. I have to take care of everything here and this  just doesn't work.

4

[C4D] Corona Goodies - User Contributions / Re: Bitmap shader conversion scripts

« on: 2024-04-15, 15:33:06 »

I'm still planning to release more scripts, here is a little work in progress :

whoa i need this! would be great if there are more shaders to be found there, thanks keep doing great helpful work :)

5

[C4D] Bug Reporting / Re: C4D crashes at closing file

« on: 2024-04-10, 12:52:26 »

same here

6

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-04-05, 12:44:06 »

Hello benjamin,

the problem does exist and you were recently with us on two computers where I showed you the problem. You are welcome to come back to our computer and I will show you the problems.

Which version of Cinema 4D and Corona Renderer are you using, if I may ask, I saw somewhere that you are not using the latest versions. I hope we finally get help, I have been writing to support and here in the forum for two months, apart from the fact that they keep saying that things cannot be reproduced, it does not mean that the problems are not there and obviously there are many here who have the problems.

1. asset browser problem
2. super extremely slow opening of scenes
3. xref problem (paths of corona bitmap shaders are not converted to absolute paths.

Forgive my stubbornness on this topic, but we have to deal with this every day and I would be happy to finally get a solution to the problem.

If you have any questions feel free to contact me (privately) and I can give you more test scenes and please tell me your setup again

Greetings
Thomas

7

[C4D] Corona Goodies - User Contributions / Re: Script for changing the size of preview of selected materials.

« on: 2024-03-31, 21:57:32 »

could be useful, thanks! :-)

8

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-03-18, 10:47:38 »

we have downgraded c4d and the problem does not occur with 2024.1.0.

9

[C4D] Daily Builds / Re: C4D scenes dont open with new Daily Build from Corona 12 March 11.

« on: 2024-03-18, 09:48:33 »

Same here, dont know its a Maxon or a Corona releated thing. We have here scenes that will load up in 1 hour. scenes that will load up before in max 30 seconds.
We did test this on a network drive with 10gbit and nvms and local on nvms, same problem.

tiglat can you try "2024.1.0" scene will load up faster here seems hotfix 2 corona 10 work here

10

[C4D] I need help! / Re: Tile Shader - Jagged Displacement and Bump

« on: 2024-03-11, 11:56:02 »

hey benjamin, could your share yours scene? Bump isn´t working for me either.
(BtW do you us another c4d/corona version? Everything is working for you :D )

I can confrim Bump is not working when using Tile shader in Bump slor.
Using filter doesn't help.

Any news regarding this?

Hi there, can you share a test scene? It is working here. What version of Corona are you using?

11

[C4D] Corona Goodies - User Contributions / Re: Quixel Bridge Importer for Corona Renderer (C4D)

« on: 2024-03-08, 17:03:32 »

great, i will definitely try it out when i find the time

12

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-02-26, 11:03:24 »

hello we have updated cienma 4d to 2024.3.1 today in the hope that the problem will no longer occur (it could have been that the problem is caused by cinema 4d) unfortunately the error still exists and we can no longer place assets in the library as the materials seem to be reset. (The bad thing is that you think it's fine, because the previews of the materials are displayed correctly, only after you put the objects from the asset browser back into a scene and look at the material properly, or render it, you see that it is basically just a simple physical standard material). The problem only exists with materials that are placed on objects, materials that are saved directly to the library - without geometry are recognized correctly)

We urgently need help with this problem!

win 11, last Corona version, c4d 2024.3.1

The data is on a network drive, everything else has already been explained a few times above

13

[C4D] General Discussion / Re: Cosmos and Vray

« on: 2024-02-19, 15:12:33 »

hey i also happened to notice this today and then i saw this thread right here.

14

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-02-06, 10:56:56 »

hello is there any news on this, the bug is there and we can't save assets that have corona materials in the assets browser. thanks

15

[C4D] Bug Reporting / Re: Bug with Physical Materials and the Asset Browser

« on: 2024-01-19, 09:23:02 »

we have textured this fire extinguisher with corona materials, then placed it in the asset browser. as you can see, the materials are not transferred correctly when you open the fire extinguisher from the assets browser. however, the preview shows that the materials are on it.the nullobject does not work for us either