Author Topic: C4D Hanging & Crashing  (Read 9343 times)

2015-10-01, 04:01:10

Fythos

  • Active Users
  • **
  • Posts: 32
    • View Profile
I'm getting a problem with the new version.

It crashes alot, when using the IR, making new materials, placing old materials from the content browser etc.
Seems it crashes when corona is forced to do any type of render, IR or material previews with the thumbnails.
I removed all my plugins already and still crashes.

Is anyone else having this behaviour?

UPDATE: I might be wrong, but i removed arnold and pixelberg and now editing materials with corona is smooth as ever with a4.
I tested this for just 20 minutes but so far no crashes, dunno wich one is it or if both but maybe it can help someone else. Ill test more tomorrow cause it's late over here.
« Last Edit: 2015-10-02, 06:59:03 by Fythos »

2015-10-01, 04:41:16
Reply #1

pBarrelas

  • Active Users
  • **
  • Posts: 82
    • View Profile
We were getting crashes mostly on R15 and R16 using the RCs. R17 seems more stable, though! I'll have to make some tests with A4!

2015-10-01, 06:49:24
Reply #2

Old man

  • Active Users
  • **
  • Posts: 13
    • View Profile
I'm also getting a problem. Сan not use old mat. C4D not responding.

2015-10-01, 09:55:14
Reply #3

olcaykayihan

  • Active Users
  • **
  • Posts: 41
    • View Profile
Old materials not responding and crashes generally interactive render

I am not sure this is bug or not but bump map and reflection chanel are giving very different results than v3

2015-10-01, 11:39:49
Reply #4

Fythos

  • Active Users
  • **
  • Posts: 32
    • View Profile
At first i thought it was old materials that were crashing it, but then i gave it a few more tries and it still crashed with the newly created materials and scenes.

Had to do a small project with some urgency and it was a nightmare to work with it. After that i had to reinstall a3 again wich hasn't crashed on me not even once on any of my machines.

Gonna wait for the fix.




2015-10-02, 04:25:07
Reply #5

sonnar

  • Active Users
  • **
  • Posts: 20
    • View Profile
yes, same problems with IR and materials here

2015-10-09, 16:20:05
Reply #6

oh.stv

  • Active Users
  • **
  • Posts: 17
    • View Profile
Same here, i also just noticed it with old Materials.

2016-10-31, 11:09:08
Reply #7

Franck BERNIERE

  • Users
  • *
  • Posts: 1
    • View Profile
Impossible to use there, crash on each time Corona use the renderer (material editing, render in the Viewport, the picture viewer, or VFB)... It's quite a shame, and after looking online for solution to solve it, I didn't find any way to solve this issue...

Cinema4D R17.055 S
A6 daily Oct 14 2016 (core 1.5 DailyBuild Oct 14 2016)

Mac Pro 2014 64gb AMD V500*2
OSX 10.9.5
« Last Edit: 2016-10-31, 11:17:57 by BerTiN25 »

2016-10-31, 17:18:29
Reply #8

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
This is a known bug.  Something in the recent Cinema update broke Corona.  It affected v17 and v18.  Works fine with 17.048.

2016-11-01, 02:49:43
Reply #9

Gnorkie

  • Active Users
  • **
  • Posts: 21
    • View Profile
This is a known bug.  Something in the recent Cinema update broke Corona.  It affected v17 and v18.  Works fine with 17.048.

Well, and how to update only to .048?

2016-11-01, 03:09:50
Reply #10

Gnorkie

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

2016-11-13, 21:18:08
Reply #11

wiem

  • Users
  • *
  • Posts: 1
    • View Profile
HI everyone,

I had the same problems with my Cinema 4d r17 (working on a mac os10.11.6) and the solution is as Gnorkie says: up- or downgrade to 17.048
Thanks a lot, Gnorkie!