Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nesha_2

Pages: [1] 2 3
1
IR of the latest build still doesn't recognize animated camera movement.

2
I think somebody (perhaps even from your team) mentioned here that IR doesn't register camera animation at all. It starts upon camera movement over and over again, but renders only the first frame. I'm talking about latest daily build. This behavior is consistent on both Win 10 and OSX (El Crap). Please check video in the attachment.
P.S. IR is now waaay more responsive.

3
hi guys,

I've a problem with the last daily build.

The rendering remains blocked on "preparing scene data" only during the second rendering.
Ex :
open my scene, i clic render. It work
I want to do another render. I clic render and it block on "preparing scene data"

If i stop, everything freeze, and i need to close C4D.

It happens on "big" scene. I've test with a very simple scene, i dont have the problem.

very embarrassing...  I'm the only one ?

MacOS Sierra10.12.6
Full-speed non-debug version
Build timestamp: Sep 29 2017 21:39:28
Version: B1 daily Sep 29 2017 (core 1.7 DailyBuild Sep 29 2017)
Cinema version: CINEMA 4D Studio R17.055 S
Plugin status: initialized successfully

No, you're not alone. Happens to me as well (MacOS El Crap 10.11.6 and Windows 10). Problem is that IR doesn't show everything as it should (bump) so previous way of working has to be used (make changes & render procedure). On second render start it gets stuck on "preparing scene data", requiring restart of the C4D, which gets irritating pretty fast. Since this prevents proper usage of the plugin, it imposes itself as FIRST issue that should be addressed ASAP in order to make use of corona plugin.
EDIT: Restarting Corona VFB after EACH render seems to "solve" the issue. Not very efficient way of working, but there you go.

4
First impressions: On macbook pro IR is pretty good. On two xeons rig (80 cores) it's blazing fast. So for this initial release with IR, seems like a good job. Shadow catcher is working as it should, as well. Didn't try IR on complex scenes. Will report back as I go.

5
Hi all, doing some test with the latest build and Cinema R19. There's a problem with the render region in VFB: it doesn't work, the rendering process ignores the region.

Hi, read what I wrote above (second post above). Perhaps you need to restart the render.

6
Hi All,

I am a mac user and have been testing daily builds every time they come out and have to keep reverting to the Alpha version that is on the downloads page of the main site. I understand that these versions may be unstable. Are any other mac users having similar problems?

I am keeping displacement off on all materials but I do use lightmix.

Phil

Mixed user here. Love working on mac and it crashes with large scenes (typically when trying to move camera), but ONLY occasionally whereas with the same scene Win machine does not. I do think it has something to do with the fact the scene is large and Mac machine has 16 Gb of RAM, whereas win machine has 64. When working on smaller scenes I don't have such problems with Corona. Pretty stable so far (except for few known issues). Worth mentioning I'm still on 10.11.6. Have had problems with Sierra, so I'll stay with El Crap for the time being (or until I switch completely to win machines - a lot of field work - waiting to see whether good win laptops with latest AMD (perhaps threadripper) or latest core i9 mobile versions will appear - which may never happen due to the power consumption of such beasts).
Hi,

I am sorry for the crashes but to be able to fix them we must reproduce the problem. I will try to create a scene with a lot of geometry, materials and lights (it does not have to be a meaningful scene only the count of objects matters) and I will try to reproduce it. Could I ask you to do the same to see if you can reliably reproduce the crash? Thank You

Nikola

It is OK, no need to be sorry. You're doing great so far. I cannot reproduce crashes reliably myself, unfortunately. For example, the scene I was working on yesterday was a massive one - not a single crash. So go figure. Could be that the new daily build fixed something or it just decided not to crash on me. Btw, while working on that same massive scene I noticed that Region render doesn't work properly or at least, the way it worked before. Now when starting render and marking render region, it doesn't start to render just that region but keeps rendering the whole thing. I have to restart render for render region to have effect. Conversely, when disabling/removing render region while rendering, whole scene doesn't start to render, it keeps rendering just the render region. Hope this won't be the way it is going to work from now on, because for big scenes it does matter it to behave as before. Thanks.
P.S. It is a real pity shadow catcher is not implemented yet. Include/Exclude tab in the light material is not functional yet?

7
Hi All,

I am a mac user and have been testing daily builds every time they come out and have to keep reverting to the Alpha version that is on the downloads page of the main site. I understand that these versions may be unstable. Are any other mac users having similar problems?

I am keeping displacement off on all materials but I do use lightmix.

Phil

Mixed user here. Love working on mac and it crashes with large scenes (typically when trying to move camera), but ONLY occasionally whereas with the same scene Win machine does not. I do think it has something to do with the fact the scene is large and Mac machine has 16 Gb of RAM, whereas win machine has 64. When working on smaller scenes I don't have such problems with Corona. Pretty stable so far (except for few known issues). Worth mentioning I'm still on 10.11.6. Have had problems with Sierra, so I'll stay with El Crap for the time being (or until I switch completely to win machines - a lot of field work - waiting to see whether good win laptops with latest AMD (perhaps threadripper) or latest core i9 mobile versions will appear - which may never happen due to the power consumption of such beasts).

8
i have 2 questions related to the latest beta:

1. whats the "standalone" in install? i cannot find it after installation - what does it do? - is it needed on "slaves" for DR ?
2. teamrender is there, yes but what about corona DR? am i missing something here or how can i enable corona DR?

Yep. Mind giving us a quick answer to this question?
UPDATE: Found this, but it is for Max. Looks like the same applies to C4D: https://coronarenderer.freshdesk.com/support/solutions/articles/5000547357-how-to-render-using-corona-standalone-
Still not sure what the regular C4D user would use it for.

9
Hello Cestmir. Sounds great! Thanks!

10
Seems like that. Sad but true.

11
Just came to my attention. Most certainly the bad news. Looks like a competition removal. They will take technology they want and probably kill Corona or make it a stepchild with little to no updates. If true, that's a real shame. Thoughts?

12
Hi all,

the next daily build (2017-07-24) of Corona for Cinema 4D Beta 1 is out.

Download link:
https://drive.google.com/drive/folders/0B7xyYS3daSJ7V3BJZWlMR2EzUG8

Changelog:
https://forum.corona-renderer.com/index.php/topic,15602.msg106037.html#msg106037

Hello, thanks for new version. Just to clear something up and to avoid confusion, here, after installation, it says "Build timestamp: Jul 18 2017 22:20:00
Version: B1 daily Jul 18 2017 (core 1.7 DailyBuild Jul 18 2017)",  not "2017-07-24" as Nikola put it above (same is in the Changelog). That is OK?
Yes,

That is OK. I built it on Jul 18 2017, but I managed to release it (so everything was tested and I was back at work) yesterday.

Nikola

Thanks for the quick reply!

13
Hi all,

the next daily build (2017-07-24) of Corona for Cinema 4D Beta 1 is out.

Download link:
https://drive.google.com/drive/folders/0B7xyYS3daSJ7V3BJZWlMR2EzUG8

Changelog:
https://forum.corona-renderer.com/index.php/topic,15602.msg106037.html#msg106037

Hello, thanks for the new version. Just to clear something up and to avoid confusion, here, after installation, it says "Build timestamp: Jul 18 2017 22:20:00
Version: B1 daily Jul 18 2017 (core 1.7 DailyBuild Jul 18 2017)",  not "2017-07-24" as Nikola put it above (same is in the Changelog). That is OK?

14
Hi All,

I have been using the most recent daily build plus the one before it for about three weeks. I am a mac user and I getting exactly the same issues across three macs (A 12 month old top spec 27inch imac, 12 month top of the range 21inch iMac, and a couple of years old mac mini). I am having issues with just random freezes causing Cinema to crash. The scenes I am render are complicated as they are architectural visualisations but no displacement is used anywhere. The crash can happen at any time, there is no pattern to it.

The other issue I have is corona also crash 100% every time before it gets below around 2% noise level, what ever version of corona I use so I have to set it to stop before then.

Finally the latest daily build is a lot slower than the alpha version on the downloads page. Also it absolutely hammers the processor, 100% activity during renders, a lot higher than other renderers I have used in the past.
Not complaining at all, loving the simplicity of corona, just thought I would report back with my issues as two out of the three macs I am using where the highest spec you could buy at the time of purchase.

If anyone has any thoughts, let me know.

Thanks,

Phil

Well, personally, I prefer all of my 80 cores to work at 100% while rendering and as far as I'm concerned, this is the way it should behave. There should be feature for adjusting how many cores you'd like to dedicate to rendering, though. Not sure if that is present right now.

15
Has anyone managed to get any results out of the bloom and glare pass yet? Its been in for a few releases but it only ever comes out as black for me. Am I doing something wrong or is this an on going issue? Cheers

Yeah, same here. Been asking same question, to no avail. Complete mystery. I'd guess it is safe to say it still doesn't work. And yet, perhaps we're doing something wrong ;)

Pages: [1] 2 3