Author Topic: Animated Textures do not work  (Read 10318 times)

2018-03-27, 19:22:49

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
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
Tutka Tutkowicz Tupolew

2018-03-27, 23:45:22
Reply #1

Eddoron

  • Active Users
  • **
  • Posts: 552
  • Achieved Pedestrian
    • View Profile
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.

2018-03-28, 13:25:21
Reply #2

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
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.
Tutka Tutkowicz Tupolew

2018-03-28, 15:36:03
Reply #3

Beanzvision

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 3882
  • Bengamin
    • View Profile
    • Cormats
I see that your using a "background" object, to my knowledge they aren't supported in Corona.
Bengamin Jerrems:
Portfolio l Click me!

2018-03-28, 16:42:21
Reply #4

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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?
Tom Grimes | chaos-corona.com
Product Manager | contact us

2018-03-28, 18:37:38
Reply #5

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
It does not work at all on a normal object with a corona material. I don't understand what's happening here.
Tutka Tutkowicz Tupolew

2018-03-28, 18:59:00
Reply #6

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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.
Tom Grimes | chaos-corona.com
Product Manager | contact us

2018-03-28, 21:38:57
Reply #7

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
413 Request Entity Too Large. Also, i followed the same procedure as in the video.
Tutka Tutkowicz Tupolew

2018-03-29, 14:15:12
Reply #8

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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?
Tom Grimes | chaos-corona.com
Product Manager | contact us

2018-03-29, 15:53:36
Reply #9

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
That error was during the scene upload. I will try it again.
Tutka Tutkowicz Tupolew

2018-03-29, 15:58:22
Reply #10

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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)
Tom Grimes | chaos-corona.com
Product Manager | contact us

2018-03-29, 17:05:12
Reply #11

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
I'm uploading a 370 mb or so rar file containing everything. When it finishes i get the error.
Tutka Tutkowicz Tupolew

2018-03-29, 17:12:36
Reply #12

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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!
Tom Grimes | chaos-corona.com
Product Manager | contact us

2018-03-29, 19:14:00
Reply #13

Sulphurous

  • Active Users
  • **
  • Posts: 24
  • fdsf
    • View Profile
uploaded
Tutka Tutkowicz Tupolew

2018-03-29, 21:17:56
Reply #14

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
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.
Tom Grimes | chaos-corona.com
Product Manager | contact us