Chaos Corona Forum

Chaos Corona for Cinema 4D => [C4D] Bug Reporting => [C4D] Resolved Bugs => Topic started by: walterfog on 2017-01-02, 11:00:31

Title: c4d OSX stop work with corona all version
Post by: walterfog on 2017-01-02, 11:00:31
I need urgent help ... this morning I do not open anymore Cinema 4d ... well .. the problem is the corona plugin because if I remove the plug c4d working fine ... I can not understand why because I have always worked quietly ... I also tried to connect to the official forums today but the site does not work .. I urgently need to understand how to solve the problem .. details:
C4D r17.048 study
OSX 10.9.5
corona  a6 all version

I tried to uninstall and re install it with the appropriate installers but nothing ... I do not know which way to turn …
I also have the c4d reports when I hardly close c4d.
Title: Re: c4d OSX stop work with corona all version
Post by: walterfog on 2017-01-02, 11:07:02
this happen with c4d r16 r17 and also r18... with fresh install or not... simply c4d OSX don't work if I have the corona plugin installed!!!
I have to say that 3 days ago everything works fine with the a6 rc6 version.... nothing change in my system, new year apart!!!
Title: Re: c4d OSX stop work with corona all version
Post by: Sergey on 2017-01-02, 12:28:12
walterfog, start the cinema4d and try to wait a few minutes. I have the one idea..
Title: Re: c4d OSX stop work with corona all version
Post by: walterfog on 2017-01-02, 12:40:06
walterfog, start the cinema4d and try to wait a few minutes. I have the one idea..

cinema is started....waiting for your help....
Title: Re: c4d OSX stop work with corona all version
Post by: Sergey on 2017-01-02, 12:51:46
walterfog, start the cinema4d and try to wait a few minutes. I have the one idea..

cinema is started....waiting for your help....

Do you started c4d with Corona plugin or without? Start c4d with Corona and wait a few minutes.
Title: Re: c4d OSX stop work with corona all version
Post by: walterfog on 2017-01-02, 12:55:33
walterfog, start the cinema4d and try to wait a few minutes. I have the one idea..

cinema is started....waiting for your help....

Do you started c4d with Corona plugin or without? Start c4d with Corona and wait a few minutes.

if i install corona cinema do not start.... simply freeze.... write what I could do... now I have to go away 30 minutes...
Title: Re: c4d OSX stop work with corona all version
Post by: Sergey on 2017-01-02, 13:01:33
On the my system (Win7x64) Cinema4d starting about 20-30 sec now. I think what problem in connecting to license server of Corona.  You will try start and wait - don't touch the c4d.
Title: Re: c4d OSX stop work with corona all version
Post by: Nikola on 2017-01-02, 13:35:24
Hi, I am back from my Christmas vacation. Does your Corona work now? (we had problems with our server) I also probably found the cause of the problem with crashing Corona and also other renderers in combination with Corona but I must make more tests yet. So I would like to ask you (especially walterfog ;-) ) for your patience.

Thank you
Title: Re: c4d OSX stop work with corona all version
Post by: walterfog on 2017-01-02, 13:44:37
Hi, I am back from my Christmas vacation. Does your Corona work now? (we had problems with our server) I also probably found the cause of the problem with crashing Corona and also other renderers in combination with Corona but I must make more tests yet. So I would like to ask you (especially walterfog ;-) ) for your patience.

Thank you

OK Nikolat... thanks for your support :-) I hope you could find very soon the solution cause I have an entire project made with c4d and corona... i don't know why corona don't work now, but simply c4d freeze in the loading plugin phase... here a screen that show whats happen...
Title: Re: c4d OSX stop work with corona all version
Post by: houska on 2017-04-24, 15:09:55
Hi, walterfog,

from your stacktrace, it is clear that what happens is that the main application thread is blocked on getting a response from the licensing server. We have fixed a hang-up in licensing recently, so it might as well be that your bug is fixed. Could you please check it?

Thanks for the report!