Recent Posts

Pages: [1] 2 3 ... 10
1
Treid the 15 may build.
I could open my testfile with the 15 may build, the one I send to Benjamin, in about 7 seconds on my Macbook air m1. On my Mac Studio it opened instantly with CR 11. Will try at the office how the latest build does with my Mac Studio.

I did notice that the testfile I send to Benjamin (saved project with assets) had lots of mappings missing in the exported tex folder. See attachment. On my Macbook these materials render black. I only noticed because I open this test file on my home MacBook Air. At the office on my Mac Studio I did not notice jpeg maps where missing in the export file.

Somehow Coronarender materials with a certain bitmap path don't export at saving a project with assets. That might explain as well the long opening times.
2
Hi there,


Thank you so much @John_Do for your suggestions. These are indeed some of the most common ways to adjust/change texture's scale.


@Konichowaa, it would be great if you could provide us with more details/info regarding what you're trying to achieve.
You can share with us some screenshots, screen recordings or even your scene project. (or at least a stripped-down version if you're not able to share your entire project).
Looking forward to hearing from you.
Have an amazing day/evening.
3
Hello eyelike,


Thank you for bringing this to our attention.
Is this happening with a specific Cosmos asset?
Are you storing your downloaded Cosmos assets on a network drive or locally?
Have you tried using different Cosmos Asstes?
I've tried reproducing this; however, I haven't had enough luck.
It works as expected. (see attached images)
My sample scene consists of a Cosmos asset (a green car), a simple plane (floor), a Corona Sky, and a Corona Sun.
I tried selecting the plane object and the car (Cosmos asset), but every time I tried, the result was always correct/expected.
Looking forward to hearing from you soon.

4
I would consider 64gb of ram minimum these days for 3D rendering.
5
[Max] I need help! / Re: How to use full Computer POWER while rendering
« Last post by romullus on Yesterday at 23:21:09 »
Don't forget that 3ds Max and Corona are not the only programs that allocates system RAM. Your Windows, browser, antivirus and many other programs needs to fitted in the memory. You open one too many tab in the browser and it might be enough for Windows to start using swap. As Tom said, you need either upgrade your PC, or start seriously optimizing your scenes. With stats like these, you're walking on knife edge.
6
Hello @Philw,


Thanks for your feedback.
I've been trying to reproduce this; however, I haven't had any luck so far. (see attached GIF)
I tried copying a Layered material (just the layered material) into a new empty file, and after pasting the Layered material, it also copied all used materials in the Layered one.
Also, I tried copying just the object using the Layered material, and it works as expected; I mean, it copies the object, the Layered material, and all materials used in the Layered one.
Looking forward to hearing from all of you.
Have an amazing day/evening.
7
[Max] I need help! / Re: CPU usage drops to ~10%
« Last post by Mirage Studio on Yesterday at 22:31:17 »
Hi Avi,

I get an error: Invalid string option: string option: int progressive.boxScramblingPassLimit = 10000

I just bought another 128gb of ram so see if that helps (I was past due for it anyways).

I was thinking more about the timing of this and I can't remember if this started happening after I upgraded from Corona 10 to 11. I'm going to downgrade back to 10 and see if that solves the issue too. I upgraded from 10 to 11 while I was still using 3dsmax 2021 and it happened both on 2021 and 2024.
8
[Max] I need help! / Re: How to use full Computer POWER while rendering
« Last post by pebble on Yesterday at 22:04:09 »
The thing is that I re-opened the same scene  I did last week, and it still show the same message as the last time, and the render its done again very fast.
9
[Max] I need help! / Re: How to use full Computer POWER while rendering
« Last post by TomG on Yesterday at 21:19:08 »
You got lucky that the scene last week wasn't also incredibly slow. The low RAM warning is one that has to be taken seriously - at worst, speed can drop to about 10% of what it should be (as the CPU has to wait for data from the hard drive, which is much slower than waiting for data from the RAM), or in other cases can just outright crash.

32GB of RAM is considered a minimum these days, with 64GB being more of a sweet spot (though there are users who have even more than that, for sure), so a 16GB machine is going to struggle when the scene hits any sort of complexity. There should be a link in that message that you can click on which will give advice on optimizing the scene, though the preferred solution if budget allows is simply to add more RAM :)
10
Brilliant!  That works perfect - thank you!
Pages: [1] 2 3 ... 10