Author Topic: MATERIAL OVERRIDE CRASH IN C4D  (Read 2926 times)

2017-09-02, 17:55:02

John_kcee

  • Users
  • *
  • Posts: 1
    • View Profile
When I try to use the material override, corona crashes and Cinema4d also crashes

2017-09-02, 19:06:33
Reply #1

burnin

  • Active Users
  • **
  • Posts: 1642
    • View Profile
Can you share a scene in question or describe it in detail with steps to reproduce?
Simple/basic stuff works here.

eg

2017-09-04, 10:42:48
Reply #2

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Can you share a scene in question or describe it in detail with steps to reproduce?
Simple/basic stuff works here.

eg


Thanks burnin, exactly my words :-)

Edot: Also, what version of Corona for C4D are you on?

2017-09-04, 14:01:09
Reply #3

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6102
    • View Profile
Tested in two full scenes here, including the free Paris Apartment scene which is quite complex, and all worked as expected here with no crash.
Tom Grimes | chaos-corona.com
Product Manager | contact us

2017-09-04, 19:56:49
Reply #4

burnin

  • Active Users
  • **
  • Posts: 1642
    • View Profile
Thanks burnin, exactly my words :-)

Edit: Also, what version of Corona for C4D are you on?

always on the latest, since i only do testing and writing down notes, helps me better manage stuff & be consistent (if i make any mistake is also easier to solve)

2017-09-05, 09:36:20
Reply #5

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
always on the latest, since i only do testing and writing down notes, helps me better manage stuff & be consistent (if i make any mistake is also easier to solve)

Oh, sorry for the confusion, I meant the OP :-)

2018-02-01, 15:12:19
Reply #6

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Closing, because of lack of information. If this or similar bug is encountered again, please report in a new thread!