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

Pages: [1] 2 3 4
1
I wonder if there is gonna be the end one day. End of new features. How far can we go. Will there be anything that can make revolution in photorealism since some authors already crossed the uncanny valley of photorealism with existing software. Is all thats left some Qol improvements and speed improvements.

Sorry for being offtopic but this got me thinking.

2
[Max] I need help! / Re: Render time is too high
« on: 2021-06-09, 12:52:21 »
Id hather not advertise any specific GPU renderers on this forum but you can just google it. RTX 2070 is as strong at 5 of those CPUs you got combined.

3
[Max] I need help! / Re: Render time is too high
« on: 2021-06-09, 11:31:55 »
You are having rather slow CPU. Take a look at benchmarks. But still it should be faster. You got quite good GPU though, maybe consider trying GPU render alternative. Your graphic card would eat that render in no time.

4
[Max] General Discussion / Re: Corona 1.3 Benchmark
« on: 2021-06-01, 11:34:54 »
Nice benchmark, but it's too old.
Dev team, could you please make a new one with interior scene + caustics, it would be great to test the brand new features and compare the results.
If it will be issued after the release of Corona 7 (with all its feature), it would be awesome.
Thanks.

I still has same correlation. If something is faster here by 30% it will be faster similar amount in any scene and any setttings.

5
Hey Guys,

When we can expect release candidate?

No pressure, just asking.

We can't even hazard a guess yet, since a major feature (tone mapping) is not even in a daily yet :) So that has to be in a daily, then it depends on bug reports or user feedback, then we will have a better idea of how much is still to be done before things could move to RC stage - but until then, who knows what bugs and user feedback there could be... maybe none all is perfect, maybe lots...

So, very much no way to put a date on an RC yet.

Tom, is tone mapping feature being actively worked on or is it still in a waiting phase. I would love to see some news about that

6
Thank you so much. I thought that there was no support from quixel to 3ds max 2022. You helped me so much. Do you know by any chance how to make it so that when I import material from bridge, its bump value is not 99 but 1 ?

7
[Max] General Discussion / Re: Corona for 3Ds MAx 2022
« on: 2021-04-27, 12:39:32 »
What a tricky installation, I tried downloading and installing 5 times and saw the green installed text every time but nowhere to see it in Max 2022. "choose Custom and check the Max 2022 option" needs to be mentioned clearly somewhere. Just waste of time.

The definition of insanity is doing the same thing over and over again and expecting a different result.

8
Hardware / Re: Threadripper 3990x vs 3970x
« on: 2021-04-13, 10:52:21 »
I will say that this depends upon your needs and budget.
I for example bought 3960x and my interactive is almost realtime responsive while renders take up to 10 minutes to render. This is for me ideal since in this 10 minutes I tweak tonemapping and other stuff so I got basically no time loss.
If we consider that unfourtunately 3ds max is still mainly single core, the good tradeoff of single core / multi core is needed.

Now if you do animations or extremely complex scenes in very high resolution and/or are a big studio that has big budget I would say to go for the 3990x. Otherwise I feel 3970x is the sweetspot.



9
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 :)

That sound great Nejc. Will try it. Thanks a lot .

10
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.

11
If you use power profile with 99% min and max power, it will lock it down too much. Thats why I use AMD Ryzen™ Master Utility where i can specify precise core speed. For example I have 3960x that runs at 3800 with single boost to 4,4.

When I render I set it to 3900 all cores. And it has around 20celsius lower temp.
If I let it go with default (3800) it actually works on 4,05 all cores.

If I use 99% power profile it goes to 3,7 which is far too low imo.

12
What I do is to change power plans or profiles inside AMD CPUapp ( I forgot the name ). So if I purely do rendering I use profile with some % lower cores clock and if I use apps with single core I go to default. This is bcs only default state can use single core boost.

13
Not that I know.

14
Dunno what you consider fast but for me, using 2133 memory makes it around 15% slower than using 3200 memory. It has diminishing returns ofc so 3200 vs 3600 would be very small difference, if any.

15
Damn guys, didnt know that. Very very interesting. Now I think I was better not being aware of this detail loss :D

Pages: [1] 2 3 4