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

Pages: [1] 2 3 ... 8
1
I can't help wondering how the Intel denoiser is fast enough for it to work in IR in vray but not Corona... different approach to CPU usage perhaps?
Don't get me wrong - I'm fully against denoisers I can't switch on or off at will during IR (rather not have a denoiser during IR at all than not be able to turn it off without restarting IR, like with Optix. Incidentally, also something Vray can and Corona can't do).
Just curious...

2
[Max] Feature Requests / Re: The most wanted feature?
« on: 2023-08-31, 23:32:54 »
I'm frankly baffled by the VFB improvements being among the least popular choices.
The VFB has been clunky and bugged since about forever, a rewrite in QT for it is supposedly in the works but what is the point of a yet another tiles map (and there are at least 2 I can think of off the top of my head - the regular tiles and the Bercon Tiles) when you're still going to have to fight the buggy and slow VFB to actually see it?

Cryptomatte? What the hell for? Corona is an arch/product viz renderer first and foremost and all the other uses are secondary (and that means all the VFX stuff you'd actually need something like comprehensive mattes for).

You are supposed to get a final image straight out of the VFB, saving you tons of time of compositing and screwing around in post. You want to do post compositing? Use Vray as THAT is its primary function and it's specially designed for VFX work with other uses being more of a bonus than a purpose.

GPU/CPU Hybrid? I understand that most who use Corona think their PCs are like toasters and have no clue on how neither software nor hardware either works or is made, replacing the whole thing if it breaks and calling on some bored IT technician to fix stuff when replacement is not an option, but it has been said many times over and I'll say it again:

To make Corona compatible with GPUs it would require literally making Corona over entirely, from scratch, to run on GPUs. This means years of work, and a whole legion of bugs for another year or so after before it actually becomes properly useful.

Again - you want hybrid rendering? Say hello to... you guessed it... Vray. Oh, and that took something like 4 - 5 years to get GPU rendering ALMOST on par with CPU rendering.


Sorry for the rant but it's disheartening to see so many not getting these things...




3
I'm using this and it serves me well.
https://www.scriptspot.com/3ds-max/plugins/corona-physical-to-legacy-free

And yes, it converts "regular" physical materials too.

4
Can confirm CPU utilization below 100% with caustics on. 3970X here. CPU usage when rendering caustics hovers around 70% (average). Same scene with all caustics off - stays at 100% usage. Difference in Rays/s is around 10 million rays between caustics on and caustics off (caustics on: 6 mil. rays/s, caustics off: 16 mil. rays/s). Simple testing scene with 3 boxes and 2 planes (a mockup of a pool). Max 2024, C10.
In C9 the CPU usage was more consistent and closer to 100% regardless of caustics and the difference in speed was almost exactly double between "caustics off" and "caustics on", in rays/s (which is expected).

5
[Max] General Discussion / Re: Max extremely slow to close
« on: 2023-06-02, 23:02:54 »
In my case, this kind of thing stopped completely in Max 2024 so it leads me to believe it's a Max thing. Max was also leaving memory dump files in the CrashDumps folder (C:\Users\[USERNAME]\AppData\Local\CrashDumps) which I had to clean out often as each dump was 600+ Mb so the folder tended to grow to 5+ GB within 2 - 3 days.

6
Hi Devs - not sure if this is an old issue, but the corona round corner map - it sometimes creates this rippled effect?  Like its not perfectlyt smooth on the edges, its like it has some form of noise on it which gives it irregular bumps on it

An example would probably be very helpful...

7
@shortcirkuit

There's the official Backburner guides, to be downloaded as PDFs from here:

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Backburner-User-Guide-and-Installation-Guide-documents.html

It seems there's no actual online versions as this is the first thing when searching for them that comes out...

8
Perhaps not quite what you'd like exactly, but you can do that with Backburner.

Run Backburner on the node and then either send the scene to rendering from your workstation to be rendered via Backburner on the node or open the scene on the node and send it to rendering directly from the node.

In server mode (which is how Backburner is running Max on the node to render stuff), Max uses only a "render" license without using the "interface" license leaving it free to be used on the workstation while the node is rendering.

Another benefit of Backburner in this arrangement is that you can actually queue up several scenes to be rendered one after another and just leave the node churning out renders while you work on other stuff.

9
As Rowan said - upgrade to 2023.3.

It could be some mix between 2023.2.2 and the new daily. 2023.2.2 WAS actually buggy (but in a pretty stealthy way. In my case, for example, it was screwing up Max files saved in previous Max versions, of all things) and 2023.3 works like a charm (and actually slightly even faster) so updating Max could fix it.
It's always a good idea to keep Max updated to the latest possible version (but can wait and see for a week or two after its release if any reports of buggyness appear) and to check out the changelog for each new Max update or version as they list what was fixed and you may find something you didn't even know was a bug but was bothering you has been fixed.

10
Have you checked with something like PruneScene to make sure there are no retrackers running amok as well as no viruses? The retracker bug and the viruses usually reside in older scene files and once they get into your system (or current Max session), that scene will end up, eventually, screwed up (i.e. slowing down, bugging out, etc.)

11
Does it happen with both regular bitmaps or with CoronaBitmap as well? Asking because I've not had it happen with the CoronaBitmap, only with the regular Bitmap from Max.

12
Gallery / Re: Soaring Gardens
« on: 2023-03-03, 19:11:17 »
What intrigues me the most is how does something with multiple thousands of tons of weight in overhangs stay up without support? Is it dependent on some as yet undiscovered construction materials with extra strength or could something like this actually be built with contemporary technology?

13
[Max] General Discussion / Re: Max extremely slow to close
« on: 2023-02-21, 17:02:45 »
I have this issue  and have had it for years. It seems to be dependent, at least for me, on the time Max has been open before closing - after a few hours of Max being open (I haven't measured it but it's at least 1+ hours), closing it will take a long time. I suspect it's a Max issue and nothing to do with Corona. Max is Max...

14
Can confirm. Latest daily was crashy (mostly when updating IR). Previous daily is noticeably more stable.

15
Just to add a further point, i dont think ive ever had it happen with a render thats actually running. Only ever in IR.

It's probably because the glitch is somehow connected to whatever procedure is checking and waiting for changes in the scene itself. Even though the Max interface is not (by default) frozen during a production render, it doesn't need to check the scene for changes and so the glitch is not happening.
In any case, this seems the most likely explanation.

Pages: [1] 2 3 ... 8