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 - Nejc Kilar

Pages: [1] 2 3 ... 69
1
[Max] Feature Requests / Re: Fuzziness option in material
« on: 2021-07-23, 12:17:43 »
I'd recommend checking out the Sheen layer that's built in to the Physical Material in v7. It doesn't create any additional geo but since you aren't looking for an extremely detailed close up shot it should work really well.

2
Hardware / Re: 3970x experiences. Heat, speed, ram etc..?
« on: 2021-07-20, 10:44:52 »
@marius iordache
Here is how I got the temps in a range I personally am much more comfortable with :) Hope it helps.

At 3,7ghz my average rays drop from 12,800 to 11,600.
Thats around 10% difference. For much lower temperature and power consumption seems very reasonable. But somehow I cannot stand this 10% slower speed. Not effectively but OCD related.

OK so I've found a simple setting to cure most of the temperature "problems". Not really problems but you know what I mean :)

So I have PBO set to AUTO which should mean its OFF from what I understand but that clearly isn't the case. If I go under the PBO settings and set the temperature limit (its called something different, can't miss it though) to a custom of say 70 degrees... Well, the CPU won't go over 70c.

It is that simple.

So now I'm getting ~3.9ghz on all cores and I retain a solid 4.3ghz/4.4ghz single core turbo - at least thats what I can monitor from Windows. The rendering speed according to the benchmark is the same as it was with PBO off, maybe sometimes falling behind by 1 second (29s -> 30s).

The temps rarely if ever go above 70c. They go above because my fan curves need a second or two to kick in high speeds :) Rendering over night is constantly at 70c.

Hope that helps :)

Hello, thank you for the reply, however i do not understand if i have to put Celsius Value into the TDP tab and then what do i put in the rest 2, maybe leave"0" and are set to auto ?. Also there's another option for cTDP in wich i put 80 and nothing happened, when i checked afterwards it was set to 0.
I searched some stuff on youtube but i got more confused.
Thank you in advance

Totally didn't see your reply, sorry! What you probably want to do is go under Precision Boost Overdrive (set it to manual) and in there you'll see a field where you can input your temperature targets.

I'm necroing this thread just in case anyone else is running into the same issue :)

3
Can you share water material used in tutorial? The one with shader ball in sea.
Thank you.

Sure thing! This one was made by our fellow Benji so all the credit goes to him (shared with his permission). Do note though that this is somewhat of a fake MTL because we don't really have refraction enabled - really wasn't needed for the effect we were going for.


4
As far as I understand it, you enable the shader by checking "Volume Effect" in the Sky object, then it creates an atmospheric haze effect.
The density you control with the scale parameter below the checkbox. There's also an Altitude setting that I don't fully understand yet (and neither why it's clipped at 1500 meters).

Hope this helps a bit at least.

Michael

The atmospheric haze effect is indeed the volume effect. I personally find it to be exceptional for exterior scenes, really makes a big difference. As Cinemike said the scale controls the density basically although do be ware that 1.0 is typically the most "real world" scale you'd want to use - you can however still change it to better control how the image looks like artistically.

Altitude on the other hand gives you do the ability to change the sky to look like it (and what lighting it emits) would at X meters of altitude. So the sky will look more blueish the higher up in the atmosphere you go (higher altitude) and the horizon line will be harder to distinguish. Really fun to use if you've are doing say a mountain cottage render :)

Hope this was helpful :)

edit: The altitude cap however appears to be a bug. Thanks for bringing it up!

5
Howdy!

Could you please try disabling the "adaptive light solver" in the render settings -> performance compartment and then try to re-render? Kind of looks like that could maybe be the culprit, would really appreciate it if you could try it out and report back.

Thanks!

6
[Max] I need help! / Re: Can not render
« on: 2021-05-26, 12:56:31 »
Corona will render indefinitely unless you specify a parameter that when reached will stop the rendering process. Those parameters are found under the Render settings -> Scene menu. In there they are called "Pass limit", "Time limit" and "Noise limit".

You can set any of the above parameters to your liking and that'll make Corona stop rendering.

But why is Corona rendering indefinitely? Well, Corona is a progressive renderer which means that each rendering "pass" adds more pixel information on top of the existing image. Basically, with each pass the image will be cleaner and less noisy because it will be better sampled.

So what if you stop rendering too soon? Well, the image will be still be "realistic" but it will be noisy. If you stop it real soon (at pass 1) in an interior it might be incredibly noisy. Leave it rendering for 50 more passes and you'll probably end up with a noise free image. No matter how much noise you have though, the realism will be there.

Probably the easiest parameter to control when it comes to stopping the rendering process is the noise limit. Typically you'll probably end up with a value of around 2-4% for most of your renders. In a studio environment it might be lower but in an interior it might be higher. Personally, because I always do test renders before I send something out, I just have it set to 3% and then if I think the image is still noisy I just render at 2% for the final image. From my experience in most projects you won't go below 1,5% or higher than 4%.

If you want to you can also set it to stop rendering after it does an X amount of passes. Typically, after using Corona for a while you'll probably have some sort of an idea of how many passes you need for a given scene but ultimately, you'll still probably do test renders in smaller resolution just in case. Alternatively, you can also just use a time limit.

Hope thats at least somewhat helpful :)

7
Hardware / Re: monitor recommendations
« on: 2021-05-13, 12:10:51 »
I'm a big fan of Rtings.com reviews. You can arrange their reviews by screen size and other "needs" :)

8
Hardware / Re: Nvidia Cuda Cores
« on: 2021-05-11, 10:35:45 »
Hi there!

Except for denoising purposes (Nvidia AI denoiser only) your GPU won't be utilized during rendering with Corona. 3ds Max / C4D will use it to display the viewport but it will by no means help you render faster - Corona is a CPU rendering engine and you can't "repurpose" GPU cores to be used as CPU ones because they work in a completely different way.

9
Off-Topic / Re: Most useless Cinema 4D version ? visualize
« on: 2021-05-10, 21:29:33 »
I had to double check if they still offer the "cut down" versions - they don't. It was talked about for a while but I think they did it a couple of versions ago when they introduced subs, seemingly it was a bit pointless to have a neutered C4D unless you REALLY KNEW you weren't going to a certain feature set.

Anyhoo, problem of the past is it not? :)

10
Hardware / Re: 3970x experiences. Heat, speed, ram etc..?
« on: 2021-04-30, 15:01:14 »
@marius iordache
Here is how I got the temps in a range I personally am much more comfortable with :) Hope it helps.

At 3,7ghz my average rays drop from 12,800 to 11,600.
Thats around 10% difference. For much lower temperature and power consumption seems very reasonable. But somehow I cannot stand this 10% slower speed. Not effectively but OCD related.

OK so I've found a simple setting to cure most of the temperature "problems". Not really problems but you know what I mean :)

So I have PBO set to AUTO which should mean its OFF from what I understand but that clearly isn't the case. If I go under the PBO settings and set the temperature limit (its called something different, can't miss it though) to a custom of say 70 degrees... Well, the CPU won't go over 70c.

It is that simple.

So now I'm getting ~3.9ghz on all cores and I retain a solid 4.3ghz/4.4ghz single core turbo - at least thats what I can monitor from Windows. The rendering speed according to the benchmark is the same as it was with PBO off, maybe sometimes falling behind by 1 second (29s -> 30s).

The temps rarely if ever go above 70c. They go above because my fan curves need a second or two to kick in high speeds :) Rendering over night is constantly at 70c.

Hope that helps :)

11
[C4D] Bug Reporting / Re: Corona don't uses all the cores
« on: 2021-04-12, 14:49:05 »
I'm back with Corona 6 now. Just wanted to raport.

Definitely a big thanks for reporting the issue :) The same goes for your input @twoheads. Thank you both!

12
...

Fortunately I am familiar with the stuff you mentioned in your 2nd paragraph, yeah the fast preview is enabled for the IR, I cannot even look at the non-denoised IR. You know, honestly speaking I like the IR more than final render in Corona. IR is extremely smooth and artistic, I have attached an example of my work here which I published the IR as my final render! Final render is or looks very mechanical to me. It either removes all the details in the scene or keeps it in absolute chaos. After 3 years of working with Corona I am still unsatisfied about this... Even for the animation I am currently working on, I am sure I won't like the final render but I don't know what to do honestly speaking...

...

By the way, if you like the slightly more "artistic" look the IR denoiser gives you (which is the Nvidia one) then you can always use it for final renders too :) Alternatively, you can also render final and then in PS (or whatever else) denoise it there and tick the "remove JPG artifacts" option. That'll make it look a bit more "smooth" in some ways :)

13
Interesting! When this happens do you have denoising set to on?

14
You are most welcome! Would be curious to hear how it goes for you :)

15
At 3,7ghz my average rays drop from 12,800 to 11,600.
Thats around 10% difference. For much lower temperature and power consumption seems very reasonable. But somehow I cannot stand this 10% slower speed. Not effectively but OCD related.

OK so I've found a simple setting to cure most of the temperature "problems". Not really problems but you know what I mean :)

So I have PBO set to AUTO which should mean its OFF from what I understand but that clearly isn't the case. If I go under the PBO settings and set the temperature limit (its called something different, can't miss it though) to a custom of say 70 degrees... Well, the CPU won't go over 70c.

It is that simple.

So now I'm getting ~3.9ghz on all cores and I retain a solid 4.3ghz/4.4ghz single core turbo - at least thats what I can monitor from Windows. The rendering speed according to the benchmark is the same as it was with PBO off, maybe sometimes falling behind by 1 second (29s -> 30s).

The temps rarely if ever go above 70c. They go above because my fan curves need a second or two to kick in high speeds :) Rendering over night is constantly at 70c.

Hope that helps :)

Pages: [1] 2 3 ... 69