1
[Max] Resolved Bugs / Re: Cosmos UI cannot init because of the following error
« on: 2022-05-06, 09:20:31 »
Aparrently the solution is to reset EDGE browser from settings. works like a charm
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.
@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 :)
@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 :)
Great work! I like the sense of light and the beautiful DOF!
Just one small small suggestion in the image balcony 2: I would not put the glare (with the star) in post. In the photography world usually, this star shapes comes when you use small aperture on the lens, but in this image, because of the small DOF, you used an open one. Only this small suggestion! :)
looks perfect , well done , may i ask about how did you do the carpet?