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

Pages: [1] 2 3 ... 45
[Max] Feature Requests / Re: The most wanted feature?
« on: Yesterday at 15:24:40 »
Cryptomatte support please. I find your lack of Cryptomatte support disturbing. The most other features on the list can be filled in by plugins but I need Cryptomatte, having full blown pipeline with Vray for years using Cryptomatte and need it. Even Blender has it. Shame on you.

Is this a joke??

How about V-Ray fur support in Corona then? Sounds reasonable?

(Report ID=CRMAX-943)

In that case, would you need a vray license to be able to use vrayfur? Or the demo would do?

whenever I change something in the scene, Interactive Render turns into blocky mess for second or two before image is cleared

You may want to play with Corona settings to see if you can improve your IR experience. Setting IR subsampling to 0 will get rid of blockiness and turning off fast preview denoise may help with messiness. You'll find the former in render setup>system>system settings and the latter in render setup>performance. You can also try to increase image upscale factor to 2 in system settings, this would greatly increase IR performance at the significant loss of image quality.

I'd also recommend checking "dissolve with previous image"

[Max] Bug Reporting / Issue with unchecking "cast shadows"
« on: 2021-09-10, 22:12:32 »

I'm using Max 2020 and Corona 7.1

It seems that there's an issue going on when an object has "cast shadows" unchecked.
I attached the scene and there's a video below.


I have a case of conversion here that doesn't make sense.

It converts what it looks like a matte object into a metal.

I think the reason the converter does that is bc the IOR is very high. Still, the reflection is at 0, so it shouldn't convert it into a metal IMO.

1- open the scene, and render IR
2- Convert, and render again.


EDIT: I'm using Corona 7 hotfix 1, Max 2020

Gallery / Re: CYAN EYED - Animated Short Film
« on: 2021-09-10, 20:34:51 »
Wow. What a an accomplishment! Congratulation!

[Max] Feature Requests / Re: The most wanted feature?
« on: 2021-09-02, 15:23:20 »
@lupaz, i'm pretty sure it shouldn't look like that. Perhaps a bug? The support might be interested in the scene.

Sending the file attached.

[Max] Feature Requests / Re: The most wanted feature?
« on: 2021-09-01, 22:11:57 »
@lupaz, i'm pretty sure it shouldn't look like that. Perhaps a bug? The support might be interested in the scene.

Sure. I'll upload the scene tomorrow morning (NY)

[Max] Feature Requests / Re: The most wanted feature?
« on: 2021-09-01, 17:06:02 »
Which is pretty much what Corona does - there's a render element for it too, the SamplingFocus, where white shows where Corona is focusing most of its processing (areas with noise) and black where it doesn't need to spend so much time calculating.

Denoising came to be simply to reduce how many passes you have to do in order to get a clean image :)

The attached is a simple scene.
It's very hard to make any sense from the SamplingFocus element.

With Fstorm (as far as I remember), in red you can see the areas that didn't reach the threshold yet, in green the areas that did, and in black the areas that have no noise (I think).

From the sampling focus element in this example, to me it's like Corona is trying to solve some random lines.

[Max] Feature Requests / Re: The most wanted feature?
« on: 2021-09-01, 15:05:04 »
while Corona do not cleanup the images and staying on the same noise level for some areas in the internal (for example corners inside room).

Do you have a scene where the noise stays on the same level for a long time? This sounds like a bug.

As far as I know, Corona was never able to clean the image entirely. I thought that was the main reason why denoising came to be.

Maybe what the OP is referring to is that Fstorm starts cleaning the whole image, then when certain areas reach a threshold, it continues to smaller areas where there's still noise, and so forth until it tries to resolve the last parts of noise.
In Fstorm it's easy to see because it has a render element that shows this clearly. You can actually stop to change the threshold and then continue processing the image until you're satisfied with the noise level.

Just my 2 cents.

Sometimes it does, sometimes it doesn't.

It doesn't ask confirmation if no changes were made. That is expected behaviour. If you ever encountered situation where you're sure that some canges have been made, yet CIE exits without confirmation, then you should report it as a bug.

Right. I meant after making changes. I'll see if it's replicable and report it.

Sometimes it does, sometimes it doesn't.
Edit: also in that message there could be a Save button. It's pretty much what every application has.

[Max] I need help! / Re: Proxy has corrupted normals
« on: 2021-08-21, 02:36:07 »
My understanding is they will be automatically fixed at render time in the data set up for rendering in memory, but not fixed in the scene - this will result in this same warning every time you render, so following the manual fix is how to fix it permanently in the scene and avoid seeing the warning again.

Got it. I'll just ignore it in my current projects then. Thanks Tom!


It'd be nice to have the CIE to ask if you want to save the changes.


Pages: [1] 2 3 ... 45