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 - tuami

Pages: [1] 2 3 ... 12
1
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.

2
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 :)

3
[C4D] Bug Reporting / Re: C4D crashes at closing file
« on: 2024-04-10, 12:52:26 »
same here

4
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


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

7
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

8
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?



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

10
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

11
[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.

12
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

13
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







14
Hi, I'll be in touch again today, this error is really preventing us from storing data in the library (which is currently absolutely necessary for us). The problem is, you think everything is working because the preview etc. looks correct, but as soon as you render, you see that the material has reset, you can also see it when you check the data set for the material. I hope the error can be solved quickly, I think many users are not at all aware that this error exists and only notice it when they really need the data from the Asset Browser.

sorry for putting a bit of pressure here.
greeting
tuami

15
having the same problem, already wrote with the support team, they have created a bug report
the problem exists if the material is assigned to a geometry and open it from the assets browser.
if you save only the material, it does not happen. it should definitely be checked.



Pages: [1] 2 3 ... 12