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

Pages: [1]
1
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.

This is strange, we try every build on our internal test scenes of course. Could we see your scene please? Maybe it's something scene-specific

It crashes only with this one. Other simpler scenes seem fine. It has lot's of volume builder meshes and the crash happens as far as I can tell immediately after these volume objects are parsed (although it might not be related at all). See my message above if you would like me to upload this scene. Thank you.

Is there any progress with this bug? Thank you!

One more possible bug. I attach a small scene here with an orange material.
Its behaviour with the native C4D renderer considering both the colour channel but more importantly the Bump channel compared to the Corona translation of the native material differs greatly. Is the expected?

2
We'll never knock back a scene file if it's suspected of causing a crash ;) The private uploader link is in my signature below. Thx

Thank you. Uploaded the scene via Dropbox

3
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.

This is strange, we try every build on our internal test scenes of course. Could we see your scene please? Maybe it's something scene-specific

It crashes only with this one. Other simpler scenes seem fine. It has lot's of volume builder meshes and the crash happens as far as I can tell immediately after these volume objects are parsed (although it might not be related at all). See my message above if you would like me to upload this scene. Thank you.

4
Since this is a disclosed project containing restricted license assets and materials where can I privately send you a link houska?

5
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.


6
Displacement division set to 1 pixel
Phong angle set to 40degs

7
Latest daily Build on MacOS 10.13.5 Cinema 4D R19

BUG
Displacement with dents noise shader (perhaps others also) create polygon artifacts on highest areas (whitest parts of the texture)

See attached image.

8
Latest build on Cinema 4D R19 MacOSX High Sierra.

* Create a material with self Illumination with a non zero intensity or a Light Material with non zero Emission eg. 10 and assign it to an object
* Scene background is empty or (in my case) not visible by camera with a Corona Compositing Tag
* In the output render settings Click Alpha and Straight Alpha
* Render your image normally with Corona VFB
* Adjust the Bloom and Glare Settings so that you get an visible light halo
* Save this as PNG

BUG: The bloom and glare effect is not stored in the transparent PNG and what remains is the object with its material

9
Greetings,
is there an issue with the Variation shader in the diffuse slot? It works great when one picks a gradient to assign a random colour, but all objects become black when I set an image as a texture in the Texture 1 slot.
thank you

10
Dear developers,

I have found that a scene I'm working on causes Corona to crash without any crash report since the 5 of September build, consistently until the latest version.
More specifically, the VFB, Picture Viewer or even the Cinema 4d Viewport go completely black after pass 6 without any error reported.

This happens both in MacOS Sierra and High Sierra and is consistent therefore I suppose that this is a deep bug carried on from early to late versions.

As the scene is zipped 200mb please message me in pm to send you a download link. Thank you for your great effort!

11
I can verify that the last version has some stability issues.
Reading the bug report there seems to be something going on with the PathTracer.

I attach the new bug report.

Thank you for all your great effort

First of all, Congrats to the developers for all those fast updates & fixes.

Testing on MacOS with the latest build and I can confirm that

all of the following:
low resolution of textures in Viewport
nonworking render regions on macOS
round edges shader
instances not updating materials if their parent updates

have been fixed with the latest two versions

The thing is that since yesterday I am having some weird crashes  ( and that pretty much never happened before )
on a large outdoor scene I am testing and since I couldn't replicate the problem in other scenes  at first I thought there was something wrong with the specific scene. I tested with both 13/OCT & 11/OCT build and they were both crashing every time.

Unfortunately! Going back to the build of 9/OCT seems to solve the problem but without all those nice fixes you introduced, so maybe it is a combination of problems.

Anyone else having the same problem?

I've attached one of the bugreports in case it could be of use.

Cheers!

Pages: [1]