Not sure at the moment on influence on them - usually not, but these are different than what we’ve seen before, in that they appear after a certain number of passes. I just rendered one of the problematic scenes, at a reduced resolution of 2,000 (down from 8,000) and reached pass 15 with no NANs; on a machine with less memory, Ben saw NANs after 8 passes or so at the same resolution. So, it could be memory related, but we don’t know for sure yet and are still testing.
If your machine is getting close to maxing out the memory (e.g. C4D is using something like 26 or 27Gb out of 32Gb - the rest likely used by Windows and other stuff), it MIGHT be that reducing the resolution and so reducing memory usage might help. But until some more tests complete, we won’t know for sure, sorry.
Hi Tom,
thanks for explanation!..There are 96GB RAM on this computer and it´s “only” an interior, so I don´t think there were some memory issues on that scene …on the same machine some really complexe exterior scenes reaching the RAM-limits were running in Beta without problems…So I test this scene in Beta now!
Also, if those affected here can try re-rendering again with a different light solver other than ‘auto’ for example" ‘scalable’ I’d be interested to know if this solves the issues. Thanks
We need to constantly update the Corona core to the newest version, because it includes important updates and fixes and sometimes also new interesting features for you. Of course, this comes with the risk that sometimes, there’s a bug that comes with the new core (which seems to be this case), but these bugs are usually fixed fast and it’s enough to update to a newer core version again. So bear with us and try the new daily once it’s out, I think the issue might be fixed there.
Of course, we might also try not updating the core so often, but then the C4D users would have to wait for the new features for a longer period of time.
For me working commercially, it is better to have less bugs and less features. It is very stressful what you’re struggling with bugs and the client is waiting for the viz.
Guys, keep patching the core Looking forward to next hotfix soon! I really keep my fingers crossed.
Changing the light solver fixed all my bugs, with strange artifacts and black dots. So for me is ok, I know how fix bugs.
That’s understandable. Our development process is set up so that we limit the amount of issues in the final releases, but sometimes it can happen. But my point was that to limit the number of issues to zero, we’d basically have to stop adding new features, which is also not in the interest of you - the users.
I switched back to beta B2 to let render this problematic scene, that produced black dots every time with the new corona version (once on pass 18, next time on pass 40 etc…):
Rendered with Beta 100 passes, and then overnight: No black dots…
As niedzviad already said…I´m also more happy with a version with less features but working stable…I really don´t want experience the situation that on the morning after an overnight-render and with a deadline in sight we stand in front of the screen with an unusable render with black dots …We often have tight deadlines and the result of the work of a whole team of architects also depends on this image when a perspective is obligatory in a project / competition.
I understand that in the development (really happy about your great work ) something can go wrong and unexpected happens…but please consider me / our situation too…
With vray for C4D I also decided once not to use the newest version but stay with the older one, as long as problems were reported and first switched after some fixes…
So I really would appreciate the info I already asked for: Will it be possible to still use Beta2 some way with a bought licence for Corona 3…?
Thanks!
I tested with the solver light Scalable and Auto. The black dots disappear, but there is a “little” problem about render time! With Scalable the render takes two hours more to reach the same noise level…
have you tried the newest daily build already? I think it might fix the black dots. Daily builds are availabe on our Google drive: Daily - Google Drive
Hi @houska,
I tested the build you asked us to try (the one on google drive - r4) last night, with the same image, the black dots disappear (at the moment). But there is another “little” problem. With previous release if I render in Cinema4D picture viewer (Shift+R), then open the Corona VFB I saw the image and I can modify and saw all channels, now NOT.
I have the image only on picture viewer…!
Please, as I ask in open ticket, I payed for the license and I would like that it works!
I use it for work, not for hobby or game.
The beta version works perfectly…Damn…What’s happened now?
Now we pay and it doesn’t works!
Looking forward to next hotfix soon! I really keep my fingers crossed.
