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 - TomG

Pages: [1] 2 3 ... 371
1
I am not sure what you mean by "addressed"? There is new functionality in the Corona Sky, which means any scene created with a new Corona version may not load and work as intended in an old Corona version - there is nothing to "address" there, as old versions can never handle new functionality, not just with Sky but with any other feature. Of course scenes from earlier Corona versions should load and render as intended in the newer Corona version, which is the important part :)

So this warning is just to tell you, don't save a scene using the latest version if you for any reason will ever ever go back to an earlier Corona version.

Oh the bit that should be addressed is, if you have multiple Corona installs at once - we'll have to keep two versions of Sky installed :)

2
[C4D] Bug Reporting / Re: camera sync
« on: Today at 12:56:46 »
Please always specify the version explicitly, because it does happen that someone for example doesn't notice a new hotfix, and believes they have the latest build, but they don't :) Explicitly saying Corona 11 HF 2 removes any such doubt or confusion (same with the DCC).

3
Most welcome!

4
[Max] Feature Requests / Re: GAUSSIAN SPLATTING
« on: Yesterday at 15:25:16 »
Virtual tours would be generating splats from renders, which should be possible with any splat generator out there I would imagine :) Can be done today via that approach I would guess, but have never tried it. The Corona side would only come in for rendering splats inside Corona (use case would almost exclusively be for surrounding environments, from what I can see).

5
[Max] Feature Requests / Re: GAUSSIAN SPLATTING
« on: Yesterday at 12:48:56 »
There are investigations and research going on into Gaussian Splatting at Chaos of course. Until that is complete though there would be no work done on integrating rendering of Gaussian Splats into Corona; we'll wait and see how the investigations work out, and then after that we'll consider if and when we'd add this to Corona. Which all adds up to this being a 2025 thing at the earliest, assuming it gets chosen for implementation.

6
Understood, and this was why we were sure to mention some months ago that animation from the host would not be in this release, but planned for the next version if all goes well. We wanted to be sure the information was out in advance as to what this would and would not do. Naturally, the integration is a large project, a lot of complex work, which is why it has a foundational release now with future functionality planned to be built on that.

8
[C4D] I need help! / Re: Team Rendering
« on: 2024-06-10, 17:18:49 »
"A render node computer just renders the scene and does not display the Cinema 4D user interface, so only one render node license is required."

No, only one GUI license is required. However, to render on two machines simultaneously, two render licenses will be required. A standard Corona license is a GUI and a render node license, while a separate render node is just a render node with no GUI license. So, with one Corona and one Corona Render Node license you can have 1 GUI open on one machine, and have two machines rendering.

Without a second render node though, only one machine can actually be rendering at once (e.g. if you just have one Corona license), and a second license (which can be just a Render Node license, which is cheaper) will be needed for the second machine if both are to render at the same time.

If you have a Corona license from before Corona 8 which you have kept subscribed and active since then, then you will still have 3 Render Nodes with it; but if you have subscribed since the release of Corona 8 when the licensing changed, you'll need an additional Render Node for each additional machine that will be rendering at the same time.

9
Covered in several other threads, including one two days ago :) a)  The operator was temporary and technical, to provide compatibility with color management workflows introduced in the latest Maxes and C4Ds. It was removed once our compatibility was improved. b) One intended for artistic use, with the full Gamma, Lift, and Gain parameters, is coming in Corona 12. Expect it in the next daily.

10
[C4D] Daily Builds / Re: missing gamma correction
« on: 2024-06-06, 17:28:17 »
It can be easy to miss - forum search functionality is horrible :( As an aside, that should be addressed toward the end of the year though, as we are looking in to new forum platforms; a long time out before we see what any decisions are, but it's good it is being looked into as I do dislike the search on here.

11
[Scatter] I need help! / Re: Corona Scatter Problem
« on: 2024-06-06, 14:30:02 »
This really should be a separate thread as it's a separate issue.

Would need to know the tech specs of your machine, in particular the GPU, as it is possible you are simply exceeding what can be displayed in the viewport in the host app (C4D in this case). As for the second about IR, would need to see examples of the scatter set up, the rendering result you are getting, you mention IR is this true also in final render, and other such details please :)

12
[C4D] Daily Builds / Re: missing gamma correction
« on: 2024-06-06, 14:25:00 »
Do see the other threads on this :) From those threads, there are two points - point 1, the gamma was added for technical reasons to adapt to the new OCIO / Color Management in Max and C4D, until we changed Corona to be compatible with that new functionality; the technical gamma was removed once Corona was compatible. Point 2, we'll be adding Gamma, Gain, and Lift to tone mapping, as the artistic gamma, as people had started using the one added purely for technical reasons as an artistic control (not its intended use), and this will be in Corona  12.

13
Do make sure Denoising is on for each LightSelect :) Also do note that if a bright light shining on an area is turned off in LightMix, that might sometimes lead to noise being seen in the area that light used to shine on. This is because Corona gives processing priority to the brighter, more important light in that area, and less processing to the other lights in that area - and you will see that they were given less processing when you turn that bright light off. For this reason it's often best to keep lights similar intensity and white in the scene / Beauty, if you plan on making large changes in LightMix, as this will keep all lights at similar importance (similar brightness), and give the most flexibility in adjusting colors (keeping them white). Does mean the Beauty will look very strange indeed, but gives more flexibility in the LightMix phase.

14
For single CPU high thread core counts, the problem was isolated some time back and the fix moved into the dailies https://forum.corona-renderer.com/index.php?topic=41598.msg221510#msg221510 Those machines are now scaling in performance as we would expect. Only dual CPU systems remain with some extra issue.

The list is, with Corona 12 dailies, every CPU is working unless you are running dual CPUs with more than 64/128 cores/threads.

PS, I have also confirmed with support that they are regularly responding to you, so not sure why you believe there is a lack of response?

15
It is possible the entire series is affected (when run in dual CPU set ups), as they all fit into the "dual CPU, high thread/core count". It's still under investigation, tracking down the actual cause is tricky here as the "obvious" candidates were ruled out some time ago and that leaves it as something much more unusual.

Pages: [1] 2 3 ... 371