Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] Bug Reporting => [C4D] Resolved Bugs => Topic started by: Sulphurous on 2018-03-27, 19:22:49
-
I'm attempting to Direct Visibility overrides with an animated material which is used for a background object. I used the same animation settings for both materials. http://prntscr.com/ix5l5j
The difference being, when used with the Corona material (because i cannot brighten up default C4D materials with Luminance) does not animate and is incredibly distorted. Observe. http://prntscr.com/ix5mkb
-
I have no idea what you've done. What medium you used for the animation etc. However, I can tell you that your direct visibility background is spherical.
-
I used frontal mapping, not spherical. http://prntscr.com/ixhrlv The material is setup like so http://prntscr.com/ixhs1g The animation works with the default Cinema materials, but not with the Corona material for some reason. http://prntscr.com/ixhse1 I used a simple image sequence for the animated background.
-
I see that your using a "background" object, to my knowledge they aren't supported in Corona.
-
On a regular object, an animated material from a sequence of bitmaps works just fine here - can't use Corona Bitmap as it doesn't have animation, but just loading it as a regular Load Image in the Texture slot works fine. But as noted the Background object is not supported so could be the culprit - does it all work for you on a normal object?
-
It does not work at all on a normal object with a corona material. I don't understand what's happening here.
-
Can you share the scene with the simple test object?
Just to confirm, here are the steps shown for a regular C4D material (random tutorial video from the web) -
I did the same thing with a CoronaMaterial and CoronaLightMaterial, dropped onto a cube, and it worked as expected. Of course this was not using CoronaBitmap, which doesn't have the animated option, so just use the usual C4D default way of loading a texture into the material.
-
413 Request Entity Too Large. Also, i followed the same procedure as in the video.
-
Is that with all animated textures, or only this one? In particular, does it work with smaller textures and not with larger (or smaller number of frames in the sequence... I am not sure if C4D loads the whole sequence into memory, perhaps?) When does the "413 request entity too large" appear, when preparing the animated texture in the bitmap loader, or at render time with Corona, or at some other point? Can you share the image sequence via the private uploader? How much RAM does your system have?
Sorry for the questions, but my first thought is that C4D is running out of memory to load the image sequence, rather than a Corona error, but I can't say for sure without knowing more info about what, when and how it all happens :)
Cheers!
EDIT - also, does the same image sequence render (on a regular object, like just a cube) with other render engines?
-
That error was during the scene upload. I will try it again.
-
Oh ok so not an error in C4D at all! But when sharing the file across the web, now it's clear!
Not sure how you are sharing, posting to the forum probably won't work, but the private uploader would be the way to go - https://corona-renderer.com/upload (there's a link on there too for super large files)
-
I'm uploading a 370 mb or so rar file containing everything. When it finishes i get the error.
-
The limit on the forum is well below that; the private uploader limit is listed on the page, it's 256 MB so your file is larger than that - you'll have to use the link at the bottom of the Private Uploader page which allows 10GB uploads. Cheers!
-
uploaded
-
All working as expected here - I stripped out the non-Corona render items (lens effects etc), deleted the background object that we know doesn't work, took off motion blur, removed animation from the camera etc, that way I could render different frames and use A/B comparison in the VFB to see if things were actually changing, and both the native C4D and the CoronaMtl with Self Illumination (I turned off the Diffuse channel) updated with the image sequence.
I did click on "Calculate" for both the native C4D and Corona materials, though both were showing a frame range already. Cinema 4D R19, Corona latest daily build.
-
Quick screen grab of the A/B comparison between frame 0 and frame 161, cube on the left is the C4D native, one on the right is the CoronaMtl.
-
This is damn peculiar
-
Have you tested a new scene with just a cube and the sequence applied in a CoronaMtl, just to check all works in that scenario? Also, strange question I know but I will ask :) Are you sure the texture isn't animating in the main scene (though you may need to remove the non-Corona compatible elements in the render set up and the Background object) - I only ask because with camera moves, motion blur, and the relatively slow animation in the sequence, it could be that it is animating, but just isn't totally clear that it is changing. I know it wasn't clear to me just looking at the realtime viewport in C4D, I had to render and do the A/B to be sure something had changed :)
For the Background object, that won't work for sure since Background objects are not supported in Corona for C4D (at this time).