Author Topic: A6 RC1 MAC does not work with most recent Cinema update.  (Read 7050 times)

2016-10-31, 22:56:48

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Corona A6 RC1 will instantly crash if you try to use it with Cinema 18.028

2016-11-01, 11:12:19
Reply #1

4b4

  • Active Users
  • **
  • Posts: 163
    • View Profile
I haven't had any crashes here using it in 18.028.

I did delete the corona folder in plugins prior to installing the latest RC, not sure if that's made a difference?

2016-11-01, 15:09:38
Reply #2

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile

2016-11-01, 21:07:04
Reply #3

4b4

  • Active Users
  • **
  • Posts: 163
    • View Profile
Missed the fact you're on a MAC...

2016-11-03, 18:17:17
Reply #4

rendart

  • Active Users
  • **
  • Posts: 13
    • View Profile
The same goes for the latest R17 update R17.055. I have tested Corona on my other machine with R17.053 and there was all fine. I'm on MAC OS 10.11.3.

2016-11-07, 09:38:38
Reply #5

davidlecardinal

  • Active Users
  • **
  • Posts: 10
    • View Profile
I tested on MAC with an older version of C4D, fine.
only Bloom doesn't work at all. :(

2016-11-09, 10:03:24
Reply #6

GokhanB

  • Active Users
  • **
  • Posts: 20
    • View Profile
same problem on macOS Sierra & C4D R17.055...Corona Render doesn't work....when I hit the "Render" button C4D crash "libCoronaCore.dylib" error....any solution?
thanks for help.

2016-11-09, 17:52:45
Reply #7

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Any update on this?  Is is a huge bug affecting everyone on a Mac with a current install of Cinema v17 & v18.

2016-11-10, 13:14:04
Reply #8

t-tucker

  • Users
  • *
  • Posts: 2
    • View Profile
Im on macOs Sierra 10.12.1, C4d R17.055 on a MacBook Pro Retina 15 (early 2013) and so far it renders well. But VFB don't update. Its not "refreshing" or "updating" when e.g. change camera position or anything else. Is this not supported yet?

2016-11-10, 13:59:56
Reply #9

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5466
    • View Profile
t-tucker - Interactive Rendering is disabled in A6, and using the dropdown in the VFB just starts a regular render. This is done as IR is not stable yet (so rather than have people try it and experience lots of crashes, it just runs a regular render, which means updates to the scene don't change the rendering), while we focus on integration between VFB and native Picture Viewer, and stability of "everything else", and integration of Corona 1.5 core for A6. Team Rendering and Interactive Rendering will then get full focus in A7! You can check progress on the C4D Roadmap, TR and IR are under bugfixes for A7 https://trello.com/c/ZrRxhsA3/17-bug-fixes

Thanks!
    Tom
Tom Grimes | chaos-corona.com
Product Manager | contact us

2016-11-10, 21:18:12
Reply #10

GokhanB

  • Active Users
  • **
  • Posts: 20
    • View Profile
Hello, I was installed "Alpha 6 RC2" a few minutes ago but same problem on macOS Sierra & C4D R17;
The plugin libCoronaCore.dylib has crashed.
More information can be found in
'/Users/HULU/Library/Preferences/MAXON/CINEMA 4D R17_89538A46/_bugreports/_BugReport.txt'.
After clicking 'OK' unsaved scene files will be saved as '_bugreports/_recovery_xxx.c4d'
« Last Edit: 2016-11-10, 21:23:52 by GokhanB »

2016-11-10, 21:39:36
Reply #11

fabio81

  • Active Users
  • **
  • Posts: 444
    • View Profile
Hi

just installed, and I noticed the difference calculation times, appear to increased

2016-11-10, 22:39:34
Reply #12

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
RC2 Mac is still completely unusable. If I touch any Corona material or hit render I will get an instant crash.

OS X 10.11.6
CINEMA R18.028 S